SAS Device Miswire
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.
The storage array contains an improper connection between two Serial Attached SCSI (SAS) ports. The Recovery Guru Details area provides specific information you will need as you follow the Recovery Steps.
Important Notes
Depending on the nature of the miswire, you may not have redundant access to the expansion enclosures. A RAID controller module failure could result in a loss of access to your data. You should correct this problem as soon as possible.
The Details area provides information about the type of miswire that was detected. The miswire types are: invalid SAS Topology, EMM Miswire, Host Channel Miswire, and Host Adapter Miswire.
The following examples are provided to help you to diagnose your miswire problem. However, your cabling configuration may differ from the examples.
Invalid SAS Topology - This miswire condition occurs when you connect the Out ports of two EMMs in different expansion enclosures. You should only connect Out ports of an EMM to an In port of an EMM in a different enclosure.
EMM Miswire - This miswire condition occurs when you connect the Out port of an EMM to the In port of the other EMM in the same enclosure. You should not connect EMMs in the same enclosure together.
Host Channel Miswire - This miswire condition occurs when you connect a Host Channel to another port on the RAID controller module enclosure or a port on another expansion enclosure. You should only connect Host Channels to an appropriate HBA or other external device.
Host Adapter Miswire - This miswire condition occurs when you connect an external Host Adapter port to any port other than a Host Channel port (Physical Disk Channel port, EMM In port, or EMM Out port). You should only connect a Host Adapter port to a Host Channel port on a RAID controller module. Important: If a Host Adapter Miswire is reported, the port on the RAID controller module or EMM that is connected to the HBA will not be able to connect to any device until after the cabling is corrected and the RAID controller module or EMM is power-cycled.
1 | Use the information provided in the Recovery Guru Details area to determine which port is the origin of the miswire. Using this information, trace the cable that is attached to the miswired channel or port to the connector on the other end. | ||||||||||||||||||||||||||||
2 | Refer to your cabling documentation to reconnect the cable to the appropriate port. It may be necessary for you to reconnect more than one cable in order to have a valid configuration. Once you have a valid cabling configuration, go to step 3. | ||||||||||||||||||||||||||||
3 | Check the Details area to see which type of miswire is being reported.
| ||||||||||||||||||||||||||||
4 | Check the Details area to see whether the miswired port is on an EMM or a RAID controller module.
| ||||||||||||||||||||||||||||
5 | 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. | ||||||||||||||||||||||||||||
6 | If you stopped I/O to the storage array in step 4, resume I/O. |
| 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.ABBXMLEvent111" 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>111</EventNumber>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertMessageId>$MPElement[Name="Dell.MDStorageArray.ABBXMLEvent111.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>