Polycom DOC2702A Manuel D’Utilisation

Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities

Polycom, Inc.

SNMP enables managing and monitoring of the MCU status by external managing systems, 
such as HP OpenView or through web applications.
The RMX’s implementation of SNMPv3 is FIPS 140 compliant.

MIBs are a collection of definitions, which define the properties of the managed object 

within the device to be managed. Every managed device keeps a database of values for each 

of the definitions written in the MIB.
The SNMP systems poll the MCU according to the MIB definitions.

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.

•

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.

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 RMX 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.

•

RMX-MIB (RMX-MIB.MIB)
—

Contains the statuses of the RMX: Startup, Normal and Major.

—

Contains all the Alarms of the RMX that are sent to the SNMP Manager.

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

The MULTI-MEDIA_MIB_TC must be compiled before compiling the other MIBs.

mib-2 1