HP P6000 Command View Suite 10.3 Release Notes (T5494-96584)

Controller inaccessible when adding a storage system
When one of the controllers that you want to add is inaccessible, the Event Log displays the
following message:
Unable to add the storage system to the monitored list: Storage System
Name: HSV340-9F60, Storage System WWN: 5001-4380-04C6-9F60 as connection
with one of the controllers could not be established or the controller
is down
This indicates that the storage system cannot be added for monitoring in HP P6000 Performance
Advisor.
Workaround: Follow the steps provided in the HP P6000 EVA Command View User Guide to
ensure that both the controllers are accessible. Then, retry adding the storage system for monitoring
in HP P6000 Performance Advisor by navigating to the P6000 Monitoring tab (Settings→HP P6000
Performance Advisor Instance→Configuration) in the Content pane and clicking Add.
Live chart not shown when one controller is down
When one controller is down or inaccessible, the live chart is not shown if you choose to view live
data samples aggregated across both the controllers.
State monitoring for data replication groups leads to multiple logging of the event
Enabling state monitoring for data replication groups in HP P6000 Performance Advisor leads to
multiple logging of the event that is generated for the first data replication group undergoing the
state change.
Workaround/Solution: Manually update the state data for a data replication group whenever
required. Select the storage system under the Monitoring tab and click Update Object Status in HP
P6000 Performance Advisor.
HP P6000 Performance Data Collector 10.3
Enhancements
Addition of new performance counters for Thin Provisioned Block Space Reclamation (SCSI
Command : UNMAP)
Workarounds and limitations
This section describes workarounds for HP P6000 Performance Data Collector 10.3.
HP P6000 Performance Data Collector drg command limitation
Deleting a DR group while running the HP Performance Data Collector drg –cont 2 command
can produce an unexpected result in the command output. More DR groups can be removed from
the command output that the DR group that you deleted.
For example, consider a system that has three DR groups (DR1, DR2, and DR3). If DR3 is deleted
while drg is running, DR2 or DR1 entries can also be deleted from the command output.
Domain names not supported in hostname parameter of fnh command
If the host name you specify in the fnh command is a full domain name (for example,
nt12345.asiapacific.xyzcompany.net
<mailto:[e-mail]>), the friendly names host file is not created.
Use localhost or the host name without the domain when running the fnh command. Examples
of supported entries follow:
evaperf fnh localhost hpadmin@localhost
evaperf fnh nt12345 [e-mail]
HP P6000 Performance Data Collector 10.3 19