HP StorageWorks Enterprise Virtual Array Online Firmware Upgrade Best Practices (5697-6388, January 2007)

Solaris
Solaris s uppor ts online controller upgrades with the following d river timeouts.
• Sun Drivers(qlc or emlxs): 60 seconds
• QLogic (qla230
0): 60 seconds
• Emulex (lpfc) : 60 seconds
Checking or changing timeouts
For S un drivers, add the following lines to /etc/system file:
set sd:sd_io_time = 60
set ssd:ssd_io_time = 60
For QLogic, edit the /kernel/drv/qla2300.conf file and change the hbax-link-down-timeout
value to 60 as follows:
hba0-link-down-timeout=60;
For Emulex, edit the /kernel/drv/lpfc.conf file and change the linkdown-tmo value to 60
as follows:
linkdown-tmo=60;
No cluster testing has been performed on Solaris.
Tru64
Tru64 has a 60 second timer for med ia com m a nd timeouts. In most cases, up to 5 retries can occur within
the kernel’s
I/O stack, which results in a 5–6 minute window before the I/O is returned to the file system.
No changes should be made to any Tru64 UNIX settings when performing an online firmware upgrade.
Online controller firmware upgrades are supported in Trucluster four-node environments where the
EVA is the cluster boot device.
OpenVMS
Online controller firmware upgrades on OpenVMS included testing in 16–node OpenVMS cluster
environments where the EVA was the cluster boot device.
In clustered environments where the system disks or quorum disks are on the storage system, the cluster
will stop processing requests while the storage system is resynchronizing. The cluster will become
available after the resynchronization. For the duration of an online code load, the cluster may log
messages related to the inability to access the quorum disk during the upgrade.
In environments where both shadow disks are on the same EVA or where they are on different arrays in a
2–node cluster, activity will stop during the o n line controller firmware upgrade.
HP StorageWorks Enterprise Virtual Array online firmware upgrade best practices
15