HP EVA P6000 HP Enterprise Virtual Array Updating Product Software Guide (xcs1 - Page 28

Mac OS X, Microsoft Windows, OpenVMS, Checking timeout values

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

Page 28 highlights

Table 7 Emulex driver parameters Parameter HPELXLPFC nodev_timeout qdepth discovery_threads Single path y 60 30 1 With Multipulse - 10 16 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 is set to 3c (60 seconds), the Microsoft Windows default. If the registry entry does not exist, you must create it. See your Windows documentation for instructions. 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. 28 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
  • 74
  • 75
  • 76
Table 7 Emulex driver parameters
With Multipulse
Single path
Parameter
—
y
HPELXLPFC
10
60
nodev_timeout
16
30
qdepth
32
1
discovery_threads
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
is set to 3c (60 seconds), the Microsoft Windows default.
If the registry entry does not exist, you must create it. See your Windows documentation for
instructions.
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.
28
Preparing for the upgrade