EATON-PXG-MIB

All MIBs › EATON-PXG-MIB

Organization: Eaton Corporation

Last Updated: 2008-01-30

Category: Domain: Power/UPS, Vendor: Eaton

Description: Eaton Power Xpert Gateway MIB for managing the Eaton PXG network card providing UPS and power device monitoring via SNMP.

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 EATON-PXG-MIB?

This is an Eaton-specific MIB for the Power Xpert Gateway (PXG) network management card, which provides SNMP-based monitoring for Eaton UPS units and other power distribution devices connected through the gateway. It exposes fault/event data organized around a general event log (eventID, eventSequenceIndex, eventDescription, eventValue) and an active alarms table (activeAlarmsTable/activeAlarmsEntry with alarmID, alarmSequenceIndex, alarmDescription, alarmValue, alarmLevel, and a count of currently active alarms via numAlarmsPresent). Its core purpose is hardware status monitoring for critical power infrastructure: active alarms and their severity level reveal conditions such as UPS battery issues, power supply faults, overload, or loss of utility power, essential for data-center and facility power-health monitoring. It is built on Eaton's proprietary "Toolkit-enabled" PXG framework rather than a single IETF standard, though power/UPS MIBs of this kind commonly coexist with the standard UPS-MIB (RFC 1628) on the same device. It is typically deployed on Eaton UPS systems and power distribution equipment in data centers and critical facilities, where facilities/IT operations staff monitor active alarms to catch power-related faults before they cause an outage. Engineers can download the EATON-PXG-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in EATON-PXG-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

Eaton Power Xpert Gateway (PXG) card
Eaton UPS and power distribution equipment

Monitoring Examples

An operator would poll numAlarmsPresent to get a quick count of active problems on the connected Eaton power equipment, then walk activeAlarmsTable/activeAlarmsEntry to read alarmID, alarmDescription, and alarmLevel for each active condition, such as a UPS on battery, low battery, or overload alarm. The eventID/eventDescription/eventValue objects provide a historical event log entry for each state change, letting an administrator correlate a rise in numAlarmsPresent with a specific power event like a utility power failure or UPS bypass activation.

What Can Be Monitored

active alarm count
active alarm ID, description, and severity level
power event log entries

Imported Objects

From EATON-OIDS

powerChain

OBJECT-IDENTITY

From ENTITY-MIB

entPhysicalName

OBJECT-TYPE

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Gauge32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SNMPv2-TC

TimeStamp

How to Use in IPNetwork Monitor

Example using numAlarmsPresent OID:

Select an Eaton Power Xpert Gateway (PXG) card / UPS and power distribution equipment 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 numAlarmsPresent into the Find box to locate it in the OID tree, then select it and click OK. The present number of active alarm conditions. 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 Gauge32-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

OID symbolic	OID numeric	Type	Access	Description
pxgMIB	1.3.6.1.4.1.534.8.1			The MIB module for objects and notifications supported by Eaton's Toolkit-enabled Power Xpert Gateways. Copyright (C) Eaton Corporation (2006-2007).
pxgNotifications	1.3.6.1.4.1.534.8.1.0
NTF powerChainCriticalAlarmEvent	1.3.6.1.4.1.534.8.1.0.1			A Critical Alarm has occurred in a Power Chain Device. Alarm and source information are contained in the OBJECTS.
NTF powerChainCautionaryAlarmEvent	1.3.6.1.4.1.534.8.1.0.2			A Cautionary Alarm has occurred in a Power Chain Device. Alarm and source information are contained in the OBJECTS.
NTF powerChainAlarmEventAcknowledged	1.3.6.1.4.1.534.8.1.0.3			A user has Acknowledged a Critical or Cautionary Alarm. This does NOT clear or 'close' a latched Alarm. Alarm and source information are contained in the OBJECTS.
NTF powerChainEventCleared	1.3.6.1.4.1.534.8.1.0.4			The condition that raised the Alarm or Event no longer exists; the three types of Events have different outcomes: 1) A latching Alarm is still considered active and will need to be Closed by a user Close Acknowledgement. 2) A non-latching Alarm is closed and its Alarm sequence completed. 3) An Event is closed and its Event sequence completed. Alarm and source information are contained in the OBJECTS.
NTF powerChainEvent	1.3.6.1.4.1.534.8.1.0.5			A non-alarming Event has occurred in a Power Chain Device. Event and source information are contained in the OBJECTS.
NTF powerChainAlarmEventClosed	1.3.6.1.4.1.534.8.1.0.6			A user has Closed a Critical or Cautionary Alarm. This Close Acknowledgement has 'closed' a latched Alarm and completed its sequence. Alarm and source information are contained in the OBJECTS.
NTF powerChainCriticalAlarm	1.3.6.1.4.1.534.8.1.0.7			A Critical Alarm has occurred in a Power Chain Device. Alarm and source information are contained in the OBJECTS.
NTF powerChainCautionaryAlarm	1.3.6.1.4.1.534.8.1.0.8			A Cautionary Alarm has occurred in a Power Chain Device. Alarm and source information are contained in the OBJECTS.
NTF powerChainAlarmAcknowledged	1.3.6.1.4.1.534.8.1.0.9			A user has Acknowledged a Critical or Cautionary Alarm. This does NOT clear or 'close' a latched Alarm. Alarm and source information are contained in the OBJECTS.
NTF powerChainAlarmCleared	1.3.6.1.4.1.534.8.1.0.10			The condition that raised the Alarm or Event no longer exists; the three types of Events have different outcomes: 1) A latching Alarm is still considered active and will need to be Closed by a user Close Acknowledgement. 2) A non-latching Alarm is closed and its Alarm sequence completed. 3) An Event is closed and its Event sequence completed. Alarm and source information are contained in the OBJECTS.
NTF powerChainAlarmClosed	1.3.6.1.4.1.534.8.1.0.11			A user has Closed a Critical or Cautionary Alarm. This Close Acknowledgement has 'closed' a latched Alarm and completed its sequence. Alarm and source information are contained in the OBJECTS.
NTF powerChainAlarmUpdated	1.3.6.1.4.1.534.8.1.0.12			An update to the alarm entry at alarmID has occurred; however, the alarmLevel has not changed due to this update. This is normally seen with latching alarms when condition that caused the alarm is removed or recurs before the alarm has been closed. Alarm and source information are contained in the OBJECTS.
pxgMIBObjects	1.3.6.1.4.1.534.8.1.1
eventInfo	1.3.6.1.4.1.534.8.1.1.1
I32 eventID	1.3.6.1.4.1.534.8.1.1.1.1	Integer32	accessible-for-notify	A unique identifier for the event.
I32 eventSequenceIndex	1.3.6.1.4.1.534.8.1.1.1.2	Integer32	accessible-for-notify	A unique identifier for a sequence of events using the same EventId.
STR eventDescription	1.3.6.1.4.1.534.8.1.1.1.3	SnmpAdminString	accessible-for-notify	A human-readable text description of the Event or Alarm.
STR eventValue	1.3.6.1.4.1.534.8.1.1.1.4	SnmpAdminString	accessible-for-notify	A human-readable text representation of the source and value of the node that caused the Event or Alarm. This text should be of the form 'SourcePath = Value' where SourcePath is the address of the node within the BACnetWS+ node tree, as accessed with web service calls.
alarms	1.3.6.1.4.1.534.8.1.1.2
G32 numAlarmsPresentEx	1.3.6.1.4.1.534.8.1.1.2.1	Gauge32	read-only	The present number of active alarm conditions.
activeAlarmsTable	1.3.6.1.4.1.534.8.1.1.2.2		not-accessible	A list of alarm table entries. The table contains zero, one, or many rows at any moment, depending upon the number of alarm conditions in effect. The table is initially empty at agent startup. The agent creates a row in the table each time an alarm condition is detected and deletes that row when that alarm is no longer active. The numbering of the table entries, using alarmID, is sparse. The number of rows in the table at any given time is reflected by the value of numAlarmsPresent.
activeAlarmsEntry	1.3.6.1.4.1.534.8.1.1.2.2.1		not-accessible	An entry containing information applicable to a particular alarm.
I32 alarmID	1.3.6.1.4.1.534.8.1.1.2.2.1.1	Integer32	accessible-for-notify	A unique identifier for the alarm. This var is not-accessible when browsing the table.
I32 alarmSequenceIndex	1.3.6.1.4.1.534.8.1.1.2.2.1.2	Integer32	read-only	A unique identifier for a sequence of alarms using the same alarmID.
STR alarmDescription	1.3.6.1.4.1.534.8.1.1.2.2.1.3	SnmpAdminString	read-only	A human-readable text description of the Event or Alarm.
STR alarmValue	1.3.6.1.4.1.534.8.1.1.2.2.1.4	SnmpAdminString	read-only	A human-readable text representation of the source and value of the node that caused the Event or Alarm. This text should be of the form 'SourcePath = Value' where SourcePath is the address of the node within the BACnetWS+ node tree, as accessed with web service calls.
INT alarmLevel	1.3.6.1.4.1.534.8.1.1.2.2.1.5	INTEGER	read-only	Enumerated value that tells the present level (status) of an activeAlarmsEntry. critical (1) - The alarm is at a critical level. cautionary (2) - The alarm is at a cautionary level (a less severe level than critical). acknowledged (3) - The user has acknowledged, but not yet closed, the cautionary or critical alarm. active (4) - Not used; would be a status for an event. cleared (5) - A transient internal level, not normally seen. closed (6) - A transient internal level, not normally seen because the activeAlarmsEntry is removed when closed. unknown (7) - Alarm status is not known. Not normally seen.
TIM alarmTime	1.3.6.1.4.1.534.8.1.1.2.2.1.6	TimeStamp	read-only	The value of sysUpTime when the alarm condition was detected. If the alarm condition was detected at the time of agent startup and presumably existed before agent startup, the value of alarmTime shall equal 0.
pxgConformance	1.3.6.1.4.1.534.8.1.2
tkEventGroup	1.3.6.1.4.1.534.8.1.2.1			The eventInfo objects that are only accessible to notifications.
tkAlarmTableGroup	1.3.6.1.4.1.534.8.1.2.2			The activeAlarms objects that are accessible to MIB browsers and notifications, except that alarmID is only accessible to notifications.
tkEventNotifyGroup	1.3.6.1.4.1.534.8.1.2.3			The Alarm and Event notifications which use the eventInfo objects.
tkAlarmNotifyGroup	1.3.6.1.4.1.534.8.1.2.4			The Alarm notifications which use the activeAlarmTable objects.
tkSimpleCompliance	1.3.6.1.4.1.534.8.1.2.5			The compliance statement for Power Xpert Gateway implementations that do not implement the activeAlarmsTable.
tkAlarmsTableCompliance	1.3.6.1.4.1.534.8.1.2.6			The compliance statement for Power Xpert Gateway implementations that do implement the activeAlarmsTable. The eventInfo objects are still used for Event-only notices.

RFC description

Reports power chain alarms and notifications from Eaton Power Xpert Gateway systems.

Start monitoring Eaton Power Xpert Gateway (PXG) card / UPS and power distribution equipment 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 EATON-PXG-MIB