Polycom RealPresence Resource Manager System Operations Guide SNMP Overview
568 Polycom, Inc.
It is important to note that you should understand how your SNMP
management system is configured to properly configure the RealPresence
Resource Manager system SNMP transport protocol requirements, SNMP
version requirements, SNMP authentication requirements, and SNMP privacy
requirements on the RealPresence Resource Manager system.
The RealPresence Resource Manager system supports three SNMP levels:
• Disabled—The RealPresence Resource Manager system SNMP processes
are turned off.
•SNMPv2c—The RealPresence Resource Manager system implements a
sub-version of SNMPv2. The key advantage of SNMPv2c is the Inform
command. Unlike Traps, Informs are messages sent to the management
system that must be positively acknowledged with a response message. If
the management system does not reply to an Inform, the RealPresence
Resource Manager system resends the Inform. SNMPv2c also has
improved error handling and improved SET commands.
One drawback of SNMPv2c is that it is subject to packet sniffing of the
clear text community string from the network traffic, because it does not
encrypt communications between the management system and SNMP
agents.
•SNMPv3—The RealPresence Resource Manager system implements the
newest version of SNMP. Its primary feature is enhanced security. The
contextEngineID
in SNMPv3 uniquely identifies each SNMP entity. The
contextEngineID
is used to generate the key for authenticated messages.
The RealPresence Resource Manager system implements SNMPv3
communication with authentication and privacy (the
authPriv
security
level as defined in the USM MIB).
— Authentication is used to ensure that traps are read by only the
intended recipient. As messages are created, they are given a special
key that is based on the
contextEngineID
of the entity. The key is
shared with the intended recipient and used to receive the message.
— Privacy encrypts the SNMP message to ensure that it cannot be read
by unauthorized users.
