ESM Firmware Mismatch

What Caused the Problem?

A drive enclosure in the storage subsystem 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 (refer to the Recovery Steps below). 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 subsystem reports existing arrays and logical drives (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 don't remove an ESM canister in the affected drive enclosure 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 enclosure. The firmware on the ESMs in the affected drive enclosure have been synchronized.

As an additional verification, access the Storage Subsystem Profile and then select the Enclosure information. Scroll down until you find the affected drive enclosure 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 enclosure. 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 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.