HP P2000 G3 MSA Array Systems - Manual (Page 48)

48 Troubleshooting
If the enclosure does not initialize
It may take up to two minutes for the enclosures to initialize. If the enclosure does not initialize:
• Perform a rescan.
• Power cycle the system.
• Make sure the power cord is properly connected, and check the power source that it is connected to.
• Check the event log for errors.
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 57 for descriptions of all LED statuses.
Is the front panel Fault 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.
Yes A fault occurred.
If installing an I/O module FRU,
the module has not gone online
and likely failed its self-test.
• Check the event log for specific information regarding
the fault.
• Isolate the fault.
• Contact an authorized service provider for assistance.
• Replace if necessary.
• If installing an I/O module FRU, try removing and
reinstalling the new I/O module, and check the event
log for errors.