HP StorageWorks 2000sa HP StorageWorks P2000 G3 MSA System Event Description R - Page 30

Informational, Error, Critical

Get HP StorageWorks 2000sa - G2 Modular Smart Array PDF manuals and user guides View all HP StorageWorks 2000sa manuals
Add to My Manuals
Save this manual to your list of manuals

Page 30 highlights

309 Informational Normally when the Management Controller (MC) is started, the IP data is obtained from the midplane FRU ID SEEPROM where it is persisted. If the system is unable to write it to the SEEPROM the last time it changed, a flag is set in flash memory. This flag is checked during startup, and if set, this event is logged and the IP data that is in flash memory is used. The only time that this would not be the correct IP data would be if the controller module was swapped and then whatever data is on the controller's flash memory is used. Recommended actions • No action required. 310 Informational After a rescan, the controller completed back-end discovery and initialization of enclosure data. Recommended actions • No action required. 311 Informational An iSCSI ping operation completed. The event specifies the number of pings that passed and the number that failed. Recommended actions • If the ping operation failed, check connectivity between the storage system and the remote host. 312 Informational This event is used by email messages and SNMP traps when testing notification settings. This event is not recorded in the event log. Recommended actions • No action required. 313 Error The indicated controller module has failed. This event can be ignored for a single-controller configuration. Recommended actions • Replace the failed controller module. The module's Fault/Service Required LED will be illuminated (not blinking). 314 Error The indicated FRU has failed or is not operating correctly. This event follows some other FRU-specific event indicating a problem. This event was defined for HP Remote Insight Support tools. Recommended actions • To determine whether the FRU needs to be replaced, see the topic about verifying component failure in the component's replacement instructions document. 315 Critical The controller module is incompatible with the enclosure. The controller will automatically shut down. If two incompatible controllers are inserted at the same time, or booted at the same time, one controller will crash and the other will hang. This behavior is expected and prevents data loss. Recommended actions • Move the controller module to a compatible enclosure. 30

  • 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
30
309
Informational
Normally when the Management Controller (MC) is started, the IP data is obtained from the midplane FRU
ID SEEPROM where it is persisted. If the system is unable to write it to the SEEPROM the last time it
changed, a flag is set in flash memory. This flag is checked during startup, and if set, this event is logged
and the IP data that is in flash memory is used. The only time that this would not be the correct IP data
would be if the controller module was swapped and then whatever data is on the controller’s flash memory
is used.
Recommended actions
•
No action required.
310
Informational
After a rescan, the controller completed back-end discovery and initialization of enclosure data.
Recommended actions
•
No action required.
311
Informational
An iSCSI ping operation completed. The event specifies the number of pings that passed and the number
that failed.
Recommended actions
•
If the ping operation failed, check connectivity between the storage system and the remote host.
312
Informational
This event is used by email messages and SNMP traps when testing notification settings. This event is not
recorded in the event log.
Recommended actions
•
No action required.
313
Error
The indicated controller module has failed.
This event can be ignored for a single-controller configuration.
Recommended actions
•
Replace the failed controller module. The module’s Fault/Service Required LED will be illuminated (not
blinking).
314
Error
The indicated FRU has failed or is not operating correctly. This event follows some other FRU-specific event
indicating a problem. This event was defined for HP Remote Insight Support tools.
Recommended actions
•
To determine whether the FRU needs to be replaced, see the topic about verifying component failure in
the component’s replacement instructions document.
315
Critical
The controller module is incompatible with the enclosure. The controller will automatically shut down. If two
incompatible controllers are inserted at the same time, or booted at the same time, one controller will crash
and the other will hang. This behavior is expected and prevents data loss.
Recommended actions
•
Move the controller module to a compatible enclosure.