Collecting and processing data from HP-UX systems

For information about managing HP-UX partition performance, see: 

Data collection considerations for HP hardware partitions

The Perform collector gathers data to provide the overall configuration of the partitioned server. Note the following data collection considerations for this environment:

  • You should run the Perform collector on any partition that is running the HP-UX operating system, so that Analyze can assemble complete picture of the server and all of the partitions on it. Unlike the other partition platforms (Oracle Solaris and AIX) where an external node controls the server, the server can be controlled and queried locally.
  • The collection of Physical Partition Configuration data is enabled by default. An option in the Collect.cfg file is available should you want to disable the collection of this metric group.
  • Data collection is supported on partitions running HP-UX (11.11, 11.23 and 11.31).

You can collect data from HP-UX partitioned systems as you would other computers. These methods are:

  • For ad-hoc data collection, use the best1collect command line executable.
  • For automated data collection, create a Manager run using the Gateway Server on either UNIX or Microsoft Windows.

Displaying data from HP hardware partitions

You can access performance data about the virtual systems by using any of the following components on the Windows Gateway Server.

Viewing System Configuration metrics for HP-UX partitions in Investigate

In the System Configuration metric group, some existing metrics have different descriptions in a HP-UX partitioned environment. The following table describes these metrics:

Metric

Description

Number Processors

The number of active physical processors on the partition.

Max Number Processors

The total number of physical processors available to the partition for nPar and vPar.

Hardware Serial Number

The partitioned server (physical system) identifier.

There are also a number of metrics that can specifically apply to HP-UX partitions. The following table describes each of these metrics:

Metric

Description

Partition Type

The specific partition implementation. For HP, the possible values are nPar, vPar, nPar/vPar. Other values are reported for other vendors partitioning systems or standalone servers, such as DSD (Oracle), LPAR, DLPAR, SPLPAR (AIX).

Logical system name

The name of the partition, which can be different from the System Name.

Viewing Physical Partition Configuration metrics in Investigate from a HP-UX partition

In the Physical Partition Configuration metric group, some existing metrics have different descriptions in a HP-UX partitioned environment. The following table describes these metrics:

Metric

Description

Logical System Name

The unique identifier for the partition.

Physical System Name

The unique identifier for the server (host). This name matches the Hardware Serial Number in the system configuration within the partition.

Physical System Model Name

The model of the server.

Total Processors

The number of physical processors available to the partition.

Active Processors

The number of physical processors currently used by the partition (for nPar) or the number of physical processors that are assigned to the partition (for a vPar). In a vPar, the processors assigned to the vPar cannot be turned offline.

Total Memory

The size of the memory allocated to the partition.

There are also a number of metrics in the Physical Partition Configuration metric group that support HP-UX partitions. The following table describes each of these metrics:

Metric

Description

Parent Name

The system complex name for a nPar. This field is blank for a vPar or a nPar/vPar combination, as the complex name is not available for vPars.

Partition Type

The type of partition implemented. Possible values are nPar, vPar, or nPar/vPar.

Unassigned Processors

The number of physical processors that are not assigned to any partition.

Active Memory

The size of the memory currently used by the partition.

Unassigned Memory

The size of the memory that is not allocated to any partition.

Displaying HP partition CPU usage in Visualizer

To view HP partition data from Visualizer, complete the following steps:

  1. Click Database > Select and select the database into which you populated the HP partition data.
  2. Click Database > Detail and select the data for the graph. Ensure that you select HPNPAR from the Virtual Type drop-down list.
  3. From the Graphics menu, select HP-UX Partition > HP NPAR VPAR Partitions Hierarchy.


HP NPAR VPAR Partitions Hierarchy

Key Analyze report to review for HP-UX partitions

Based on the collected data, Analyze identifies each type of partition, correlates the data to establish the physical to logical system relationship, builds the partitioning model for Predict, creates the hierarchical report for partitioned systems, and generates the Visualizer input file. 

The Physical System report enables you to analyze data specific to HP-UX partitions.

Physical System report for HP-UX partitions

This report displays a two-tier hierarchy for HP-UX partitioned servers: the nPar, vPar and vPars running under an nPar. (For a vPar running on an nPar, the vPar name is prefixed with the nPar name.) 

Analyze Physical System report for HP-UX Partitions 

 

The following table describes each of the columns in the report:

Column

Description

Physical System

The name of the physical system (host).

Logical System

The name of the logical system for nPar and vPar. For a vPar running on an nPar, the vPar name is prefixed with the nPar name.

Partition Type

The type of partition implemented. Possible values are: nPar, vPar, or nPar/vPar.

Active Processors

The number of active processors for the partition. For the physical system, this field is the sum of all partitions.

Dedicated Processors

The number of dedicated physical processors for the partition.

CPU Model

The system vendor and model. Only reported for a physical system.

Memory

The size of total physical memory (for the physical system) or the size of allocated memory (for logical systems). Reported in Mbytes.

CPU Utilization

The percentage of CPU usage (out of 100) times number of active processors.

Was this page helpful? Yes No Submitting... Thank you

Comments