Monitoring IBM Power HMC
This is an optional feature, disabled by default in the Instana backend. To enable this optional feature, see the page for your Instana deployment: SaaS, Self-Hosted Custom Edition (Kubernetes or Red Hat OpenShift Container Platform), or Self-Hosted Classic Edition (Docker)
- Supported versions
- Accessing Power HMC information
- Configuration
- Metrics collection
- Manage events from managed system and HMC console
- Troubleshoot
Supported versions
Instana supports the Power HMC API version HMC V10, which includes compatibility with Power10, Power9, and Power8 systems, allowing for the retrieval of metrics and configuration data.
Accessing Power HMC information
When the agent is configured and deployed on a remote server for collecting the Power HMC metrics, the Power HMC sensor reports detailed data about the system and other resources.
Platform view
IBM Power is one of the items in the Platform menu in the Instana UI. This menu item gives direct access to the Power HMC console and systems.
Infrastructure view
From the Infrastructure menu in the Instana UI, you can view the map of the Power HMC entities in the Map tab. To view the metrics, complete the following steps:
- In the sidebar of the Instana UI, select Infrastructure.
- Click a specific monitored host. You can see a host dashboard with all the collected metrics and monitored processes.
Configuration
Enable data collection
To enable data collection for systems that you want to monitor by using Instana, follow the steps:
- Open the HMC console.
- Go to the Systems tab from the navigation bar.
- Click the host systems that you want to monitor, go to the Performance tab, and click Turn on/off performance data collection.
- Enable performance collection by switching the green toggle to on and click Ok.
- Set the sampling rate by clicking Performance > Change sampling rate of utilization data and set to the desired rate. You are suggested to use
5 minutesas the sampling rate.
To collect energy-consumption related metrics, see How to enable energy monitoring for IBM Power systems. Furthermore, for Power9 and Denali Power10 (FSP-based) systems, enable Intelligent Platform Management Interface (IPMI) from Advanced System Management Interface (ASMI).
- From ASMI interface, go to System Configuration > Security > External Services Management, and enable IPMI.
Required permissions
To make the sensor connect to Power HMC and monitor the metrics, you need to have the hmcviewer role and enable the Performance and Capacity Monitoring (PCM) preferences for the managed systems. To aggregate the PCM data, you need to enable Long-Term Monitoring (LTM). Also, enable the following flags:
-
LongTermMonitorEnabled: Long term monitoring configuration value
-
AggregationEnabled: Utilization data aggregation configuration value
-
EnergyMonitorEnabled: Energy monitoring status
Sensor configuration
To connect to Power HMC server, you need to configure the following properties in the agent configuration <agent_install_dir>/etc/instana/configuration.yaml:
Only remote monitoring is supported for IBM Power HMC Instana sensor.
com.instana.plugin.powerhmc:
remote: # multiple hosts supported
- host: ''# hostname or IP of Power HMC server
port: ''# default port is '12443' of Power HMC API Server
user: '' # username to access the Power HMC server api
password: '' # password to access the Power HMC server api
availabilityZone: 'PowerHMC Remote Monitoring'
poll_rate: 300 # Poll rate in seconds. Poll rate can not be lesser than 300 seconds. If it is configured below 300 seconds then default value (300 seconds) will be set.
eventsPollRate: 900 # Poll rate in seconds. Poll rate can not be lesser than 900 seconds. If it is configured below 900 seconds then default value (900 seconds) will be set.
If the poll rate that you set on Instana is lower than the minimum poll rate on the Power HMC server, the minimum poll rate is applied.
Prerequisites on AIX
On AIX 7.2, XL C/C++ Runtime for AIX 16.1.0 Fix Pack 7 or later versions, check whether the fileset libc++.rte is installed.
lslpp -l |grep libc++.rte
Metrics collection
Currently, supoort is provided for the following metrics:
- Processor, memory, and network metrics for power-managed systems.
- Processor and memory metrics for hypervisor.
- Processor, memory, network, and storage metrics for logical partitions (LPARs) and virtual I/O servers (VIOSes).
Performance metrics
Hardware management console (HMC)
The following table lists all the HMCs that are part of the configuration:
| Metric | Description | Granularity |
|---|---|---|
| Hostaname | Hostname or IP address of the HMC. | 300 seconds |
| Systems | Total number of systems that are managed by this HMC. | 300 seconds |
| Partitions | Total number of LPARs that are managed by this HMC. | 300 seconds |
| Virtual I/O Servers | Total number of VIOSes that are managed by this HMC. | 300 seconds |
List of managed systems
The following table lists all the managed systems across all the HMCs. If the same system is managed by two or more than two HMCs, only one system is listed.
| Metric | Description | Granularity |
|---|---|---|
| Name | Hostname or IP address of the HMC. | 300 seconds |
| Systems | Total number of systems that are managed by this HMC. | 300 seconds |
| Partitions | Total number of LPARs that are managed by this HMC. | 300 seconds |
| Virtual I/O Servers | Total number of VIOSes that are managed by this HMC. | 300 seconds |
| Utilized Processing Units | Number of processing units that are used by the partitions in the pool for a particular time interval. | 300 seconds |
| Utilized Processing Units (%) | Percentage of processing units that are used by the partitions in the pool for a particular time interval. (Utilized processing units/Assigned processing units) × 100. | 300 seconds |
| Memory Available (MB) | Free memory (in megabytes) that is available for assignment. | 300 seconds |
| Memory Available (%) | (Available memory/Configurable memory) × 100. | 300 seconds |
| Machine Type-Model | Machine type and model of the managed system. | 300 seconds |
| Machine Serial | Serial number of the managed system. | 300 seconds |
Managed system
System processor utilization
The following metrics are provided for processor related to each managed system:
| Metric | Description | Granularity |
|---|---|---|
| Utilized processing units | Number of processing units that are used in the particular interval. | 300 seconds |
| Available processing units | Number of processing units available for assignment. | 300 seconds |
| Configurable processing units | Number of processing units that are configurable. | 300 seconds |
| Utilized processing units (%) | (Used processing units/Configurable processing units) × 100. | 300 seconds |
| Available processing units (%) | (Configurable processing units/Total processing units) × 100. | 300 seconds |
| Configurable processing units (%) | (Available processing units/Configurable processing units) × 100. | 300 seconds |
System memory
The following metrics are provided for memory related to each managed system:
| Metric | Description | Granularity |
|---|---|---|
| Available memory | Free memory (in megabytes) which is available for assignment. | 300 seconds |
| Configurable memory | Memory (in megabytes) that are configurable. | 300 seconds |
| Assigned memory to LPARs | Memory assigned to LPARs. | 300 seconds |
| Available memory (%) | (Available memory/Configurable memory) × 100. | 300 seconds |
| Configurable memory (%) | (Configurable memory/Total memory) × 100. | 300 seconds |
| Assigned memory to LPARs (%) | (Assigned memory to LPARs/Configurable memory) × 100. | 300 seconds |
System firmware
The following metrics are provided for firmware:
| Metric | Description | Granularity |
|---|---|---|
| Utilized Processing Units | Number of processing units that are used by the hypervisor for the specific time interval. | 300 seconds |
| Assigned Memory (MB) | Amount of memory (in megabytes) on the managed system that is being assigned to system firmware for the time interval. | 300 seconds |
Shared processor pool (SPP)
The following metrics are provided for shared processor pool related to each managed system:
| Metric | Description | Granularity |
|---|---|---|
| Name | Pool Name. | 300 seconds |
| Entitled Processing Units | Entitled pool capacity is the sum of the entitlement capacities of the partitions in the shared processor pool plus the reserved pool capacity. | 300 seconds |
| Assigned Processing Units | Number of processing units that are assigned to the pool for a specific time interval. | 300 seconds |
| Utilized Processing Units (%) | Percentage of processing units that are used by the partitions in the pool for a specific time interval. (Utilized processing units/Assigned processing units) × 100. | 300 seconds |
| Available Processing Units (%) | Percentage of processing units that are available for assignment for the time interval. (Available processing units/Assigned processing units) × 100. | 300 seconds |
| Utilized Processing Units | Number of processing units that are used by the partitions in the pool for a particular time interval. | 300 seconds |
| Available Processing Units | Number of processing units that are available for assignment for the time interval. | 300 seconds |
| Current Reserved Processing Units | Number of processing units that are reserved for temporary use by the uncapped partitions in the shared processor pool. | 300 seconds |
| Entitled Processing Units Used (%) | Calculated value. For example, for Shared Processor Pool with Pool ID 0: [((Sum of Utilized Processing Units for all VMs with Pool ID 0)/(Sum of Entitled Processing Units of all VMs with Pool ID 0 + Current Reserved Processing Units for Pool ID 0)) × 100]. | 300 seconds |
Shared processor pool
More details of each shared processor pool is provided in the individual dashboards.
SPP processor utilization
The following metrics are provided for processors in each shared processor pool:
| Metric | Description | Granularity |
|---|---|---|
| Entitled Processing Units | Entitled pool capacity is the sum of the entitlement capacities of the partitions in the shared processor pool plus the reserved pool capacity. | 300 seconds |
| Utilized Processing Units | Number of processing units that are used by the partitions in the pool for a particular time interval. | 300 seconds |
| Available Processing Units | Number of processing units that are available for assignment for the time interval. | 300 seconds |
| Current Reserved Processing Units | Number of processing units that are reserved for temporary use by the uncapped partitions in the shared processor pool. | 300 seconds |
| Utilized Processing Units (%) | Percentage of processing units that are used by the partitions in the pool for a particular time interval. (Utilized processing units/Assigned processing units) × 100. | 300 seconds |
| Available Processing Units (%) | Percentage of processing units that are available for assignment for the time interval. (Available processing units/Assigned processing units) × 100. | 300 seconds |
| Entitled Processing Units Used (%) | Calculated value. For example, for Shared Processor Pool with Pool ID 0: [((Sum of Utilized Processing Units for all VMs with Pool ID 0)/(Sum of Entitled Proc Units of all VMs with Pool ID 0 + Current Reserved Processing Units for Pool ID 0)) × 100]. | 300 seconds |
Logical partitions for each SPP
The list of LPARs for each SPP is displayed. For more details, go to LPAR dashboard by clicking any of the LPARs.
Logical partitions (LPAR)
Logical partitions
The list of LPARs for each managed system is displayed. For more details, go to LPAR dashboard by clicking any of the LPARs.
The following KPIs are provided for each LPARs:
| Metric | Description | Granularity |
|---|---|---|
| Partition Id | Partition Id of the specific LPAR. | 300 seconds |
| Name | Name of the partition. | 300 seconds |
| State | State of the partition. | 300 seconds |
| Mode | Mode of the processor. For dedicated processors, the value is specified, whereas for shared processors, it can be either capped or uncapped. | 300 seconds |
| Logical Memory | Current memory size in megabytes. | 300 seconds |
| Maximum Virtual Processors | Maximum Virtual Processors that are assigned to the logical partition for a set time interval. | 300 seconds |
| Entitled processing units (%) | (Utilized processing units/Entitled processing units) × 100. | 300 seconds |
LPAR processor utilization
The following metrics are provided for processor related to each partition:
| Metric | Description | Granularity |
|---|---|---|
| Utilized Processing Units | Total processing units that are used for a particular time interval. | 300 seconds |
| Max Processing Units | Maximum processing units that are assigned to the partition for a specific time interval. | 300 seconds |
| Entitled Processing Units | Entitled processing units to a partition for a specific time interval. | 300 seconds |
| Entitled Processing Units Used (%) | (Utilized processing units/Entitled processing units) × 100. | 300 seconds |
LPAR maximum CPU capacity
The following metric is provided for how much maximum CPU capacity is being used.
| Metric | Description | Granularity |
|---|---|---|
| Maximum CPU Capacity Utilization (%) | (Utilized processing units/Current virtual processing units) × 100. | 300 seconds |
LPAR memory
The following metrics are provided for memory related to each partition:
| Metric | Description | Granularity |
|---|---|---|
| Logical Memory | Logical memory in megabyte of the partition during the interval. | 300 seconds |
| Backed Physical | Physical memory from the Shared Memory pool that is backing the partition's logical address space. | 300 seconds |
| Total IO | Size of memory the partition is entitled to I/O map (in megabytes). | 300 seconds |
| Mapped IO | Size of memory the partition has I/O mapped (in megabytes). | 300 seconds |
LPAR network
Virtual ethernet adapters
The following metrics are provided for virtual ethernet adapters related to each partition:
| Metric | Description | Granularity |
|---|---|---|
| VLAN ID | VLAN ID of the virtual ethernet adapter. | 300 seconds |
| Adapter ID | ID of the shared ethernet adapter. | 300 seconds |
| VIOS ID | ID of the VIOS the adapter is connected to. | 300 seconds |
| VSwitch ID | Vswitch ID of the virtual ethernet adapter. | 300 seconds |
| Physical Location | Physical location of the adapter. | 300 seconds |
| Packets Sent/s | Number of physical packets that are sent by the adapter for the time interval. | 300 seconds |
| Packets Received/s | Number of physical packets that are received by the adapter for the time interval. | 300 seconds |
| Packets Dropped/s | Number of physical packets that are dropped by the adapter for the time interval. | 300 seconds |
| Bytes Sent/s | Number of bytes sent to the physical adapter that is associated with a virtual adapter. It is per second for a specific time interval. | 300 seconds |
| Bytes Received/s | Number of bytes received by the physical adapter that is associated with the virtual adapter. It is per second for a specific time interval. | 300 seconds |
| Bytes Transferred/s | Number of physical packets that are dropped by the adapter for the time interval. | 300 seconds |
| Bytes Transferred Physical/s | Number of bytes that are transferred by physical adapter for a specific time interval. | 300 seconds |
SR-IOV logical ports
The following metrics are provided for SR-IOV logical ports related to each partition:
| Metric | Description | Granularity |
|---|---|---|
| DRC-Index | DRC index of the SR-IOV logical port. | 300 seconds |
| VNIC Device Mode | Virtual Network Interface Controller (VNIC) device mode. Valid values are NonVNIC, SharedVNIC, and DedicatedVNIC. | 300 seconds |
| Configuration Type | Configuration type of the SR-IOV logical port: Nonconfigured, Ethernet, FC, FCoE, and RoCE. | 300 seconds |
| Physical Port ID | Physical Port ID of the associated physical adapter for the SR-IOV logical port. | 300 seconds |
| Physical Location | Physical location code of the port. | 300 seconds |
| Packets Sent/s | Number of physical packets that are sent by the adapter for the time interval. | 300 seconds |
| Packets Received/s | Number of physical packets that are received by the adapter for the time interval. | 300 seconds |
| Packets Dropped/s | Number of physical packets that are dropped by the adapter for the time interval. | 300 seconds |
| Bytes Sent/s | Number of bytes sent to the physical adapter that is associated with the virtual adapter. It is per second for a particular time interval. | 300 seconds |
| Bytes Received/s | Number of bytes received by the physical adapter that is associated with the virtual adapter. It is per second for a particular time interval. | 300 seconds |
| Bytes Transferred/s | Number of bytes transferred per second for a particular time interval through the physical adapter that is associated with the virtual adapter. | 300 seconds |
| Error In/s | Number of errors that are received per second for a particular time interval. | 300 seconds |
| Error Out/s | Number of errors that are transmitted per second for a particular time interval. | 300 seconds |
LPAR storage
Generic virtual adapters
The following metrics are provided for generic virtual adapters related to each partition:
| Metric | Description | Granularity |
|---|---|---|
| ID | Id of the adapter. | 300 seconds |
| Type | Type of adapter. | 300 seconds |
| VIOS ID | Id of the VIOS the adapter is connected to. | 300 seconds |
| Physical Location | Physical location of the adapter. | 300 seconds |
| No. Of Reads/s | Number of read requests that are coming to the adapter per second for a particular time interval. | 300 seconds |
| No. Of Writes/s | Number of write requests that are coming to the adapter per second for a particular time interval. | 300 seconds |
| Bytes Read/s | Number of bytes that are read through the adapter per second for a particular time interval. | 300 seconds |
| Bytes Write/s | Number of bytes that are written through the adapter per second for a particular time interval. | 300 seconds |
| Bytes Transmitted/s | Number of bytes that are transmitted through the adapter per second for a particular time interval. | 300 seconds |
Virtual Fiber Channel adapters
The following metrics are provided for fiber channel adapters related to each partition:
| Metric | Description | Granularity |
|---|---|---|
| WWPN | WWPN of the Fiber Channel adapter. | 300 seconds |
| WWPN2 | WWPN2 of the Fiber Channel adapter. | 300 seconds |
| Physical Port WWPN | WWPN of the physical port. | 300 seconds |
| VIOS ID | Id of the VIOS the adapter is connected to. | 300 seconds |
| Physical Location | Physical location of the adapter. | 300 seconds |
| No. Of Reads/s | Number of read requests that are coming to the adapter per second for a particular time interval. | 300 seconds |
| No. Of Writes/s | Number of write requests that are coming to the adapter per second for a particular time interval. | 300 seconds |
| Bytes Read/s | Number of bytes that are read through the adapter per second for a particular time interval. | 300 seconds |
| Bytes Write/s | Number of bytes that are written through the adapter per second for a particular time interval. | 300 seconds |
| Bytes Transmitted/s | Number of bytes that are transmitted through the adapter per second for a particular time interval. | 300 seconds |
| Running Speed (in GBps) | Running speed of the Fiber channel adapter in GBPS. | 300 seconds |
Virtual I/O server (VIOS)
Virtual I/O servers
The list of VIOSes for each managed systems is displayed. For more details, go to the VIOS dashboard by clicking any of the VIOSes.
The following KPIs are provided for each VIOSes:
| Metric | Description | Granularity |
|---|---|---|
| Partition ID | Partition ID of the specific VIOS. | 300 seconds |
| Name | Name of the VIOS. | 300 seconds |
| State | State of the VIOS. | 300 seconds |
| Mode | Mode of the processor. The value for dedicated processor is donated, and the values for shared processors are capped or uncapped. | 300 seconds |
| Utilized memory (%) | (Utilized memory in MB/Assigned memory in MB) × 100. | 300 seconds |
| Entitled Processing Units (%) | (Utilized processing units/Entitled processing units) × 100. | 300 seconds |
VIOS processor utilization
The following metrics are provided for processor related to each Virtual I/O Server:
| Metric | Description | Granularity |
|---|---|---|
| Utilized Processing Units | Total processing units that are used for a particular time interval. | 300 seconds |
| Max Processing Units | Max processing units that are assigned to the partition for a particular time interval. | 300 seconds |
| Entitled Processing Units | Entitled processing units to a partition for a specific time interval. | 300 seconds |
| Entitled Processing Units Used (%) | (Utilized processing units/Entitled processing units) × 100. | 300 seconds |
VIOS maximum CPU capacity
The percentage of the maximum physical CPU available to this VIOS that is actually used.
| Metric | Description | Granularity |
|---|---|---|
| Maximum CPU Capacity Utilization (%) | (Utilized processing units/Current virtual processing units) × 100. | 300 seconds |
VIOS memory
The following metrics are provided for memory related to each VIOS:
| Metric | Description | Granularity |
|---|---|---|
| Utilized Memory | Overall Memory Utilization (in megabytes) for the time interval. | 300 seconds |
| Assigned Memory | Assigned memory to the VIOS. | 300 seconds |
| Utilized Memory (%) | (Utilized memory in MB/Assigned memory in MB) × 100 . | 300 seconds |
VIOS network
Generic adapters
The following metrics are provided for generic adapters related to each VIOS:
| Metric | Description | Granularity |
|---|---|---|
| ID | Adapter ID. | 300 seconds |
| Type | Type of the adapter. | 300 seconds |
| Physical Location | Physical location of the adapter. | 300 seconds |
| Packets Sent/s | Number of physical packets that are sent by the adapter for the time interval. | 300 seconds |
| Packets Received/s | Number of physical packets that are received by the adapter for the time interval. | 300 seconds |
| Packets Dropped/s | Number of physical packets that are dropped by the adapter for the time interval. | 300 seconds |
| Sent Bytes/s | Number of bytes sent to the physical adapter that is associated with the virtual adapter. It is per second for a particular time interval. | 300 seconds |
| Received Bytes/s | Number of bytes received by the physical adapter that is associated with the virtual adapter. It is per second for a particular time interval. | 300 seconds |
| Transferred Bytes/s | Number of physical packets that are dropped by the adapter for the time interval. | 300 seconds |
Shared adapters
The following metrics are provided for shared adapters related to each VIOS:
| Metric | Description | Granularity |
|---|---|---|
| ID | Adapter ID. | 300 seconds |
| Type | Type of the adapter. | 300 seconds |
| Bridged Adapters | List of ids of generic adapters attached to a shared ethernet adapter (SEA). | 300 seconds |
| Physical Location | Physical location of the adapter. | 300 seconds |
| Packets Sent/s | Number of physical packets that are sent by the adapter for the time interval. | 300 seconds |
| Packets Received/s | Number of physical packets that are received by the adapter for the time interval. | 300 seconds |
| Packets Dropped/s | Number of physical packets that are dropped by the adapter for the time interval. | 300 seconds |
| Sent Bytes/s | Number of bytes sent to the physical adapter that is associated with the virtual adapter. It is per second for a particular time interval. | 300 seconds |
| Received Bytes/s | Number of bytes received by the physical adapter that is associated with the virtual adapter. It is per second for a particular time interval. | 300 seconds |
| Transferred Bytes/s | Number of physical packets that are dropped by the adapter for the time interval. | 300 seconds |
Virtual ethernet adapters
The following metrics are provided for virtual ethernet adapters related to each VIOS:
| Metric | Description | Granularity |
|---|---|---|
| VLAN ID | VLAN ID. | 300 seconds |
| VSwitch ID | Virtual switch ID. | 300 seconds |
| Physical Location | Physical location of the adapter. | 300 seconds |
| Packets Sent/s | Number of physical packets that are sent by the adapter for the time interval. | 300 seconds |
| Packets Received/s | Number of physical packets that are received by the adapter for the time interval. | 300 seconds |
| Packets Dropped/s | Number of physical packets that are dropped by the adapter for the time interval. | 300 seconds |
| Bytes Sent/s | Number of bytes sent to the physical adapter that is associated with the virtual adapter. It is per second for a particular time interval. | 300 seconds |
| Bytes Received/s | Number of bytes received by the physical adapter that is associated with the virtual adapter. It is per second for a particular time interval. | 300 seconds |
| Bytes Transferred/s | Number of physical packets that are dropped by the adapter for the time interval. | 300 seconds |
| Bytes Transferred Physical/s | Number of bytes that are transferred by the physical adapter for a particular time interval. | 300 seconds |
SR-IOV logical port
The following metrics are provided for the SR-IOV logical port related to each VIOS:
| Metric | Description | Granularity |
|---|---|---|
| DRC-Index | DRC index of the SR-IOV logical port. | 300 seconds |
| Physical Location | Physical Location Code of the port. | 300 seconds |
| Packets Sent/s | Number of physical packets that are sent by the adapter for the time interval. | 300 seconds |
| Packets Received/s | Number of physical packets that are received by the adapter for the time interval. | 300 seconds |
| Bytes Sent/s | Number of bytes sent to the physical adapter that is associated with the virtual adapter. It is per second for a particular time interval. | 300 seconds |
| Bytes Received/s | Number of bytes received by the physical adapter that is associated with the virtual adapter. It is per second for a particular time interval. | 300 seconds |
| Bytes Transferred/s | Number of bytes transferred per second for a particular time interval through the physical adapter that is associated with the virtual adapter. | 300 seconds |
| Error In/s | Number of errors that are received per second for a particular time interval. | 300 seconds |
| Error Out/s | Number of errors that are transmitted per second for a particular time interval. | 300 seconds |
VIOS storage
Generic physical adapters
The following metrics are provided for generic physical adapters related to each VIOS:
| Metric | Description | Granularity |
|---|---|---|
| ID | Id of the adapter. | 300 seconds |
| Type | Type of adapter. | 300 seconds |
| Physical Location | Physical location of the adapter. | 300 seconds |
| No. Of Reads/s | Number of read requests that are coming to the adapter per second for a particular time interval. | 300 seconds |
| No. Of Writes/s | Number of write requests that are coming to the adapter per second for a particular time interval. | 300 seconds |
| Bytes Read/s | Number of bytes that are read through the adapter per second for a particular time interval. | 300 seconds |
| Bytes Write/s | Number of bytes that are written through the adapter per second for a particular time interval. | 300 seconds |
| Bytes Transmitted/s | Number of bytes that are transmitted through the adapter per second for a particular time interval. | 300 seconds |
Generic virtual adapters
The following metrics are provided for generic virtual adapters related to each VIOS:
| Metric | Description | Granularity |
|---|---|---|
| ID | Id of the adapter. | 300 seconds |
| Type | Type of adapter. | 300 seconds |
| Physical Location | Physical location of the adapter. | 300 seconds |
| No. Of Reads/s | Number of read requests that are coming to the adapter per second for a particular time interval. | 300 seconds |
| No. Of Writes/s | Number of write requests that are coming to the adapter per second for a particular time interval. | 300 seconds |
| Bytes Read/s | Number of bytes that are read through the adapter per second for a particular time interval. | 300 seconds |
| Bytes Write/s | Number of bytes that are written through the adapter per second for a particular time interval. | 300 seconds |
| Bytes Transmitted/s | Number of bytes that are transmitted through the adapter per second for a particular time interval. | 300 seconds |
Fiber Channel adapters
The following metrics are provided for fiber channel adapters related to each VIOS:
| Metric | Description | Granularity |
|---|---|---|
| ID | Id of the adapter. | 300 seconds |
| WWPN | World Wide Port Name (WWPN) of the Fiber Channel adapter. | 300 seconds |
| Number of Ports | Number of ports that are configured in each Fiber Channel Adapters. | 300 seconds |
| Physical Location | Physical location of the adapter. | 300 seconds |
| No. Of Reads/s | Number of read requests that are coming to the adapter per second for a particular time interval. | 300 seconds |
| No. Of Writes/s | Number of write requests that are coming to the adapter per second for a particular time interval. | 300 seconds |
| Bytes Read/s | Number of bytes that are read through the adapter per second for a particular time interval. | 300 seconds |
| Bytes Writes | Number of bytes that are written through the adapter per second for a particular time interval. | 300 seconds |
| Bytes Transmitted/s | Number of bytes that are transmitted through the adapter per second for a particular time interval. | 300 seconds |
| Running Speed (in GBps) | Running speed of the Fiber channel adapter in GBPS. | 300 seconds |
Shared storage pool
The following metrics are provided for the shared storage pool related to each VIOS:
| Metric | Description | Granularity |
|---|---|---|
| ID | Id of the adapter. | 300 seconds |
| No. Of Reads/s | Number of read requests that are coming to the adapter per second for a particular time interval. | 300 seconds |
| No. Of Writes/s | Number of write requests that are coming to the adapter per second for a particular time interval. | 300 seconds |
| Bytes Read/s | Number of bytes that are read through the adapter per second for a particular time interval. | 300 seconds |
| Bytes Write/s | Number of bytes that are written through the adapter per second for a particular time interval. | 300 seconds |
| Bytes Transmitted/s | Number of bytes that are transmitted through the adapter per second for a particular time interval. | 300 seconds |
| Total Space | Total space of the shared storage pool at the end of the time interval. | 300 seconds |
| Used Space | Used space of the shared storage pool at the end of the time interval. | 300 seconds |
Managed system network
SR-IOV adapters
The following metrics are provided for SR-IOV adapters related to each managed system:
| Metric | Description | Granularity |
|---|---|---|
| DRC-Index | DRC index of the SR-IOV adapter. | 300 seconds |
| Physical Port ID | ID that is assigned to the physical port. | 300 seconds |
| Physical Location | Physical location code of the port. | 300 seconds |
| Packets Sent/s | Number of packets sent to the physical adapter that is associated with the LPAR or VIOS virtual adapter per second for a particular time interval. | 300 seconds |
| Packets Received/s | Number of packets received by the physical adapter that is associated with the LPAR or VIOS virtual adapter per second for a particular time interval. | 300 seconds |
| Packets Dropped/s | Number of packets dropped by the physical adapter that is associated with the LPAR or VIOS virtual adapter per second for a particular time interval. | 300 seconds |
| Bytes Sent/s | Number of bytes sent to the physical adapter that is associated with the LPAR or VIOS virtual adapter per second for a particular time interval. | 300 seconds |
| Bytes Received/s | Number of bytes received by the physical adapter that is associated with the LPAR or VIOS virtual adapter per second for a particular time interval. | 300 seconds |
| Bytes Transferred/s | Total number of bytes that are transferred per second for a particular time interval. It’s the summation of sentBytes and receivedBytes. | 300 seconds |
| Error In/s | Number of errors that are received per second for a particular time interval. | 300 seconds |
| Error Out/s | Number of errors that are transmitted per second for a particular time interval. | 300 seconds |
vNIC details
The following metrics are provided for vNIC adapters that are related to each managed system:
| Metric | Description | Granularity |
|---|---|---|
| Virtual Slot Number | Virtual slot number of the vNIC adapter. | 300 seconds |
| LPAR ID | LPAR ID that is associated with the vNIC adapter. | 300 seconds |
| Dynamic Reconfig ID | Dynamic reconfiguration connector ID of the vNIC adapter. | 300 seconds |
| Port VLAN ID | Port VLAN ID that is associated with the vNIC adapter. | 300 seconds |
| MAC Address | MAC address that is associated with the vNIC adapter. | 300 seconds |
| OS Device | OS device name that is associated with the vNIC adapter. | 300 seconds |
| Desired Mode | Preferred mode of operation for the vNIC adapter. | 300 seconds |
| LPAR | LPAR that is associated with the vNIC adapter. | 300 seconds |
| Device Type | Device type that is associated with the backing device. | 300 seconds |
| Status | Status of the backing device. | 300 seconds |
| Fail-Over Priority | Fail-over priority for the backing device. | 300 seconds |
| Related SRIOV Adapter ID | Backed SR-IOV adapter ID that is associated with the vNIC adapter. | 300 seconds |
| SRIOV Physical Port ID | Backed SR-IOV physical port ID that is associated with the vNIC adapter. | 300 seconds |
Managed system energy monitoring
Energy monitoring provides information about the power consumption data of a managed system, along with generated heat from inlet, CPU, and baseboards. Make sure that the EnergyMonitorEnabled parameter is enabled for the managed system.
| Metric | Description | Granularity |
|---|---|---|
| UUID | Universally Unique IDentifier (UUID) of the managed system. | 300 seconds |
| Name | Name of the managed system. | 300 seconds |
| Power Consumption (Watts) | Power that is consumed by the system for the specific interval, in watts. | 300 seconds |
| Machine Type - Model | Machine type and model of the managed system. | 300 seconds |
| Serial Number | Serial number of the managed system. | 300 seconds |
| Sample Type | Type of the sample. | 300 seconds |
| Entity Id | The ID of the entity. The value can be for inlet, CPU, or baseboard. | 300 seconds |
| Entity Instance | Instance name of the entity. The value can be for inlet, CPU, or baseboard. | 300 seconds |
| Temperature Reading | Heat that is generated by the entities for the time interval, in Celsius. | 300 seconds |
To set alerts for the Inlet temperatures metrics, complete the following steps:
-
From the navigation menu in the Instana UI, select Settings > Team Settings > Alerts.
-
Create an alert. For more information about creating an alert, see Configure an alert.
-
On the Create A New Event dashboard, enter the following values in the Conditions section:
- Entity Type:
pHMC System - Metric:
Inlet Temperature Reading > inletTemperatures.{entityid}.temperatureReading - Matching Operator:
contains - entityId:
<_Entity ID in Inlet Temperatures Table_> - Aggregation:
_min_ - Operator:
>= - Count:
<_threshold count_>
- Entity Type:
To set the temperature reading alert of CPU and Baseboard, follow the preceding steps and enter the following values in the Condition section:
-
Metric:
CPU Temperature Reading > cpuTemperatures.{entityid}.temperatureReading -
entityId:
<_Entity ID in CPU Temperatures Table_> -
Metric:
Baseboard Temperature Reading > baseBoardTemperatures.{entityid}.temperatureReading -
entityId:
<_Entity ID in Baseboard Temperatures Table_>
Manage events from managed system and HMC console
Critical events gets triggered from managed systems and HMCs due to some failures or incidents. The following types of events are sent to Instana for display in the event page:
- Critical hardware messages from managed systems.
- Critical console events from HMCs.
Troubleshoot
-
403 Forbidden The HTTP 403 Forbidden response status code indicates that the server understands the request but refuses to authorize it.
Solution: Verify the credentials that are provided in the
configuration.yamlfile with all the required permissions to the user. -
204 No Content The HTTP 204 No Content success status response code indicates that a request has succeeded but server does not return any contents.
Solution: Power HMC sensor uses aggregated metrics and API query data in last 5 minutes (see the poll rate in the configuration) from Power HMC. Sometimes there is mismatch in the timestamp because of different time zone of the HMC server. Hence, API returns the
204code because no contents are available. To workaround this problem, set the timezone of the Power HMC server to UTC. -
Import self-signed certificate that are used by Power HMC server If Power HMC server uses a self-signed certificate, make sure that it is imported into the jvm's cacert. Also, if you see following exception in the log, it indicates that Power HMC server uses a self-signed certificate, and it needs to be imported into the jvm's cacert.
sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target. PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target.Solution: Import a self-signed certificate by following the instructions from Self-Signed Certificate.
-
The self-signed certificate has a invalid Subject Alternate Name(SAN) The server certificate is invalid if the SAN does not have the expected IP address.
Solution: Correct the server certificate, and import it again.