AIX Monitoring

power-hmc-exporter

Map your entire PowerVM virtualization layer from the HMC: shared CPU & memory pools, the LPAR↔VIOS relationships, and SEA / NPIV / VSCSI attribution — as Prometheus metrics with the cross-reference labels already resolved. Turn hours of lsmap/fcstat correlation into a Grafana dashboard. Agentless, three dashboards included, per-LPAR annual license.

30-Day Returns
power-hmc-exporter $ 149

power-hmc-exporter — Your Entire PowerVM Virtualization Layer, Mapped

Most Power monitoring stops at the operating system: CPU, memory and disks inside each LPAR. The questions that actually cost you time live one layer down, in the virtualization — which shared pool is saturated, which VIOS is the bottleneck for which LPARs, which partition is hammering a physical Fibre Channel port through NPIV, which LPARs sit behind a given SEA and VLAN. Answering them today means hand-correlating lsmap, lshwres, fcstat and the HMC into a spreadsheet.

power-hmc-exporter reads the HMC’s Performance & Capacity Monitoring (PCM) facility and reconstructs that whole topology as live Prometheus metrics — processor and memory pools, the LPAR ↔ VIOS service relationships, and the SEA / NPIV / VSCSI mappings — with the cross-reference labels already resolved. The spreadsheet archaeology becomes a Grafana dashboard.

Power HMC Overview Grafana dashboard: HMC up, managed systems, poll duration, max PCM sample age, system processor and memory, top LPARs by CPU and NPIV

Processor & memory pools

Stop guessing about pool contention

Per-managed-system shared processor pool utilization and memory pool allocation versus total, entitled-versus-consumed for every LPAR and VIOS, capped-versus-uncapped borrowing against entitlement, and virtual-processor ceilings. See which pool is running tight and which partitions are borrowing from it — before your users feel it, not after.

Per-System dashboard: CPU and RAM allocation versus total, shared CPU pool utilization timeseries and Top 15 LPARs by processor units
LPAR ↔ VIOS

Every LPAR’s serving VIOS, resolved for you

Each per-LPAR network and storage series already carries the serving VIOS — the primary SEA VIOS (self-correcting on a SEA failover), the VIOS behind each NPIV physical port, the vhost serving each VSCSI disk. No id→name joins, no lsmap archaeology. A built-in noisy-neighbour view surfaces the VIOS uplinks each critical LPAR actually depends on.

labels already resolved
# the serving VIOS, SEA and VLAN are on the series itself —
# no join against lsmap / lshwres needed
power_hmc_lpar_network_received_bytes{
  system="sys01", lpar="lpar07",
  vlan_id="191", sea="ent10",
  vios="vios02"} 4.81e+08

power_hmc_lpar_vfc_read_bytes{
  lpar="lpar07", fc="fcs1",
  vios="vios02"} 1.66e+09
SEA · NPIV · VSCSI

Network and storage, attributed to the LPAR

SEA throughput broken down by the LPARs and VLANs riding it. NPIV virtual-FC traffic mapped to the physical FC port and the VIOS bridging it, with Top-N consumers per port. VSCSI I/O tied to the serving vhost. The cross-team questions that used to need a war-room — “who is saturating fcs1?”, “which LPAR is flooding this SEA?” — answered on one screen.

Per-System Fibre Channel section: NPIV throughput per physical FC port broken down by LPAR, and Top 15 NPIV consumers
Productivity & performance

Hours of correlation become seconds on a dashboard

Drill from a pool, SEA or FC-port spike straight to the offending LPAR and the VIOS bridging it — in seconds, not an afternoon of topas, lsmap and fcstat. Right-size pools and entitlements with evidence, charge back shared-adapter usage per LPAR, and cut the back-and-forth between your AIX, network and storage teams. One central exporter polls the HMC — nothing is installed on your partitions.

Per-LPAR dashboard: upstream VIOS bandwidth (noisy-neighbour diagnostics) showing FC port saturation and SEA throughput on the serving VIOS for a single partition

Three Grafana dashboards, included

Three ready-to-import dashboards ship in the package — import the JSON, pick your Prometheus datasource, done. From the estate-wide bird’s-eye view, down to a single managed system, down to one partition and the VIOS it leans on.
Per-System dashboard: VIOS CPU and memory utilization with Shared Ethernet Adapter throughput by VLAN and per-LPAR SEA usage

Performance firefighting

Drill from a saturated shared pool, SEA or physical FC port to the exact LPAR responsible and the VIOS serving it — across the whole estate, in seconds. No more correlating four tools by hand under pressure.

Capacity & right-sizing

Pool headroom, entitled-versus-consumed, uncapped borrowing and virtual-processor ceilings — the evidence you need to resize LPARs, rebalance shared pools and plan a hardware refresh before contention bites.

Shared-adapter chargeback

Attribute SEA and NPIV throughput per LPAR and per physical port. Turn shared VIOS network and SAN infrastructure into defensible per-tenant cross-charges, backed by real time-series data.

Cross-team clarity

One source of truth the AIX, network and storage teams can all read. The LPAR ↔ VIOS ↔ SEA ↔ FC-port chain is laid out explicitly, so escalations stop bouncing between teams and the spreadsheet archaeology goes away.

Specs & Requirements

Monitors IBM Power Systems via the HMC — managed systems, LPARs (AIX, IBM i, Linux on Power), and VIOS
HMC REST API enabled with PCM aggregation on. Verified against HMC V10 R3 SP1063
Exporter host Linux x86_64 (RHEL 9.x verified). Statically-linked binary, no runtime dependencies — runs on glibc and musl distributions alike
Connectivity TCP 12443 from the exporter host to each HMC
Network One TCP port (default 9876) for Prometheus scraping
Prometheus 2.x or 3.x (OpenMetrics compatible)
Grafana 9.x – 12.x (three dashboards included: overview, per-system, per-LPAR)
Service Hardened systemd unit and dedicated service account installed by install.sh

Deploy in 5 minutes

One central host, no agent on your partitions. Download the tarball, extract, run the installer — it creates the service account, places the binary, installs the systemd unit and an environment template (preserving any existing credentials). Set your HMC connection details and enable the service.

# 1. Extract and install
tar xzf power-hmc-exporter-v0.9.0-linux-amd64.tar.gz
cd power-hmc-exporter-v0.9.0-linux-amd64/
sudo ./install.sh

# 2. Set HMC host / user / password
sudo vi /etc/sysconfig/power-hmc-exporter

# 3. Enable and start the service
sudo systemctl enable --now power-hmc-exporter
journalctl -u power-hmc-exporter -f

Then add the scrape target to prometheus.yml and import the three dashboards under grafana/ via Dashboards → Import.

Configuration options
Variable Description
PHMC_HMC_HOST HMC hostname or IP (required)
PHMC_HMC_USER HMC user, typically hscroot (required)
PHMC_HMC_PASSWORD / PHMC_HMC_PASSWORD_FILE HMC password, inline or from a file (the file form is preferred)
PHMC_HMC_PORT HMC REST API port (default 12443)
PHMC_INSECURE_SKIP_VERIFY Skip TLS verification for self-signed HMC certificates (default false)
PHMC_LISTEN_ADDR Exporter HTTP listen address (default :9876)
PHMC_POLL_INTERVAL Interval between HMC poll cycles (default 60s)
PHMC_REQUEST_TIMEOUT Per-API-call timeout (default 30s)
PHMC_MAX_CONCURRENCY Max concurrent HMC requests per cycle (default 6; lower to 1 for sequential)

Licensing

Commercial per-LPAR annual subscription. The price is per monitored LPAR, per year — there is no separate fee for the host the exporter runs on. Volume discounts available for larger estates. A fully-functional 30-day free trial is included; contact legal@aixwatch.com for licensing inquiries.

Frequently Asked Questions

What does this give me that an in-LPAR exporter doesn’t?

The virtualization layer. An OS-level exporter sees CPU, memory and disks inside one partition. power-hmc-exporter sees the shared processor and memory pools, the VIOS serving each LPAR, and the SEA / NPIV / VSCSI mappings between them — the relationships that an in-LPAR agent has no visibility into, and that otherwise live only in lsmap / lshwres output.

Do I have to install anything on my LPARs?

No. power-hmc-exporter runs centrally and polls the HMC REST API. Your AIX, IBM i and Linux-on-Power partitions are untouched. That is also why licensing is counted per monitored LPAR rather than per installation.

How does it know which VIOS serves which LPAR?

It resolves the relationships from the PCM data and stamps them onto the metrics as labels — the primary SEA VIOS for each per-LPAR network series (self-correcting on a SEA failover), the VIOS behind each NPIV physical port, and the vhost serving each VSCSI disk. You filter and group by VIOS, SEA or FC port directly, with no id→name join.

Which HMC versions are supported?

It is verified against HMC V10 R3 SP1063 with the REST API enabled and PCM aggregation turned on for the managed systems of interest. The PCM endpoints used are the V10 nested ManagedSystem/LogicalPartition paths.

How fresh is the data?

The HMC PCM facility has an intrinsic processing latency of roughly 6–7 minutes on V10 — this is the console, not the exporter. The exporter exposes power_hmc_system_pcm_sample_age_seconds so you can alert on staleness (a 15-minute threshold is recommended).

Can it monitor more than one HMC?

Yes. Run one exporter instance per HMC and scrape them all into the same Prometheus; the Grafana dashboards aggregate across managed systems with a Managed System selector.

Where do the Fibre Channel error metrics come from?

HMC PCM does not expose FC port error counters, so those panels read aix_fcstat_* from a separate AIX_exporter scraped into the same Prometheus, joined on the AIX partition name. Where no AIX_exporter is present, the panels simply show No data and the rest of the dashboard is unaffected.

Does it run on any Linux distribution?

Yes. The binary is statically linked with no external dependencies — it has been verified on Ubuntu, Debian, RHEL/AlmaLinux, Fedora, Arch and Alpine (musl). RHEL 9.x is the reference platform.

What does the free trial include?

The 30-day trial is fully functional — the complete metric set and all three dashboards — so you can evaluate it against your own estate before purchasing per-LPAR subscriptions.