Avago Technologies Syncro 9361-8i - Manual (Page 76)

Avago Technologies
- 76 -
Syncro CS 9361-8i and Syncro CS 9380-8e Solution User Guide 
October 2014
Chapter 4: Troubleshooting
Event Messages and Error Messages
4.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.
You cannot update a physical drive (PD)
or enclosure/ESM firmware with an
active HA cluster. 1. Shut down one node for the duration of the PD/ESM
firmware update process.
2. After the update has been completed, you can return
the previously shutdown node to an operational state.
Both SAS cables are pulled from one
node while IOs is running in Linux, which
causes all IOs to stop after the virtual
drives failed over to the peer node. 1. Restart IO from a client (the surviving peer node will
service IO).
When you create a cluster with a
configuration that consists of both
non-shared VDs and shared VDs, some of
the shared VDs are in failed state as
cluster disks in the failover cluster
manager. 1. You can make the failed cluster disks online, but if you
create a VD that is meant to be Quorum disk, and if it is
in failed state after cluster creation, another random VD
is assigned as Quorum instead.
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: identifier> now manages PD:
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
Table 2 Error Situations and Solutions (Continued)
Problem Possible Cause Solution