beautypg.com

No data collected for a managed node, Data timestamp appears to be incorrect, Dynamic memory in hp integrity virtual machines – HP Matrix Operating Environment Software User Manual

Page 67: Producing graphs and reports, Using the profile viewer

background image

No data collected for a managed node

If you do not obtain data on systems from which you expect to collect data, it is possible that the
system has not been licensed for use with Capacity Advisor, either through Matrix Operating
Environment or through HP Capacity Advisor Consolidation software.

Data timestamp appears to be incorrect

For best accuracy in providing simulation solutions and historic reporting of actual system resource
use, it is assumed that the time clocks of managed nodes are synchronized with the time clock of
the central management server. If, on gathering or collecting data, the date stamp on your data
is not current, the time or time zone on a managed node may be set incorrectly in relation to the
CMS.

Dynamic memory in HP Integrity virtual machines

A dynamic memory feature is available in HP Integrity virtual machines. This allows the memory
allocated to each virtual machine to be changed without rebooting the virtual machine. Capacity
Advisor is aware of this feature and records both the memory allocated to each virtual machine,
as well as how much of this memory is in use for each five-minute interval. Both of these values are
correct when the virtual machines are using the dynamic memory feature.

When a virtual machine is running HP-UX 11.23, most built-in commands such as top and sar
will not be aware of the dynamic memory feature and can show memory sizes that are different
from what is recorded by Capacity Advisor. For example, if a virtual machine is initially booted
with 16 GB of memory, and is then re-sized to 4 GB, the built-in commands will not know about
the change and will show 16 GB for physical RAM. Capacity Advisor, however, will show that
the available memory for the VM is 4 GB. Also, when a virtual machine is sized less than its
maximum size, some built-in commands will show the kernel using more memory than it is actually
using.

Producing graphs and reports

Capacity Advisor can generate both graphical and tabular data for presentation in either a report
format or within an adjustable profile viewer.

Using the Profile Viewer

A profile viewer provides a quick summary of historical resource utilization, presenting data
graphically as well as in tabular summaries. See also “Profile Viewer Screen” in Capacity Advisor
Help
for specific descriptions of the screen functions.

A profile viewer can be accessed from the system meters on the Visualization tab, the Optimize
menu, or from the meters or menu selections on the Edit Scenario tabs in Capacity Advisor.

NOTE:

A Matrix OE Visualization memory meter indicates the total memory in use — including

memory used by the kernel and the disk buffer cache.

In Capacity Advisor Profile Viewer, however, only the total memory needed by applications, rather
than what is used, is graphed (both Linux and HP-UX will fill all of unused memory with a disk
buffer cache). The memory used by the kernel and the disk buffer cache is excluded. The idea here
is that when simulating capacity for planning purposes, where you stack multiple workloads on a
single system, you would not want to include the kernel and disk buffer cache more than once in
your memory calculation.

A profile viewer opened from the Visualization tab generally displays the resource utilization data
collected from a real node in your environment.

However, for non-OS node types such as an enclosure, a complex, or a vpar monitor, which do
not have an operating system (OS) or hypervisor from which to collect actual resource utilization

Producing graphs and reports

67