Polycom RealPresence Resource Manager System Operations Guide Working with SNMP
570 Polycom, Inc.
Setting Description
Transport Specifies the transport protocol for SNMP
communications. SNMP can be implemented over
two transport protocol:
TCP—This protocol has error-recovery services,
message delivery is assured, and messages are
delivered in the order they were sent. Some SNMP
managers only support SNMP over TCP.
UDP—This protocol does not provide
error-recovery services, message delivery is not
assured, and messages are not necessarily
delivered in the order they were sent.
Because UDP doesn't have error recovery
services, it requires fewer network resources. It is
well suited for repetitive, low-priority functions like
alarm monitoring.
Port Specifies the port that the RealPresence Resource
Manager system uses for general SNMP
messages. By default, the RealPresence Resource
Manager system uses port 161.
Community For SNMPv2c, specifies the context for the
information, which is the SNMP group to which the
devices and management stations running SNMP
belong.
The RealPresence Resource Manager system has
only one valid context—by default,
public
—which
is identified by this Community name. The
RealPresence Resource Manager system will not
respond to requests from management systems
that do not belong to its community.
V3 Context Name For SNMPv3, specifies the context for the
information. The RealPresence Resource Manager
system has only one valid context, which is
identified by
contextName
(in our case—an empty
string) and
contextEngineID
.
V3 Local Engine Id For SNMPv3, displays the RealPresence Resource
Manager system
contextEngineID
for SNMPv3.
Security User For SNMPv3, specifies the security name required
to access a monitored MIB object.
