GESINGLEUPS-MIB Table View

A list of input table entries.  The number of entries
is given by the value of upsInputNumLines.(*)

A list of output table entries.  The number of
entries is given by the value of upsOutputNumLines.(*)

A list of bypass table entries.  The number of
entries is given by the value of upsBypassNumLines.(*)

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 a condition is
detected and deletes that row when that condition no
longer pertains.  The agent creates the first row with
upsAlarmId equal to 1, and increments the value of
upsAlarmId each time a new row is created, wrapping to
the first free value greater than or equal to 1 when
the maximum value of upsAlarmId would otherwise be
exceeded.  Consequently, after multiple operations,
the table may become sparse, e.g., containing entries
for rows 95, 100, 101, and 203 and the entries should
not be assumed to be in chronological order because
upsAlarmId might have wrapped.
          
Alarms are named by an AutonomousType (OBJECT
IDENTIFIER), upsAlarmDescr, to allow a single table to
reflect well known alarms plus alarms defined by a
particular implementation, i.e., as documented in the
private enterprise MIB definition for the device.  No
two rows will have the same value of upsAlarmDescr,
since alarms define conditions.  In order to meet this
requirement, care should be taken in the definition of
alarm conditions to insure that a system cannot enter
the same condition multiple times simultaneously.
          
The number of rows in the table at any given time is
reflected by the value of upsAlarmsPresent.(*)

A list of receptacle table entries.  The number of
entries is given by the value of upsReceptacleNum.

A list of event table entries.  The number of entries is always
10, and the value of upsEventTableSize gives the number of valid
entries from the begging of the table.  Invalid entries return 0.
          
To prevent problems with simultaneous queries from several agents,
these values MUST be accessed using several PDUs in the
same SNMP message (<number> is (1..10)):
          
PDU-SET upsSetStartingTimeStamp <time> 
PDU-SET upsEventGetNext <number>
PDU-GET upsEventTableSize
PDU-GET upsEventCode,upsEventStatus,upsEventTime 1
PDU-GET upsEventCode,upsEventStatus,upsEventTime 2
..
PDU-GET upsEventCode,upsEventStatus,upsEventTime <number>
          
The table is read up to requested number of events and the
management software afterwards decides which entries are
valid, as indicated by the upsEventTableSize.

A list of parameter entries. The number of entries is always
16, and the value of upsParameterTableSize gives the number of valid
entries from the begging of the table. Invalid entries return 0.
          
To prevent problems with simultaneous queries from several agents,
these values MUST be accessed using several PDUs in the
same SNMP message (<number> is (1..16)):
          
Read sequence:
          
PDU-SET upsSetStartingAddress <addr>
PDU-SET upsParametersRead <number>
PDU-GET upsParameterTableSize
PDU-GET upsParameterValue 1
PDU-GET upsParameterValue 2
..
PDU-GET upsParameterValue <number>
          
The table is read up to requested number of events and the
management software afterwards decides which entries are
valid, as indicated by the upsParameterTableSize.
          
Write sequence:
          
PDU-SET upsSetStartingAddress <addr>
PDU-SET upsParameterValue 1
PDU-SET upsParameterValue 2
..
PDU-SET upsParameterValue <number>
PDU-SET upsParametersWrite <number>