User guide

LSI Corporation
- 49 -
Syncro CS 9286-8e Solution User Guide
March 2013
Chapter 5: Troubleshooting
Event Messages and Error Messages
0x01d8 Warning Controller property mismatch
detected with Peer controller
A mismatch exists between the
controller properties and the peer
controller properties.
Controller properties do not match between
the controller and peer controller. To resolve,
set the mismatched controller property to a
common value.
0x01d9 Warning FW version does not match
Peer controller
A mismatch exists between the
controller and peer controller
firmware versions.
This condition can occur when an HA
controller is introduced to the HA domain
during a controller firmware update. To
resolve, upgrade or downgrade the controller
or peer controller firmware to the same
version.
0x01da Warning Advanced Software Option(s)
<option names> mismatch
detected with Peer controller
A mismatch exists between the
controller and peer controller
advanced software options.
This case does not result in an incompatibility
that can affect HA functionality, but it can
impact the effectiveness of the advanced
software options. To resolve, enable an
identical level of advanced software options
on both controllers.
0x01db Information Cache mirroring is online Cache mirroring is established
between the controller and the peer
controller. VDs with write-back cache
enabled are transitioned from write-
through mode to write-back mode.
None - Informational
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:
<VD identifier> 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 4 HA-DAS MSM Events and Messages (Continued)
Number
Severity
Level
Event Text Cause Resolution