Physical Disk Channel Data Rate Detection Mismatch
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.
A mismatch in data rate has been detected in the physical disk channel listed in the Recovery Guru Details area. This problem can occur for the following reasons:
An SFP in the RAID controller module enclosure does not match the data rate previously established by the physical disk channel.
An SFP in a expansion enclosure does not match the data rate previously established by the physical disk channel.
A data rate switch on a expansion enclosure is set to a speed that conflicts with the data rate previously established by the physical disk channel. Some models of expansion enclosures auto-detect the data rate, and therefore, do not have data rate switches.
There are faulty SFPs in either the RAID controller module enclosure or expansion enclosure, or there are faulty cables.
The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Important Note
The port has been bypassed and will not transfer any data until this problem is resolved.
1 | Check the Recovery Guru Summary area to see if a failed SFP is being reported.
| ||||||||||||||||||
2 | Refer to the Details area, and compare the Current data rate for the affected physical disk channel with the Maximum data rate for the SFP in the RAID controller module enclosure's affected port.
| ||||||||||||||||||
3 | Check the SFP in the expansion enclosure that is connected to the port listed in the Details area. The SFP may be failed or may not match the data rate of the rest of the storage array.
| ||||||||||||||||||
4 | Check the data rate switches on the expansion enclosures connected to the physical disk channel listed in the Details area. A data rate switch may be set to a speed that conflicts with the data rate of the RAID controller module's physical disk channel.
| ||||||||||||||||||
5 | Unplug and reconnect the cable at both ends of the port specified in the Details area. Click the Recheck button to rerun the Recovery Guru.
| ||||||||||||||||||
6 | Replace the cable attached to the port specified in the Details area, and then go to step 6. | ||||||||||||||||||
7 | 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 |
<Rule ID="Dell.MDStorageArray.ABBXMLEvent327" 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>327</EventNumber>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertMessageId>$MPElement[Name="Dell.MDStorageArray.ABBXMLEvent327.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>