Important Notes; Installation Instructions - HP StorageWorks 2000fc - G2 Modular Smart Array Firmware Release Notes

• Fixed some issues in the Japanese version of the GUI.
• Fixed an issue where the SMU page was not updating after creating volumes (GUI).
• Fixed an issue where the user inactivity timeout was not working properly (GUI).

Important notes

WARNING!
Do not power cycle or restart during the firmware update. This can result in loss of capabilities for
the unit.
CAUTION:
Updating Array controller firmware with only one Array controller requires the MSA2000 system to
be offline. In a single-controller system, updating firmware causes all disks to be temporarily
inaccessible. Stop I/O to vdisks before updating the firmware.
IMPORTANT:
Reverting the firmware version back to M100R18-05 from the M110 code branch requires HP technical
support.
NOTE:
Smart Components are available for this firmware. These are located on the Windows and Linux
software deliverables page for this storage product.
It takes approximately 10 minutes for the firmware to load and for the automatic restart to complete
with the first controller. With a second controller, the full process time is approximately 25 minutes.
All firmware flash progress messages are logged to \CPQSYSTEM\Log\cpqsetup.log on
the system drive in Windows and /var/cpq/Component.log in Linux.
The Smart Component manages the FTP & Partner Firmware Update (PFU) enable / disable settings.
Updating array controller firmware may result in receiving new event messages that are not de-
scribed in earlier versions of documentation. For comprehensive event message documentation,
see the most current version of the HP StorageWorks 2000 G2 Modular Smart Array Reference
Guide .

Installation instructions

When planning for a firmware upgrade, select and schedule an appropriate time to perform an online
upgrade. For redundant controller systems, to ensure the success of an online upgrade, selecting the
appropriate time is essential. Because the online firmware upgrade is performed while host I/Os are
being serviced, the I/O load can impact the upgrade process. Selecting a period of low I/O activity
will ensure the upgrade completes as quickly as possible, and will avoid disruptions to hosts and
applications due to timeouts.
6