HP StorageWorks 2/128 HP StorageWorks Core Switch 2/64 and SAN Director 2/128 - Page 81

Boot, Diagnostics

Page 81 highlights

Boot Boot completes in a minimum of three minutes if POST is run. In addition to POST, boot includes the following steps after POST is complete: • Universal port configuration is performed. • Links are initialized. • Fabric is analyzed. If any ports are connected to other switches, the switch participates in a fabric configuration. • The switch obtains a Domain ID and assigns port addresses. • Unicast routing tables are constructed. • Normal port operation is enabled. Diagnostics Diagnostic tests are automatically run during POST to check the status of the switch. Any error messages generated during POST are sent to the error logs and to the serial console, if connected. Diagnostic tests can also be run manually to test and troubleshoot the hardware and the firmware, including internal connections and circuitry, transceivers, and port cables. However, diagnostic tests are generally intended for use by support personnel. NOTE: Diagnostic error messages do not necessarily indicate that the switch requires maintenance. Each diagnostic test can be implemented by entering the related command through a telnet or serial session. For a list of diagnostic tests and commands, refer to the HP StorageWorks procedures user guide for the Fabric OS version running on your switch. All diagnostic tests are run at link speeds of both 1 and 2 Gb/s. They might temporarily lock the transmit and receive speeds to a specific speed. Some diagnostic tests require interconnecting the ports to each other or using loopback plugs. If ports are interconnected, the media (cables and transceivers) at each end of the connection must be of the same type. For example, short wavelength media must be connected to short wavelength media, and likewise with long wavelength media and copper media. For more information about diagnostic tests and how to run them, refer to the HP StorageWorks procedures user guide for the Fabric OS version running on your switch. Core Switch 2/64 and SAN Director 2/128 installation guide 81

  • 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
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166

81
Core Switch 2/64 and SAN Director 2/128 installation guide
Boot
Boot completes in a minimum of three minutes if POST is run. In addition to POST, boot
includes the following steps after POST is complete:
Universal port configuration is performed.
Links are initialized.
Fabric is analyzed. If any ports are connected to other switches, the switch participates in a
fabric configuration.
The switch obtains a Domain ID and assigns port addresses.
Unicast routing tables are constructed.
Normal port operation is enabled.
Diagnostics
Diagnostic tests are automatically run during POST to check the status of the switch. Any error
messages generated during POST are sent to the error logs and to the serial console, if
connected.
Diagnostic tests can also be run manually to test and troubleshoot the hardware and the
firmware, including internal connections and circuitry, transceivers, and port cables. However,
diagnostic tests are generally intended for use by support personnel.
NOTE:
Diagnostic error messages do not necessarily indicate that the switch requires
maintenance.
Each diagnostic test can be implemented by entering the related command through a telnet or
serial session. For a list of diagnostic tests and commands, refer to the
HP StorageWorks
procedures user guide
for the Fabric OS version running on your switch.
All diagnostic tests are run at link speeds of both 1 and 2 Gb/s. They might temporarily lock
the transmit and receive speeds to a specific speed. Some diagnostic tests require
interconnecting the ports to each other or using loopback plugs. If ports are interconnected,
the media (cables and transceivers) at each end of the connection must be of the same type.
For example, short wavelength media must be connected to short wavelength media, and
likewise with long wavelength media and copper media.
For more information about diagnostic tests and how to run them, refer to the
HP StorageWorks
procedures user guide
for the Fabric OS version running on your switch.