19.08.2013 Views

RMX 2000 Administrator's Guide - Polycom Support

RMX 2000 Administrator's Guide - Polycom Support

RMX 2000 Administrator's Guide - Polycom Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 16-<strong>RMX</strong> Administration and Utilities<br />

16-82<br />

3 Alarm Fault trap. The third trap type is a family of traps defined in<br />

the POLYCOM-<strong>RMX</strong>-MIB file, these traps are associated with the<br />

<strong>RMX</strong> active alarm and clearance (proprietary SNMP trap).<br />

rmxFailedConfigUserListInLinuxAlarmFault notification received<br />

from: 172.22.189.154 at 5/20/2007 7:04:22 PM<br />

Time stamp: 0 days 00h:01m:11s.71th<br />

Agent address: 172.22.189.154 Port: 32777 Transport: IP/UDP<br />

Protocol: SNMPv2c Notification<br />

Manager address: 172.22.172.34 Port: 162 Transport: IP/UDP<br />

Community: public<br />

Bindings (6)<br />

Binding #1: sysUpTime.0 *** (timeticks) 0 days<br />

00h:01m:11s.71th<br />

Binding #2: snmpTrapOID.0 *** (oid)<br />

rmxFailedConfigUserListInLinuxAlarmFault<br />

Binding #3: rmxAlarmDescription *** (octets) Insufficient<br />

resources<br />

Binding #4: rmxActiveAlarmDateAndTime *** (octets) 2007-6-<br />

19,16:7:15.0,0:0<br />

Binding #5: rmxActiveAlarmIndex *** (gauge32) 2<br />

Binding #6: rmxActiveAlarmListName *** (octets) Active<br />

Alarm Table<br />

* Binding #7: rmxActiveAlarmRmxStatus *** (rmxStatus) major<br />

Figure 3 An Example of an Alarm Fault Trap<br />

Each trap is sent with a time stamp, the agent address and the manager<br />

address.<br />

Status Trap Content<br />

The MCU sends status traps for the status MAJOR - a trap is sent when<br />

the card/MCU status is MAJOR.<br />

All trap content is considered “MAJOR”.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!