Administration and Utilities
Polycom®, Inc. 506
Traps
The MCU is able to send Traps to different managers. Traps are messages that are sent by the MCU to the
SNMP Manager when an event such as MCU Reset occurs.
Guidelines
Version 1, Version 2 and Version 3 traps are supported.
When SNMPv3 is selected only SNMPv3 Queries and Traps receive responses.
A mixture of Version 1, Version 2 and Version 3 traps is not permitted.
MIB Files
The H.341 standard defines the MIBs that H.320 and H.323 MCUs must comply with. In addition, other MIBs
should also be supported, such as MIB-II and the ENTITY MIB, which are common to all network entities.
The MIBs are contained in files in the SNMP MIBS sub-directory of the Collaboration Server root directory.
The files should be loaded to the SNMP external system and compiled within that application. Only then can
the SNMP external application perform the required monitoring tasks.

Private MIBs

RMX-MIB (RMX-MIB.MIB)
Contains the statuses of the Collaboration Server: Startup, Normal and Major.
Contains all the Alarms of the Collaboration Server that are sent to the SNMP Manager.

Support for MIB-II Sections

The following table details the MIB-II sections that are supported:

The Alarm-MIB

MIB used to send alarms. When a trap is sent, the Alarm-MIB is used to send it.

H.341-MIB (H.341 – H.323)

Gives the address of the gatekeeper.
Supports H.341-MIB of SNMP events of H.323.
The MULTI-MEDIA_MIB_TC must be compiled before compiling the other MIBs.
Supported MIB-II Sections
Section Object Identifier
system mib-2 1
interfaces mib-2 2
ip mib-2 4