Home
  •  

Monitor REC_ESM_CODE_VERSION_MISMATCH (31)

NetAppSANtricity.FailureID_0031_Monitor (UnitMonitor)

The firmware versions
for the ESM cards in a tray do not match.

Knowledge Base article:

ESM Firmware Mismatch

What Caused the Problem?

A drive tray in the storage array contains ESM canisters with different firmware versions. The software should resolve this mismatch problem by automatically synchronzing the firmware between the two ESMs. However, there are conditions which may cause the automatic synchronization to not occur. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.

Important Note

An ESM canister firmware mismatch can affect how the storage array reports existing disk pools, volume groups and volumes (some of them may not display).

Recovery Steps

1

Wait at least 15 minutes before going to step 2. This should be sufficient time for the ESM automatic synchronization process to complete.

IMPORTANT: During this time, make sure that you do not remove an ESM canister in the affected drive tray reported in the Details area.

2

Review the following information before clicking the

Recheck

button. Once you have reviewed the information, click the

Recheck

button to rerun the Recovery Guru.

If after clicking the Recheck button...

Then...

The ESM firmware mismatch no longer appears in the Summary area for the affected drive tray.

The firmware on the ESMs in the affected drive tray have been synchronized.

As an additional verification, access the Storage Array Profile and then select the Tray information. Scroll down until you find the affected drive tray and ensure that the firmware on the two ESMs is the same.

The ESM firmware mismatch continues to appear in the Summary area for the affected drive tray.

The automatic synchronization has probably failed because of one of the conditions given below.

  • The host running the management software does not have the Event Monitor service started.

  • The Event Monitor service was not running when the ESM firmware was downloaded to one of the ESMs.

  • The proper firmware file was not found in the firmware repository directory on the host running the management software.

  • An ESM failure occurred or an ESM was removed during the synchronization.

  • The synchronization failed for some other reason.

a

Check to make sure that the Event Monitor service is started on the host. Start it if it is currently stopped. Once started, this should detect the current mismatch condition and begin the automatic synchronization.

b

Check the host's operating system log for entries related to the ESM firmware automatic synchronization to further pinpoint the problem.

c

If the ESM firmware mismatch problem continues to be reported, you can synchronize the two ESMs by manually downloading the appropriate firmware using the ESM firmware download option in the storage management software.

Element properties:

TargetNetAppSANtricity.StorageArray
Parent MonitorNetAppSANtricity.StorageArrayAvailability
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeNetAppSANtricity.FailureUnitMonitorType
RemotableTrue
AccessibilityInternal
Alert Message
Alert: REC_ESM_CODE_VERSION_MISMATCH
The firmware versions
for the ESM cards in a tray do not match. Alert Value: {0}
RunAsDefault
CommentMachine generated entity

Source Code:

<UnitMonitor ID="NetAppSANtricity.FailureID_0031_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_ESM_CODE_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="NetAppSANtricity.StateIdC732198BD7108B68ECCF96F0A04E0019" MonitorTypeStateID="NoIssue" HealthState="Success"/>

    <OperationalState ID="NetAppSANtricity.StateId11840281C889ABE53662815935331E88" MonitorTypeStateID="IssueFound" HealthState="Error"/>

  </OperationalStates>

  <Configuration>

    <FailureID>31</FailureID>

    <IntervalSeconds>361</IntervalSeconds>

    <TimeoutSeconds>300</TimeoutSeconds>

    <Trace>0</Trace>

  </Configuration>

</UnitMonitor>