The controller detected an HBA cabled to a drive channel. To protect the array, the controller will attempt to disable the SAS port within the array that is attached to the HBA.
What Caused the Problem?
The storage array contains an improper connection between a HBA port and a SAS drive channel port. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Important Notes
This miswire will be detected if a SAS port is found to be connected to an expansion port on the controller, or if one of the ESM's reports initiator capability and has a SAS address that is not from the controller that detected it or from the alternate controller.
Due to the nature of this miswire condition, the port on the controller or ESM with dual-expansion channels that is connected to the HBA will be disabled to protect the storage array from unauthorized access. For controllers with a dedicated expansion channel, the miswire will be detected but the port will not be disabled.
The Details area provides information about the miswire and will indicate the affected host adapter and ESM ports.
Recovery Steps
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 from the miswired channel or port to the HBA port 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 |
| ||||||
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 again. If the failure still persists, contact your Technical Support Representative. |
| Target | NetAppESeries.StorageArray | ||
| Parent Monitor | NetAppESeries.StorageArrayAvailability | ||
| Category | Custom | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | Error | ||
| Alert Priority | Normal | ||
| Alert Auto Resolve | True | ||
| Monitor Type | NetAppESeries.FailureUnitMonitorType | ||
| Remotable | True | ||
| Accessibility | Internal | ||
| Alert Message |
| ||
| RunAs | Default | ||
| Comment | Machine generated entity |
Home
<UnitMonitor ID="NetAppESeries.FailureID_0451_Monitor" Accessibility="Internal" Enabled="true" Target="NetAppESeries.StorageArray" ParentMonitorID="NetAppESeries.StorageArrayAvailability" Remotable="true" Priority="Normal" TypeID="NetAppESeries.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">
<Category>Custom</Category>
<AlertSettings AlertMessage="NetAppESeries.REC_SAS_HOST_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="NetAppESeries.StateIdBD0E0A6310A085C743E00A1781FC2D04" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateId19A6550E047FB983F9D9F6146BA338A1" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>451</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>