One or more Soyuz expansion channels are not externally connected to the alternate controller due to cabling or expansion tray power issues. One or both of the controllers may have completely lost access to one or more expansion trays.
What Caused the Problem?
A controller has lost redundant paths to an expansion tray. Loss of external redundancy can result from any of the following:
Disconnected or faulty drive cables
Removed, improperly seated, or faulty ESM canister
The expansion tray has lost power
The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Caution: Risk of Data Loss. If the storage array is running live I/O, disconnecting additional cables may cause incoming writes to affected volumes to fail.
Caution:
Potential loss of data accessibility.
If the Summary area is reporting any other problems, it is very important that you resolve this problem first. Once this problem has been resolved, you can continue with fixing any other problems reported. Attempting to resolve other problems first while this problem is still present can lead to a loss of data accessibility.
Caution:
Electrostatic discharge can damage sensitive components.
Use a grounding wrist strap or other anti-static precautions before removing or handling components.
Important Notes
Correct this failure as soon as possible. Although the storage array is still operational, a level of redundancy has been lost.
Problems of disconnected or missing cables typically occur when the storage array is cabled for the first time, or when an expansion tray has been added to the storage array. Depending on the number of cables that are not properly connected, data accessibility may or may not be lost. In most cases, even if data is still accessible, if another cable is disconnected, all I/O to that tray will fail.
If you have recently cabled, rearranged or disconnected cables for the storage array, follow the provided diagram to trace which cables may not be connected correctly.
If I/O to an expansion tray fails, data may not be accessible and any affected volumes could fail.
Depending on which cables are disconnected, some expansion trays may not be visible on the
Hardware
tab in the Array Management Window.
The Details area reports the affected controller and the missing channel over which it cannot communicate with the tray.
Recovery Steps
1 | Ensure that each expansion tray has power.
| ||||||||||||
2 | The following diagram shows the supported cabling configuration. Follow the diagram and check for any disconnected or damaged cables by tracing the cables from the controller tray's missing channel (identified in the Details area) to the expansion trays.
| ||||||||||||
3 | Reconnect any cables that have been disconnected, or replace any cables that appear to be damaged. | ||||||||||||
4 | 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 |
Home
<UnitMonitor ID="NetAppESeries.FailureID_0449_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_LOSS_OF_EXTERNAL_REDUNDANCY_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.StateIdCA4230CF84E2C36CB7C7662D5CA5CB87" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateId8FB48EA21563D76F4795C98482A9459B" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>449</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>