Operation
15
4.3 RFC 1628 UPS MIB
UPS units log alarms in the RFC 1628 UPS MIB. Traps for the UPS
units are generated out of the RFC 1628 UPS MIB. There are four
traps that may be sent for the UPS units: Trap On Battery, Trap Test
Completed, Trap Alarm Entry Added and Trap Alarm Entry Removed.
The trap On Battery is sent when the UPS is operating on battery
power. This trap will be sent once a minute until the UPS either shuts
down or is no longer running on battery power. This trap provides the
Estimated Minutes Remaining on Battery, the Seconds on Battery
and the Configured Low Battery Time. The Trap Test Completed is
sent when a UPS diagnostic test is completed. This trap provides the
Test ID of the test that has been performed, the Test Spin Lock, the
Test Results Summary, the Test Results Detail, the Test Start Time
and the Test Elapsed Time. The Trap Alarm Entry Added is sent
when an alarm is placed into the alarm table and provides the alarm
ID and the alarm description. This trap is not sent on the following
alarms: On Battery and Test In Progress. The Trap Alarm entry
Removed is sent when an alarm is removed from the alarm table and
provides the alarm ID and the alarm description. This trap is not sent
out when the Test In Progress alarm is removed from the alarm table.
4.3.1 SNMP Traps
Below is the definition on how events are handled in RFC1628.
* Two similar event traps (notifications) are sent to their destination
or NMS system. The event traps are differentiated by their trap type.
Type 3 = Condition ADDED to the event table, Type 4 = Condition
REMOVED from the event table.
*Each event trap contains the following three bindings of information:
1. Trap ID. The ID represents the location or placeholder in the table
to find event information.
2. The OID reference of the well-known alarm. Note: Below are the
OID references for RFC1628 alarms. These are not Liebert-unit
specific, but rather RFC1628 specific.
3. Time ticks or system uptime that represents when an event
occurred.