5 event messages and error messages – Avago Technologies Syncro CS 9271-8i User Manual
Page 77
LSI Corporation
- 77 -
Syncro CS 9271-8i Solution User Guide
October 2013
Chapter 5: Troubleshooting
Event Messages and Error Messages
5.5
Event Messages and Error Messages
Each message that appears in the MegaRAID Storage Manager event log has an error level that indicates the severity
of the event, as listed in the following table.
Error Level Meaning
The following table lists MegaRAID Storage Manager event messages that might appear in the MSM event log when
the Syncro CS system is running.
Table 3 Event Error Levels
Error Level
Meaning
Information
Informational message. No user action is necessary.
Warning
Some component might be close to a failure point.
Critical
A component has failed, but the system has not lost data.
Fatal
A component has failed, and data loss has occurred or will occur.
Table 4 HA-DAS MSM Events and Messages
Number
Severity
Level
Event Text
Cause
Resolution
0x01cc
Information
Peer controller entered HA
Domain
A compatible peer controller entered
the HA domain.
None - Informational
0x01cd
Information
Peer controller exited HA
Domain
A peer controller is not detected or
has left the HA domain.
Planned conditions such as a system restart
due to scheduled node maintenance are
normal. Unplanned conditions must be further
investigated to resolve.
0x01ce
Information
Peer controller now manages
PD:
A PD is now managed by the peer
controller.
None - Informational
0x01cf
Information
Controller ID:
A PD is now managed by the
controller.
None - Informational
0x01d0
Information
Peer controller now manages
VD:
A VD is now managed by the peer
controller.
None - Informational
0x01d1
Information
Controller ID:
A VD is now managed by the
controller.
None - Informational
0x01d2
Critical
Target ID conflict detected.
VD:
restricted from Peer controller
Multiple VD target IDs are in conflict
due to scenarios that might occur
when the HA domain has a missing
cross-link that establishes direct
controller-to-controller
communication (called split-brain
condition).
The Peer controller cannot access VDs with
conflicting IDs. To resolve, re-establish the
controller-to-controller communication path
to both controllers and perform a reset of one
system.
0x01d3
Information
Shared access set for VD:
A VD access policy is set to Shared.
None - Informational
0x01d4
Information
Exclusive access set for VD:
A VD access policy is set to Exclusive.
None - Informational