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

Table Of Contents
HP P6000 Performance Data Collector 10.0
This section describes workarounds for HP P6000 Performance Data Collector 10.0.
Workarounds and limitations
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:xyz@asiapacific.xyzcompany.net>),
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 xyz@asiapacific.xyzcompany.net
Windows Performance Monitor limitations
When using Windows Performance Monitor to view HP P6000 Performance Data Collector performance
data on a management server running Windows 2003 Enterprise Edition, Windows Performance
Monitor may hang when the number of counters exceeds 900 (for example, a virtual disk object that
exceeds 100 instances, with 9 counters per instance).
pd and hps command limitation
The incorrect enclosure and bay IDs are displayed in the evaperf pd command when running XCS
6.000.
HSV200 controllers running XCS 6.000 report the enclosure and bay ID as "-" on one of the
controllers after a reboot.
evaperf nall command fails to execute
The evaperf nall command fails to execute in continuous mode on a Windows 2008 server in
both local mode and remote mode. Use the evaperf all command instead.
hist command limitation
When used with the object type state_diskgroup, the hist command does not display data for
the EVA4400 and EVA6400/8400.
HP P6000 Performance Data Collector 10.0 23