The controller is configured with an unsupported cache memory size.
What Caused the Problem?
A controller currently contains more total cache memory than the controller supports. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Important Notes
This problem typically occurs when controller memory is upgraded to an amount above what is currently allowed.
The controller only utilizes the portion of the cache memory that it is certified to support. For example, if the controller is certified for a maximum of 4GB, and there is currently 8GB installed, then the controller will only use 4GB out of the 8GB for I/O purposes.
To ensure a complete configuration restore (both disk pool and traditional volume group), it is highly recommended that storage array configuration data is backed up prior to executing this procedure. This is especially important for simplex storage arrays, and controllers that operate without the use of batteries. To save your configuration, open either the Command Line Interface (CLI), or the Script Editor from the Enterprise Management Window (EMW), and execute the following command:
save storageArray dbmDatabase sourceLocation=onboard controller[a] contentType=all file="hostfile.zip";
Recovery Steps
If... | Then... |
Your storage array has one controller | Go to Procedure for Storage Arrays with One Controller. |
Your storage array has two controllers | Go to Procedure for Storage Arrays with Two Controllers. |
Procedure for Storage Arrays with One Controller
1 | Stop all I/O from all hosts to this storage array. When the Cache Active LED on the controller is no longer blinking (may take several minutes), proceed to step 2. Caution: Risk of Data Loss. You must wait for the Cache Active LED to stop blinking to ensure that all cache has been written to disk. | ||||||
2 | Click the Save As button in the Recovery Guru dialog to save the remaining steps to file. The remaining recovery steps will no longer be accessible from the Recovery Guru dialog after you complete step 3. | ||||||
3 | Remove the controller canister that contains the affected cache backup device (listed in the Component requiring service field in the Details area). | ||||||
4 | Refer to the Enterprise Management Window (EMW) to view which management method you are using to manage this storage array.
| ||||||
5 | Insert the controller canister securely into place. After the controller appears on the Hardware tab in the AMW, go to step 6. Note: Write caching will be reinstated (if applicable for each volume) once the controller's battery is fully charged and has completed any required learn cycles (if applicable). | ||||||
6 | 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. |
Procedure for Storage Arrays with Two Controllers
1 | If there are any hosts connected to this storage array that are NOT running a host-based, multi-path failover driver, stop I/O to the storage array from each of these hosts. | ||||||
2 | Place the affected controller offline. The affected controller is listed in the Component requiring service field in the Details area.
| ||||||
3 | Read all of the following steps before taking any action. The remaining recovery steps will no longer be accessible from the Recovery Guru dialog after you complete step a.
|
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_0223_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_UNSUPPORTED_CACHE_MEMORY_SIZE_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.StateId5DF9E171131338C1DAE650871D4FD57D" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateId8BB212F8BCF30CFA5FC28C8E4DA59E2D" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>223</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>