EATON-PXG-MIB: View SNMP OID List / Download MIB

VENDOR: EATON CORPORATION


 Home MIB: EATON-PXG-MIB
Download as:   
SNMPv2-CONF, ENTITY-MIB, SNMP-FRAMEWORK-MIB, SNMPv2-SMI, EATON-OIDS, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 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
         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.
         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.
         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.
         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.
         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.
         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.
         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.
         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.
         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.
         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.
         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.
         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
             eventID 1.3.6.1.4.1.534.8.1.1.1.1 integer32 no-access
A unique identifier for the event.
             eventSequenceIndex 1.3.6.1.4.1.534.8.1.1.1.2 integer32 no-access
A unique identifier for a sequence of events using the same EventId.
             eventDescription 1.3.6.1.4.1.534.8.1.1.1.3 snmpadminstring no-access
A human-readable text description of the Event or Alarm.
             eventValue 1.3.6.1.4.1.534.8.1.1.1.4 snmpadminstring no-access
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
             numAlarmsPresent 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 no-access
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 no-access
An entry containing information applicable to a particular alarm.
                     alarmID 1.3.6.1.4.1.534.8.1.1.2.2.1.1 integer32 no-access
A unique identifier for the alarm. This var is not-accessible when browsing the table.
                     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.
                     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.
                     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.
                     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. Enumeration: 'unknown': 7, 'acknowledged': 3, 'critical': 1, 'closed': 6, 'active': 4, 'cleared': 5, 'cautionary': 2.
                     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.