HP Capacity Advisor 7.2 User Guide

Capacity Advisor 6.x or later to improve the accuracy of the performance measure. See “Creating
a workload” (page 80) and “Editing a workload” (page 81).
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 Microsoft
Support for this issue.
Socket and core count seem off on Microsoft Windows Server 2003 and
HP-UX 11 v2 (IA and PA) systems
Windows Server 2003 and HP-UX 11i v2 (11.23) (IA and PA platforms) might not correctly report
the number of processor sockets in a multi-core/hyperthreading environment.
The following patches are required to fix this issue:
• For Windows Server 2003, apply the KB932370 patch. For more information, see http://
support.microsoft.com/kb/932370/.
• For HP-UX 11i v2, apply the PHKL_37803 patch. Go to https://h20566.www2.hp.com/
portal/site/hpsc/public/and log in to the HP Support Center using your HP Passport. Select
Patch management from Download options, then enter PHKL_37803 in the search box. After
downloading, execute the command sh PHKL_37803, and install the depot file that is
generated.
You must have an active software update support agreement to access patch management.
No patch is necessary for Windows Server 2008 or HP-UX 11 v3.
HP-UX 11 v1 is no longer supported.
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 Systems Insight Manager (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 how this can occur:
• An VMware ESX VM guest is initially discovered by Systems Insight Manager horizontally
only, with no IP address or host name (only the ESX host is explicitly discovered in Systems
Insight Manager, 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 discovery can also find Microsoft Hyper-V hosts with a
similar effect if the guests are later rediscovered with valid host name or IP address.)
• If a system is multi-homed and its multiple IP addresses or network names are discovered in
Systems Insight Manager, only one "system node" is recorded in HP SIM to represent that
server (the Primary IP Address). This node will contain the list of IP addresses and network
names for that system. HP SIM randomly selects which IP address and network name pair
becomes the default Primary IP Address used for the node's short name. If you edit the “System
Properties” and change the "Primary IP Address", any data associated with the previous
workload name reference will be “lost”.
164 Troubleshooting in Capacity Advisor