Job Management Partner 1/Performance Management - Agent Option for Platform Description, User's Guide and Reference

[Contents][Glossary][Index][Back][Next]

1.3.4 Operation in virtualized systems

This subsection explains how to use PFM - Agent for Platform to monitor performance in virtualized systems.

Organization of this subsection
(1) Objectives of operation in virtualized systems
(2) Monitoring resources in virtualized systems
(3) Examples of using of PFM - Agent for Platform in a virtualized system
(4) Precautions regarding usage of PFM - Agent for Platform in virtualized systems
(5) Virtualized system functionality and collected performance data
(6) Data collected for each virtualized system
(7) Identifying processes that have the same name in a virtualized system

(1) Objectives of operation in virtualized systems

The following explains the advantages of virtualized systems, and the objectives in running PFM - Agent for Platform in a virtualized system.

(a) Advantages of virtualized systems

Virtualized systems are attracting attention as a technology that makes the most of excess system resources. For example, with the current one-server, one-application paradigm, most servers consistently have excess resources. Specifically, except for times of server job congestion, usually only 5% to 7% of resources are used. Virtualized systems are a way to solve this issue.

Virtualized systems also have the following advantages:

(b) Objectives of performance monitoring

As discussed above, the benefits of a virtualized system are greatest when system resources are used in the proper amounts. Virtualized systems cannot be used effectively if system resources are overconsumed, or at the other extreme, hardly used at all.

In situations like these, the status of resource consumption can be monitored to determine whether the current system is set up effectively.

At a basic level, PFM - Agent for Platform is designed to collect information about a single physical operating system. However, it can be used creatively to monitor performance information that depends on virtualized systems.

The main objectives of using PFM - Agent for Platform to monitor virtualized system performance are as follows:

In virtualized systems, specific bottlenecks might adversely affect performance of the entire virtualized system. The following may cause such bottlenecks:

The following explains methods for using PFM - Agent for Platform to monitor the performance of virtualized systems. Note that the thresholds shown here for performance monitoring are just reference values. Use the appropriate values based on the system configuration and usage.

(2) Monitoring resources in virtualized systems

(a) Overview

The following are the most important system resources to be monitored for performance:

In a virtualized system, some performance data for the above resources might not be collected or might become meaningless when changed dynamically. Performance changes for each OS, or by each virtualized system.

(b) Installing PFM - Agent for Platform in a virtualized system

In a virtualized system, each type of resource is basically managed by virtualized functionality (software or hardware), and configured by being allocated to different logical partitions. The managed resources include processors, memory, disks, and networks.

These resources can be obtained as performance data on the logical partition on which PFM - Agent for Platform is installed.

Some virtualized systems distinguish between guest OSs and host OSs, as is the case with VMWare, Virtage, and other software-based virtualizations. The host OS manages the guest OS, and the guest OS runs on the host OS. In such cases, PFM - Agent for Platform is installed on the guest OS to monitor performance.

PFM - Agent for Platform collects performance data on the installed logical partition, or guest OS.

Precautionary note
Because the host OS for VMWare is a special OS for managing virtualized functionality, operation of applications is not guaranteed. Since Virtage creates an off-disk management area called an SVP (Service Processor) frame, data collected by PFM - Agent for Platform cannot be saved as a database in this management area.

(c) Setting up PFM - Agent for Platform in a virtualized system

The procedures for collecting information for an installed instance of PFM - Agent for Platform are the same for virtualized systems. The existing settings can be used as is.

When a virtual machine is set up using a virtualized system, and PFM - Agent for Platform is installed on the machine, PFM - Agent for Platform collects performance data about the virtual machine.

(3) Examples of using of PFM - Agent for Platform in a virtualized system

The following gives simple examples of usage in a virtualized system.

(a) Determining whether to change virtualized system settings

If there are extra physical resources despite the consumption of a significant amount of resources on a specific guest OS or logical partition, we recommend that you change the virtualized system settings.

PFM - Agent for Platform can be used as a tool to determine these kinds of situations.

The following graph shows a case in which the allocation of processor resources is not sufficient.

Figure 1-6 Case in which processor resource allocation is not sufficient (during processor usage monitoring)

[Figure]

Because the processor usage for logical partition A is 100%, the allocation ratio is being switched. However, the processor usage for logical partition A does not decrease, while the processor for logical partition B is not fully used. In cases like this, change the allocation ratio settings.

The following graph shows a case in which the allocation of processor resources is sufficient.

Figure 1-7 Case in which processor resource allocation is sufficient (during processor usage monitoring)

[Figure]

The processor resource ratio is being switched while there are many processes in the queue for logical partition A. As a result, the number of processes in the queue for logical partition A is decreasing.

(b) Determining whether additional physical resources are needed

If physical resources always seem to be heavily loaded, consider adding another physical resource.

Note, however, that even when a single guest OS or logical partition is heavily loaded in a virtualized system, the system-wide load might seem light. Therefore, check whether all guest OSs or all logical partitions are heavily loaded.

When using PFM - Agent for Platform to check the load status in a virtualized system, you might require a different perspective from the one you use for an ordinary environment.

A virtualized system contains resources that can be changed dynamically, such as processors and memory. Therefore, when monitoring processor and memory usage, also monitor the items not easily affected by dynamic changes in resources, such as the current queue length and paging frequency.

The following graph gives an example of processor resources.

Figure 1-8 Case in which additional processor resources are recommended (during processor usage monitoring)

[Figure]

In the figure example, the allocation ratio is being switched due to the heavy load on processor usage for logical partition B, but usage is high for both logical partitions A and B. In this kind of case, physical resources are insufficient.

(4) Precautions regarding usage of PFM - Agent for Platform in virtualized systems

The performance data collected by PFM - Agent for Platform in a virtualized system is specific to each virtual machine. Therefore, install PFM - Agent for Platform on each virtual machine.

Performance data about each virtual machine cannot be collected from the overall virtualized system, or from the management machine.

The following are precautions regarding the collection of information for each resource.

(a) Precautions regarding collection of processor information

The processor usage collected in a virtualized system might not yield the intended values. This is because the virtualized system divides up processor resources and dynamically allocates them to other logical partitions. For example, if significant amounts of processor resources are being used in a specific logical partition due to a heavy load, only limited processor resources might be available for other logical partitions.

Figure 1-9 Case in which collected values differ due to dynamic resource changes

[Figure]

Note that if an application on a given logical partition is using a physical processor, jobs on other logical partitions might be forced to wait due to the operation. In this case, processor usage cannot be accurately ascertained.

(b) Precautions regarding collection of memory information

As with processors, information about memory usage in a virtualized system may also differ from the system-wide ratio, due to dynamic resource changes.

For example, when 256 MB of memory area is allocated, and only 64 MB of it is used, PFM - Agent for Platform displays a value of 25% for the memory usage allocation. In this case, when the memory allocation area is dynamically changed from 256 MB to 128 MB, PFM - Agent for Platform displays 50% for the memory usage. Keep in mind that an unexpected warning might occur when a memory resource is specified for an alarm.

Figure 1-10 Case in which the memory resource is specified for an alarm

[Figure]

(c) Precautions regarding collection of disk information

As with processor resources, sometimes disk busy rates cannot be accurately ascertained. For example, on a virtualized system, some jobs may be using physical disk resources while others are waiting due to operation.

(d) Precautions regarding collection of network information

PFM - Agent for Platform measures only incoming and outgoing packets for network information. Therefore, operation in a virtualized system is the same as normal usage, but in some cases virtual network information is displayed for network information. This is not an issue, because PFM - Agent for Platform collects network information recognized by the OS running on the virtual machine.

(e) Precautions regarding collection of process information

Process-related performance data consists of items that show the process count and items that show the amount of resources used by processes. In both cases, since data on the logical partition is obtained for virtualized systems, this process information does not reflect the entire virtualized system.

PFM - Agent for Platform collects both the number of processes on each logical partition, and the amount of resources being used by the processes.

(5) Virtualized system functionality and collected performance data

In virtualized systems, the setup of provided resources differs depending on how the system is implemented. Also, resource changes might or might not require temporary stoppage of a logical partition. If a logical partition needs to be stopped, this should not affect much because PFM - Agent for Platform is also stopped. However, if a logical partition does not need to be stopped, and the system resources change dynamically, the performance data obtained by PFM - Agent for Platform might be significantly affected. In this case, we recommend that you collect performance data not significantly affected by dynamic resource changes.

The following table shows the resources that can be collected for each virtualized system.

Table 1-21 Resources for each virtualized system

Virtualized system Resource
Processor count Memory Disk Network
Zone -- -- TS --
APV DS DS TS TS
I-VM (VSE) TS TS TS TS
VMware ESX Server 3.0 TS TS TS TS
Virtage TS TS -- TS
WPAR DS DS DS --

Legend:
DS: Dynamic change is possible.
TS: The logical partition needs to be temporarily stopped.
--: Not supported

(a) Zone

l Zone functionality

Unlike the logical resource partitioning functions implemented in other OSs (for example, LPAR in AIX and VMware), the zone functionality installed in Solaris 10 or later provides an application workspace. Accordingly, the positioning of a virtualized system based on zones slightly differs from that of virtualized systems on other OSs. Despite the difference, however, zones are used like similar functions in other OSs (for example, for the implementation of multiple OSs in a single system).

l Structure of the zone functionality

There are two types of zones: a global zone and a non-global zone. The global zone has almost the same meaning as the entire system, whereas a non-global zone represents an application workspace provided by the system.

In an ordinary virtualized system, resources are completely separated from the system when viewed by the user. In a virtualized system based on the zone functionality, resources other than disks are basically owned by the global zone.

PFM - Agent for Platform can collect information about the global zone and non-global zones. Note that some types of information about a non-global zone cannot be collected depending on the record. For details, see Table 1-28.

Figure 1-11 Concept of an ordinary virtualized system and the zone functionality

[Figure]

In a non-global zone, the zone functionality operates by using a single file system as seen from the global zone.

Part of the file system of the global zone is shared in the non-global zone.

In the following example, the entities of sbin and usr under zone a, zone b, and zone c are sbin and usr under /.

Figure 1-12 Example of a zone configuration

[Figure]

l Monitoring resources in the global zone

When PFM - Agent for Platform is running in the global zone, you can set the ALL Zone Collection for Process property to select the zone for which process information is collected. The ALL Zone Collection for Process property is set in the list of Agent Collector service properties for PFM - Web Console. You can set either of the following values for the ALL Zone Collection for Process property.

Y
Collect process information for the global zone and non-global zones.

N
Collect process information for the global zone.

The set property will be obtained when PFM - Agent for Platform is started. If the ALL Zone Collection for Process property has not been set, the default of Y is set.

The following figure shows process information that is collected when PFM - Agent for Platform is running in the global zone.

Figure 1-13 Process information collected for the global zone

[Figure]

l Monitoring resources in a non-global zone

When PFM - Agent for Platform is running in a non-global zone, information only about that non-global zone is collected regardless of the setting of the ALL Zone Collection for Process property. The following figure shows the process information that is collected when PFM - Agent for Platform is running in a non-global zone.

Figure 1-14 Process information collected for a non-global zone

[Figure]

(b) APV

l APV functions

APV is extended functionality that implements an integrated virtualized system. APV provides the following functions:

l APV structure

APV uses components to implement a virtualized system.

A simple explanation of the APV structure is that the Micro-Partitioning function allocates one processor resource to multiple LPARs so that the LPARs can use physical device resources limited by the VIOS function. IVM (APV) is the software that facilitates the use of these resources.

Figure 1-15 APV structure

[Figure]

l Using PFM - Agent for Platform on APV

When using PFM - Agent for Platform on APV, note that information about processors and memory is changed dynamically. Also note that when you use records for handling processor information, a different type of operation might be required depending on whether your virtualized system creates the same number of instances as the processors that can be allocated.

Processor information
For a record that indicates processor information, the number of instances displayed is ten times as many as the number of processors partitioned by the Micro-Partitioning function. Note, however, that this only means that a maximum of 10 logical processors can be allocated to one processor, and a single instance will not always be 10% of the processor resources. Thus, when one physical processor is partitioned into four logical processors by using the Micro-Partitioning function, the total usage of these processors will be 100%. The remaining six logical processors that have not been allocated are displayed as Offline, which means that they are not in use.
When the SMT function is used, one physical processor is partitioned into two logical processors. Operation is therefore the same as when the Micro-Partitioning is used.

Memory
Be careful when setting an alarm for memory as a resource that can be changed dynamically. Even when the amount of memory used is fixed, if the allocated memory resources are reduced, memory usage will grow, and could cause alarms to be reported unintentionally.

Devices
Disk performance data is only collected for logical partition groups on LPARs. System-wide performance data cannot be collected.

(c) I-VM (VSE)

l I-VM (VSE) functions

I-VM (VSE) is provided as a function of the VSE environment. I-VM (VSE) provides a sub-CPU partitioning capability that dynamically partitions a processor resource into 5% units and then allocates the units to logical partitions. By using this function, you can set a maximum of 20 logical processors for one physical processor. When this function is used, PFM - Agent for Platform collects performance data for the logically partitioned processors.

In addition to processor resources, I-VM (VSE) supports sharing of I/O by multiple logical partitions and supports memory virtualization. Because I-VM (VSE) supports Linux as well as HP-UX, Linux compatibility is also provided.

l I-VM (VSE) structure

The processor resource allocation function provided by I-VM (VSE) is almost the same as the Micro-Partitioning function provided by AIX.

Figure 1-16 I-VM (VSE) structure

[Figure]

l Using PFM - Agent for Platform on I-VM (VSE)

When using PFM - Agent for Platform on I-VM (VSE), note that the information about processors, memory, and devices is changed.

Processor information
A record that indicates processor information displays the same number of instances as the number of virtual processors allocated to the virtual machine.
Because the resources allocated to the virtual processor on I-VM (VSE) change dynamically, the amount of resources that is actually used differs even when the processor usage is the same. For example, 30% of the processor resources might be allocated to processor #1 whose usage is 50%. If the allocation ratio changes to 60%, the usage of processor #1 becomes 25% (in actuality, there is a margin of error due to overhead and the kernel structure). Accordingly, to determine whether the processor usage is low, you should use fields that are unlikely to be affected by processor resource allocation, such as the current queue length.

Memory
Although I-VM (VSE) supports memory virtualization, virtualized memory cannot be changed dynamically. Accordingly, operation can proceed on a virtual machine the same way as on a non-virtual machine.

Devices
As with memory, I-VM (VSE) supports I/O virtualization. Disk performance data is only collected for logical partition groups. System-wide performance data cannot be collected.

(d) VMware ESX Server 3.0

VMware is software that provides virtualized systems on the Intel architecture. Because it provides virtualized systems implemented in software, it is a general purpose implementation that can run flexibly on several environments.

l VMware ESX Server functionality

Like other virtualized systems, VMware provides the following functionality:

VMware manages combinations of the above functionality to create a virtual machine (VM). The created VM is recognized as a single host from other hosts, and can be treated the same as a physical machine.

Because multiple VMs can be created and run, operating systems like Linux and Windows can run concurrently.

l VMware ESX Server configuration

VMware implements a virtualized system by creating a distinction between a host OS and a guest OS.

To set up a virtualized system:

  1. Install Windows, Linux, or another OS on the actual hardware.

  2. Install VMware on the installed host OS.
    Here, the OS on which VMware is installed is called the host OS.

  3. Use VMware to create a VM.
    Install other operating systems on the created VM. An operating system installed on the VM is called a guest OS.

As shown above, VMware uses a parent/child configuration to implement a virtualized system, in which the guest OS is executed on the host OS.

One feature of VMware ESX Server is that a specialized custom OS is used as the host OS instead of Windows or Linux. In other words, VMware ESX Server implements a virtualized system in which Windows or Linux is running on a specialized custom OS.

Depending on the type of VMware, the host OS can also be Windows or Linux instead of the custom OS.

Figure 1-17 VMware configuration

[Figure]

l Using PFM - Agent for Platform on VMware ESX Server

Keep the following in mind when using PFM - Agent for Platform on VMware ESX Server.

Installing PFM - Agent for Platform
To use PFM - Agent for Platform, install it on the guest OS. Because the host OS for VMware ESX Server is a custom OS optimized to implement virtualized systems with VMware, operation of applications is not guaranteed.

Processor information
In a virtualized system, if sufficient resources are not allocated to the host OS, the impact will extend to the operation of the host OS. In particular, the impact is significant on processor resources. If overload occurs, it might be difficult to determine whether the processor resources allocated to the VM are insufficient, or whether the host OS processor resources are insufficient.
VMware also has a feature that allows upper and lower limits to be set for processor usage allocation, which can cause wide swings in usage because resource switching is automatically performed within the set range.
If this seems to be the case, monitor items that are not easily impacted by dynamic changes to processor resources, such as the current queue length.

Memory
Be careful when setting an alarm for memory as a resource that can be changed dynamically. Even when the amount of used memory is fixed, if the allocated memory resources are reduced, memory usage will grow, and could cause alarms to be reported unintentionally.

Devices
Disk performance data is collected only for logical partition groups on the guest OS. System-wide performance data including the host OS cannot be collected. For the network adapter information, information about virtual network adapters allocated to the guest OS is obtained.

(e) Virtage

l Virtage functionality

Like other virtualized systems, Virtage provides the following functionality:

Virtage manages the above functionality to implement a virtualized system. Whenever any resource is changed, the logical partition needs to be temporarily stopped.

l Virtage configuration

Like VMware, Virtage has a parent/child configuration.

To set up a virtualized system on Virtage:

  1. Install Virtage on the SVP.

  2. Start the installed instance of Virtage.

  3. Create and set up a virtual machine.

  4. Start the virtual machine.

l Using PFM - Agent for Platform on Virtage

Keep the following in mind when using PFM - Agent for Platform on Virtage.

Installing PFM - Agent for Platform
Because Virtage is configured in a special environment called an SVP frame, do not install PFM - Agent for Platform on an SVP frame.

Processor information
Because a virtualized system based on Virtage runs after the logical partition is set up, the number of processors is not changed while PFM - Agent for Platform is running. Accordingly, operation can be performed as usual, but the number of allocated processors may not match the number of processors that physically exist.

Memory
Because a virtualized system based on Virtage implements runs after the logical partition is set up, the amount of memory is not changed while PFM - Agent for Platform is running. Accordingly, operation can be performed as usual.

Devices
Disk performance data is collected only for logical partition groups. System-wide performance data including the host OS cannot be collected. For the network adapter information, information about virtual network adapters allocated to the logical partition is obtained.

(f) WPAR

l WPAR function

WPAR included in AIX V6.1 or later provides a function that runs multiple AIX V6.1 instances, which are virtualized as software, in a single LPAR. There are two types of WPAR environments, system WPAR and application WPAR. The global environment required for configuring WPAR is also provided. The following describes these environments.

l WPAR structure

The structure of WPAR is similar to that of Solaris Zone, which provides workspace for applications.

In the global environment, you can display or interact with the processes, file systems, and other system components allocated on WPAR running in the system. A new instance of WPAR can be created only in the global environment. Another instance of WPAR cannot be created in the WPAR environment. Most management tasks can be executed only in the global environment. Most commands behave differently depending on whether they are executed in the global environment or in the WPAR environment.

PFM - Agent for Platform can collect performance data in the following cases:

l Monitoring resources in the global environment

When PFM - Agent for Platform is running in the global environment, you can set the ALL WPAR Collection for Process property to select the environment for which process information is collected. The ALL WPAR Collection for Process property is set in the list of Agent Collector service properties for PFM - Web Console. You can set either of the following values for the ALL WPAR Collection for Process property.

Y
Collect process information for the global environment and all WPAR environments.

N
Collect process information for the global environment.

The set property will be obtained when PFM - Agent for Platform is started. If the ALL WPAR Collection for Process property has not been set, the default of Y is set.

The following figure shows the process information that is collected when PFM - Agent for Platform is running in the global environment.

Figure 1-18 Process information collected for the global environment

[Figure]

l Monitoring resources in a system WPAR environment

When PFM - Agent for Platform is running in a system WPAR environment, information only about that system WPAR environment is collected regardless of the setting of the ALL WPAR Collection for Process property. The following figure shows the process information that is collected when PFM - Agent for Platform is running in the system WPAR environment.

Figure 1-19 Process information collected for the system WPAR environment

[Figure]

l Using PFM - Agent for Platform on WPAR

When using PFM - Agent for Platform on WPAR, note that the information about processors and memory is dynamically changed.

Installing PFM - Agent for Platform
PFM - Agent for Platform can be installed in the global environment or system WPAR environment. Note, however, that when you install PFM - Agent for Platform in the system WPAR environment, the following information cannot be obtained because a separate application environment is provided due to the characteristics of WPAR.
  • Information about the WPAR environments other than the system WPAR environment in which PFM - Agent for Platform is installed
  • Some device information, such as /dev/mem and /dev/kmem
  • Some network information related to the NFS Server
When you configure a system WPAR environment after PFM - Agent for Platform is installed in the global environment, the files related to PFM - Agent for Platform are copied to the system WPAR environment. However, this does not affect PFM - Agent for Platform in the global environment. Note that the copy of the PFM - Agent for Platform instance in the system WPAR environment cannot be used as is. To use PFM - Agent for Platform in the system WPAR environment, you need to manually delete the files related to PFM - Agent for Platform (all files under the /opt/jp1pc directory) in the system WPAR environment. Then perform a new installation of PFM - Agent for Platform.

Processor information
Because a virtualized system based on WPAR runs according to the allocation ratio of the processor, the number of processors is not changed while PFM - Agent for Platform is running. However, because the processor allocation ratio can be dynamically changed while the system is running, information such as the processor usage for applications might be affected.

Memory
Be careful when setting an alarm for memory as a resource that can be changed dynamically. Even when the amount of memory used is fixed, if the allocated memory resources are reduced, memory usage will grow, and could cause alarms to be reported unintentionally.

Devices
When monitoring devices on WPAR, information for only logical partition groups on WPAR can be collected. To collect information for physical partition groups, install PFM - Agent for Platform in the global environment and monitor the devices in the global environment.

(6) Data collected for each virtualized system

n Global zone, non-global zone, and APV, I-VM (VSE), VMware ESX Server 3.0, and Virtage environments

The following table describes the data collected by PFM - Agent for Platform running in a virtualized system in the global zone, non-global zone, APV, I-VM (VSE), VMware ESX Server 3.0, and Virtage environments. For example, when you collect data of the PD record in an environment where PFM - Agent for Platform is running in the shared-IP non-global zone, the Shared-IP Non-Global Zone column indicates This zone only. This means that the data only for the shared-IP non-global zone will be collected. When you collect data of the PI record in this environment, the Shared-IP Non-Global Zone column indicates Entire system, which means that the data for the global zone and non-global zones will be collected.

Table 1-22 Data collected for each virtualized system (global zone, non-global zone, APV, I-VM (VSE), VMware ESX Server 3.0, and Virtage environments)

Record Global Zone Non-Global Zone APV and I-VM (VSE) VMware ESX Server 3.0 and Virtage
Shared-IP Non-Global Zone Exclusive-IP Non-Global Zone
PD Entire system This zone only This zone only Processes on the logical partition Processes on the guest OS
PD_APP Entire system This zone only This zone only Processes on the logical partition Processes on the guest OS
PD_FSL Entire system This zone only This zone only Local disk information on the logical partition Local disk information in the guest OS
PD_FSR Information is collected only for the global zone. Information about a remote file system (NFS) installed in the non-global zone cannot be obtained. This zone only This zone only Remote file system information registered on the logical partition Remote file system information registered in the guest OS
PD_PDI Entire system This zone only This zone only Processes on the logical partition Processes on the guest OS
PD_PDS Entire system This zone only This zone only Processes on the logical partition Processes on the guest OS
PD_PGM Entire system This zone only This zone only Processes on the logical partition Processes on the guest OS
PD_TERM Entire system This zone only This zone only Processes on the logical partition Processes on the guest OS
PD_UPD Specified value Specified value Specified value Performance data that the user specified on the logical partition Performance data that the user specified in the guest OS
PD_UPDB Specified value Specified value Specified value Performance data that the user specified on the logical partition Performance data that the user specified in the guest OS
PD_USER Entire system This zone only This zone only Processes on the logical partition Processes on the guest OS
PI#1 Entire system Entire system Entire system System values on the logical partition System values in the guest OS
PI_CPUP Entire system Entire system Entire system Processor information allocated to the logical partition Processor information allocated to the guest OS
PI_DEVD Entire system Entire system Entire system Disk information allocated to the logical partition Disk information allocated to the guest OS
PI_DEVS Entire system Entire system Entire system Disk information allocated to the logical partition Disk information allocated to the guest OS
PI_NIND#2 Interface information shared by the global zone and all shared-IP non-global zones -- This zone only NIC information allocated to the logical partition NIC information allocated to the guest OS
PI_NINS#2 Interface information shared by the global zone and all shared-IP non-global zones -- This zone only NIC information allocated to the logical partition NIC information allocated to the guest OS
PI_UPI Specified value Specified value Specified value Performance data that the user specified on the logical partition Performance data that the user specified in the guest OS
PI_UPIB Specified value Specified value Specified value Performance data that the user specified on the logical partition Performance data that the user specified in the guest OS
PI_WGRP Entire system This zone only This zone only Processes on the logical partition Processes on the guest OS
PL_MESS Specified value Specified value Specified value The file specified in evfile or the Messages File property The file specified in evfile or the Messages File property

Legend:
--: Not collected

#1
For the following fields, interface information is collected even in the non-global zone environment:
ICMP Pkts In, ICMP Pkts Out, ICMP6 Pkts In, ICMP6 Pkts Out, IP Pkts In, IP Pkts Out, IP6 Pkts In, IP6 Pkts Out, TCP Pkts In, TCP Pkts Out, Total Pkts, Total Pkts In, Total Pkts Out, UDP Pkts In, UDP Pkts Out
For the following fields, however, information is not collected in the global zone or non-global zone environment:
NFS Server Lookup Ops, NFS Server Ops/sec, NFS Server Read Ops, NFS Server Read Ops/sec, NFS Server Total Bad Ops, NFS Server Total Ops, NFS Server Write Ops, NFS Server Write Ops/sec

#2
Physical interface information is collected. Because the shared-IP non-global zone is a logical zone, no information is collected.

n WPAR environment

The following table describes the data collected by PFM - Agent for Platform running in a WPAR environment. For example, when you collect data of the PD record in an environment where PFM - Agent for Platform is running in a system WPAR environment, the System WPAR column indicates System WPAR environment. This means that the data only for the system WPAR environment is collected. When you collect data of the PI record in this environment, the System WPAR column indicates Global environment and system WPAR environment, which means that the data for the global environment and system WPAR environments will be collected.

Table 1-23 Data collected for each virtualized system (WPAR environment)

Record Field Global environment System WPAR
PD All Global environment System WPAR environment
PD_FSL All Global environment System WPAR environment
PD_FSR All Global environment System WPAR environment
PI# 1-Minute Run Queue Avg,
15-Minute Run Queue Avg,
5-Minute Run Queue Avg,
Active CPUs,
Alloc Mem %,
Alloc Mem Mbytes,
Alloc Swap %,
Alloc Swap Mbytes,
Block Ops,
Block Reads,
Block Writes,
Cache Read %,
Cache Write %,
Context Switches,
CPU %,
Faults,
Free Mem %,
Free Mem Mbytes,
Free Swap %,
Free Swap Mbytes,
Idle %,
Kernel CPU %,
Logical I/O Ops,
Logical Read Mbytes,
Logical Reads,
Logical Write Mbytes,
Logical Writes,
Major Faults,
Pages In,
Pages Out,
Physical I/O Ops,
Physical Reads,
Physical Writes,
Run Queue,
Swapped-In Pages,
Swapped-Out Pages,
System Calls,
Total Idle Time,
Total Kernel-Mode Time,
Total Page Scans,
Total Physical Mem Mbytes,
Total Swap Mbytes,
Total User-Mode Time,
Total Wait Time,
User CPU %,
Wait %		 Global environment and all WPAR environments Global environment and system WPAR environment
ICMP Pkts In,
ICMP Pkts Out,
ICMP6 Pkts In,
ICMP6 Pkts Out,
IP Pkts In,
IP Pkts Out,
IP6 Pkts In,
IP6 Pkts Out,
NFS Client Lookup Ops,
NFS Client Ops/sec,
NFS Client Read Ops,
NFS Client Read Ops/sec,
NFS Client Total Bad Ops,
NFS Client Total Ops,
NFS Client Write Ops,
NFS Client Write Ops/sec,
NFS Server Lookup Ops,
NFS Server Ops/sec,
NFS Server Read Ops,
NFS Server Read Ops/sec,
NFS Server Total Bad Ops,
NFS Server Total Ops,
NFS Server Write Ops,
NFS Server Write Ops/sec,
Processes,
Processes Ended,
Processes Started,
TCP Pkts In,
TCP Pkts Out,
Total Pkts,
Total Pkts In,
Total Pkts Out,
UDP Pkts In,
UDP Pkts Out,
Users		 Global environment and all WPAR environments System WPAR environment
Block Reads/sec,
Block Writes/sec,
Context Switches/sec,
Logical Reads/sec,
Logical Writes/sec,
Major Faults/sec,
Page Scans/sec,
Pages In/sec,
Pages Out/sec,
Swapped-In Pages/sec,
Swapped-Out Pages/sec,
System Calls/sec,
Total Faults/sec		 Global environment and all WPAR environments --
Boot Time,
Interval,
Record Time,
System Up Time		 Global environment System WPAR environment
Record Name,
Record Type		 Fixed value Fixed value
Interrupts,
Interrupts/sec,
Mem I/O Ops,
Minor Faults,
Minor Faults/sec,
Other Pkts In,
Other Pkts Out,
Page Reclaims/sec,
Page-In Ops,
Page-In Ops/sec,
Page-Out Ops,
Page-Out Ops/sec,
Page Ops/sec,
Software Lock Faults,
Software Lock Faults/sec,
Swap-In Ops,
Swap-Ins/sec,
Swap-Out Ops,
Swap-Outs/sec,
Total Page Ops,
Total Page Reclaims,
Total Swaps,
Total Swaps/sec,
Traps,
Traps/sec		 -- --
PI_CPUP CPU %,
Context Switches,
Idle %,
Idle Time,
System %,
System Calls,
System Time,
User %,
User Time,
Wait %,
Wait Time		 Global environment and all WPAR environments Global environment and system WPAR environment
Context Switches/sec,
Sys Calls/sec		 Global environment and all WPAR environments --
Boot Time,
Interval,
Record Time,
Up Time		 Global environment System WPAR environment
Processor ID,
Status,
Type		 Global environment Global environment
Record Name,
Record Type		 Fixed value Fixed value
Interrupts,
Interrupts/sec,
Traps,
Traps/sec		 -- --
PI_DEVD All Global environment --
PI_DEVS All Global environment --
PI_NIND All Global environment System WPAR environment
PL_MESS All Global environment System WPAR environment

Legend:
--: Not collected

#
For the following fields, information is not collected in the system WPAR environment:
NFS Server Lookup Ops, NFS Server Ops/sec, NFS Server Read Ops, NFS Server Read Ops/sec, NFS Server Total Bad Ops, NFS Server Total Ops, NFS Server Write Ops, NFS Server Write Ops/sec

(7) Identifying processes that have the same name in a virtualized system

In a virtualized system, a host might contain processes that have the same name. The following describes how to identify such processes in the virtualized system.

(a) Zone environment

If processes that have the same name exist in the global and non-global zones, check the value of the Virtual Env ID field to determine the zone from which the process information for the PD and PD_APP records was collected.

n PD record

For process information obtained by the PD record, the following table describes the relationship between the property setting and the obtained information.

Table 1-24 When PFM - Agent for Platform is installed in the global zone in an environment in which zones have been created

ALL ZONE Collection for Process property setting Obtained information
Data is collected from: Virtual Env ID field value
Yes Global zone and all non-global zones ID of each zone#
No Global zone 0

#
When process information is collected from the global zone, the virtualized environment ID (value of the Virtual Env ID field) is 0. When process information is collected from a non-global zone, the virtualized environment ID (value of the Virtual Env ID field) is the ID assigned to that non-global zone.

Table 1-25 When PFM - Agent for Platform is installed in a non-global zone in an environment in which zones have been created

ALL ZONE Collection for Process property setting Obtained information
Data is collected from: Virtual Env ID field value
Yes Non-global zone where PFM - Agent for Platform is installed Non-global zone ID
No Non-global zone where PFM - Agent for Platform is installed Non-global zone ID

Reference note:
The following table describes the relationship between the property setting and obtained information in an environment in which no zones have been created.

Table 1-26 When PFM - Agent for Platform is installed in the global zone in an environment in which no zones have been created

ALL ZONE Collection for Process property setting Obtained information
Data is collected from: Virtual Env ID field value
Yes Global zone 0
No Global zone 0

n PD_APP record

For process information obtained by the PD_APP record, the following table describes the relationship between the property setting and the obtained information. Note that for the PD_APP record, you can set the ADD AN APPLICATION MONITORING SETTING FOR VIRTUAL ENVIRONMENT property to restrict the environment from which process information is to be collected.

Table 1-27 When PFM - Agent for Platform is installed in the global zone in an environment in which zones have been created

Property settings Obtained information
ALL WPAR Collection for Process ADD AN APPLICATION MONITORING SETTING FOR VIRTUAL ENVIRONMENT Data is collected from: Virtual Env ID field value
Yes Blank Global zone and all non-global zones Blank
Yes 0 Global zone 0
Yes ID of the existing non-global zone Specified non-global zone environment ID of the specified non-global zone
Yes ID of the nonexistent non-global zone -- --
No Blank Global zone Blank
No 0 Global zone 0
No ID of the existing non-global zone -- --
No ID of the nonexistent non-global zone -- --

Legend:
--: Neither collected nor displayed in a report

Table 1-28 When PFM - Agent for Platform is installed in the non-global zone in an environment in which zones have been created

Property settings Obtained information
ALL WPAR Collection for Process ADD AN APPLICATION MONITORING SETTING FOR VIRTUAL ENVIRONMENT Data is collected from: Virtual Env ID field value
Yes Blank Non-global zone where PFM - Agent for Platform is installed Blank
Yes 0 -- --
Yes ID of the non-global zone where PFM - Agent for Platform is installed Non-global zone where PFM - Agent for Platform is installed ID of the non-global zone where PFM - Agent for Platform is installed
Yes ID of the non-global zone where PFM - Agent for Platform is not installed -- --
No Blank Non-global zone where PFM - Agent for Platform is installed Blank
No 0 -- --
No ID of the non-global zone where PFM - Agent for Platform is installed Non-global zone where PFM - Agent for Platform is installed ID of the non-global zone where PFM - Agent for Platform is installed
No ID of the non-global zone where PFM - Agent for Platform is not installed -- --

Legend:
--: Neither collected nor displayed in a report

Reference note:
The following table describes the relationship between the property settings and obtained information in an environment in which no zones have been created.

Table 1-29 When PFM - Agent for Platform is installed in the global zone in an environment in which no zones have been created

Property settings Obtained information
ALL WPAR Collection for Process ADD AN APPLICATION MONITORING SETTING FOR VIRTUAL ENVIRONMENT Data is collected from: Virtual Env ID field value
Yes Blank Global zone Blank
Yes 0 Global zone 0
Yes Value other than 0 -- --
No Blank Global zone Blank
No 0 Global zone 0
No Value other than 0 -- --

Legend:
--: Neither collected nor displayed in a report

(b) WPAR environment

If processes that have the same name exist in the global environment and WPAR environment, check the value of the Virtual Env ID field to determine the environment from which the process information for the PD and PD_APP records was collected.

n PD record

For process information obtained by the PD record, the following table describes the relationship between the property setting and the obtained information.

Table 1-30 When PFM - Agent for Platform is installed in the global environment in an environment in which a system WPAR has been created

ALL WPAR Collection for Process property setting Obtained information
Data is collected from: Virtual Env ID field value
Yes Global environment and all WPAR environments ID of each WPAR#
No Global environment 0

#
When process information is collected from the global environment, the virtualized environment ID (value of the Virtual Env ID field) is 0. When process information is collected from a WPAR environment, the virtualized environment ID (value of the Virtual Env ID field) is the ID assigned to that WPAR environment.

Table 1-31 When PFM - Agent for Platform is installed in a system WPAR environment in an environment in which a system WPAR has been created

ALL WPAR Collection for Process property setting Obtained information
Data is collected from: Virtual Env ID field value
Yes System WPAR environment in which PFM - Agent for Platform is installed 0
No System WPAR environment in which PFM - Agent for Platform is installed 0

Reference note:
The following table describes the relationship between the property setting and obtained information in an environment in which no system WPAR has been created.

Table 1-32 When PFM - Agent for Platform is installed in the global environment in an environment in which no system WPAR has been created

ALL WPAR Collection for Process property setting Obtained information
Data is collected from: Virtual Env ID field value
Yes Global environment 0
No Global environment 0

n PD_APP record

For process information obtained by the PD_APP record, the following table describes the relationship between the property setting and the obtained information. Note that for the PD_APP record, you can set the ADD AN APPLICATION MONITORING SETTING FOR VIRTUAL ENVIRONMENT property to restrict the environment from which process information is collected.

Table 1-33 When PFM - Agent for Platform is installed in the global environment in an environment in which a system WPAR has been created

Property settings Obtained information
ALL WPAR Collection for Process ADD AN APPLICATION MONITORING SETTING FOR VIRTUAL ENVIRONMENT Data is collected from: Virtual Env ID field value
Yes Blank Global environment and all WPAR environments Blank
Yes 0 Global environment 0
Yes ID of the existing WPAR Specified WPAR environment ID of the specified WPAR
Yes ID of the non-existing WPAR -- --
No Blank Global environment Blank
No 0 Global environment 0
No ID of the existing WPAR -- --
No ID of the non-existing WPAR -- --

Legend:
--: Neither collected nor displayed in a report

Table 1-34 When PFM - Agent for Platform is installed in a system WPAR environment in an environment in which a system WPAR has been created

Property settings Obtained information
ALL WPAR Collection for Process ADD AN APPLICATION MONITORING SETTING FOR VIRTUAL ENVIRONMENT Data is collected from: Virtual Env ID field value
Yes Blank System WPAR environment in which PFM - Agent for Platform is installed Blank
Yes 0 System WPAR environment in which PFM - Agent for Platform is installed 0
Yes Value other than 0 -- --
No Blank System WPAR environment in which PFM - Agent for Platform is installed Blank
No 0 System WPAR environment in which PFM - Agent for Platform is installed 0
No Value other than 0 -- --

Legend:
--: Neither collected nor displayed in a report

Reference note:
The following table describes the relationship between the property settings and obtained information in an environment in which no system WPAR has been created.

Table 1-35 When PFM - Agent for Platform is installed in a global environment in an environment in which no system WPAR has been created

Property settings Obtained information
ALL WPAR Collection for Process ADD AN APPLICATION MONITORING SETTING FOR VIRTUAL ENVIRONMENT Data is collected from: Virtual Env ID field value
Yes Blank Global environment Blank
Yes 0 Global environment 0
Yes Value other than 0 -- --
No Blank Global environment Blank
No 0 Global environment 0
No Value other than 0 -- --

Legend:
--: Neither collected nor displayed in a report

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.