HP 6400/8400 HP StorageWorks Enterprise Virtual Array Updating Product Softwar - Page 34

Checking timeout values, NetWare, OpenVMS, Solaris, Checking or changing timeouts

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

Page 34 highlights

• If you are in a VMware environment where you are running as a Windows guest, see "VMware" on page 35. 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 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 OpenVMS The limit for LUN timeout is 120 seconds. NOTE: OpenVMS handles the controller reboot seen at the conclusion of the controller software upgrade process. Disks on the controller display a Mount Verify status during the controller reboot but regain Mounted status and resume I/O operations upon the completion of the controller reboot. No changes need to be made to any OpenVMS default settings when performing an online controller software upgrade. Online controller software upgrades are supported in OpenVMS cluster environments where the EVA 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 /etc/system file: 34 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
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
•
If you are in a VMware environment where you are running as a Windows guest, see
“
VM-
ware
”
on page 35.
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
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
OpenVMS
The limit for LUN timeout is 120 seconds.
NOTE:
OpenVMS handles the controller reboot seen at the conclusion of the controller software upgrade
process. Disks on the controller display a Mount Verify status during the controller reboot but regain
Mounted status and resume I/O operations upon the completion of the controller reboot. No changes
need to be made to any OpenVMS default settings when performing an online controller software
upgrade.
Online controller software upgrades are supported in OpenVMS cluster environments where the EVA
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
/etc/system
file:
Preparing for the upgrade
34