●
Informational – A configuration or state change occurred, or a problem occurred that the system corrected. No immediate
action is required.
The event logs record all system events. Review the logs to identify fault and cause of the failure. For example, a host could lose
connectivity to a disk group if a user changes channel settings without taking the storage resources that are assigned to it into
consideration. In addition, the type of fault can help you isolate the problem to either hardware or software.
Isolate the fault
Occasionally, it might become necessary to isolate a fault. This is true with data paths, due to the number of components
comprising the data path. For example, if a host-side data error occurs, it could be caused by any of the components in the data
path: controller module, cable, or data host.
Host I/O
When troubleshooting disk drive and connectivity faults, stop I/O to the affected disk groups from all hosts as a data protection
precaution.
As an extra data protection precaution, it is helpful to conduct regularly scheduled backups of your data.
2U enclosure LEDs
Use the LEDs on the 2U enclosure to help troubleshoot initial start-up problems.
2U enclosure Ops panel
The front of the enclosure has an Ops panel that is located on the left ear flange of the 2U chassis. The Ops panel is a part of
the enclosure chassis, but is not replaceable on-site.
Figure 31. Ops panel LEDs—2U enclosure front panel
Table 9. Ops panel functions—2U enclosure front panel
Indicator
Description
Color
Status
System power
Green
On steady: at least one PCM is supplying power
Off: system not operating regardless of AC present
Status/Health
Blue
On steady: system is powered on and controller is ready
Blinking (2 Hz): Enclosure management is busy (for example, when
booting or performing a firmware update)
Amber
On steady: module fault present (may be associated with a Fault LED on
a controller module, IOM, or PCM)
Blinking: logical fault (2 s on, 1 s off)
28
Troubleshooting and problem solving
