 Feedback
|
Table Of Contents
RIPv2 Monitoring with SNMP Using the RFC 1724 MIB Extensions
Prerequisites for RIPv2 Monitoring with SNMP Using the RFC 1724 MIB Extensions
Restrictions for RIPv2 Monitoring with SNMP Using the RFC 1724 MIB Extensions
Information About RIPv2 Monitoring with SNMP Using the RFC 1724 MIB Extensions
How to Enable RIPv2 Monitoring with SNMP Using the RIPv2: RFC124 MIB Extensions
Enabling SNMP Read-Only Access on the Router
Configuration Examples for RIPv2 Monitoring with SNMP Using the RIPv2: RFC124 MIB Extensions
Querying the RIP Interface Status Table Objects: Example
Querying the RIP Interface Configuration Table Objects: Example
Feature Information for RIPv2: RFC 1724 MIB Extensions
RIPv2 Monitoring with SNMP Using the RFC 1724 MIB Extensions
First Published: February 27, 2006Last Updated: February 27, 2006This document describes the Cisco IOS implementation of RFC 1724, RIP Version 2 MIB Extensions. RFC 1724 defines Management Information Base (MIB) objects that allow you to monitor RIPv2 using Simple Network Management Protocol (SNMP).
Finding Feature Information in This Module
Your Cisco IOS software release may not support all of the features documented in this module. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported, use the "Feature Information for RIPv2: RFC 1724 MIB Extensions" section.
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•
Prerequisites for RIPv2 Monitoring with SNMP Using the RFC 1724 MIB Extensions
•
•
•
•
•
Prerequisites for RIPv2 Monitoring with SNMP Using the RFC 1724 MIB Extensions
•
•
•
–
–
–
–
Restrictions for RIPv2 Monitoring with SNMP Using the RFC 1724 MIB Extensions
This implementation of the RIPv2 MIB does not track any data associated with a RIP Virtual Routing and Forwarding (VRF) instance. Only interfaces that are assigned IP addresses in the IP address space configured by the network network-address command in RIP router configuration mode are tracked. Global data is tracked only for changes to the main routing table.
Information About RIPv2 Monitoring with SNMP Using the RFC 1724 MIB Extensions
The following sections contain information about MIB objects standardized as part of RFC 1724, and benefits of the RFC 1724 MIB.
RIPv2 MIB
This section describes the MIB objects that are provided by RFC 1724 definitions. The RIPv2 MIB consists of the following managed objects:
•
•
•
•
Table 1, Table 2, and Table 3 show the objects that are provided by RFC 1724 RIPv2 MIB definitions. The objects are listed in the order in which they appear within the RFC 1724 RIPv2 MIB, per the tables that describe them. The statistics for all of the objects in the global counters can be obtained by querying the rip2Globals object identifier (OID) using snmpwalk, or a similar SNMP toolset command on your NMS.
Table 1 shows the RFC 1724 RIPv2 MIB global counter objects.
The objects in the RFC 1724 RIPv2 MIB interface table track information on a per interface basis. All object in the RFC 1724 RIPv2 MIB interface table, except for the rip2IfStatAddress object, represent newly tracked data within RIP. There are no equivalent show commands for these objects. All objects in the RIPv2 MIB interface table are implemented read-only.
Table 2 shows the RFC 1724 RIPv2 MIB interface table objects. The statistics for all objects in the interface table can be obtained by querying the sequence name Rip2IfStatEntry using snmpwalk or a similar SNMP toolset command on your NMS.
The objects in the RFC 1724 RIPv2 MIB interface configuration table track information on a per interface basis. Except for the Rip2IfConfAuthType object, the data for the objects in the RFC 1724 RIPv2 MIB interface configuration table can also be gathered with the show ip protocol commands. All objects in the RIPv2 MIB interface table are implemented read-only.
Table 3 shows the RIPv2 MIB interface configuration table objects. The statistics for all objects in the configuration table can be obtained by querying the sequence name rip2IfConfEntry using snmpwalk or a similar SNMP toolset command on your NMS.
Benefits of the RIPv2 MIB
The RFC 1724 RIPv2 MIB extensions allow network managers to monitor the RIPv2 routing protocol using SNMP through the addition of new global counters and table objects that previously were not supported by the RFC 1389 RIPv2 MIB. The new global counters and table objects are intended to facilitate quickly changing routes or failing neighbors.
How to Enable RIPv2 Monitoring with SNMP Using the RIPv2: RFC124 MIB Extensions
This section contains the following tasks:
•
•
Enabling SNMP Read-Only Access on the Router
There are no router configuration tasks required for the RIPv2: RFC124 MIB Extensions feature itself. SNMP read-only access to the objects in the RFC 1724 RIPv2 MIB is enabled when you configure the SNMP server read-only community string on the router.
Note
Perform this task to configure the SNMP server read-only community string on the router to enable SNMP read-only access to MIB objects (including the RFC 1724 RIPv2 MIB extensions) on the router.
SNMP Community Strings
Routers can have multiple read-only SNMP community strings. When you configure an SNMP read-only community string for the snmp-server command on the router, an existing SNMP snmp-server read-only community string is not overwritten. For example, if you enter the snmp-server community string1 ro and snmp-server community string2 ro commands on the router, the router will have two valid read-only community strings—string1 and string2. If this is not the behavior that you desire, use the no snmp-server community string ro command to remove an existing SNMP read-only community string.
Timesaver
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Verifying the Status of the RIPv2: RFC124 MIB Extensions on the Router and Your Network Management Station
Perform this optional task on your NMS to verify the status of the RFC 1724 RIPv2 MIB extensions on the router and on your NMS.
Note
Prerequisites
Your NMS must have the RFC 1724 MIB installed.
SUMMARY STEPS
1.
DETAILED STEPS
Step 1
Use the snmpwalk command for the rip2Globals object in the RFC 1724 RIPv2 MIB to display the data for the objects associated with this object. This step verifies that the NMS is configured to send queries for objects in the RFC 1724 RIPv2 MIB and that the router is configured to respond to the queries.
$ snmpwalk -m all -v2c 10.0.0.253 -c T8vCx3 rip2GlobalsRIPv2-MIB::rip2GlobalRouteChanges.0 = Counter32: 5RIPv2-MIB::rip2GlobalQueries.0 = Counter32: 1$
Configuration Examples for RIPv2 Monitoring with SNMP Using the RIPv2: RFC124 MIB Extensions
This section contains the following examples:
•
•
Querying the RIP Interface Status Table Objects: Example
The following example shows how to send an SNMP query to obtain data for all objects in the RIP interface status table using the snmpwalk command.
$ snmpwalk -m all -v2c 10.0.0.253 -c T8vCx3 Rip2IfStatEntryRIPv2-MIB::rip2IfStatAddress.10.0.0.253 = IpAddress: 10.0.0.253RIPv2-MIB::rip2IfStatAddress.172.16.1.1 = IpAddress: 172.16.1.1RIPv2-MIB::rip2IfStatAddress.172.16.2.1 = IpAddress: 172.16.2.1RIPv2-MIB::rip2IfStatAddress.172.17.1.1 = IpAddress: 172.17.1.1RIPv2-MIB::rip2IfStatAddress.172.17.2.1 = IpAddress: 172.17.2.1RIPv2-MIB::rip2IfStatRcvBadPackets.10.0.0.253 = Counter32: 0RIPv2-MIB::rip2IfStatRcvBadPackets.172.16.1.1 = Counter32: 1654RIPv2-MIB::rip2IfStatRcvBadPackets.172.16.2.1 = Counter32: 1652RIPv2-MIB::rip2IfStatRcvBadPackets.172.17.1.1 = Counter32: 1648RIPv2-MIB::rip2IfStatRcvBadPackets.172.17.2.1 = Counter32: 1649RIPv2-MIB::rip2IfStatRcvBadRoutes.10.0.0.253 = Counter32: 0RIPv2-MIB::rip2IfStatRcvBadRoutes.172.16.1.1 = Counter32: 0RIPv2-MIB::rip2IfStatRcvBadRoutes.172.16.2.1 = Counter32: 0RIPv2-MIB::rip2IfStatRcvBadRoutes.172.17.1.1 = Counter32: 0RIPv2-MIB::rip2IfStatRcvBadRoutes.172.17.2.1 = Counter32: 0RIPv2-MIB::rip2IfStatSentUpdates.10.0.0.253 = Counter32: 0RIPv2-MIB::rip2IfStatSentUpdates.172.16.1.1 = Counter32: 0RIPv2-MIB::rip2IfStatSentUpdates.172.16.2.1 = Counter32: 0RIPv2-MIB::rip2IfStatSentUpdates.172.17.1.1 = Counter32: 0RIPv2-MIB::rip2IfStatSentUpdates.172.17.2.1 = Counter32: 0RIPv2-MIB::rip2IfStatStatus.10.0.0.253 = INTEGER: active(1)RIPv2-MIB::rip2IfStatStatus.172.16.1.1 = INTEGER: active(1)RIPv2-MIB::rip2IfStatStatus.172.16.2.1 = INTEGER: active(1)RIPv2-MIB::rip2IfStatStatus.172.17.1.1 = INTEGER: active(1)RIPv2-MIB::rip2IfStatStatus.172.17.2.1 = INTEGER: active(1)The following example shows how to send an SNMP query to obtain data for the rip2IfStatStatus object for all of the interfaces in the RIP interface status table using the snmpwalk command.
$ snmpwalk -m all -v2c 10.0.0.253 -c T8vCx3 rip2IfStatStatusRIPv2-MIB::rip2IfStatStatus.10.0.0.253 = INTEGER: active(1)RIPv2-MIB::rip2IfStatStatus.172.16.1.1 = INTEGER: active(1)RIPv2-MIB::rip2IfStatStatus.172.16.2.1 = INTEGER: active(1)RIPv2-MIB::rip2IfStatStatus.172.17.1.1 = INTEGER: active(1)RIPv2-MIB::rip2IfStatStatus.172.17.2.1 = INTEGER: active(1)$The following example shows how to send an SNMP query to obtain data for the rip2IfStatStatus object for a specific interface IP address in the RIP interface status table using the snmpget command.
$ snmpget -m all -v2c 10.0.0.253 -c T8vCx3 rip2IfStatStatus.10.0.0.253RIPv2-MIB::rip2IfStatStatus.10.0.0.253 = INTEGER: active(1)$Querying the RIP Interface Configuration Table Objects: Example
The following example shows how to send an SNMP query to obtain data for all objects in the RIP interface configuration table using the snmpwalk command.
$ snmpwalk -m all -v2c 10.0.0.253 -c T8vCx3 rip2IfConfEntryRIPv2-MIB::rip2IfConfAddress.10.0.0.253 = IpAddress: 10.0.0.253RIPv2-MIB::rip2IfConfAddress.172.16.1.1 = IpAddress: 172.16.1.1RIPv2-MIB::rip2IfConfAddress.172.16.2.1 = IpAddress: 172.16.2.1RIPv2-MIB::rip2IfConfAddress.172.17.1.1 = IpAddress: 172.17.1.1RIPv2-MIB::rip2IfConfAddress.172.17.2.1 = IpAddress: 172.17.2.1RIPv2-MIB::rip2IfConfDomain.10.0.0.253 = ""RIPv2-MIB::rip2IfConfDomain.172.16.1.1 = ""RIPv2-MIB::rip2IfConfDomain.172.16.2.1 = ""RIPv2-MIB::rip2IfConfDomain.172.17.1.1 = ""RIPv2-MIB::rip2IfConfDomain.172.17.2.1 = ""RIPv2-MIB::rip2IfConfAuthType.10.0.0.253 = INTEGER: noAuthentication(1)RIPv2-MIB::rip2IfConfAuthType.172.16.1.1 = INTEGER: noAuthentication(1)RIPv2-MIB::rip2IfConfAuthType.172.16.2.1 = INTEGER: noAuthentication(1)RIPv2-MIB::rip2IfConfAuthType.172.17.1.1 = INTEGER: noAuthentication(1)RIPv2-MIB::rip2IfConfAuthType.172.17.2.1 = INTEGER: noAuthentication(1)RIPv2-MIB::rip2IfConfAuthKey.10.0.0.253 = ""RIPv2-MIB::rip2IfConfAuthKey.172.16.1.1 = ""RIPv2-MIB::rip2IfConfAuthKey.172.16.2.1 = ""RIPv2-MIB::rip2IfConfAuthKey.172.17.1.1 = ""RIPv2-MIB::rip2IfConfAuthKey.172.17.2.1 = ""RIPv2-MIB::rip2IfConfSend.10.0.0.253 = INTEGER: ripVersion2(4)RIPv2-MIB::rip2IfConfSend.172.16.1.1 = INTEGER: ripVersion2(4)RIPv2-MIB::rip2IfConfSend.172.16.2.1 = INTEGER: ripVersion2(4)RIPv2-MIB::rip2IfConfSend.172.17.1.1 = INTEGER: ripVersion2(4)RIPv2-MIB::rip2IfConfSend.172.17.2.1 = INTEGER: ripVersion2(4)RIPv2-MIB::rip2IfConfReceive.10.0.0.253 = INTEGER: rip2(2)RIPv2-MIB::rip2IfConfReceive.172.16.1.1 = INTEGER: rip2(2)RIPv2-MIB::rip2IfConfReceive.172.16.2.1 = INTEGER: rip2(2)RIPv2-MIB::rip2IfConfReceive.172.17.1.1 = INTEGER: rip2(2)RIPv2-MIB::rip2IfConfReceive.172.17.2.1 = INTEGER: rip2(2)RIPv2-MIB::rip2IfConfDefaultMetric.10.0.0.253 = INTEGER: 1RIPv2-MIB::rip2IfConfDefaultMetric.172.16.1.1 = INTEGER: 1RIPv2-MIB::rip2IfConfDefaultMetric.172.16.2.1 = INTEGER: 1RIPv2-MIB::rip2IfConfDefaultMetric.172.17.1.1 = INTEGER: 1RIPv2-MIB::rip2IfConfDefaultMetric.172.17.2.1 = INTEGER: 1RIPv2-MIB::rip2IfConfStatus.10.0.0.253 = INTEGER: active(1)RIPv2-MIB::rip2IfConfStatus.172.16.1.1 = INTEGER: active(1)RIPv2-MIB::rip2IfConfStatus.172.16.2.1 = INTEGER: active(1)RIPv2-MIB::rip2IfConfStatus.172.17.1.1 = INTEGER: active(1)RIPv2-MIB::rip2IfConfStatus.172.17.2.1 = INTEGER: active(1)RIPv2-MIB::rip2IfConfSrcAddress.10.0.0.253 = IpAddress: 10.0.0.253RIPv2-MIB::rip2IfConfSrcAddress.172.16.1.1 = IpAddress: 172.16.1.1RIPv2-MIB::rip2IfConfSrcAddress.172.16.2.1 = IpAddress: 172.16.2.1RIPv2-MIB::rip2IfConfSrcAddress.172.17.1.1 = IpAddress: 172.17.1.1RIPv2-MIB::rip2IfConfSrcAddress.172.17.2.1 = IpAddress: 172.17.2.1$The following example shows how to send an SNMP query to obtain data for the rip2IfConfAddress object for all interfaces in the RIP interface configuration table using the snmpwalk command.
$ snmpwalk -m all -v2c 10.0.0.253 -c T8vCx3 rip2IfConfAddressRIPv2-MIB::rip2IfConfAddress.10.0.0.253 = IpAddress: 10.0.0.253RIPv2-MIB::rip2IfConfAddress.172.16.1.1 = IpAddress: 172.16.1.1RIPv2-MIB::rip2IfConfAddress.172.16.2.1 = IpAddress: 172.16.2.1RIPv2-MIB::rip2IfConfAddress.172.17.1.1 = IpAddress: 172.17.1.1RIPv2-MIB::rip2IfConfAddress.172.17.2.1 = IpAddress: 172.17.2.1$Where to Go Next
For more information about SNMP and SNMP operations, see the "Configuring SNMP Support" chapter of the Cisco IOS Network Management Configuration Guide, Release 12.4.
Additional References
The following sections provide references related to RIPv2: RFC 1724 MIB Extensions.
Related Documents
RIP configuration
Cisco IOS IP Routing Protocols Configuration Guide, Release 12.4
RIP commands
Cisco IOS IP Routing Protocols Configuration Guide, Release 12.4T
SNMP configuration
Cisco IOS Network Management Configuration Guide, Release 12.4
SNMP commands
Cisco IOS Network Management Command Reference, Release 12.4T
Standards
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RIPv2 MIB
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
Technical Assistance
Command Reference
This feature uses no new or modified commands.
Glossary
OID—object identifier, A managed object within the object tree.
SNMP—Simple Network Management Protocol, a protocol used to monitor and manage networking devices.
snmpwalk—An SNMP command to query statistics from a branch in the MIB.
snmpget—An SNMP command to query statistics from a specific OID in the MIB.
Note
Feature Information for RIPv2: RFC 1724 MIB Extensions
Table 4 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Cisco IOS software images are specific to a Cisco IOS software release, a feature set, and a platform. Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Note
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2006 Cisco Systems, Inc. All rights reserved.
