Failed EMM
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:
Open Start >> Programs >> Dell >> MD Storage Manager >> Modular Disk Storage Manager Client.
If the MD Storage Array is already being managed by MDSM, you can proceed with the Causes and Resolution sections.
From Edit -> Add Storage Array, provide the IP address of the MD Storage Array and Add it to the discovered devices configuration in order to manage it.
Select the MD Storage Array and follow the steps specified in this recovery guru.
An EMM has failed in an expansion enclosure. 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
Although the expansion enclosure is still operational, you should correct this failure as soon as possible. If the other EMM or its communication path fails, all I/O to that expansion enclosure will fail.
In some cases, if both EMMs have failed, the physical disks in the expansion enclosure will be automatically spun down (failed) to avoid potential damage to the physical disks. If the physical disks are spun down, the Recovery Guru may also report physical disk, virtual disk, and channel failures. However, do NOT use the associated procedures for these reported failures. Instead, contact your technical support representative.
For some failures, the fault indicator light on an EMM will not be on.
There are several conditions which may cause loss of communication with the EMM. Use your hardware manual to help diagnose the problem.
Both EMM in the same expansion enclosure must have the same firmware version and be of the same hardware type.
Service Action Allowed Important Information:
The Service action (removal) allowed field in the Details area indicates whether or not you can safely remove the component. If the SAA field is NO, then the affected component must remain in place until you service another component first.
The Service action LED on Component field in the Details area indicates whether or not a physical SAA LED is present on the hardware component. This field does NOT indicate whether the LED is ON or OFF (that indication is provided by the Service action (removal) allowed field).
If a component does not have an SAA LED, then it is OK to remove the component when its fault LED is lit and the Service action (removal) allowed field = YES in the Details area.
The Service action (removal) allowed field shown in the Details area and the physical SAA LED on the hardware component (if supported) MUST match before you remove the affected component. In rare cases (such as multiple problems), the status of the LED and the SAA field may not match. If there is a mismatch, then you should NOT remove the component until these indications match.
1 |
| ||||||
2 | Check to make sure there is power to the expansion enclosure and that the external physical disk cables are secure. Caution: Risk of Data Loss. Disconnecting expansion enclosure cables to the remaining optimal EMM while I/O is in progress can cause data loss!
| ||||||
3 | Refer to the Details area to identify the failed EMM. Caution: Risk of Data Loss. Make sure you correctly identify the failed EMM. If you have two EMMs, removing the remaining optimal EMM while I/O is in progress can cause loss of access to data! | ||||||
4 | Reseating the affected EMM may clear the failure being reported. While the cables are still connected to the EMM, remove the EMM from the expansion enclosure, wait 10 seconds, and re-insert the EMM firmly. Wait 40 seconds, then click the Recheck button to rerun the Recovery Guru to ensure the failure has been fixed.
| ||||||
5 |
| ||||||
6 | Replace the failed EMM. Make sure that the replacement EMM is the same as the EMM that is remaining in the expansion enclosure (hardware type and firmware version). | ||||||
7 | Using the labels created in step 5, reconnect the cables to the replaced EMM. Wait 40 seconds, then go to step 8. | ||||||
8 | 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. |
| Target | Microsoft.SystemCenter.ManagementServer | ||
| Category | Alert | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | Warning | ||
| Alert Priority | Normal | ||
| Remotable | True | ||
| Alert Message |
|
| 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 |
Home
<Rule ID="Dell.MDStorageArray.ABBXMLEvent4" 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>4</EventNumber>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertMessageId>$MPElement[Name="Dell.MDStorageArray.ABBXMLEvent4.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>