EATON-PXG-MIB

File: EATON-PXG-MIB.mib (18151 bytes)

Imported modules

SNMPv2-SMI SNMPv2-TC ENTITY-MIB
SNMP-FRAMEWORK-MIB SNMPv2-CONF EATON-OIDS

Imported symbols

MODULE-IDENTITY OBJECT-TYPE NOTIFICATION-TYPE
Gauge32 Integer32 TimeStamp
entPhysicalName SnmpAdminString MODULE-COMPLIANCE
OBJECT-GROUP NOTIFICATION-GROUP powerChain

Defined Types

ActiveAlarmsEntry  
SEQUENCE    
  alarmID Integer32
  alarmSequenceIndex Integer32
  alarmDescription SnmpAdminString
  alarmValue SnmpAdminString
  alarmLevel INTEGER
  alarmTime TimeStamp

Defined Values

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).
MODULE-IDENTITY    

pxgMIBObjects 1.3.6.1.4.1.534.8.1.1
OBJECT IDENTIFIER    

eventInfo 1.3.6.1.4.1.534.8.1.1.1
OBJECT IDENTIFIER    

alarms 1.3.6.1.4.1.534.8.1.1.2
OBJECT IDENTIFIER    

eventID 1.3.6.1.4.1.534.8.1.1.1.1
A unique identifier for the event.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..2147483647  

eventSequenceIndex 1.3.6.1.4.1.534.8.1.1.1.2
A unique identifier for a sequence of events using the same EventId.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..2147483647  

eventDescription 1.3.6.1.4.1.534.8.1.1.1.3
A human-readable text description of the Event or Alarm.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  SnmpAdminString  

eventValue 1.3.6.1.4.1.534.8.1.1.1.4
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.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  SnmpAdminString  

numAlarmsPresent 1.3.6.1.4.1.534.8.1.1.2.1
The present number of active alarm conditions.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

activeAlarmsTable 1.3.6.1.4.1.534.8.1.1.2.2
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.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    ActiveAlarmsEntry

activeAlarmsEntry 1.3.6.1.4.1.534.8.1.1.2.2.1
An entry containing information applicable to a particular alarm.
Status: current Access: not-accessible
OBJECT-TYPE    
  ActiveAlarmsEntry  

alarmID 1.3.6.1.4.1.534.8.1.1.2.2.1.1
A unique identifier for the alarm. This var is not-accessible when browsing the table.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..2147483647  

alarmSequenceIndex 1.3.6.1.4.1.534.8.1.1.2.2.1.2
A unique identifier for a sequence of alarms using the same alarmID.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 1..2147483647  

alarmDescription 1.3.6.1.4.1.534.8.1.1.2.2.1.3
A human-readable text description of the Event or Alarm.
Status: current Access: read-only
OBJECT-TYPE    
  SnmpAdminString  

alarmValue 1.3.6.1.4.1.534.8.1.1.2.2.1.4
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.
Status: current Access: read-only
OBJECT-TYPE    
  SnmpAdminString  

alarmLevel 1.3.6.1.4.1.534.8.1.1.2.2.1.5
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.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER critical(1), cautionary(2), acknowledged(3), active(4), cleared(5), closed(6), unknown(7)  

alarmTime 1.3.6.1.4.1.534.8.1.1.2.2.1.6
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.
Status: current Access: read-only
OBJECT-TYPE    
  TimeStamp  

pxgNotifications 1.3.6.1.4.1.534.8.1.0
OBJECT IDENTIFIER    

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.
Status: current Access: read-only
NOTIFICATION-TYPE    

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.
Status: current Access: read-only
NOTIFICATION-TYPE    

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.
Status: current Access: read-only
NOTIFICATION-TYPE    

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.
Status: current Access: read-only
NOTIFICATION-TYPE    

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.
Status: current Access: read-only
NOTIFICATION-TYPE    

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.
Status: current Access: read-only
NOTIFICATION-TYPE    

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.
Status: current Access: read-only
NOTIFICATION-TYPE    

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.
Status: current Access: read-only
NOTIFICATION-TYPE    

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.
Status: current Access: read-only
NOTIFICATION-TYPE    

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.
Status: current Access: read-only
NOTIFICATION-TYPE    

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.
Status: current Access: read-only
NOTIFICATION-TYPE    

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.
Status: current Access: read-only
NOTIFICATION-TYPE    

pxgConformance 1.3.6.1.4.1.534.8.1.2
OBJECT IDENTIFIER    

tkEventGroup 1.3.6.1.4.1.534.8.1.2.1
The eventInfo objects that are only accessible to notifications.
Status: current Access: read-only
OBJECT-GROUP    

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.
Status: current Access: read-only
OBJECT-GROUP    

tkEventNotifyGroup 1.3.6.1.4.1.534.8.1.2.3
The Alarm and Event notifications which use the eventInfo objects.
Status: current Access: read-only
NOTIFICATION-GROUP    

tkAlarmNotifyGroup 1.3.6.1.4.1.534.8.1.2.4
The Alarm notifications which use the activeAlarmTable objects.
Status: current Access: read-only
NOTIFICATION-GROUP    

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.
Status: current Access: read-only
MODULE-COMPLIANCE    

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.
Status: current Access: read-only
MODULE-COMPLIANCE