EATON-PXG-MIB
The MIB module for objects and notifications supported by
Eaton's Toolkit-enabled Power Xpert Gateways.
Copyright (C) Eaton Corporation (2006-2007).
- Source file
EATON-PXG-MIB- Last revised
- Identity
pxgMIB- Base OID
1.3.6.1.4.1.534.8.1
Imported Objects
| EATON-OIDS | powerChain |
| ENTITY-MIB | entPhysicalName |
| SNMP-FRAMEWORK-MIB | SnmpAdminString |
| SNMPv2-CONF | MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page) |
| SNMPv2-SMI | Gauge32 Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) |
| SNMPv2-TC | TimeStamp |
Net-SNMP examples using the eaton MIB directory Show commands
These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.
Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'EATON-PXG-MIB' -M '/opt/observium/mibs/eaton:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'EATON-PXG-MIB::pxgMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'EATON-PXG-MIB' -M '/opt/observium/mibs/eaton:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'EATON-PXG-MIB::pxgMIB'
Objects (19)
Showing 19 of 19 objects
Object legend
Table
Row
Column
Scalar
Node
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.1.3.6.1.4.1.534.8.1 |
||
.1.3.6.1.4.1.534.8.1.0 |
||
.1.3.6.1.4.1.534.8.1.1 |
||
.1.3.6.1.4.1.534.8.1.1.1 |
||
|
Integer32
|
.1.3.6.1.4.1.534.8.1.1.1.1 |
|
|
Integer32
|
.1.3.6.1.4.1.534.8.1.1.1.2 |
|
.1.3.6.1.4.1.534.8.1.1.1.3 |
||
.1.3.6.1.4.1.534.8.1.1.1.4 |
||
.1.3.6.1.4.1.534.8.1.1.2 |
||
.1.3.6.1.4.1.534.8.1.1.2.1 |
||
.1.3.6.1.4.1.534.8.1.1.2.2 |
||
.1.3.6.1.4.1.534.8.1.1.2.2.1 |
||
|
Integer32
|
.1.3.6.1.4.1.534.8.1.1.2.2.1.1 |
|
|
Integer32
|
.1.3.6.1.4.1.534.8.1.1.2.2.1.2 |
|
.1.3.6.1.4.1.534.8.1.1.2.2.1.3 |
||
.1.3.6.1.4.1.534.8.1.1.2.2.1.4 |
||
|
Enumeration
|
.1.3.6.1.4.1.534.8.1.1.2.2.1.5 |
|
.1.3.6.1.4.1.534.8.1.1.2.2.1.6 |
||
.1.3.6.1.4.1.534.8.1.2 |
Dependencies (8) 6 direct · 2 transitive Show tree and compile order Hide dependency details
Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.
Dependency tree
Dependency-first compile order
- SNMPv2-SMIrfc
- SNMPv2-TCrfc
- EATON-OIDSeaton
- IANA-ENTITY-MIBrfc
- SNMPv2-CONFrfc
- SNMP-FRAMEWORK-MIBrfc
- UUID-TC-MIBrfc
- ENTITY-MIBrfc
- EATON-PXG-MIBeatonselected
Conformance Groups (4)
|
The eventInfo objects that are only accessible to notifications.
|
.1.3.6.1.4.1.534.8.1.2.1
|
|
|
The activeAlarms objects that are accessible to MIB browsers
and notifications, except that alarmID is only accessible to notifications. |
.1.3.6.1.4.1.534.8.1.2.2
|
|
|
powerChainCriticalAlarmEvent powerChainCautionaryAlarmEvent powerChainAlarmEventAcknowledged powerChainEventCleared powerChainEvent powerChainAlarmEventClosed
The Alarm and Event notifications which use the eventInfo objects.
|
.1.3.6.1.4.1.534.8.1.2.3
|
|
|
powerChainCriticalAlarm powerChainCautionaryAlarm powerChainAlarmAcknowledged powerChainAlarmCleared powerChainAlarmClosed powerChainAlarmUpdated
The Alarm notifications which use the activeAlarmTable objects.
|
.1.3.6.1.4.1.534.8.1.2.4
|
Compliance Statements (2)
OID
.1.3.6.1.4.1.534.8.1.2.5The compliance statement for Power Xpert Gateway implementations that
do not implement the activeAlarmsTable.
do not implement the activeAlarmsTable.
Required groups
| mandatory | tkEventGroup | |
| mandatory | tkEventNotifyGroup |
OID
.1.3.6.1.4.1.534.8.1.2.6The compliance statement for Power Xpert Gateway implementations that
do implement the activeAlarmsTable.
The eventInfo objects are still used for Event-only notices.
do implement the activeAlarmsTable.
The eventInfo objects are still used for Event-only notices.
Required groups
| mandatory | tkEventGroup | |
| mandatory | tkAlarmTableGroup | |
| mandatory | tkEventNotifyGroup | |
| mandatory | tkAlarmNotifyGroup |
Notifications / Traps (12)
| Name | OID | Description |
|---|---|---|
.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. |
|
.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. |
|
.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. |
|
.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. |
|
.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. |
|
.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. |
|
.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. |
|
.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. |
|
.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. |
|
.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. |
|
.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. |
|
.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. |