Specifications
Configuring for SNMP Access
17-6
When you create a community name without specifying an address the access
server assigns the default address ANY. The address ANY enables any NMS that
knows this community name to GET or SET information about the access server.
Example: Configuring Community Names for Access by Any NMS
The following example shows how to create the community name SNUGS
without specifying an address:
Local> CHANGE SNMP COMMUNITY "SNUGS" SET ENABLED
Local> CHANGE SNMP ENABLED
Configuring a Community Name with an Address
You can configure a community name so that only an NMS with a given address
can access the access server with SNMP commands. Use the CHANGE SNMP
COMMUNITY community-name ADDRESS command to configure the
community name in this way.
Example: Configuring Community Names for Access from a Specific NMS
The following example shows how to create community name BUGS. Only the
NMS with the address 195.1.1.1 can GET or SET information about the server:
Local> CHANGE SNMP COMMUNITY "BUGS" ADDRESS 195.1.1.1
Local> CHANGE SNMP COMMUNITY "BUGS" SET ENABLED
Local> CHANGE SNMP ENABLED
One IP Address for a Community Name
Each community name can have only one IP address assigned. The access server
rejects the addresses 0.0.0.0 and 255.255.255.255. By default, GET and GETNEXT
are enabled when you create a community name.
Configuring Community Names to Send TRAP Messages
You can optionally configure the access server to send TRAP messages to a
specific NMS for each community name. The access server generates TRAP
messages in response to the events listed in the following table:
This Event: Occurs When:
Cold start The access server was reinitialized.
Line up A network data link session was established on port n.










