The controller detected a loop in the SAS domain that constitutes a drive channel. To protect the array, the controller will attempt to break the loop by disabling the expansion-out ports on the affected channel.
What Caused the Problem?
The storage array has detected that an improper connection exists in the SAS drive channels, resulting in SAS ports being discovered more than one time on a single channel. This is considered an illegal configuration. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Important Notes
A SAS loop miswire is created if three or more expanders are connected in such a way that there is more than one possible path between any two points in the configuration.
Due to the nature of this miswire condition, the drive expansion Out port in or above the loop for one of the channels will be disabled.
The Details area provides information about the miswire and will indicate the affected channel and drive expansion ports.
Recovery Steps
1 | Use the information provided in the Recovery Guru Details area to determine which drive expansion ports are the origin of the drive channel loop miswire. Using this information, trace the cable that is attached from the miswired drive expansion port to the ESM ports indicated. |
2 | Refer to the cabling documentation originally shipped with your controller/drive tray 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 | Select the Monitor > Health > Recover from Miswire menu option to re-enable the SAS port within the drive channel providing access to the expansion trays. |
4 | Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure is not cleared, try to power-cycle ALL of the components involved in the miswire. If the failure still persists, contact your Technical Support Representative. |
| Target | NetAppSANtricity.StorageArray | ||
| Parent Monitor | NetAppSANtricity.StorageArrayAvailability | ||
| Category | Custom | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | Error | ||
| Alert Priority | Normal | ||
| Alert Auto Resolve | True | ||
| Monitor Type | NetAppSANtricity.FailureUnitMonitorType | ||
| Remotable | True | ||
| Accessibility | Internal | ||
| Alert Message |
| ||
| RunAs | Default | ||
| Comment | Machine generated entity |
Home<UnitMonitor ID="NetAppSANtricity.FailureID_0453_Monitor" Accessibility="Internal" Enabled="true" Target="NetAppSANtricity.StorageArray" ParentMonitorID="NetAppSANtricity.StorageArrayAvailability" Remotable="true" Priority="Normal" TypeID="NetAppSANtricity.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">
<Category>Custom</Category>
<AlertSettings AlertMessage="NetAppSANtricity.REC_SAS_LOOP_MISWIRE_AlertMessageResourceID">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/Property[@Name='FailureDescription']$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="NetAppSANtricity.StateIdF1E4EC3E7CA0B8DC93B99A3B6BBFF4CF" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppSANtricity.StateId50DA6358870910C5BACEFD1A044B03FB" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>453</FailureID>
<IntervalSeconds>361</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>