Installation guide

38 Book Title without trademarks, or an abbreviated book title March 2008
Firmware Upgrade can Lock Volumes While Appearing Completed and
Array Showing Optimal State.
Bug 6595884 –A firmware upgrade/baseline installation can lock volumes longer
than the process indicates. The array can report the upgrade completed and show an
optimal state but the process can still lock the volumes.
Workaround –Wait an extra five to ten minutes and try again.
Primary Volume Create Commands do not Display
Bug 6608890 –The array is limited in commands it can process simultaneously and
CAM is not doing validation and queuing of (primarily volume create) commands.
Workaround –Check scripts for volume modification status before you issue new
volume modification commands.
Primary Volume in a Replication Set Cannot Exceed the Size of the
Secondary Volume
Bug 6596281 If a data replication set is created between two volumes with the
primary volume having a size less than the secondary volume, the primary volume
can be expanded till it reaches the size of the secondary volume.
Replication Status May be Listed Incorrectly when the Primary Volume
Fails
Bug 6561709 –When the primary volume in a replication set fails, the management
software may incorrectly list the volume as replicating.
Service Advisor Does Not Verify Disk is Ready to be Removed
Bug 6501029 –When the management software lists a disk as failed and the Service
Advisor procedure for replacing drives is followed, the step to verify that the disk is
ready to remove may not list the failed disk.
Workaround –Use an alternative menu option, Array Troubleshooting and Recovery,
to view the status of the disk