HP 6100 HP 4x00/6x00/8x00 Enterprise Virtual Array Updating Product Software G - Page 29

Mac OS X, Microsoft Windows, Checking timeout values, NetWare - driver mac

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

Page 29 highlights

Emulex Driver parameters (with Multipulse) • nodev_timeout=10 • qdepth=16 • discovery_threads=32 To check or set Linux parameters, use the set_parm executable found in the /opt/hp/ directory. When executed, the options to change timeout values are displayed. NOTE: • The timeout values must be increased for Emulex single path (without multipath support) and QLogic single path being used in the environment. This is not only important for online upgrades but for general data integrity. • Online controller software upgrades are supported with Linux boot devices. Mac OS X Online controller software upgrade is not supported for arrays connected to Mac OS X hosts. Any controller software upgrade must be done offline for Mac OS X servers. Microsoft Windows For Microsoft Windows, consider the following guidelines: • Ensure that MPIO is installed and both paths are active and have access to the array. • EVA boot devices are supported with online controller software upgrades, but the page-file disk must not be on the boot device during an online upgrade. By default, the page file disk is on the boot device; you must change the location of the page file disk if the EVA is being used as a boot device and you want to perform a controller software upgrade online. 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 node. The cluster may hang in this situation and require a cluster reboot to recover. A work-around 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 restart the secondary node to return it to the cluster. Checking timeout values The key timeout setting in the registry at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Disk\TimeoutValue should be set to 3c (60 seconds), which is the Microsoft Windows default. If the registry entry does not exist, you must create it. See your Windows documentation for instructions. 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 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
Emulex Driver parameters (with Multipulse)
•
nodev_timeout=10
•
qdepth=16
•
discovery_threads=32
To check or set Linux parameters, use the
set_parm
executable found in the
/opt/hp/<driver-specific>
directory. When executed, the options to change timeout values
are displayed.
NOTE:
•
The timeout values must be increased for Emulex single path (without multipath support) and
QLogic single path being used in the environment. This is not only important for online upgrades
but for general data integrity.
•
Online controller software upgrades are supported with Linux boot devices.
Mac OS X
Online controller software upgrade is not supported for arrays connected to Mac OS X hosts. Any
controller software upgrade must be done offline for Mac OS X servers.
Microsoft Windows
For Microsoft Windows, consider the following guidelines:
•
Ensure that MPIO is installed and both paths are active and have access to the array.
•
EVA boot devices are supported with online controller software upgrades, but the page-file
disk must not be on the boot device during an online upgrade. By default, the page file disk
is on the boot device; you must change the location of the page file disk if the EVA is being
used as a boot device and you want to perform a controller software upgrade online. 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 node. The cluster may hang in this
situation and require a cluster reboot to recover. A work-around 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 restart the secondary node to return it to the cluster.
Checking timeout values
The key timeout setting in the registry at
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Disk\TimeoutValue
should be set to 3c (60 seconds), which is the Microsoft Windows default.
If the registry entry does not exist, you must create it. See your Windows documentation for
instructions.
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
Managing host I/O timeouts for an online upgrade
29