Specifications

4-108
Cisco MWR 2941 Mobile Wireless Edge Router Software Configuration Guide, Release 12.2(33)MRB
OL-21227-02
Chapter 4 Configuring the Cisco MWR 2941 Router Using the CLI
Monitoring and Managing the Cisco MWR 2941 Router
The Cisco MWTM integrates with any SNMP-based monitoring system, such as Cisco Info Center
products. In addition, the Cisco MWTM collects a large amount of performance data that can be
exported or directly accessed from the database. This data can then be used by performance reporting
applications. For more information about MWTM, see
http://www.cisco.com/en/US/products/ps6472/tsd_products_support_series_home.html.
Configuring SNMP Support
Use the following instructions to configure SNMP support: setting up the community access,
establishing a message queue for each trap host, enabling the router to send SNMP traps, enabling SNMP
traps for alarms, and enabling SNMP traps for a specific environment. You might also need to enter other
configuration commands, depending on the requirements for your system configuration and the
protocols you plan to route on the interface.
Note To view the current MIBs that the Cisco MWR 2941 supports, see the Release Notes for Cisco MWR
2941 Mobile Wireless Edge Router for Cisco IOS Release 12.2(33)MRA.
Note In the following procedure, press the Return key after each step unless otherwise noted. At any time,
you can exit the privileged level and return to the user level by entering disable at the Router# prompt.
To configure a Cisco MWR 2941 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]
• 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
• length—Integer that specifies the number of trap events that can be held before the queue must be
emptied.