HP StorageWorks 3000/5000 Enterprise Virtual Array release notes (VCS 4.100) (5697-7028, November 2007)

• An indicator to display the progress of disk ungrouping op erations.

• Online upgrade support from VCS 4 .00x to VCS 4.100

• Windows Ser ver 2008 host mode

• Queue depth resolution support in IBM AIX host mode

Additional operating system support

Support for the following operating systems has been ad ded since the release of VCS 4.007:

• Linux Red Hat A

dvanced Server 5.0

• Windows Server 2003 SP2 (x86 and IA32)

Operating systems no longer suppor ted

ThefollowingoperatingsystemisnolongersupportedinVCS4.100:

• SP4 of N ovell N etWare 6.5

Fixes

The following ﬁxes have been implemented in VCS 4.100.

Controller termination

The following issues which caused controller termination or restarts have been resolved:

• Conﬂicts between write buffer and allocation routine

• Access to unallocated policy memor y

• Management commands from multiple initiators

• Invalid cache node deallocation

• Recursive termination due to allocated cache page

• ExcessiveI/Oontheproxycontroller

• Large transfer size read requests to proxy controller

HP Contin

uous Access EVA

• After a site failover, the LUN presentation is restored to avoid duplicate naming.

• Dealloc

ated DR log space is properly returned to disk group.

• DR group state change completes if there is a tunnel closure.

• Target host conne ction states are properly reported to HP Comma nd EVA.

• Access t

o virtual disks by HP OpenVMS hosts is retained after a site failover.

• Prevent erroneous transition of the DR log disk to the proxy controller.

• Added event informatio n to monitor and diagnose H P Continuous Access EVA replication

tunnel

activity.

• Allow the failover mechanism to interrupt the group online process.

General

• Management commands continue to be processed if there is an improper command term ination.

• Metadata updates are retried to prevent inadvertently declaring drive failures.

• Mode pages are properly populated after a controller reset.

• Detailed information indicating when and how array initializa tion occurs has been add ed to the

Controller Event Log.

• Inserted drives are discovered within the device discover y period.