HP 4400 HP Enterprise Virtual Array Updating Product Software Guide (XCS 10000 - Page 29

Mac OS X, Microsoft Windows, Checking timeout values

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

Page 29 highlights

• failover = 0 • load_balancing = 1 • excludemodel = 0x0 • auto_restore = 0xA0 Emulex driver parameters (single path) • HPELXLPFC = y • nodev_timeout = 60 • qdepth = 30 • discovery_threads = 1 Emulex driver parameters (with Multipulse) • nodev_timeout = 10 • qdepth = 16 • discovery_threads = 32 To check or set Linux parameters, use the set_parm executable located in the /opt/hp/ directory. When executed, the options to change timeout values are displayed. NOTE: • You must increase timeout values for Emulex single path (without multipath support) and QLogic single path used in this environment. This is important for both online upgrades and general data integrity. • Online controller software upgrades are supported with Linux boot devices. Mac OS X Online controller software upgrades are not supported for arrays connected to Mac OS X hosts. Controller software upgrades must be done offline for Mac OS X hosts. Microsoft Windows Guidelines for Microsoft Windows follow: • Ensure that MPIO is installed and both paths are active and have access to the array. • Array boot devices are supported with online controller software upgrades, but the page-file disk must not be on the array being upgraded during an online upgrade. See your Windows documentation for instructions on changing the location of the page-file disk. • If the array being upgraded is used as a quorum disk in a Microsoft Windows cluster, an online controller software upgrade may cause the cluster to time out on the quorum disk and attempt to transition disks on that node to the surviving (secondary) node. The cluster may hang in this situation and require a cluster reboot to recover. A workaround is to transition all disks on the secondary node to the primary node, stop the cluster services, and shut down the secondary node before starting the controller software upgrade. Once the upgrade is complete, restart the cluster services and the secondary node to return it to the cluster. • Shut down the secondary node to prevent automatic failover. Checking timeout values Ensure that the key timeout setting in the registry at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Disk\TimeoutValue Managing host I/O timeouts for an online upgrade 29

  • 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
  • 74
  • 75
  • 76
  • 77
•
failover = 0
•
load_balancing = 1
•
excludemodel = 0x0
•
auto_restore = 0xA0
Emulex driver parameters (single path)
•
HPELXLPFC = y
•
nodev_timeout = 60
•
qdepth = 30
•
discovery_threads = 1
Emulex driver parameters (with Multipulse)
•
nodev_timeout = 10
•
qdepth = 16
•
discovery_threads = 32
To check or set Linux parameters, use the
set_parm
executable located in the
/opt/hp/
<driver>
directory. When executed, the options to change timeout values are displayed.
NOTE:
•
You must increase timeout values for Emulex single path (without multipath support) and QLogic
single path used in this environment. This is important for both online upgrades and general
data integrity.
•
Online controller software upgrades are supported with Linux boot devices.
Mac OS X
Online controller software upgrades are not supported for arrays connected to Mac OS X hosts.
Controller software upgrades must be done offline for Mac OS X hosts.
Microsoft Windows
Guidelines for Microsoft Windows follow:
•
Ensure that MPIO is installed and both paths are active and have access to the array.
•
Array boot devices are supported with online controller software upgrades, but the page-file
disk must not be on the array being upgraded during an online upgrade. See your Windows
documentation for instructions on changing the location of the page-file disk.
•
If the array being upgraded is used as a quorum disk in a Microsoft Windows cluster, an
online controller software upgrade may cause the cluster to time out on the quorum disk and
attempt to transition disks on that node to the surviving (secondary) node. The cluster may
hang in this situation and require a cluster reboot to recover. A workaround is to transition
all disks on the secondary node to the primary node, stop the cluster services, and shut down
the secondary node before starting the controller software upgrade. Once the upgrade is
complete, restart the cluster services and the secondary node to return it to the cluster.
•
Shut down the secondary node to prevent automatic failover.
Checking timeout values
Ensure that the key timeout setting in the registry at
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Disk\TimeoutValue
Managing host I/O timeouts for an online upgrade
29