Bay Networks 6300 Supplement Manual page 426

Chapter 2 Simple Network Management Protocol (SNMP)
Remote Annex 6300 Supplement to the Remote Annex Administrator's Guide for UNIX
B-60
Defining the Community String
Each SNMP message contains a community string in its header. The
receiving SNMP agent tries to match the message's string with an existing
community string list. If there is no match, the SNMP agent discards the
message without responding to the sender.
The keyword community defines an SNMP community name from
which the RA 6300 responds to requests. At system start-up, the SNMP
agent requires at least one community string to be defined in the
configuration file. If the file does not contain a community string, the
RA 6300 defaults to the community name public (unless SNMP is
disabled in the parameter disabled_modules). There is no notion of read-
only or read-write communities.
You can specify up to four SNMP community names in the gateway
section of the configuration file, but each community requires a separate
line. The RA 6300 adds these communities to the SNMP agent's
community table. The syntax is:
snmp community name
Defining Trap Hosts and Traps
The RA 6300 employs two methods for defining the host addresses it
uses when generating SNMP trap messages.
• The first method defines up to ten static trap hosts in the
configuration file using the SNMP trap host syntax.
• The second method loads the trap hosts (if any) from the
configuration file into the Trap Host Table (i.e., the
anxTrapHostTable objects in the proprietary MIB). You can
modify this table by adding or deleting trap hosts. However, the
changes you make directly through the table will be lost when
the RA 6300 reboots. If you want your changes to be permanent,
you must use the configuration file.
Book B