HP AA988A HP StorageWorks 2012sa Modular Smart Array user guide (488320-002, J - Page 54

Review the Event Logs, Isolate the Fault, consideration. In addition

Get HP AA988A - Modular Smart Array Storage Controller SCSI PDF manuals and user guides
UPC - 829160184661
View all HP AA988A manuals
Add to My Manuals
Save this manual to your list of manuals

Page 54 highlights

When a fault occurs, the Fault ID status LED on an enclosure's right ear (see Figure 1-1) illuminates. Check the LEDs on the back of the enclosure to narrow the fault to a FRU, connection, or both. The LEDs also help you identify the location of a FRU reporting a fault. Use SMU to verify any faults found while viewing the LEDs. SMU is also a good tool to use in determining where the fault is occurring if the LEDs cannot be viewed due to the location of the system. SMU provides you with a visual representation of the system and where the fault is occurring. It can also provide more detailed information about FRUs, data, and faults. Review the Event Logs The event logs record all system events. It is very important to review the logs, not only to identify the fault, but also to search for events that might have caused the fault to occur. For example, a host could lose connectivity to a virtual disk if a user changes channel settings without taking the storage resources assigned to it into consideration. In addition, the type of fault can help you isolate the problem to hardware or software. Isolate the Fault Occasionally it might become necessary to isolate a fault. This is particularly true with data paths due to the number of components the data path consists of. 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. 54 HP StorageWorks 2012sa Modular Smart Array user guide • May 2008

  • 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
54
HP StorageWorks 2012sa Modular Smart Array user guide
•
May 2008
When a fault occurs, the Fault ID status LED on an enclosure’s right ear (see
Figure 1-1) illuminates. Check the LEDs on the back of the enclosure to narrow the
fault to a FRU, connection, or both. The LEDs also help you identify the location of
a FRU reporting a fault.
Use SMU to verify any faults found while viewing the LEDs. SMU is also a good
tool to use in determining where the fault is occurring if the LEDs cannot be viewed
due to the location of the system. SMU provides you with a visual representation of
the system and where the fault is occurring. It can also provide more detailed
information about FRUs, data, and faults.
Review the Event Logs
The event logs record all system events. It is very important to review the logs, not
only to identify the fault, but also to search for events that might have caused the
fault to occur. For example, a host could lose connectivity to a virtual disk if a user
changes channel settings without taking the storage resources assigned to it into
consideration. In addition, the type of fault can help you isolate the problem to
hardware or software.
Isolate the Fault
Occasionally it might become necessary to isolate a fault. This is particularly true
with data paths due to the number of components the data path consists of. 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.