The failure type is LD FW Version Mismatch.
What Caused the Problem?
The controller listed in the Details area is running a different version of controller firmware than the previous controller. This problem can occur for the following reasons:
There is only one controller in the storage array (Simplex mode).
You replaced the previous (native) controller with a new (foreign) controller which has a different version of controller firmware.
The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Caution: Electrostatic discharge can damage sensitive components. Always use proper antistatic protection when handling components. Touching components without using a proper ground may damage the equipment.
Important Notes
Due to this error condition, the only task you can perform on this storage array is to download the appropriate version of controller firmware to the new (foreign) controller.
Host I/O and all other configuration tasks will not be available until the controller firmware is the appropriate version.
You should always replace a controller with one of the same sub-model. Controllers with different sub-models may not support the same version of controller firmware.
Recovery Steps
1 | Refer to the Details area to determine which version of controller firmware is expected by the storage array.
| ||||||
2 |
| ||||||
3 | From the Array Management Window (AMW), select the Upgrade > Controller Firmware > Upgrade menu option. Note: If the storage array is in locked-down mode, the menu option will not be available in the AMW. Instead, select the "Download Firmware" link on the Summary tab. | ||||||
4 | Complete the appropriate steps in the "Download Controller Firmware" dialog to update the controller firmware to the appropriate version. When the transfer is complete and the new firmware has successfully been updated, the controller will reboot automatically. | ||||||
5 | Wait for the storage management software to update (all of the tasks will reappear under the tabs), and then go to step 6. | ||||||
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. |
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_0301_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_LD_FW_VERSION_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="NetAppESeries.StateId1D174870A8FB00F9B5FDCAED848ED627" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateId6C91F5FACB2CEC33CEBA0852DA63E5A1" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>301</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>