
Configuring SNMP, BootP, DHCP, and RARP Services
2-4
303542-A Rev 00
An SNMP community is a logical relationship between an SNMP agent and one
or more SNMP managers. You define communities locally at the agent. The agent
establishes one community for each desired combination of authentication and
access control characteristics. You assign each community a unique name (within
the agent), and all members of a community have the same access privileges,
either read-only or read-write:
• Read-only: members can view configuration and performance information.
• Read-write: members can view configuration and performance information,
and also change the configuration.
By defining a community, an agent limits access to its MIB, to a selected set of
management stations. By using more than one community, the agent can provide
different levels of MIB access to different management stations.
All SNMP message exchanges consist of a community name and a data field,
which contains the SNMP operation and its associated operands. You can
configure the SNMP agent to receive requests and send responses only from
managers that are members of a known community.
If the agent knows the community name in the SNMP message and knows that the
manager generating the request is a member of that community, it considers the
message to be authentic and gives it the access allowed for members of that
community. In this way, the SNMP community prevents unauthorized managers
from viewing or changing the configuration of a router.
SNMP Implementation Notes
This section contains information about features specific to the Bay Networks
implementation of SNMP.
Internet Protocol
SNMP uses the User Datagram Protocol (UDP) to transport its messages. You
must enable the Internet Protocol (IP) to use UDP and SNMP.
Events and Traps
An event is a change in the operating status of a router. The router stores the event
as a single entry in a memory-resident log.
Komentáře k této Příručce