HP EVA P6550 HP P6000 EVA Updating Product Software Guide (XCS 11200000) (5697 - Page 30

OpenVMS, Solaris, VMware, Checking or changing timeouts, VMware ESX Hypervisor timeouts

Get HP EVA P6550 PDF manuals and user guides View all HP EVA P6550 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 30 highlights

If this registry entry is created or changed, reboot the Windows system for the new timeout value to take effect. OpenVMS The maximum LUN timeout value is 120 seconds. NOTE: OpenVMS tolerates the controller reboot that occurs at the end of the controller software upgrade process. Disks on the controller display the Mount Verify status during the controller reboot but return to Mounted status and resume I/O operations when the controller reboot is complete. You do not need to change any OpenVMS default settings when performing an online controller software upgrade. Online controller software upgrades are supported in OpenVMS cluster environments where the array is the cluster boot device. Solaris Solaris supports online controller software 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 the /etc/system file: set sd:sd_io_time=60 set ssd:ssd_io_time=60 For the QLogic driver, edit the /kernel/drv/qla2300.conf file and change the hbax-link-down-timeout value to 60: hba0-link-down-timeout=60; For the Emulex driver, edit the /kernel/drv/lpfc.conf file and change the linkdown-tmo value to 60: linkdown-tmo=60; VMware VMware ESX (Hypervisor) timeouts VMware ESX (Hypervisor) does not time I/O for a guest operating system. Therefore, the SCSI timeouts on commands issued by each VMware guest (Linux, Windows, Solaris) are the timeouts set for these systems. Using HP P6000 Command View on a Windows 2008 guest system on ESX 4.1 or 5 When using HP P6000 Command View installed on a Windows guest system of ESX 4.1 or 5.0, use one of the following methods to upgrade the firmware to ensure a successful upgrade, or your array code load will fail in a VMware Guest OS configuration: • Array-based management module • HP P6000 Command View installed on a physical server (SBM) • Direct Path I/O mapping from ESX (requires supported hardware on the ESX server) 30 Preparing for the upgrade

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
If this registry entry is created or changed, reboot the Windows system for the new timeout value
to take effect.
OpenVMS
The maximum LUN timeout value is 120 seconds.
NOTE:
OpenVMS tolerates the controller reboot that occurs at the end of the controller software
upgrade process. Disks on the controller display the Mount Verify status during the controller reboot
but return to Mounted status and resume I/O operations when the controller reboot is complete.
You do not need to change any OpenVMS default settings when performing an online controller
software upgrade.
Online controller software upgrades are supported in OpenVMS cluster environments where the
array is the cluster boot device.
Solaris
Solaris supports online controller software 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 the
/etc/system
file:
set sd:sd_io_time=60
set ssd:ssd_io_time=60
For the QLogic driver, edit the
/kernel/drv/qla2300.conf
file and change the
hbax-link-down-timeout
value to 60:
hba0-link-down-timeout=60;
For the Emulex driver, edit the
/kernel/drv/lpfc.conf
file and change the
linkdown-tmo
value to 60:
linkdown-tmo=60;
VMware
VMware ESX (Hypervisor) timeouts
VMware ESX (Hypervisor) does not time I/O for a guest operating system. Therefore, the SCSI
timeouts on commands issued by each VMware guest (Linux, Windows, Solaris) are the timeouts
set for these systems.
Using HP P6000 Command View on a Windows 2008 guest system on ESX 4.1 or 5
When using HP P6000 Command View installed on a Windows guest system of ESX 4.1 or 5.0,
use one of the following methods to upgrade the firmware to ensure a successful upgrade, or your
array code load will fail in a VMware Guest OS configuration:
•
Array-based management module
•
HP P6000 Command View installed on a physical server (SBM)
•
Direct Path I/O mapping from ESX (requires supported hardware on the ESX server)
30
Preparing for the upgrade