8100 Updating Product Software Guide (XCS 6.250) (5697-1716, February 2012)

Invalid firmware image file (Status code 21006)

If the XCS image file is the wrong one, an Operation failed message is displayed

(Figure 26 (page 59)). Click OK to return to the Initialized Storage System Properties window.

Figure 26 Invalid firmware image file (Status code 21006)

EMU communication events following an XCS 6.200 upgrade

Symptom

If you have recently upgraded from XCS 6.200 on the HP x000 or x100 Enterprise Virtual Arrays,

you may see Drive Enclosure Environmental Monitoring Unit (EMU) communication events logged

in the controller event log for multiple enclosures. The events, typically seen within fifteen minutes

after upgrading, are logged as follows:

063ec513: The HSV210 controller has detected an enclosure on the Fibre

Channel but is unable to communicate with the Drive Enclosure EMU on

the enclosure address bus, or the Drive Enclosure EMU is reporting an

invalid enclosure number.

These events may also be seen against multiple enclosures after insertion or removal of a physical

disk drive, fibre channel cable or I/O module, or when other Fibre Channel loop events occur that

can cause a loop reset seen as a controller restart or resynchronization of one or both controllers.

These events have very short duration and have no impact on host I/O.

Resolution

When these messages are observed, it is not necessary or recommended to replace the EMUs or

any other part. To avoid this issue, apply one of the following workarounds:

Workaround 1 — Resynchronize the controllers.

NOTE: Depending on the configuration of the array, the time to perform the resynchronization

of the array controllers may exceed 60 seconds. When performing this workaround online, to

ensure resynchronization time of less than 60 seconds, the total allocated capacity should be 10

TB or less, and the configuration cannot contain DR groups. To assist in this process, consider the

recommendations in “Evaluating your configuration” (page 21).

TIP: If you are resynchronizing the controllers offline, resynchronization time limits do not apply.

Workaround 2 — Restart the master controller.

Workaround 3 — Perform the following procedure:

If the problem was observed before the upgrade from XCS 6.200, verify that a hardware issue is

not causing the problem by confirming that the EMUs, enclosure address bus cables, terminators,

and junction boxes are all properly installed and seated. If all hardware is in good working order

and the problem persists, the following procedure has been found effective in resolving the issue:

EMU communication events following an XCS 6.200 upgrade 59