The controller detected that the two drive channels have been wired together. To protect the array, the controller will attempt to disable the expansion ports for one of the drive channels.
What Caused the Problem?
The storage array has detected that an improper connection exists between the two SAS drive channels - they have either been connected, either directly or indirectly, through an expander in an ESM. The Recovery Guru Details area provides specific information you will need as you follow the Recovery Steps.
Important Notes
There are two different methods of drive channel expansion available on the different models of controllers. You should determine the expansion method being used by your controller model and refer to the cabling guide shipped with your controller tray or drive tray before attempting to correct this miswire:
If your controller has only one expansion port per controller, it uses the common channel expansion method.
If your controller has more than one expansion port per controller and the ports are labeled Port 1 and Port 2, it also uses the common channel expansion method.
If your controller has more than one expansion port per controller and the expansion ports are labeled Ch 1 and Ch 2, it uses the direct channel expansion method.
When attaching expansion drive trays to common channel controllers, a cable from the controller in the A slot must be connected to the ESM in the A slot of the first expansion drive tray. A cable from the controller in the B slot must be connected to the ESM in the B slot of the last expansion drive tray. Additional expansion drive trays are connected with a single cable from the Out port on the ESM in the same slot location in the previous expansion drive tray.
On common channel expansion controllers with multiple ports, the second expansion port can be connected to the same ESM as the first port providing a wider connection, or the second expansion port can be used to create a second stack of expansion drive trays. When using two stacks of expansion drive trays, no connections may be made between the stacks except the connection from the controller expansion ports.
When attaching expansion drive trays to direct expansion controllers, the channels must be connected into a common SAS domain by attaching a cable from each channel from both the A and B controllers to the ESM in a common expansion drive tray. For example, a cable from Controller A, Ch 1 and a cable from Controller B, Ch1 must be connected to the ESM in the A slot of the first expansion drive tray. The Ch 2 ports of both controllers must then be connected to the ESM in the B slot of the last expansion drive tray. Additional expansion drive trays are connected with a single cable from the Out port on the ESM in the same slot location in the previous expansion drive tray.
When a cross channel miswire is detected for either common channel expansion or direct channel expansion controllers, the exact location of the miswire will be identified in the Details Area. For controllers using the direct channel expansion method, the Out port for the affected channel will be automatically disabled. The controller will not be able to connect to any expansion drive trays until the cabling is corrected and the port is re-enabled.
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 to the miswired channel or port to the connector on the other end. | ||||||
2 | Refer to your 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_0452_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_CROSS_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.StateId8CE118CF7358B8EA4F45783F61A1B5B" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateId7D4149C33FDC778D6595F6511E49DB6D" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>452</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>