AIX LPAR VM Information Test
This test auto-discovers the LPARs on a pSeries server, reports the amount of CPU and memory resources that each LPAR is configured with, reveals the extent of usage of the allocated resources by every LPAR, and also updates you with the powered-on status of these LPARs. Using the measures reported by this test, the following can be quickly ascertained:
- Which LPAR is currently powered-off?
- Which LPAR is utilizing virtual CPU and virtual memory optimally? Are there any resource-hungry LPARs? If so, which ones are they?
- Is any LPAR under-sized/over-sized in terms of the CPU and memory allocated to it? If so, which one is it?
- What is the maximum limit to which the processing capacity of an LPAR can be allowed to grow?
- What is the processing capacity configuration of every LPAR's shared resource pool?
Target of the test : An IBM pSeries server
Agent deploying the test : A remote agent
Outputs of the test : One set of results for each LPAR configured on the IBM pSeries server being monitored.
| Parameter | Description |
|---|---|
|
Test period |
How often should the test be executed |
|
Host |
The IP address of the host for which this test is to be configured. |
|
Port |
Indicate the port at which the specified Host listens. By default, this is NULL. |
|
HMC Server IP |
This test connects to an HMC server to perform LPAR discovery and to collect host-level and "outside view" metrics from the pSeries server. To enable this communication, first, provide the IP address/host name of the HMC server in the HMC Server IP text box. If the eG manager had automatically discovered the target pSeries server by connecting to an HMC server in the environment, then, the IP address/host name will be automatically displayed in the HMC Server IP text box. and user credentials pertaining to that HMC server However, if the pSeries server being monitored was manually added to the eG Enterprise system (and not auto-discovered via the HMC server), then, you will have to explicitly provide the IP address of the HMC server that manages the target pSeries server in the HMC Server IP text box. |
|
HMC Console Username, HMC Console Password and Confirm Password |
This test makes REST API requests to the HMC console to pull the metrics. For this purpose, the test needs to be configured with the credentials of a user who can access the HMC console in the HMC Console Username and HMC Console Password text boxes. Confirm the HMC Console Password by retyping it in the Confirm Password text box. |
|
Measurement |
Description |
Measurement Unit |
Interpretation |
||||||
|---|---|---|---|---|---|---|---|---|---|
|
Is LPAR powered on? |
Whether this LPAR is powered on or not. |
|
If this measure returns the value 'Yes', it indicates that the LPAR is powered-on. The value 'No' on the other hand indicates that the LPAR is powered off. The table below displays the values that can be reported by this measure, and their numeric equivalents:
Note: By default, this measure reports one of the Measure Values listed in the table above. The graph of this measure however will represent the VM status using the numeric equivalents - 0 or 1. |
||||||
|
Online virtual CPUs |
Indicates the number of virtual CPUs currently being used by this LPAR. |
Number |
A high value of this measure indicates excessive CPU usage by an LPAR. Comparing the value of this measure across LPARs will enable you to quickly and accurately point to that LPAR that is consuming too much CPU. To know whether the CPU resources of this LPAR are capped or uncapped, use the detailed diagnosis of this measure. This will additionally reveal the partition ID and type (whether dedicated or shared) as well. |
||||||
|
Maximum virtual CPUs |
Indicates the maximum number of virtual CPUs that can be utilized by this LPAR. |
Number |
|
||||||
|
Minimum virtual CPUs |
Indicates the minimum number of virtual CPUs configured for this LPAR. |
Number |
|
||||||
|
Online memory |
Indicates the amount of allocated memory resources currently utilized by this LPAR. |
MB |
A high value of this measure indicates excessive memory usage by an LPAR. Comparing the value of this measure across LPARs will enable you to quickly and accurately point to that LPAR that is consuming too much memory. |
||||||
|
Maximum memory |
Indicates the maximum amount of memory that this LPAR can use. |
MB |
|
||||||
|
Minimum memory |
Indicates the minimum amount of memory allocated to this LPAR. |
MB |
|
||||||
|
Capacity increment |
Indicates the minimum capacity (in units of 1/100 of a physical processor) that can be added to or removed from this partition's processor capacity. |
Number |
This measure indicates the granule at which changes to Entitled Capacity can be made. A value in whole multiples indicates a Dedicated LPAR. |
||||||
|
Maximum capacity |
Indicates the maximum number of processing units that this LPAR can use. |
Number |
The entitled capacity of the LPAR can go up to the value of this measure. |
||||||
|
Minimum capacity |
Indicates the minimum number of processing units required by this LPAR for its functioning. |
Number |
The entitled capacity of the LPAR cannot go down beyond the value of this measure. |
||||||
|
Active physical CPUs in system |
Indicates the current number of active physical CPUs in the system containing this LPAR. |
Number |
|
||||||
|
Maximum physical CPUs in system |
Indicates the maximum number of physical CPUs that can be used by this LPAR. |
Number |
|
||||||
|
Active CPUs in pool |
Indicates the maximum number of CPUs available to this LPAR's shared processor pool. |
Number |
|
||||||
|
Shared physical CPUs in system |
Indicates the number of physical CPUs available for use by shared processor LPARs. |
Number |
|
||||||
|
Entitled capacity of pool |
Indicates the number of processing units that this LPAR's shared processor pool is entitled to receive. |
Number |
|
||||||
|
Maximum capacity of pool |
Indicates the maximum number of processing units available to this LPAR's shared processor pool. |
Processing units |
|
||||||
|
Unallocated capacity |
Indicates the sum of the number of processor units unallocated from shared LPARs in an LPAR group. |
Processing units |
This sum does not include the processor units unallocated from a dedicated LPAR, which can also belong to the group. The unallocated processor units can be allocated to any dedicated LPAR (if it is greater than or equal to 1.0 ) or shared LPAR of the group. |
||||||
|
Unallocated weight |
Indicates the number of variable processor capacity weight units currently unallocated within the LPAR group. |
Processing units |
|
To know whether the CPU resources of an LPAR are capped or uncapped, use the detailed diagnosis of this Online virtual CPUs measure.
Figure 1 : The detailed diagnosis of the Online virtual CPUs measure
