Home
  •  

Monitor REC_ESM_HARDWARE_MISMATCH (104)

NetAppSANtricity.FailureID_0104_Monitor (UnitMonitor)

The ESM cards
in a tray do not match.

Knowledge Base article:

ESM Hardware Type Mismatch

What Caused the Problem?

A drive tray in the storage array contains ESM canisters with different hardware (such as a mixture of switched and non-switched ESMs or a SATA ESM and a Fibre Channel ESM). The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.

 Caution: Possible loss of data accessibility. Do not remove a component when either (1) the Service Action (removal) Allowed (SAA) field in the Details area of this recovery procedure is NO (), or (2) the SAA LED on the affected component is OFF (note that some products do not have SAA LEDs). Removing a component while its SAA LED is OFF may result in temporary loss of access to your data. Refer to the following Important Notes for more detail.

 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

Recovery Steps

1

The ESM firmware and hardware information is available in the Storage Array Profile.

a

Review the Recovery Guru Details area to identify which drive tray is affected by the mismatch.

b

Select the

Monitor > Reports > Storage Array Profile

menu option in the Array Management Window, and then select the

Hardware > Trays

tab.

c

Scroll down until you find the "Drive Tray x Overall Component Information" section.

Note: x is the drive tray number listed in the Details area.

d

Under each ESM Canister subheading, locate and record the following information for each ESM (left and right):

  • Firmware version:

  • Product ID:

  • Part number:

2

If...

Then...

You do NOT have a replacement ESM canister or are unable to determine if you have a replacement ESM canister with the same firmware version and hardware type as one of the canisters in the affected tray

Contact your Technical Support Representative.

You have a replacement ESM canister with the same firmware version and hardware type as the canister that will remain in the affected tray

Read the following notes and then perform the procedure:

  • Make sure you have determined which ESM canister should remain in the drive tray.

  • Make sure that the replacement ESM canister is the same as the ESM that will remain in the drive tray (hardware type and firmware version).

  • Wait approximately 40 seconds before inserting a replacement ESM canister.

  • Wait 10 seconds for the storage array to detect and register the replacement ESM canister.

Remove one of the ESM canisters in the affected tray and insert a replacement ESM. Then, go to step 3.

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.

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_HARDWARE_MISMATCH
The ESM cards
in a tray do not match. Alert Value: {0}
RunAsDefault
CommentMachine generated entity

Source Code:

<UnitMonitor ID="NetAppSANtricity.FailureID_0104_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_HARDWARE_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.StateIdE04836927443E522FF5AA345D1B65E81" MonitorTypeStateID="NoIssue" HealthState="Success"/>

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

  </OperationalStates>

  <Configuration>

    <FailureID>104</FailureID>

    <IntervalSeconds>361</IntervalSeconds>

    <TimeoutSeconds>300</TimeoutSeconds>

    <Trace>0</Trace>

  </Configuration>

</UnitMonitor>