HP StorageWorks HSG80 Enterprise/Modular Storage RAID Array Fibre Channel Solution Software V8.7A for Novell NetWare Release Notes

Patching ACS
7Release Notes – HSG80 Enterprise/Modular Storage RAID Array Fibre Channel Solution
Software Version 8.7A for Novell NetWare
If the ACS version is not Version 8.7 or a subsequently patched version of ACS
Version 8.7, contact your support provider for instructions on how to obtain the
updated version.
If the ACS version is Version 8.7P, you need additional layered application software
beyond this Solution Software Kit to take advantage of the added functionality of
these versions. See "Layered Software Applications", page 19, for additional
information on compatible layered application software.
ACS Version 8.7 is fully compatible with Version 8.7A Solution Software. In addition,
Version 8.7A Solution Software is backward compatible with ACS Version 8.6, which
benefits the upgrade process across your SAN.
Patching ACS
Each ACS patch builds on the current version of ACS and all previously installed
patches. ACS patches must be installed in order, from lowest to highest, when multiple
patches are installed. ACS patches are available for download from the following
StorageWorks website:
http://h18000.www1.hp.com/products/storageworks/softwaredrivers/acs/index.html
ACS patch downloads come packaged with the instructions and scripts needed to
apply the patch. See the HSG80 Array Controller ACS Version 8.7 Maintenance and
Service Guide for further information on patching ACS.
For multi-bus configurations, use the following procedure in addition to those
provided with the ACS patch download:
1. Apply ACS patches to both controllers.
2. Move all units to
OTHER_CONTROLLER, one unit at a time, using Secure Path
software. Moving the units in this manner is not a requirement, but it lets the
controller do less work than when moving all the units at once.
3. Reboot
THIS_CONTROLLER during a slow time (when controllers are running at
more than 50% idle). The patch takes effect once the controller is rebooted.
4. Repeat these steps for
OTHER_CONTROLLER by moving all units to
THIS_CONTROLLER and rebooting OTHER_CONTROLLER during a slow time.