NetWare
No changes are needed for NetWare operating system timeouts. The default values from HBA are:
• Login retry count: 8
• Port down retry count: 16
• Link down timeout: 8
OpenVMS
The limit for LUN timeout is 120 seconds.
NOTE:
OpenVMS handles the controller reboot seen at the conclusion of the firmware update process. Disks
on the controller display a Mount Verify status during the controller reboot but regain Mounted status
and resume I/O operations upon the completion of the controller reboot. No changes need to be
made to any OpenVMS default settings when performing an online controller software upgrade.
Online controller software upgrades are supported in OpenVMS cluster environments where the EVA
is the cluster boot device.
Solaris
Solaris supports online controller upgrades with the following driver timeouts:
• Sun Drivers (qlc or emlxs): 60 seconds
• QLogic (qla2300): 60 seconds
• Emulex (lpfc): 60 seconds
Checking or changing timeouts
For Sun 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;
Tru64
Tru64 has a 60 second timer for media command 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 I/O is returned to the file
system. No changes should be made to any Tru64 settings when performing an online controller
software upgrade.
Pre-upgrade tasks32
To Next Page
Loading...
Need help?
General