HP P9000 Command View Advanced Edition Software Update 7.1.0-01 Release Notes (TB581-96073, June 2011)

Managing more than 128,000 volumes by using Device Manager
When using Device Manager to manage more than 128,000 volumes, specify a narrowing condition
for a storage system or a host when a user creates a logical group or searches volumes.
• If narrowing conditions by host parameter: Specify the narrowing condition to reduce the number
of volumes allocated to each host to less than 128,000.
• If narrowing conditions by storage system parameter: Specify the narrowing condition to reduce
the number of volumes for each storage system to less than 128,000.
KAIC90139-E error
If this error occurs, take action according to the message and ensure that the Device Manager server
is running properly.
If this is due to a temporary network error during command execution, check the configuration
information again later. The Device Manager server might have processed command execution requests.
SMI-S Indication function
In interop namespace, only the query described in SMI-S1.3 can be set for the Query property of
CIM_IndicationFilter.
Using Device Manager agent on VMware ESX Server 4.x or VMware ESXi Server 4.x
guest operating system
When using the Device Manager agent to manage copy pairs on the VMware ESX Server 4.x or
VMware ESXi Server 4.x guest operating system, the following might occur:
• After creating a copy pair from the GUI, the copy type of the target volumes remains unpaired.
• After deleting a copy pair from the GUI, the copy type of the target volumes does not change.
To display the correct copy type status, refresh the storage system.
Length of Device Manager agent host name
The length of the Device Manager agent host name must not exceed 50 bytes.
Device Manager manages VMware ESX 3.5 without using VMware vSphere
Management Assistant (vMA)
If Device Manager manages multiple instances of VMware ESX 3.5 without using vMA, only one
virtual machine can be managed among virtual machines whose configuration files have the same
name and that name exceeds 60 bytes (for example, the full path with the virtual machine working
location: [Datastore1] vm1/vm1.vmx).
Upgrading Device Manager in environment with virtualization servers
In an environment where Device Manager manages virtualization servers, after upgrading Device
Manager, be sure to refresh the information for all managed virtualization servers.
If the virtualization servers are managed in a system configuration where VMware vMA monitors
VMware vCenter, re-register the vMA information with Device Manager to refresh the information for
all virtualization servers connected to the VMware vCenter.
20 Important considerations