HP 2000sa HP StorageWorks 2312sa and 2324sa Modular Smart Array user guide (48 - Page 52

Diagnostic steps, Correcting enclosure IDs

Page 52 highlights

Correcting enclosure IDs When installing a system with drive enclosures attached, the enclosure IDs might not agree with the physical cabling order. This is because the controller might have been previously attached to some of the same enclosures during factory testing and it attempts to preserve the previous enclosure IDs if possible. To correct this condition, make sure that both controllers are up, and perform a rescan using SMU or the CLI. This will reorder the enclosures, but can take up to two minutes for the enclosure IDs to be corrected. To perform a rescan using the CLI, type the following command: rescan To rescan using SMU: 1. Verify that both controllers are operating normally. 2. In the Configuration View panel, right-click the system and select Tools > Rescan Disk Channels. 3. Click Rescan. Diagnostic steps This section describes possible reasons and actions to take when an LED indicates a fault condition. See LED descriptions on page 37 for descriptions of all LED statuses. Is the front panel Fault LED amber? Answer No Yes Possible Reasons System functioning properly. A fault condition exists. Actions No action required. • Check the LEDs on the back of the controller to narrow the fault to a FRU, connection, or both. • Check the event log for specific information regarding the fault. Is the controller back panel OK LED off? Answer No Yes Possible Reasons System functioning properly. The controller module is not powered on. The controller module has failed. Actions No action required. • Check that the controller module is fully inserted and latched in place, and that the enclosure is powered on. • Check the event log for specific information regarding the failure. Is the controller back panel Fault/Service Required LED amber? Answer No Yes (blinking) Possible Reasons System functioning properly. One of the following errors occurred: • Hardware-controlled power-up error • Cache flush error • Cache self-refresh error Actions No action required. • Restart this controller from the other controller using SMU or the CLI. • Remove the controller and reinsert it. • Contact an authorized service provider for assistance. • Replace the controller. 52 Troubleshooting

  • 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

52
Troubleshooting
Correcting enclosure IDs
When installing a system with drive enclosures attached, the enclosure IDs might not agree with the
physical cabling order. This is because the controller might have been previously attached to some of the
same enclosures during factory testing and it attempts to preserve the previous enclosure IDs if possible. To
correct this condition, make sure that both controllers are up, and perform a rescan using SMU or the CLI.
This will reorder the enclosures, but can take up to two minutes for the enclosure IDs to be corrected.
To perform a rescan using the CLI, type the following command:
rescan
To rescan using SMU:
1.
Verify that both controllers are operating normally.
2.
In the Configuration View panel, right-click the system and select
Tools > Rescan Disk Channels.
3.
Click
Rescan
.
Diagnostic steps
This section describes possible reasons and actions to take when an LED indicates a fault condition. See
LED descriptions
on page 37 for descriptions of all LED statuses.
Is the front panel Fault LED amber?
Is the controller back panel OK LED off?
Is the controller back panel Fault/Service Required LED amber?
Answer
Possible Reasons
Actions
No
System functioning properly.
No action required.
Yes
A fault condition exists.
Check the LEDs on the back of the controller to narrow
the fault to a FRU, connection, or both.
Check the event log for specific information regarding
the fault.
Answer
Possible Reasons
Actions
No
System functioning properly.
No action required.
Yes
The controller module is not
powered on.
The controller module has
failed.
Check that the controller module is fully inserted and
latched in place, and that the enclosure is powered
on.
Check the event log for specific information regarding
the failure.
Answer
Possible Reasons
Actions
No
System functioning properly.
No action required.
Yes
(blinking)
One of the following errors
occurred:
Hardware-controlled
power-up error
Cache flush error
Cache self-refresh error
Restart this controller from the other controller using
SMU or the CLI.
Remove the controller and reinsert it.
Contact an authorized service provider for assistance.
Replace the controller.