The two controllers in the storage array have different cache memory capacities.
What Caused the Problem?
There is a mismatch in the cache memory for the storage array. This problem can occur for the following reasons:
Two controllers have different sizes of total installed cache memory. For example, Controller A has 2GB of total cache memory and Controller B has 4GB of total cache memory.
Two controllers have the same size of total installed cache memory, but there is probably a BIOS version mismatch.
There is a mismatch in the attributes of the cache memory between the two controllers (such as the buffer layout version, raw pool sizes, or Error Detection Coding (EDC) enabled values).
Important Notes
This problem typically occurs when you replace a controller that has a different type or size of memory than the controller that remained in the storage array.
This problem can also occur if the cache memory DIMMs were replaced. Replacing or changing the size of the cache memory inside a controller is typically not a supported operation.
Until this problem is corrected, write caching (including caching with mirroring) will be disabled.
If the two controllers have different sizes of total installed cache memory, the storage array will use the smaller capacity of cache memory between the two controllers. For example, if Controller A has 2GB of total cache memory and Controller B has 4GB of total cache memory, then both controllers will only use 2GB.
Recovery Steps
1 | Record the total cache memory size for each controller:
| ||||||||||||||||||
2 |
| ||||||||||||||||||
3 | Obtain a replacement controller that has the same sub-model and memory size as the controller you are leaving in the storage array. | ||||||||||||||||||
4 | Place the controller you want to remove offline:
| ||||||||||||||||||
5 | 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.
| ||||||||||||||||||
6 | Click Recheck 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 |
<UnitMonitor ID="NetAppSANtricity.FailureID_0231_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_CACHE_MEM_SIZE_MISMATCH_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.StateId56D0A79773A6E5B0EC77091115621F90" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppSANtricity.StateIdD11640E85DE33706C68738C97355A9FC" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>231</FailureID>
<IntervalSeconds>361</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>