EMPIRE-CALPARA-MIB

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › EMPIRE-CALPARA-MIB

Organization: CA Technologies

Last Updated: 2010-09-14

Category: Domain: Server/Host Monitoring, Vendor: Empire/SystemEDGE

Description: Empire SystemEDGE CA LPara MIB providing logical partition monitoring objects for CA-managed server environments.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is EMPIRE-CALPARA-MIB?

EMPIRE-CALPARA-MIB is a vendor MIB from Empire Technologies' SystemEDGE agent, providing an Agent Instrumentation Module (AIM) called "calpara" for monitoring IBM Logical Partitions (LPARs) managed via CA products. It exposes an inventory table of LPAR instances, including instance name, system name, and the associated Hardware Management Console (HMC) name and credentials used to query LPAR data. It is used to monitor the software status of virtualized IBM Power server partitions, letting an admin check LPAR instance entries to confirm each partition is correctly configured and reachable via its associated HMC, effectively monitoring partition/software configuration status. It depends on the broader Empire SystemEDGE MIB tree, indicated by its empire, unix, and traps object groups, for base agent conventions and trap definitions. It is typically deployed on IBM Power Systems/AIX environments using SystemEDGE agents for centralized LPAR configuration monitoring in enterprise data centers. Engineers can download the EMPIRE-CALPARA-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in EMPIRE-CALPARA-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

  • IBM Power Systems servers running AIX with logical partitions (LPARs)
  • SystemEDGE agent hosts

Monitoring Examples

The lparAimInstanceTable/lparAimInstanceEntry rows, keyed by lparAimInstanceUID, expose lparAimInstanceName, lparAimInstanceSysName, and lparAimInstanceHMCName so an admin can verify each monitored LPAR is correctly associated with its managing HMC. Checking lparAimInstanceRowStatus and lparAimInstanceDataStatus reveals whether a given LPAR instance's monitoring configuration is active or has an error, such as a stale or invalid HMC credential. The lparAimInstanceCount object gives a quick total of configured LPAR instances, useful for confirming none have silently disappeared from the inventory after an HMC change.

What Can Be Monitored

  • LPAR instance inventory
  • LPAR-to-HMC association
  • LPAR monitoring configuration status
  • LPAR instance count
Imported Objects

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-SMI

Counter64
Gauge32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
enterprises

From SNMPv2-TC

DisplayString
RowStatus

How to Use in IPNetwork Monitor

Example using lparAimStatvDiskKBRead OID:

Select an IBM Power Systems/AIX host with LPAR (monitored via CA SystemEDGE agent) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type lparAimStatvDiskKBRead into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. It reports the total number of KB read. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter64-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Monitors IBM Logical Partition (LPAR) system and resource utilization on SystemEDGE LPAR monitoring platforms.

Start monitoring IBM Power Systems/AIX host with LPARs (monitored via CA SystemEDGE agent) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download EMPIRE-CALPARA-MIB