Monitor Description for (458)
What Caused the Problem?
The controller was automatically placed in Data Assurance Service Mode due to an excessive number of Data Assurance errors detected. These errors will need to be evaluated by a Technical Support Representative. 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 Data Assurance 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.
If the alternate controller is in lockdown mode, it must be evaluated and brought back online by your Technical Support Representative first. The controller in lockdown mode has the most current data and data loss could occur if the controller in service mode is brought online first.
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 | Contact your Technical Support Representative. It is important that you perform the proper troubleshooting actions as directed by your Technical Support Representative before placing the controller back online in step 2. | ||||||
2 | Perform the following steps at the instruction of your Technical Support Representative 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 | NetAppSANtricity.StorageArray | ||
| Parent Monitor | NetAppSANtricity.StorageArrayAvailability | ||
| Category | Custom | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | Error | ||
| Alert Priority | Normal | ||
| Alert Auto Resolve | True | ||
| Monitor Type | NetAppSANtricity.FailureUnitMonitorType | ||
| Remotable | True | ||
| Accessibility | Internal | ||
| Alert Message |
| ||
| RunAs | Default | ||
| Comment | Machine generated entity |
Home<UnitMonitor ID="NetAppSANtricity.FailureID_0458_Monitor" Accessibility="Internal" Enabled="true" Target="NetAppSANtricity.StorageArray" ParentMonitorID="NetAppSANtricity.StorageArrayAvailability" Remotable="true" Priority="Normal" TypeID="NetAppSANtricity.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">
<Category>Custom</Category>
<AlertSettings AlertMessage="NetAppSANtricity.REC_PI_ERROR_SERVICE_MODE_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="NetAppSANtricity.StateId24A742F857BC2269F2F76871ED91C9F7" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppSANtricity.StateId922640050935181B5666BD08B332B436" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>458</FailureID>
<IntervalSeconds>361</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>