HP StorageWorks P9000 Command View Advanced Edition Suite Software 7.1.1-01 Release Notes (TB581-96070, September 2011)

Using the Device Manager agent on the 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 behaviors might occur if creating or
deleting a copy pair from the GUI:
• Even after a copy pair is created, the copy type of the target volumes remains unpaired.
• Even after a copy pair is deleted, the copy type of the target volumes does not change.
To correctly display the copy type status, refresh the storage system.
Host name length of Device Manager agent host
The host name length of the Device Manager agent host must be 50 bytes or less.
When Device Manager manages VMware ESX 3.5 without using VMware vSphere
Management Assistant (vMA)
If Device Manager is managing multiple instances of VMware ESX 3.5 without using vMA, only one
virtual machine can be managed among any virtual machines whose configuration files have the same
name
4
and whose configuration file names
4
exceed 60 bytes. Use vMA to avoid this situation.
Example:
[Datastore1] vm1/vm1.vmx
4
The full path with the virtual machine working location.
Upgrading Device Manager in an environment where virtualization servers are managed
In an environment where Device Manager manages virtualization servers, after upgrading Device
Manager, make sure to refresh the information for all the managed virtualization servers.
If virtualization servers are managed in a system configuration where vMA monitors VMware vCenter,
reregister the vMA information into Device Manager to refresh the information for all the virtualization
servers connected to the monitored VMware vCenter.
Managing copy pairs on the Windows hosts with multiple NICs
When all of the following conditions are met on the hosts that manage copy pairs and are connected
to Replication Manager, use the Advanced Settings option in Windows Network Connections to adjust
the order in which NICs or IPv4 and IPv6 addresses are accessed.
• One Windows host manages copy pair P-VOL and another Windows host manages copy pair
S-VOL.
• The host that manages P-VOL has multiple NICs.
• The host that manages S-VOL has multiple NICs.
• The name of the host that manages S-VOL described in the configuration definition file in the host
that manages P-VOL.
• The name of the host that manages P-VOL described in the configuration definition file in the host
that manages S-VOL.
• The following IP addresses in 1 and 2 are not the same, or the IP addresses as noted in 3 and 4
are not the same:
1. The IP address of the host that manages P-VOL is resolved by the host itself.
2. The IP address that DNS resolves from the name of the host that manages P-VOL described
in the configuration definition file of the host that manages S-VOL.
34 Important considerations