Home
  •  

Monitor REC_LOST_REDUNDANCY_ESM (34)

IBMStorageSubsystem.FailureID_0034_Monitor (UnitMonitor)

Monitor Description for (34)

Knowledge Base article:

ESM Canister - Loss of Communication

What Caused the Problem?

Communication has been lost to one of the dual ESM canisters in a drive enclosure. The drive enclosure has only one I/O path available. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.

 Caution: Electrostatic discharge can damage sensitive components. Always use proper antistatic protection when handling components. Touching components without using a proper ground may damage the equipment.

Important Notes

Recovery Steps

1

Fix any other problems reported by the Recovery Guru before attempting to fix this problem.

2

To determine the non-working channel, start at the drive channel on the controller enclosure corresponding to the working channel (refer to the labels on the back of the controller enclosure if needed).

3

Trace the cable from the working channel to the optimal ESM canister in the affected drive enclosure.

Caution: Possible loss of data accessibility. Do not disconnect any cables on the working channel. Disconnecting any cables on the working channel will result in loss of access to your data.

4

Locate the other ESM canister in the affected drive enclosure (this is the canister on the non-working channel).

5

Reseating the ESM canister on the non-working channel may clear the failure being reported.

a

While the cables are still connected, remove the ESM canister from the drive enclosure.

Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO.

b

Wait 10 seconds, and then re-insert the canister firmly.

c

Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure the failure has been fixed.

d

If

Then

This failure is no longer reported in the Summary area

If a "Degraded Drive Channel" problem is also being reported in the Summary area, then go to step 10; otherwise, you are finished with this procedure.

This failure is still reported in the Summary area

Go to step 6.

6

If...

Then...

The cable is connected directly to the ESM canister on the non-working channel

Remove the cable.

Go to step 7.

The cable is connected to an interface transceiver such as a GBIC or SFP

Leave the cable connected and remove the interface transceiver from the ESM canister.

Go to step 7.

7

Repeat step 5 to check the Service action (removal) allowed status for the ESM, and then replace the ESM canister on the non-working channel using the following notes:

  • Make sure that the replacement ESM canister is the same as the ESM that is remaining in the drive enclosure (hardware type and firmware version).

  • If the affected drive enclosure uses ESM canisters with external switches, verify that they are set to the same values as the switches on the remaining ESM.

  • Wait 40 seconds for the storage subsystem to detect and register the ESM canister.

  • Go to step 8.

8

Reconnect the cable or interface transceiver to the replaced ESM canister and wait 40 seconds. If a "Degraded Drive Channel" problem is also being reported in the Summary area, then go to step 9; otherwise, go to step 10.

9

Select the

Advanced >> Troubleshooting >> Drive Channels

pull-down menu option, highlight the degraded drive channel, and then click the

Set Optimal

button.

Note: The drive channel status may automatically be reset to Degraded if the controller again determines that the channel is not operating properly.

10

Click the

Recheck

button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.

Element properties:

TargetIBMStorageSubsystem.StorageSubsystem
Parent MonitorIBMStorageSubsystem.StorageSubsystemAvailability
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeIBMStorageSubsystem.FailureUnitMonitorType
RemotableTrue
AccessibilityInternal
Alert Message
Alert: REC_LOST_REDUNDANCY_ESM
Alert Value: {0}
RunAsDefault
CommentMachine generated entity

Source Code:

<UnitMonitor ID="IBMStorageSubsystem.FailureID_0034_Monitor" Accessibility="Internal" Enabled="true" Target="IBMStorageSubsystem.StorageSubsystem" ParentMonitorID="IBMStorageSubsystem.StorageSubsystemAvailability" Remotable="true" Priority="Normal" TypeID="IBMStorageSubsystem.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">

  <Category>Custom</Category>

  <AlertSettings AlertMessage="IBMStorageSubsystem.REC_LOST_REDUNDANCY_ESM_AlertMessageResourceID">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>Error</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Data/Context/Property[@Name='FailureDescription']$</AlertParameter1>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="IBMStorageSubsystem.StateIdE28389C0301232A124A58F4D2825D546" MonitorTypeStateID="NoIssue" HealthState="Success"/>

    <OperationalState ID="IBMStorageSubsystem.StateId5774DC9FA2720B67A3C1C177B0915FCA" MonitorTypeStateID="IssueFound" HealthState="Error"/>

  </OperationalStates>

  <Configuration>

    <FailureID>34</FailureID>

    <IntervalSeconds>59</IntervalSeconds>

    <TimeoutSeconds>300</TimeoutSeconds>

    <Trace>0</Trace>

  </Configuration>

</UnitMonitor>