Avago Technologies Syncro CS 9271-8i - Manual (Page 79)

LSI Corporation
- 79 -
Syncro CS 9271-8i Solution User Guide
October 2013 Chapter 5: Troubleshooting
Event Messages and Error Messages
The following table shows HA-DAS boot events and messages.
0x01dc Warning Cache mirroring is offline Cache mirroring is not active between
the controller and the peer controller.
VDs with write-back cache enabled
are transitioned from write-back
mode to write-through mode. This condition can occur if cache coherency is
lost, such as a communication failure with the
peer controller or VD in write-back mode
when pending writes go offline, or with
pinned cache scenarios. To resolve, reestablish
proper cabling and hardware connections to
the peer controller or disposition a controller's
pinned cache.
0x01dd Critical Cached data from peer
controller is unavailable. VD:
access policy
is set to Blocked. The peer controller has cached data
for the affected VDs, but is not present
in the HA domain. The VD access
policy is set to Blocked until the peer
controller can flush the cache data to
the VD. This condition can occur when cache
coherency is lost due to failure of
communication with the peer controller. To
resolve, bring the peer controller online and
reestablish communication paths to the peer
controller. If the peer controller is
unrecoverable, restore data from a backup or
manually set the access policy (data is
unrecoverable).
0x01e9 Critical Direct communication with
peer controller(s) was not
established. Please check
proper cable connections. The peer controller might be passively
detected, but direct controller-to-
controller communication could not
be established due to a split brain
condition.
A split brain condition occurs when
the two server nodes are not aware of
each other’s existence but can access
the same end device/drive.
Attempts to create a VD that is not supported
by the peer controller result in a creation
failure. To resolve, create a VD that aligns with
the peer controller VD support level.
Attempts to introduce an unsupported VD
that is managed by the peer controller result
in rejection of the VD by the controller. To
resolve, convert the unsupported VD to one
that is supported by both controllers, or
migrate the data to a VD that is supported by
both controllers.
Table 5 HA-DAS Boot Events & Messages
Boot Event Text Generic Conditions when each event occurs Actions to resolve
Peer controller firmware is not HA compatible.
Please resolve firmware version/settings
incompatibility or press 'C' to continue in Safe
Mode (all drives will be hidden from this
controller). An incompatible peer controller parameter is
detected. The peer controller is rejected from
entering the HA domain. The peer controller might have settings that do
not match the controller. These settings might
be corrected by a firmware update. To resolve,
update the firmware for the peer controller
and/or controller to ensure that they are at the
same version.
Peer controller hardware is not HA compatible.
Please replace peer controller with compatible
unit or press 'C' to continue in Safe Mode (all
drives will be hidden from this controller). A peer controller is not compatible with the
controller in the HA domain. Entering Safe
Mode protects the VDs by blocking access to
the controller to allow the incompatibility to be
corrected. The peer controller hardware does not exactly
match the controller. To resolve, replace the
peer controller with a unit that matches the
controller hardware
Direct communication with peer controller(s)
was not established. Please check proper cable
connections. The peer controller can be passively detected,
but direct controller-to-controller
communication could not be established due
to split-brain conditions caused by a missing
cross link. A cross link to establish direct peer controller
communication is not present. To resolve,
check all SAS links in the topology for proper
routing and connectivity.
Table 4 HA-DAS MSM Events and Messages (Continued)
Number
Severity
Level
Event Text Cause Resolution