Home
  •  

Dell MD Array EMM - Loss of Communication

Dell.MDStorageArray.ABBXMLEvent34 (Rule)

Knowledge Base article:

Summary

EMM - Loss of Communication

The causes and resolutions refer to the Dell Modular Disk Storage Manager recovery guru. Launch Dell Modular Disk Storage Manager to diagnose and fix the recovery failure as follows:

Causes

Communication has been lost to one of the dual EMMs in an expansion enclosure. The expansion 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

Resolutions

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 physical disk channel on the RAID controller module enclosure corresponding to the working channel (refer to the labels on the back of the RAID controller module enclosure if needed).

3

Trace the cable from the working channel to the optimal EMM in the affected expansion 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 EMM in the affected expansion enclosure (this is the EMM on the non-working channel).

5

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

a

While the cables are still connected, remove the EMM from the expansion enclosure.

Note: The Service Action (removal) Allowed (SAA) 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 SAA is NO.

b

Wait 10 seconds, and then re-insert the EMM 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 Physical Disk 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 EMM on the non-working channel

Remove the cable.

Go to step 7.

7

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

a

Make sure that the replacement EMM is the same as the EMM that is remaining in the expansion enclosure (hardware type and firmware version).

b

If the affected expansion enclosure uses EMMs with external switches, verify that they are set to the same values as the switches on the remaining EMM.

c

Wait 40 seconds for the storage array to detect and register the EMM.

d

Go to step 8.

8

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

9

Select the Hardware > Enclosure > View/Edit > Physical Disk Channels... menu option, highlight the degraded physical disk channel, and then click the Set Optimal... button.

Note: The physical disk channel status may automatically be reset to Degraded if the RAID controller module 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:

TargetMicrosoft.SystemCenter.ManagementServer
CategoryAlert
EnabledTrue
Alert GenerateTrue
Alert SeverityWarning
Alert PriorityNormal
RemotableTrue
Alert Message
Dell MD Array EMM - Loss of Communication
{0}

Member Modules:

ID Module Type TypeId RunAs 
DS DataSource Microsoft.Windows.ScriptGenerated.EventProvider Default
Alert WriteAction System.Health.GenerateAlert Default
WriteToDW WriteAction Microsoft.SystemCenter.DataWarehouse.PublishEventData Default

Source Code:

<Rule ID="Dell.MDStorageArray.ABBXMLEvent34" Enabled="onEssentialMonitoring" Target="SystemCenter!Microsoft.SystemCenter.ManagementServer" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">

  <Category>Alert</Category>

  <DataSources>

    <DataSource ID="DS" TypeID="Windows!Microsoft.Windows.ScriptGenerated.EventProvider">

      <ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>

      <ScriptName>RBODEventGenerator</ScriptName>

      <EventNumber>34</EventNumber>

    </DataSource>

  </DataSources>

  <WriteActions>

    <WriteAction ID="Alert" TypeID="SystemHealth!System.Health.GenerateAlert">

      <Priority>1</Priority>

      <Severity>1</Severity>

      <AlertMessageId>$MPElement[Name="Dell.MDStorageArray.ABBXMLEvent34.StringResource"]$</AlertMessageId>

      <AlertParameters>

        <AlertParameter1>$Data/EventDescription$</AlertParameter1>

      </AlertParameters>

      <Suppression>

        <SuppressionValue>$Data/EventDisplayNumber$</SuppressionValue>

        <SuppressionValue>$Data/Channel$</SuppressionValue>

        <SuppressionValue>$Data/PublisherName$</SuppressionValue>

        <SuppressionValue>$Data/LoggingComputer$</SuppressionValue>

        <SuppressionValue>$Data/EventCategory$</SuppressionValue>

        <SuppressionValue>$Data/EventLevel$</SuppressionValue>

        <SuppressionValue>$Data/UserName$</SuppressionValue>

        <SuppressionValue>$Data/EventNumber$</SuppressionValue>

        <SuppressionValue>$Data/EventDescription$</SuppressionValue>

      </Suppression>

      <Custom1/>

      <Custom2/>

      <Custom3/>

      <Custom4/>

      <Custom5/>

      <Custom6/>

      <Custom7/>

      <Custom8/>

      <Custom9/>

      <Custom10/>

    </WriteAction>

    <WriteAction ID="WriteToDW" TypeID="SCDW!Microsoft.SystemCenter.DataWarehouse.PublishEventData"/>

  </WriteActions>

</Rule>