HP StorageWorks 3000/5000 Enterprise Virtual Array release notes (VCS 3.110) (5697-8109, March 2009)

• Red Hat Enterprise Linux 2.1
• IBM AIX 5.1
• OpenVMS 8.2 (IA64)
• Novell NetWare 5.1, 6.0
NOTE:
The previous edition of these release notes (5697–6378, August 2007) incorrectly listed HP-UX 11.00
as no longer being supported. HP-UX 11.00 is still supported with VCS 3.110.
Fixes
The following issues have been resolved in VCS 3.110:
General issues
• Addressed an issue where a single disk drive failure could lead to RAID1 inoperative state.
• The fault detection logic on the backend that prevents unnecessary disk and port failures is en-
hanced.
• A power cycle of a device Fibre Channel loop switch may, in some instances, lead to a failure of
the connected port, leading to a Single Port on Fibre (SPOF) condition.
• During regeneration of a failed disk drive, error monitoring thresholds are suspended to remove
the possibility of soft errors leading to a dual disk failure within a single redundant storage set
(RSS).
• Addressed an issue which may occur when background allocation of virtual disk space is in pro-
gress and a write is received for space which is not yet mapped leads to the inability to completely
delete a LUN.
• Corrected an issue where a high number of writes on a Data Replication tunnel may lead to
missing data within the tunnel which results in a resource allocation issue.
• Detailed information has been added to Controller Event logs for loop recovery events (Event
0x063b0008) to assist support personnel.
• Previously added support for the 30-10022-01 RoHS compliant loop switch has been removed
due to an issue caused by modified loop timing.
• Detailed information indicating when and how array initialization occurs has been added to the
Controller Event Log.
• A progress indicator has been added to allow the display of device ungrouping operations within
HP Command View EVA.
• Within an HP Continuous Access EVA environment fault isolation between source and the destin-
ation EVAs has been enhanced.
• An issue which could lead to data inconsistency between source and destination arrays has been
addressed.
• An issue which lead to stalling of reconstruction or merging operations of VRAID5 disk groups
has been addressed.
• A disk drive, in some instances, may simultaneously induce a persistent condition on both the Fibre
Channel loops, blocking the communication with all the other disk drives sharing the same dual
Fibre Channel loops. This issue is addressed.
• An issue which could prevent leveling and migration process from completing has been addressed.
4