Home
  •  

Dell MD Array RAID Controller Module Submodel Not Supported

Dell.MDStorageArray.ABBXMLEvent99 (Rule)

Knowledge Base article:

Summary

RAID Controller Module Submodel Not Supported

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

The submodel number associated with this RAID controller module was not set at the factory or it is not supported by the RAID controller module firmware. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.

Caution: Possible loss of data accessibility. Do not remove a component when either (1) the Service action (removal) allowed (SAA) field in the Details area of this recovery procedure is NO, or (2) the SAA LED on the affected component is OFF (note that some products do not have SAA LEDs). Removing a component while its SAA LED is OFF may result in temporary loss of access to your data. Refer to the following Important Notes for more detail.

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

Check the replacement part number of the remaining, operating RAID controller module to ensure that you have a replacement RAID controller module that has the same replacement part number.

a

On the Hardware tab in the Array Management Window (AMW), select the remaining RAID controller module.

b

Identify the "Replacement part number" in the Properties pane.

Note: Depending on the model of your RAID controller module, the battery may be integrated inside the RAID controller module, rather than residing in a separate module. If the RAID controller module you are replacing contains a battery, you may have to insert the battery from the old RAID controller module into the new replacement RAID controller module. Consult your hardware documentation for details.

If...

Then...

You have a replacement RAID controller module that has the same part number

Go to step 2 to replace the incompatible RAID controller module.

You have a replacement RAID controller module that does NOT have the same part number

Do not continue with the remaining recovery steps and contact your Technical Support Representative.

2

Remove the incompatible RAID controller module (0 or 1) listed in the Details area.

Note: There is nothing wrong with the incompatible RAID controller module and that it may be compatible with another storage array. It can be used as a replacement for a RAID controller module that has the same replacement part number.

3

If...

Then...

You are using In-Band management of the storage array

(Refer to the Network Management Type column in the Enterprise Management Window)

Go to step 4.

You are using Out-of-Band management of the storage array

(Refer to the Network Management Type column in the Enterprise Management Window)

Before you insert a new RAID controller module into the storage array, you must update the DHCP/BOOTP server so that it will associate the new RAID controller module's hardware Ethernet (MAC) address with the DNS/network name and IP address previously assigned to the removed RAID controller module.

To update the DHCP/BOOTP server, find the entry associated with the removed RAID controller module and replace its Ethernet (MAC) address with the new RAID controller module's Ethernet (MAC) address. The RAID controller module's Ethernet (MAC) address is located on an Ethernet ID label on the RAID controller module in the form xx.xx.xx.xx.xx.xx.

When you are finished, go to step 4.

4

Make sure at least 1 minute has elapsed then insert the new (compatible) RAID controller module securely into place. After the RAID controller module appears on the Hardware tab in the AMW, confirm that the RAID controller module has an Optimal status.

5

It may be necessary to redistribute the virtual disks to their preferred RAID controller module. Navigate to the Storage > Virtual Disk > Advanced > Redistribute Virtual Disks... menu option in the AMW.

If...

Then...

The menu option is available

Select the menu option to redistribute virtual disks back to their preferred RAID controller module.

Go to step 6.

The menu option is not available (grayed out)

The virtual disks are already associated with their preferred RAID controller modules and no action is needed.

Go to step 6.

6

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 RAID Controller Module Submodel Not Supported
{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.ABBXMLEvent99" 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>99</EventNumber>

    </DataSource>

  </DataSources>

  <WriteActions>

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

      <Priority>1</Priority>

      <Severity>1</Severity>

      <AlertMessageId>$MPElement[Name="Dell.MDStorageArray.ABBXMLEvent99.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>