This is obsolete.
What Caused the Problem?
A controller was placed in Service mode. This could be caused by the following:
The controller was manually placed in Service mode for diagnostic or recovery reasons at the instruction of a Technical Support Representative.
The controller has lost access to all expansion enclosures and was automatically placed in Service mode.
The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Important Notes
It is important to understand why the controller was placed in Service mode and determine that any problems associated with placing the controller in Service mode have been corrected before attempting to change the status of the controller to Online.
The volumes that were originally owned by the affected controller have been moved to the alternate controller. These volumes will be automatically redistributed back to the controller that owns them if the controller is placed directly back online. This redistribution will not occur if the controller is placed offline and then online.
If write caching on any volume is enabled, it might be automatically suspended until this issue is corrected and all batteries are fully charged (if batteries are present). To see if caching is disabled, use the
Storage > Volume > Change > Cache Settings
menu option. Any option with the red dot icon is currently suspended.
Recovery Steps
1 | Before placing the controller back online in step 2, ensure that you have corrected any problems that may have led to the controller being placed in Service mode. | ||||||
2 | Perform the following steps to place the controller back online:
| ||||||
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 |
Home
<UnitMonitor ID="NetAppESeries.FailureID_0029_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_PASSIVE_CTL_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.StateId3333D178959B442B89379ED6C4BB4A0C" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateId7840B823FFF7741448B23DCAF4554B14" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>29</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>