The drive side fibre
channel ports have been incorrectly connected.
What Caused the Problem?
Two or more drive channels are connected to the same Fibre Channel loop. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Caution
:
Possible loss of data accessibility.
It is very important that you resolve this miswire problem along with any other miswire problem that is reported in the Recovery Guru Summary Area before attempting to resolve any other problem that is being reported in the Summary Area. Resolving non-miswire problems with miswire problems still present can lead to a loss of data accessibility.
Caution: Risk of data loss. It is highly recommended that you suspend all I/O before performing this procedure. Removing cables from a working storage array can cause data loss. If you are not familiar with your cabling configuration, contact your Technical Support Representative.
Important Note
When two or more drive channels are connected to the same Fibre Channel loop, the storage array could behave unpredictably.
Recovery Steps
1 | Use the information provided in the Details area to determine which drive channels are miswired. Trace the cables from the controller tray's miswired channel connections to the drive trays. Follow the cable paths until you find a connection where two different channels are connected to the same ESM canister. The following diagrams show common miswire configurations:
|
2 | Reconnect the cables so there is only one drive channel on a Fibre Channel loop. Use the interface cable routing examples in the controller tray and drive tray installation guide as a reference. |
3 | 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 | 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 |
<UnitMonitor ID="NetAppESeries.FailureID_0038_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_CHANNEL_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.StateIdF69037C62EE54449C4484C889A9D441E" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateId8DC0F0142A988C194C6D66C4B341C249" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>38</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>