HP 6400/8400 HP StorageWorks Enterprise Virtual Array updating product softwar - Page 34

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

Page 34 highlights

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 firmware upgrades are supported with Linux boot devices. Mac OS X Online firmware upgrade is not supported for Mac OS X. All firmware upgrades 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. • Boot devices are supported with online controller firmware upgrades, but the page-file disk should not be on the boot device during an online upgrade. • 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. • You cannot boot from SAN in this environment. 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. NetWare NOTE: When NetWare is used with the EVA4400, it is not supported in an HP Continuous Access EVA environment. 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 34 Pre-upgrade tasks

  • 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
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86

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 firmware upgrades are supported with Linux boot devices.
Mac OS X
Online firmware upgrade is not supported for Mac OS X. All firmware upgrades 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.
Boot devices are supported with online controller firmware upgrades, but the page-file disk should
not be on the boot device during an online upgrade.
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.
You cannot boot from SAN in this environment.
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.
NetWare
NOTE:
When NetWare is used with the EVA4400, it is not supported in an HP Continuous Access EVA
environment.
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
Pre-upgrade tasks
34