HP P6000 Command View 10.0 Release Notes (T5494-96528, March 2012)

Table Of Contents
Setting the Network Time Protocol server time using array-based management
When setting the Network Time Protocol (NTP) server time using array-based management, the system
time is not updated immediately. The system time should update to match the NTP server within 10
minutes.
Not able to log in to HP Replication Solutions Manager server
If the Windows TEMP environment variable is not set correctly, you may not be able to log in to the
HP Replication Solutions Manager server. Ensure that the TEMP environment variable is pointing to
an existing folder and the folder is accessible.
Best practice for online migration
Before initiating the online migration operation, be sure to perform a full backup of the virtual disk.
Write cache policy not maintained when migrating a virtual disk
When migrating the Vraid type and/or disk group of a virtual disk using the Online virtual disk
migration feature, the write cache policy is set to write-back. If the virtual disk had write cache policy
set to write-through, the policy is changed to write-back.
Multi-home Agent IP does not change for SNMP traps for different VLANs
Server-based HP P6000 Command View can be installed on a multi-homed server where multiple IP
addresses are configured. The array can be accessed from any of the IP addresses of the server through
HP P6000 Command View. Consider the following when using HP P6000 Command View on a
multi-homed server:
If the network is not accessible through an IP address on the server, the array will remain actively
managed by HP P6000 Command View on that IP address. However, it may be necessary to use
an HP P6000 Command View instance on another IP address to take management of the array
away from the inaccessible HP P6000 Command View instance.
When SNMP traps are configured from HP P6000 Command View, the SNMP agent IP address
that generates the trap will be the same, regardless of the destination IP address to which the trap
is to be sent. The agent IP address will be the IP address from which the array is actively managed.
Online virtual disk migration limitation
HP P6000 Command View should not be restarted or management of the array transferred while a
migration is in progress. Doing so will cause HP P6000 Command View to abandon the migration
tasks, leaving behind temporary mirrorclones that must be deleted manually. This does not impact host
I/O directed at the original virtual disk.
Changing the management IP address of an iSCSI controller using the CLI
When the management IP address of the iSCSI controller is changed using the CLI, HP P6000 Command
View loses connection with the iSCSI controller, resulting in a Not Available status displayed in the
iSCSI controller GUI pages. To correct this, use the HP P6000 Command View GUI to delete the
existing iSCSI controller, and then add the new IP address using the Add iSCSI controller page.
Using an FCoE CNA-based server with MPX200 connectivity
When managing an EVA using an FCoE Converged Network Adapter-based server and through
MPX200 connectivity, unpresenting the last FCoE LUN from the MPX200 iSCSI controller may cause
HP P6000 Command View to lose communication with the array. To resolve this issue, use the lunmask
add wizard in the MPX200 CLI to present LUN 0 from each array target WWN to each MPX200
FCoE port and to each management server FCoE-CNA port. To gather the necessary information, use
the show fc, show targets, and show initiators MPX200 CLI commands. Then, use the
lunmask add wizard.
HP P6000 Command View 11