Cisco 3825 - Manual (Page 92)

4-34
Cisco 3825 Mobile Wireless Edge Router Software Configuration Guide
OL-15667-03
Chapter 4 Configuring the Cisco 3825 Mobile Wireless Edge Router in a RAN-O Solution with the Command-Line
Configuration Sequence
To configure a Cisco 3825 for SNMP, follow these steps while in the global configuration mode:
Step 1 To set up the community access string to permit access to the SNMP, use the snmp-server community
command. The no form of this command removes the specified community string.
Router(config)# snmp-server community string [view view-name] [ro | rw] [number]
Where:
• string—Community string that acts like a password and permits access to the SNMP protocol.
• view view-name—(Optional) Name of a previously defined view. The view defines the objects
available to the community.
• ro—(Optional) Specifies read-only access. Authorized management stations are only able to
retrieve MIB objects.
• rw—(Optional) Specifies read-write access. Authorized management stations are able to both
retrieve and modify MIB objects.
• number—(Optional) Integer from 1 to 99 that specifies an access list of IP addresses that are allowed
to use the community string to gain access to the SNMP agent.
For example, the following command sets up the community access string as xxxxx with read-only
access:
Router(config)# snmp-server community xxxxx RO
Step 2 To establish the message queue length for each trap host, use the snmp-server queue-length command.
Router(config)# snmp-server queue-length length
Where length is the integer that specifies the number of trap events that can be held before the queue
must be emptied.
For example, the following command establishes the number of trap events to 100:
Router(config)# snmp-server queue-length 100
Step 3 To enable the router to send SNMP traps or informs (SNMP notifications), use the snmp-server enable
traps command. Use the no form of this command to disable SNMP notifications.
Router(config)# snmp-server enable traps [notification-type] [notification-option]
Where:
• notification-type—snmp [authentication]—Enables RFC 1157 SNMP notifications. Note that use
of the authentication keyword produces the same effect as not using the authentication keyword.
Both the snmp-server enable traps snmp and snmp-server enable traps snmp authentication
forms of this command will globally enable (or, if using the no form, disable) the following SNMP
traps:
– authentication failure
– linkup
– linkdown
– coldstart
– warmstart