HP XP P9000 Command View Advanced Edition Suite Software 7.5.0-02 Release Notes (TB581-96351, July 2013)

The Device Manager agent settings for the command device were specified incorrectly.1.
2. Performance information was retrieved.
3. Performance information of the same class as item 2 was retrieved again.
• The Smart pool used capacity value next to the pool cylinder, which was displayed when a logical
group was selected in the Mobility tab, was incorrect.
• It took a long time to refresh P9500 storage systems from Device Manager or Replication Manager,
to delete Smart volumes from Device Manager, and to delete a Smart pool from the Device
Manager GUI.
• When THP monitoring was executed using manual mode or custom mode for P9500, the "last
monitoring start time" and "last monitoring end time" that include UTC time offset were displayed
incorrectly in the Device Manager GUI.
• When the CLI GetStorageArray (Subtarget=replicationInfo) command was executed,
the split time of snapshot pairs that include UTC time zone offset was displayed incorrectly in the
Device Manager CLI.
• When you logged in to the Device Manager, an authentication error KAPM01095-E was incorrectly
generated to a system log or an event log.
• In the Advanced Options on the Allocate Volumes dialog box or the Allocate Like Volumes dialog
box, appropriate items might not be displayed for the drive type, the drive speed (RPM), and the
RAID level.
The Show Plan button might not be active, so you could not allocate any volumes.
• If you selected a volume that belonged to host group 0 for a port on which LUN security was
enabled, and then opened the Allocate Like Volumes dialog box, the KAIC15635-E message
was generated, and you could not execute the Allocate Like Volumes operation.
• The KAIC16009-E message was generated if you selected the Filter button in a Health Check
Report, and none of the following filter conditions were displayed in the Filter dialog box:
◦ Cache Utilization
◦ CLPR Cache Utilization
◦ MP Utilization by MPB
◦ MP Utilization by MPU
◦ CHP Utilization by CHA
◦ DKP Utilization by DKA
◦ Processor Utilization
◦ Affected Logical Groups
• Host Data Collector (for Windows) might not have started.
• In a new installation of Host Data Collector, if the installation path contained special characters,
the installation completed with no error notification, but Host Data Collector did not work properly.
• If Host Data Collector (for Windows) was installed in a path that contained consecutive spaces,
Host Data Collector could not be uninstalled.
• If the environment variable tmp in Windows contained special characters, the installation of Host
Data Collector (for Windows) was not successful.
• After an upgrade installation, all Host Data Collector properties were set to their default values.
• Incorrect files were created in the /tmp directory on a Solaris host when the host was discovered
or refreshed by Host Data Collector.
Fixes 7