Data seems to be incorrect or lost – HP Matrix Operating Environment Software User Manual
Page 162
Data seems to be incorrect or lost
VM guest resource utilization appears to exceed the resource utilization of its VM host
When
viewing historical resource utilization data in a profile viewer, it can appear that the utilization
of a resource by a given VM guest exceeds the utilization of that resource by its VM host at a
given instance of time. (For example, you might see the I/O usage occasionally exceed the VM
host's high-water mark value (the dashed blue line in a profile viewer graph).
In reality, it should never be possible for a VM guest's resource utilization to exceed that of its
host, since the utilization shown for a VM host is the aggregation of a resource's utilization for
all VM guests running on that host. Yet this does occur on rare occasions due to differences in
how the data was collected, interpolated, and averaged into the 5–minute intervals that Capacity
Advisor stores in its database.
Such anomalies become insignificant when the data is averaged over sample intervals greater
than 5 minutes.
Note that this situation typically occurs only when a single guest is running on the host and is
creating a very large load on the host.
Socket count is missing or seems incomplete in population report
Socket information is not
always available due to limitations in data collection from some platforms or when leveraging
data collection techniques that do not include socket count in their collection. There is no remedy
in these situations.
Workload performance seems inaccurate
Using benchmarks for data normalization is new with
the 6.0 release. This change affects workloads defined with static profiles in previous releases
because they use clock speed to determine performance. Suggested action: Such workloads that
are still used for planning should be redefined or edited in Capacity Advisor 6.0 to improve the
accuracy of the performance measure. See
“Creating a workload” (page 97)
and
.
CPU utilization seems high on managed nodes running Microsoft Windows 2003 Server
Agentless
data collection might not be accurate on hyper-threaded systems. Suggested action: Update
Microsoft Windows 2003 Server so that it correctly reports the number of physical
hyperthreading-enabled processors or the number of physical multi-core processors. See
for this issue.
Socket and core count seem off on Microsoft Windows 2003 and HP-UX 11 v2 (IA and PA) systems
Windows 2003 and HP-UX 11 v2 (IA and PA platforms) operating systems may not correctly
report the number of processor sockets in a multicore/hyperthreading environment. Suggested
action: The following patches are required to correct this issue.
•
For Windows 2003, apply the KB932370 patch. For more information, see
.
•
For HP-UX 11 v2, apply the PHKL_37803 patch. You can download this patch from
After downloading, execute the command
sh PHKL_37803
, and install the depot file that is generated.
No patch is necessary for Windows 2008 or HP-UX 11 v3. This information does not apply to
HP-UX 11 v1.
Data seems to have disappeared
The profileID that Capacity Advisor uses to store whole-OS
performance data (profiles) is based on a system's network name, as currently discovered in HP
SIM (as seen in the System Page for the managed node).* If a system is later re-identified, but
with a different network name, any data collected under the old name will no longer be associated
with the managed system under its new network name. The data may still exist in the database,
but because it is no longer identified with the managed system from which it was collected, it
cannot be viewed or used for capacity planning.
The following are some examples of
•
An VMware ESX VM guest is initially discovered by HP SIM horizontally only, with no IP
address or host name (only the ESX host is explicitly discovered in HP SIM, and VMware
Tools are not installed/running on the guest). Later, the guest is discovered with a valid host
name/IP address (that is, VMware Tools are subsequently installed on the guest). (Horizontal
162
Troubleshooting in Capacity Advisor