HP Surestore S10 Service and User Manual (Short- and Long-Wave) - Page 70

Troubleshooting Procedures

Get HP Surestore S10 - Hub PDF manuals and user guides View all HP Surestore S10 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 70 highlights

Troubleshooting Procedures If there is a problem accessing a device connected to the hub, the source of the problem can be with the device, the hub, the host, or any of the connections between the host and the device. Follow the steps below to investigate the problem from the most likely to the least likely cause. In addition, check the troubleshooting tables in this chapter for solutions to specific symptoms. 1. For HP-UX servers, run ioscan from the server's console. - If the hardware paths for all FC-AL devices connected to the hub are listed in ioscan, the connection from the host to the device is good, and problems accessing a device probably originate in the software, driver, or device. - If the hardware path for a FC-AL device connected to the hub is not listed in ioscan, the source of the problem is likely to be bad connections, duplicate hardware addresses, a faulty device, or a faulty hub (see steps 2 through 5). The hub does not appear in ioscan output because it does not have a hardware address. For HP NetServers, open the SCSI Adapters window, then click the Devices tab. If the device is not displayed, the problem is likely to be bad connections, duplicate hardware addresses, a faulty device, or a faulty hub (see steps 2 through 5). The hub does not appear in this window because it does not have a hardware address. 2. Inspect the cabling between the hub and FC-AL devices. Check for loose, dirty, broken, or bent cabling and connectors. Cables should attach with an audible click. 3. Check the loop ID (hardware address) of each device on the loop and eliminate any duplicate addresses. Reset the hub after changing any loop ID, then run ioscan to make sure there are no duplicate addresses. Duplicate addresses can be indicated by "NO H/W"in the S/W State field. 4. Inspect the FC-AL device for a fault. Follow the instructions that came with the device. Make sure you check the fiber optic transmit or receiving port on the device. 5. Inspect the hub LED indicators for apparent problems (see Table 2 on page 70). If the Fault LED is lit, either the fans or the hub is faulty. If a cable is connected to a port 68 Troubleshooting Procedures

  • 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
68
Troubleshooting Procedures
Troubleshooting Procedures
If there is a problem accessing a device connected to the hub, the source of the problem
can be with the device, the hub, the host, or any of the connections between the host and
the device. Follow the steps below to investigate the problem from the most likely to the
least likely cause. In addition, check the troubleshooting tables in this chapter for solutions
to specific symptoms.
1.
For HP-UX servers
, run ioscan from the server’s console.
–
If the hardware paths for all FC-AL devices connected to the hub are listed in ioscan,
the connection from the host to the device is good, and problems accessing a device
probably originate in the software, driver, or device.
–
If the hardware path for a FC-AL device connected to the hub is not listed in ioscan,
the source of the problem is likely to be bad connections, duplicate hardware
addresses, a faulty device, or a faulty hub (see steps 2 through 5).
The hub does not
appear in ioscan output because it does not have a hardware address.
For HP NetServers
, open the
SCSI Adapters
window, then click the
Devices
tab. If
the device is not displayed, the problem is likely to be bad connections, duplicate
hardware addresses, a faulty device, or a faulty hub (see steps 2 through 5).
The hub
does not appear in this window because it does not have a hardware address.
2.
Inspect the cabling between the hub and FC-AL devices
. Check for loose, dirty,
broken, or bent cabling and connectors. Cables should attach with an audible click.
3.
Check the loop ID (hardware address) of each device on the loop and eliminate
any duplicate addresses
. Reset the hub after changing any loop ID, then run ioscan to
make sure there are no duplicate addresses. Duplicate addresses can be indicated by
“NO H/W” in the S/W State field.
4.
Inspect the FC-AL device for a fault
. Follow the instructions that came with the
device. Make sure you check the fiber optic transmit or receiving port on the device.
5.
Inspect the hub LED indicators for apparent problems
(see Table 2 on page 70). If
the Fault LED is lit, either the fans or the hub is faulty. If a cable is connected to a port