Cisco IOS IP Routing: RIP Configuration Guide...cisco ios ip routing: rip configuration guide...

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706 USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 527-0883

Cisco IOS IP Routing: RIP Configuration Guide Release 15.1

http://www.cisco.com

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1002R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

Cisco IOS IP Routing: RIP Configuration Guide © 2010 Cisco Systems, Inc. All rights reserved.

i

About Cisco IOS Software Documentation

Last Updated: March 26, 2010

This document describes the objectives, audience, conventions, and organization used in Cisco IOS software documentation. Also included are resources for obtaining technical assistance, additional documentation, and other information from Cisco. This document is organized into the following sections:

• Documentation Objectives, page i

• Audience, page i

• Documentation Conventions, page i

• Documentation Organization, page iii

• Additional Resources and Documentation Feedback, page xi

Documentation ObjectivesCisco IOS documentation describes the tasks and commands available to configure and maintain Cisco networking devices.

AudienceThe Cisco IOS documentation set is intended for users who configure and maintain Cisco networking devices (such as routers and switches) but who may not be familiar with the configuration and maintenance tasks, the relationship among tasks, or the Cisco IOS commands necessary to perform particular tasks. The Cisco IOS documentation set is also intended for those users experienced with Cisco IOS software who need to know about new features, new configuration options, and new software characteristics in the current Cisco IOS release.

Documentation ConventionsIn Cisco IOS documentation, the term router may be used to refer to various Cisco products; for example, routers, access servers, and switches. These and other networking devices that support Cisco IOS software are shown interchangeably in examples and are used only for illustrative purposes. An example that shows one product does not necessarily mean that other products are not supported.

About Cisco IOS Software DocumentationDocumentation Conventions

ii

This section contains the following topics:

• Typographic Conventions, page ii

• Command Syntax Conventions, page ii

• Software Conventions, page iii

• Reader Alert Conventions, page iii

Typographic ConventionsCisco IOS documentation uses the following typographic conventions:

Command Syntax ConventionsCisco IOS documentation uses the following command syntax conventions:

Convention Description

^ or Ctrl Both the ^ symbol and Ctrl represent the Control (Ctrl) key on a keyboard. For example, the key combination ^D or Ctrl-D means that you hold down the Control key while you press the D key. (Keys are indicated in capital letters but are not case sensitive.)

string A string is a nonquoted set of characters shown in italics. For example, when setting a Simple Network Management Protocol (SNMP) community string to public, do not use quotation marks around the string; otherwise, the string will include the quotation marks.


bold Bold text indicates commands and keywords that you enter as shown.

italic Italic text indicates arguments for which you supply values.

[x] Square brackets enclose an optional keyword or argument.

... An ellipsis (three consecutive nonbolded periods without spaces) after a syntax element indicates that the element can be repeated.

| A vertical line, called a pipe, that is enclosed within braces or square brackets indicates a choice within a set of keywords or arguments.

[x | y] Square brackets enclosing keywords or arguments separated by a pipe indicate an optional choice.

{x | y} Braces enclosing keywords or arguments separated by a pipe indicate a required choice.

[x {y | z}] Braces and a pipe within square brackets indicate a required choice within an optional element.

About Cisco IOS Software DocumentationDocumentation Organization

iii

Software ConventionsCisco IOS software uses the following program code conventions:

Reader Alert ConventionsCisco IOS documentation uses the following conventions for reader alerts:

Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.

Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the manual.

Timesaver Means the described action saves time. You can save time by performing the action described in the paragraph.

Documentation OrganizationThis section describes the Cisco IOS documentation set, how it is organized, and how to access it on Cisco.com. It also lists the configuration guides, command references, and supplementary references and resources that comprise the documentation set. It contains the following topics:

• Cisco IOS Documentation Set, page iv

• Cisco IOS Documentation on Cisco.com, page iv

• Configuration Guides, Command References, and Supplementary Resources, page v


Courier font Courier font is used for information that is displayed on a PC or terminal screen.

Bold Courier font Bold Courier font indicates text that the user must enter.

< > Angle brackets enclose text that is not displayed, such as a password. Angle brackets also are used in contexts in which the italic font style is not supported; for example, ASCII text.

! An exclamation point at the beginning of a line indicates that the text that follows is a comment, not a line of code. An exclamation point is also displayed by Cisco IOS software for certain processes.

[ ] Square brackets enclose default responses to system prompts.


iv

Cisco IOS Documentation SetThe Cisco IOS documentation set consists of the following:

• Release notes and caveats provide information about platform, technology, and feature support for a release and describe severity 1 (catastrophic), severity 2 (severe), and select severity 3 (moderate) defects in released Cisco IOS software. Review release notes before other documents to learn whether updates have been made to a feature.

• Sets of configuration guides and command references organized by technology and published for each standard Cisco IOS release.

– Configuration guides—Compilations of documents that provide conceptual and task-oriented descriptions of Cisco IOS features.

– Command references—Compilations of command pages in alphabetical order that provide detailed information about the commands used in the Cisco IOS features and the processes that comprise the related configuration guides. For each technology, there is a single command reference that supports all Cisco IOS releases and that is updated at each standard release.

• Lists of all the commands in a specific release and all commands that are new, modified, removed, or replaced in the release.

• Command reference book for debug commands. Command pages are listed in alphabetical order.

• Reference book for system messages for all Cisco IOS releases.

Cisco IOS Documentation on Cisco.comThe following sections describe the organization of the Cisco IOS documentation set and how to access various document types.

Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

New Features List

The New Features List for each release provides a list of all features in the release with hyperlinks to the feature guides in which they are documented.

Feature Guides

Cisco IOS features are documented in feature guides. Feature guides describe one feature or a group of related features that are supported on many different software releases and platforms. Your Cisco IOS software release or platform may not support all the features documented in a feature guide. See the Feature Information table at the end of the feature guide for information about which features in that guide are supported in your software release.

Configuration Guides

Configuration guides are provided by technology and release and comprise a set of individual feature guides relevant to the release and technology.

http://www.cisco.com/go/cfn


v

Command References

Command reference books contain descriptions of Cisco IOS commands that are supported in many different software releases and on many different platforms. The books are organized by technology. For information about all Cisco IOS commands, use the Command Lookup Tool at http://tools.cisco.com/Support/CLILookup or the Cisco IOS Master Command List, All Releases, at http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html.

Cisco IOS Supplementary Documents and Resources

Supplementary documents and resources are listed in Table 2 on page xi.

Configuration Guides, Command References, and Supplementary ResourcesTable 1 lists, in alphabetical order, Cisco IOS software configuration guides and command references, including brief descriptions of the contents of the documents. The Cisco IOS command references contain commands for Cisco IOS software for all releases. The configuration guides and command references support many different software releases and platforms. Your Cisco IOS software release or platform may not support all these technologies.

Table 2 lists documents and resources that supplement the Cisco IOS software configuration guides and command references. These supplementary resources include release notes and caveats; master command lists; new, modified, removed, and replaced command lists; system messages; and the debug command reference.

For additional information about configuring and operating specific networking devices, and to access Cisco IOS documentation, go to the Product/Technologies Support area of Cisco.com at the following location:

http://www.cisco.com/go/techdocs

Table 1 Cisco IOS Configuration Guides and Command References

Configuration Guide and Command Reference Titles Features/Protocols/Technologies

• Cisco IOS AppleTalk Configuration Guide

• Cisco IOS AppleTalk Command Reference

AppleTalk protocol.

• Cisco IOS Asynchronous Transfer Mode Configuration Guide

• Cisco IOS Asynchronous Transfer Mode Command Reference

LAN ATM, multiprotocol over ATM (MPoA), and WAN ATM.

http://tools.cisco.com/Support/CLILookup

http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html



vi

• Cisco IOS Bridging and IBM Networking Configuration Guide

• Cisco IOS Bridging Command Reference

• Cisco IOS IBM Networking Command Reference

Transparent and source-route transparent (SRT) bridging, source-route bridging (SRB), Token Ring Inter-Switch Link (TRISL), and token ring route switch module (TRRSM).

Data-link switching plus (DLSw+), serial tunnel (STUN), block serial tunnel (BSTUN); logical link control, type 2 (LLC2), synchronous data link control (SDLC); IBM Network Media Translation, including Synchronous Data Logical Link Control (SDLLC) and qualified LLC (QLLC); downstream physical unit (DSPU), Systems Network Architecture (SNA) service point, SNA frame relay access, advanced peer-to-peer networking (APPN), native client interface architecture (NCIA) client/server topologies, and IBM Channel Attach.

• Cisco IOS Broadband Access Aggregation and DSL Configuration Guide

• Cisco IOS Broadband Access Aggregation and DSL Command Reference

PPP over ATM (PPPoA) and PPP over Ethernet (PPPoE).

• Cisco IOS Carrier Ethernet Configuration Guide

• Cisco IOS Carrier Ethernet Command Reference

Connectivity fault management (CFM), Ethernet Local Management Interface (ELMI), IEEE 802.3ad link bundling, Link Layer Discovery Protocol (LLDP), media endpoint discovery (MED), and Operation, Administration, and Maintenance (OAM).

• Cisco IOS Configuration Fundamentals Configuration Guide

• Cisco IOS Configuration Fundamentals Command Reference

Autoinstall, Setup, Cisco IOS command-line interface (CLI), Cisco IOS file system (IFS), Cisco IOS web browser user interface (UI), basic file transfer services, and file management.

• Cisco IOS DECnet Configuration Guide

• Cisco IOS DECnet Command Reference

DECnet protocol.

• Cisco IOS Dial Technologies Configuration Guide

• Cisco IOS Dial Technologies Command Reference

Asynchronous communications, dial backup, dialer technology, dial-in terminal services and AppleTalk remote access (ARA), dial-on-demand routing, dial-out, ISDN, large scale dial-out, modem and resource pooling, Multilink PPP (MLP), PPP, and virtual private dialup network (VPDN).

• Cisco IOS Flexible NetFlow Configuration Guide

• Cisco IOS Flexible NetFlow Command Reference

Flexible NetFlow.

• Cisco IOS High Availability Configuration Guide

• Cisco IOS High Availability Command Reference

A variety of high availability (HA) features and technologies that are available for different network segments (from enterprise access to service provider core) to facilitate creation of end-to-end highly available networks. Cisco IOS HA features and technologies can be categorized in three key areas: system-level resiliency, network-level resiliency, and embedded management for resiliency.

• Cisco IOS Integrated Session Border Controller Command Reference

A VoIP-enabled device that is deployed at the edge of networks. An SBC is a toolkit of functions, such as signaling interworking, network hiding, security, and quality of service (QoS).

Table 1 Cisco IOS Configuration Guides and Command References (continued)



vii

• Cisco IOS Intelligent Services Gateway Configuration Guide

• Cisco IOS Intelligent Services Gateway Command Reference

Subscriber identification, service and policy determination, session creation, session policy enforcement, session life-cycle management, accounting for access and service usage, and session state monitoring.

• Cisco IOS Interface and Hardware Component Configuration Guide

• Cisco IOS Interface and Hardware Component Command Reference

LAN interfaces, logical interfaces, serial interfaces, virtual interfaces, and interface configuration.

• Cisco IOS IP Addressing Services Configuration Guide

• Cisco IOS IP Addressing Services Command Reference

Address Resolution Protocol (ARP), Network Address Translation (NAT), Domain Name System (DNS), Dynamic Host Configuration Protocol (DHCP), and Next Hop Address Resolution Protocol (NHRP).

• Cisco IOS IP Application Services Configuration Guide

• Cisco IOS IP Application Services Command Reference

Enhanced Object Tracking (EOT), Gateway Load Balancing Protocol (GLBP), Hot Standby Router Protocol (HSRP), IP Services, Server Load Balancing (SLB), Stream Control Transmission Protocol (SCTP), TCP, Web Cache Communication Protocol (WCCP), User Datagram Protocol (UDP), and Virtual Router Redundancy Protocol (VRRP).

• Cisco IOS IP Mobility Configuration Guide

• Cisco IOS IP Mobility Command Reference

Mobile ad hoc networks (MANet) and Cisco mobile networks.

• Cisco IOS IP Multicast Configuration Guide

• Cisco IOS IP Multicast Command Reference

Protocol Independent Multicast (PIM) sparse mode (PIM-SM), bidirectional PIM (bidir-PIM), Source Specific Multicast (SSM), Multicast Source Discovery Protocol (MSDP), Internet Group Management Protocol (IGMP), and Multicast VPN (MVPN).

• Cisco IOS IP Routing: BFD Configuration Guide Bidirectional forwarding detection (BFD).

• Cisco IOS IP Routing: BGP Configuration Guide

• Cisco IOS IP Routing: BGP Command Reference

Border Gateway Protocol (BGP), multiprotocol BGP, multiprotocol BGP extensions for IP multicast.

• Cisco IOS IP Routing: EIGRP Configuration Guide

• Cisco IOS IP Routing: EIGRP Command Reference

Enhanced Interior Gateway Routing Protocol (EIGRP).

• Cisco IOS IP Routing: ISIS Configuration Guide

• Cisco IOS IP Routing: ISIS Command Reference

Intermediate System-to-Intermediate System (IS-IS).

• Cisco IOS IP Routing: ODR Configuration Guide

• Cisco IOS IP Routing: ODR Command Reference

On-Demand Routing (ODR).

• Cisco IOS IP Routing: OSPF Configuration Guide

• Cisco IOS IP Routing: OSPF Command Reference

Open Shortest Path First (OSPF).

• Cisco IOS IP Routing: Protocol-Independent Configuration Guide

• Cisco IOS IP Routing: Protocol-Independent Command Reference

IP routing protocol-independent features and commands. Generic policy-based routing (PBR) features and commands are included.




viii

• Cisco IOS IP Routing: RIP Configuration Guide

• Cisco IOS IP Routing: RIP Command Reference

Routing Information Protocol (RIP).

• Cisco IOS IP SLAs Configuration Guide

• Cisco IOS IP SLAs Command Reference

Cisco IOS IP Service Level Agreements (IP SLAs).

• Cisco IOS IP Switching Configuration Guide

• Cisco IOS IP Switching Command Reference

Cisco Express Forwarding, fast switching, and Multicast Distributed Switching (MDS).

• Cisco IOS IPv6 Configuration Guide

• Cisco IOS IPv6 Command Reference

For IPv6 features, protocols, and technologies, go to the IPv6 “Start Here” document.

• Cisco IOS ISO CLNS Configuration Guide

• Cisco IOS ISO CLNS Command Reference

ISO Connectionless Network Service (CLNS).

• Cisco IOS LAN Switching Configuration Guide

• Cisco IOS LAN Switching Command Reference

VLANs, Inter-Switch Link (ISL) encapsulation, IEEE 802.10 encapsulation, IEEE 802.1Q encapsulation, and multilayer switching (MLS).

• Cisco IOS Mobile Wireless Gateway GPRS Support Node Configuration Guide

• Cisco IOS Mobile Wireless Gateway GPRS Support Node Command Reference

Cisco IOS Gateway GPRS Support Node (GGSN) in a 2.5-generation general packet radio service (GPRS) and 3-generation universal mobile telecommunication system (UMTS) network.

• Cisco IOS Mobile Wireless Home Agent Configuration Guide

• Cisco IOS Mobile Wireless Home Agent Command Reference

Cisco Mobile Wireless Home Agent, an anchor point for mobile terminals for which mobile IP or proxy mobile IP services are provided.

• Cisco IOS Mobile Wireless Packet Data Serving Node Configuration Guide

• Cisco IOS Mobile Wireless Packet Data Serving Node Command Reference

Cisco Packet Data Serving Node (PDSN), a wireless gateway that is between the mobile infrastructure and standard IP networks and that enables packet data services in a code division multiple access (CDMA) environment.

• Cisco IOS Mobile Wireless Radio Access Networking Configuration Guide

• Cisco IOS Mobile Wireless Radio Access Networking Command Reference

Cisco IOS radio access network products.

• Cisco IOS Multiprotocol Label Switching Configuration Guide

• Cisco IOS Multiprotocol Label Switching Command Reference

MPLS Label Distribution Protocol (LDP), MPLS Layer 2 VPNs, MPLS Layer 3 VPNs, MPLS traffic engineering (TE), and MPLS Embedded Management (EM) and MIBs.

• Cisco IOS Multi-Topology Routing Configuration Guide

• Cisco IOS Multi-Topology Routing Command Reference

Unicast and multicast topology configurations, traffic classification, routing protocol support, and network management support.

• Cisco IOS NetFlow Configuration Guide

• Cisco IOS NetFlow Command Reference

Network traffic data analysis, aggregation caches, and export features.



http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-roadmap.html


ix

• Cisco IOS Network Management Configuration Guide

• Cisco IOS Network Management Command Reference

Basic system management; system monitoring and logging; troubleshooting, logging, and fault management; Cisco Discovery Protocol; Cisco IOS Scripting with Tool Control Language (Tcl); Cisco networking services (CNS); DistributedDirector; Embedded Event Manager (EEM); Embedded Resource Manager (ERM); Embedded Syslog Manager (ESM); HTTP; Remote Monitoring (RMON); SNMP; and VPN Device Manager Client for Cisco IOS software (XSM Configuration).

• Cisco IOS Novell IPX Configuration Guide

• Cisco IOS Novell IPX Command Reference

Novell Internetwork Packet Exchange (IPX) protocol.

• Cisco IOS Optimized Edge Routing Configuration Guide

• Cisco IOS Optimized Edge Routing Command Reference

Optimized edge routing (OER) monitoring; Performance Routing (PfR); and automatic route optimization and load distribution for multiple connections between networks.

• Cisco IOS Quality of Service Solutions Configuration Guide

• Cisco IOS Quality of Service Solutions Command Reference

Traffic queueing, traffic policing, traffic shaping, Modular QoS CLI (MQC), Network-Based Application Recognition (NBAR), Multilink PPP (MLP) for QoS, header compression, AutoQoS, Resource Reservation Protocol (RSVP), and weighted random early detection (WRED).

• Cisco IOS Security Command Reference Access control lists (ACLs); authentication, authorization, and accounting (AAA); firewalls; IP security and encryption; neighbor router authentication; network access security; network data encryption with router authentication; public key infrastructure (PKI); RADIUS; TACACS+; terminal access security; and traffic filters.

• Cisco IOS Security Configuration Guide: Securing the Data Plane

Access Control Lists (ACLs); Firewalls: Context-Based Access Control (CBAC) and Zone-Based Firewall; Cisco IOS Intrusion Prevention System (IPS); Flexible Packet Matching; Unicast Reverse Path Forwarding (uRPF); Threat Information Distribution Protocol (TIDP) and TMS.

• Cisco IOS Security Configuration Guide: Securing the Control Plane

Control Plane Policing, Neighborhood Router Authentication.

• Cisco IOS Security Configuration Guide: Securing User Services

AAA (includes 802.1x authentication and Network Admission Control [NAC]); Security Server Protocols (RADIUS and TACACS+); Secure Shell (SSH); Secure Access for Networking Devices (includes Autosecure and Role-Based CLI access); Lawful Intercept.

• Cisco IOS Security Configuration Guide: Secure Connectivity

Internet Key Exchange (IKE) for IPsec VPNs; IPsec Data Plane features; IPsec Management features; Public Key Infrastructure (PKI); Dynamic Multipoint VPN (DMVPN); Easy VPN; Cisco Group Encrypted Transport VPN (GETVPN); SSL VPN.




x

• Cisco IOS Service Advertisement Framework Configuration Guide

• Cisco IOS Service Advertisement Framework Command Reference

Cisco Service Advertisement Framework.

• Cisco IOS Service Selection Gateway Configuration Guide

• Cisco IOS Service Selection Gateway Command Reference

Subscriber authentication, service access, and accounting.

• Cisco IOS Software Activation Configuration Guide

• Cisco IOS Software Activation Command Reference

An orchestrated collection of processes and components to activate Cisco IOS software feature sets by obtaining and validating Cisco software licenses.

• Cisco IOS Software Modularity Installation and Configuration Guide

• Cisco IOS Software Modularity Command Reference

Installation and basic configuration of software modularity images, including installations on single and dual route processors, installation rollbacks, software modularity binding, software modularity processes, and patches.

• Cisco IOS Terminal Services Configuration Guide

• Cisco IOS Terminal Services Command Reference

DEC, local-area transport (LAT), and X.25 packet assembler/disassembler (PAD).

• Cisco IOS Virtual Switch Command Reference Virtual switch redundancy, high availability, and packet handling; converting between standalone and virtual switch modes; virtual switch link (VSL); Virtual Switch Link Protocol (VSLP).

Note For information about virtual switch configuration, see the product-specific software configuration information for the Cisco Catalyst 6500 series switch or for the Metro Ethernet 6500 series switch.

• Cisco IOS Voice Configuration Library

• Cisco IOS Voice Command Reference

Cisco IOS support for voice call control protocols, interoperability, physical and virtual interface management, and troubleshooting. The library includes documentation for IP telephony applications.

• Cisco IOS VPDN Configuration Guide

• Cisco IOS VPDN Command Reference

Layer 2 Tunneling Protocol (L2TP) dial-out load balancing and redundancy; L2TP extended failover; L2TP security VPDN; multihop by Dialed Number Identification Service (DNIS); timer and retry enhancements for L2TP and Layer 2 Forwarding (L2F); RADIUS Attribute 82 (tunnel assignment ID); shell-based authentication of VPDN users; tunnel authentication via RADIUS on tunnel terminator.

• Cisco IOS Wide-Area Networking Configuration Guide

• Cisco IOS Wide-Area Networking Command Reference

Frame Relay; Layer 2 Tunnel Protocol Version 3 (L2TPv3); L2VPN Pseudowire Redundancy; L2VPN Interworking; Layer 2 Local Switching; Link Access Procedure, Balanced (LAPB); and X.25.

• Cisco IOS Wireless LAN Configuration Guide

• Cisco IOS Wireless LAN Command Reference

Broadcast key rotation, IEEE 802.11x support, IEEE 802.1x authenticator, IEEE 802.1x local authentication service for Extensible Authentication Protocol-Flexible Authentication via Secure Tunneling (EAP-FAST), Multiple Basic Service Set ID (BSSID), Wi-Fi Multimedia (WMM) required elements, and Wi-Fi Protected Access (WPA).



About Cisco IOS Software DocumentationAdditional Resources and Documentation Feedback

xi

Table 2 lists documents and resources that supplement the Cisco IOS software configuration guides and command references.

Additional Resources and Documentation FeedbackWhat’s New in Cisco Product Documentation is released monthly and describes all new and revised Cisco technical documentation. The What’s New in Cisco Product Documentation publication also provides information about obtaining the following resources:

• Technical documentation

• Cisco product security overview

• Product alerts and field notices

• Technical assistance

Cisco IOS technical documentation includes embedded feedback forms where you can rate documents and provide suggestions for improvement. Your feedback helps us improve our documentation.

Table 2 Cisco IOS Supplementary Documents and Resources

Document Title or Resource Description

Cisco IOS Master Command List, All Releases Alphabetical list of all the commands documented in all Cisco IOS releases.

Cisco IOS New, Modified, Removed, and Replaced Commands

List of all the new, modified, removed, and replaced commands for a Cisco IOS release.

Cisco IOS System Message Guide List of Cisco IOS system messages and descriptions. System messages may indicate problems with your system, may be informational only, or may help diagnose problems with communications lines, internal hardware, or system software.

Cisco IOS Debug Command Reference Alphabetical list of debug commands including brief descriptions of use, command syntax, and usage guidelines.

Release Notes and Caveats Information about new and changed features, system requirements, and other useful information about specific software releases; information about defects in specific Cisco IOS software releases.

MIBs Files used for network monitoring. To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator.

RFCs Standards documents maintained by the Internet Engineering Task Force (IETF) that Cisco IOS documentation references where applicable. The full text of referenced RFCs may be obtained at the following URL:

http://www.rfc-editor.org/

http://www.cisco.com/go/mibs

http://www.rfc-editor.org/

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

About Cisco IOS Software DocumentationAdditional Resources and Documentation Feedback

xii

CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.



© 2008–2009 Cisco Systems, Inc. All rights reserved.

i

Using the Command-Line Interface in Cisco IOS Software

Last Updated: October 14, 2009

This document provides basic information about the command-line interface (CLI) in Cisco IOS software and how you can use some of the CLI features. This document contains the following sections:

• Initially Configuring a Device, page i

• Using the CLI, page ii

• Saving Changes to a Configuration, page xi

• Additional Information, page xii

For more information about using the CLI, see the “Using the Cisco IOS Command-Line Interface” section of the Cisco IOS Configuration Fundamentals Configuration Guide.

For information about the software documentation set, see the “About Cisco IOS Software Documentation” document.

Initially Configuring a DeviceInitially configuring a device varies by platform. For information about performing an initial configuration, see the hardware installation documentation that is provided with the original packaging of the product or go to the Product/Technologies Support area of Cisco.com at http://www.cisco.com/go/techdocs.

After you have performed the initial configuration and connected the device to your network, you can configure the device by using the console port or a remote access method, such as Telnet or Secure Shell (SSH), to access the CLI or by using the configuration method provided on the device, such as Security Device Manager.

http://www.cisco.com/en/US/docs/ios/fundamentals/configuration/guide/cf_cli-basics.html

http://www.cisco.com/en/US/docs/ios/preface/aboutios.html

http://www.cisco.com/en/US/docs/ios/preface/aboutios.html


Using the Command-Line Interface in Cisco IOS SoftwareUsing the CLI

ii

Changing the Default Settings for a Console or AUX Port

There are only two changes that you can make to a console port and an AUX port:

• Change the port speed with the config-register 0x command. Changing the port speed is not recommended. The well-known default speed is 9600.

• Change the behavior of the port; for example, by adding a password or changing the timeout value.

Note The AUX port on the Route Processor (RP) installed in a Cisco ASR 1000 series router does not serve any useful customer purpose and should be accessed only under the advisement of a customer support representative.

Using the CLIThis section describes the following topics:

• Understanding Command Modes, page ii

• Using the Interactive Help Feature, page v

• Understanding Command Syntax, page vi

• Understanding Enable and Enable Secret Passwords, page vii

• Using the Command History Feature, page viii

• Abbreviating Commands, page ix

• Using Aliases for CLI Commands, page ix

• Using the no and default Forms of Commands, page x

• Using the debug Command, page x

• Filtering Output Using Output Modifiers, page x

• Understanding CLI Error Messages, page xi

Understanding Command ModesThe CLI command mode structure is hierarchical, and each mode supports a set of specific commands. This section describes the most common of the many modes that exist.

Table 1 lists common command modes with associated CLI prompts, access and exit methods, and a brief description of how each mode is used.


iii

Table 1 CLI Command Modes

Command Mode Access Method Prompt Exit Method Mode Usage

User EXEC Log in. Router> Issue the logout or exit command.

• Change terminal settings.

• Perform basic tests.

• Display device status.

Privileged EXEC From user EXEC mode, issue the enable command.

Router# Issue the disable command or the exit command to return to user EXEC mode.

• Issue show and debug commands.

• Copy images to the device.

• Reload the device.

• Manage device configuration files.

• Manage device file systems.

Global configuration

From privileged EXEC mode, issue the configure terminal command.

Router(config)# Issue the exit command or the end command to return to privileged EXEC mode.

Configure the device.

Interface configuration

From global configuration mode, issue the interface command.

Router(config-if)# Issue the exit command to return to global configuration mode or the end command to return to privileged EXEC mode.

Configure individual interfaces.

Line configuration

From global configuration mode, issue the line vty or line console command.

Router(config-line)# Issue the exit command to return to global configuration mode or the end command to return to privileged EXEC mode.

Configure individual terminal lines.


iv

ROM monitor From privileged EXEC mode, issue the reload command. Press the Break key during the first 60 seconds while the system is booting.

rommon # >

The # symbol represents the line number and increments at each prompt.

Issue the continue command.

• Run as the default operating mode when a valid image cannot be loaded.

• Access the fall-back procedure for loading an image when the device lacks a valid image and cannot be booted.

• Perform password recovery when a Ctrl-Break sequence is issued within 60 seconds of a power-on or reload event.

Diagnostic (available only on Cisco ASR 1000 series routers)

The router boots or enters diagnostic mode in the following scenarios. When a Cisco IOS process or processes fail, in most scenarios the router will reload.

• A user-configured access policy was configured using the transport-map command, which directed the user into diagnostic mode.

• The router was accessed using an RP auxiliary port.

• A break signal (Ctrl-C, Ctrl-Shift-6, or the send break command) was entered, and the router was configured to enter diagnostic mode when the break signal was received.

Router(diag)# If a Cisco IOS process failure is the reason for entering diagnostic mode, the failure must be resolved and the router must be rebooted to exit diagnostic mode.

If the router is in diagnostic mode because of a transport-map configuration, access the router through another port or use a method that is configured to connect to the Cisco IOS CLI.

If the RP auxiliary port was used to access the router, use another port for access. Accessing the router through the auxiliary port is not useful for customer purposes.

• Inspect various states on the router, including the Cisco IOS state.

• Replace or roll back the configuration.

• Provide methods of restarting the Cisco IOS software or other processes.

• Reboot hardware (such as the entire router, an RP, an ESP, a SIP, a SPA) or other hardware components.

• Transfer files into or off of the router using remote access methods such as FTP, TFTP, and SCP.

Table 1 CLI Command Modes (continued)

Command Mode Access Method Prompt Exit Method Mode Usage


v

EXEC commands are not saved when the software reboots. Commands that you issue in a configuration mode can be saved to the startup configuration. If you save the running configuration to the startup configuration, these commands will execute when the software is rebooted. Global configuration mode is the highest level of configuration mode. From global configuration mode, you can enter a variety of other configuration modes, including protocol-specific modes.

ROM monitor mode is a separate mode that is used when the software cannot load properly. If a valid software image is not found when the software boots or if the configuration file is corrupted at startup, the software might enter ROM monitor mode. Use the question symbol (?) to view the commands that you can use while the device is in ROM monitor mode.

rommon 1 > ?alias set and display aliases commandboot boot up an external processconfreg configuration register utilitycont continue executing a downloaded imagecontext display the context of a loaded imagecookie display contents of cookie PROM in hex...rommon 2 >

The following example shows how the command prompt changes to indicate a different command mode:

Router> enableRouter# configure terminalRouter(config)# interface ethernet 1/1Router(config-if)# ethernetRouter(config-line)# exitRouter(config)# endRouter#

Note A keyboard alternative to the end command is Ctrl-Z.

Using the Interactive Help FeatureThe CLI includes an interactive Help feature. Table 2 describes the purpose of the CLI interactive Help commands.

Table 2 CLI Interactive Help Commands

Command Purpose

help Provides a brief description of the Help feature in any command mode.

? Lists all commands available for a particular command mode.

partial command? Provides a list of commands that begin with the character string (no space between the command and the question mark).

partial command<Tab> Completes a partial command name (no space between the command and <Tab>).

command ? Lists the keywords, arguments, or both associated with the command (space between the command and the question mark).

command keyword ? Lists the arguments that are associated with the keyword (space between the keyword and the question mark).


vi

The following examples show how to use the help commands:

helpRouter> help

Help may be requested at any point in a command by entering a question mark '?'. If nothing matches, the help list will be empty and you must backup until entering a '?' shows the available options.

Two styles of help are provided:

1. Full help is available when you are ready to enter a command argument (e.g. 'show ?') and describes each possible argument.

2. Partial help is provided when an abbreviated argument is entered and you want to know what arguments match the input (e.g. 'show pr?'.)

?Router# ?Exec commands: access-enable Create a temporary access-List entry access-profile Apply user-profile to interface access-template Create a temporary access-List entry alps ALPS exec commands archive manage archive files<snip>

partial command?Router(config)# zo?zone zone-pair

partial command<Tab>Router(config)# we<Tab> webvpn

command ?Router(config-if)# pppoe ? enable Enable pppoe max-sessions Maximum PPPOE sessions

command keyword ?Router(config-if)# pppoe enable ? group attach a BBA group <cr>

Understanding Command SyntaxCommand syntax is the format in which a command should be entered in the CLI. Commands include the name of the command, keywords, and arguments. Keywords are alphanumeric strings that are used literally. Arguments are placeholders for values that a user must supply. Keywords and arguments may be required or optional.

Specific conventions convey information about syntax and command elements. Table 3 describes these conventions.


vii

The following examples show syntax conventions:

Router(config)# ethernet cfm domain ? WORD domain nameRouter(config)# ethernet cfm domain dname ? level Router(config)# ethernet cfm domain dname level ? <0-7> maintenance level numberRouter(config)# ethernet cfm domain dname level 7 ? <cr>

Router(config)# snmp-server file-transfer access-group 10 ? protocol protocol options <cr>

Router(config)# logging host ? Hostname or A.B.C.D IP address of the syslog server ipv6 Configure IPv6 syslog server

Understanding Enable and Enable Secret PasswordsSome privileged EXEC commands are used for actions that impact the system, and it is recommended that you set a password for these commands to prevent unauthorized use. Two types of passwords, enable (not encrypted) and enable secret (encrypted), can be set. The following commands set these passwords and are issued in global configuration mode:

• enable password

• enable secret password

Table 3 CLI Syntax Conventions

Symbol/Text Function Notes

< > (angle brackets) Indicate that the option is an argument.

Sometimes arguments are displayed without angle brackets.

A.B.C.D. Indicates that you must enter a dotted decimal IP address.

Angle brackets (< >) are not always used to indicate that an IP address is an argument.

WORD (all capital letters) Indicates that you must enter one word.

Angle brackets (< >) are not always used to indicate that a WORD is an argument.

LINE (all capital letters) Indicates that you must enter more than one word.

Angle brackets (< >) are not always used to indicate that a LINE is an argument.

<cr> (carriage return) Indicates the end of the list of available keywords and arguments, and also indicates when keywords and arguments are optional. When <cr> is the only option, you have reached the end of the branch or the end of the command if the command has only one branch.

—


viii

Using an enable secret password is recommended because it is encrypted and more secure than the enable password. When you use an enable secret password, text is encrypted (unreadable) before it is written to the config.text file. When you use an enable password, the text is written as entered (readable) to the config.text file.

Each type of password is case sensitive, can contain from 1 to 25 uppercase and lowercase alphanumeric characters, and can start with a numeral. Spaces are also valid password characters; for example, “two words” is a valid password. Leading spaces are ignored, but trailing spaces are recognized.

Note Both password commands have numeric keywords that are single integer values. If you choose a numeral for the first character of your password followed by a space, the system will read the number as if it were the numeric keyword and not as part of your password.

When both passwords are set, the enable secret password takes precedence over the enable password.

To remove a password, use the no form of the commands: no enable password or no enable secret password.

For more information about password recovery procedures for Cisco products, see http://www.cisco.com/en/US/products/sw/iosswrel/ps1831/ products_tech_note09186a00801746e6.shtml.

Using the Command History FeatureThe command history feature saves, in a command history buffer, the commands that you enter during a session. The default number of saved commands is 10, but the number is configurable within the range of 0 to 256. This command history feature is particularly useful for recalling long or complex commands.

To change the number of commands saved in the history buffer for a terminal session, issue the terminal history size command:

Router# terminal history size num

A command history buffer is also available in line configuration mode with the same default and configuration options. To set the command history buffer size for a terminal session in line configuration mode, issue the history command:

Router(config-line)# history [size num]

To recall commands from the history buffer, use the following methods:

• Press Ctrl-P or the Up Arrow key—Recalls commands beginning with the most recent command. Repeat the key sequence to recall successively older commands.

• Press Ctrl-N or the Down Arrow key—Recalls the most recent commands in the history buffer after they have been recalled using Ctrl-P or the Up Arrow key. Repeat the key sequence to recall successively more recent commands.

Note The arrow keys function only on ANSI-compatible terminals such as the VT100.

• Issue the show history command in user EXEC or privileged EXEC mode—Lists the most recent commands that you entered. The number of commands that are displayed is determined by the setting of the terminal history size and history commands.

http://www.cisco.com/en/US/products/sw/iosswrel/ps1831/products_tech_note09186a00801746e6.shtml

http://www.cisco.com/en/US/products/sw/iosswrel/ps1831/products_tech_note09186a00801746e6.shtml


ix

The command history feature is enabled by default. To disable this feature for a terminal session, issue the terminal no history command in user EXEC or privileged EXEC mode or the no history command in line configuration mode.

Abbreviating CommandsTyping a complete command name is not always required for the command to execute. The CLI recognizes an abbreviated command when the abbreviation contains enough characters to uniquely identify the command. For example, the show version command can be abbreviated as sh ver. It cannot be abbreviated as s ver because s could mean show, set, or systat. The sh v abbreviation also is not valid because the show command has vrrp as a keyword in addition to version. (Command and keyword examples are from Cisco IOS Release 12.4(13)T.)

Using Aliases for CLI CommandsTo save time and the repetition of entering the same command multiple times, you can use a command alias. An alias can be configured to do anything that can be done at the command line, but an alias cannot move between modes, type in passwords, or perform any interactive functions.

Table 4 shows the default command aliases.

To create a command alias, issue the alias command in global configuration mode. The syntax of the command is alias mode command-alias original-command. Following are some examples:

• Router(config)# alias exec prt partition—privileged EXEC mode

• Router(config)# alias configure sb source-bridge—global configuration mode

• Router(config)# alias interface rl rate-limit—interface configuration mode

To view both default and user-created aliases, issue the show alias command.

For more information about the alias command, see http://www.cisco.com/en/US/docs/ios/fundamentals/command/reference/cf_a1.html.

Table 4 Default Command Aliases

Command Alias Original Command

h help

lo logout

p ping

s show

u or un undebug

w where

http://www.cisco.com/en/US/docs/ios/fundamentals/command/reference/cf_a1.html


x

Using the no and default Forms of CommandsMost configuration commands have a no form that is used to reset a command to its default value or disable a feature or function. For example, the ip routing command is enabled by default. To disable this command, you would issue the no ip routing command. To re-enable IP routing, you would issue the ip routing command.

Configuration commands may also have a default form, which returns the command settings to their default values. For commands that are disabled by default, using the default form has the same effect as using the no form of the command. For commands that are enabled by default and have default settings, the default form enables the command and returns the settings to their default values.

The no form is documented in the command pages of command references. The default form is generally documented in the command pages only when the default form performs a different function than the plain and no forms of the command. To see what default commands are available on your system, enter default ? in the appropriate command mode.

Using the debug CommandA debug command produces extensive output that helps you troubleshoot problems in your network. These commands are available for many features and functions within Cisco IOS software. Some debug commands are debug all, debug aaa accounting, and debug mpls packets. To use debug commands during a Telnet session with a device, you must first enter the terminal monitor command. To turn off debugging completely, you must enter the undebug all command.

For more information about debug commands, see the Cisco IOS Debug Command Reference at http://www.cisco.com/en/US/docs/ios/debug/command/reference/db_book.html.

Caution Debugging is a high priority and high CPU utilization process that can render your device unusable. Use debug commands only to troubleshoot specific problems. The best times to run debugging are during periods of low network traffic and when few users are interacting with the network. Debugging during these periods decreases the likelihood that the debug command processing overhead will affect network performance or user access or response times.

Filtering Output Using Output ModifiersMany commands produce lengthy output that may use several screens to display. Using output modifiers, you can filter this output to show only the information that you want to see.

The following three output modifiers are available:

• begin regular-expression—Displays the first line in which a match of the regular expression is found and all lines that follow.

• include regular-expression—Displays all lines in which a match of the regular expression is found.

• exclude regular-expression—Displays all lines except those in which a match of the regular expression is found.

To use one of these output modifiers, type the command followed by the pipe symbol (|), the modifier, and the regular expression that you want to search for or filter. A regular expression is a case-sensitive alphanumeric pattern. It can be a single character or number, a phrase, or a more complex string.

http://www.cisco.com/en/US/docs/ios/debug/command/reference/db_book.html

Using the Command-Line Interface in Cisco IOS SoftwareSaving Changes to a Configuration

xi

The following example illustrates how to filter output of the show interface command to display only lines that include the expression “protocol.”

Router# show interface | include protocol

FastEthernet0/0 is up, line protocol is upSerial4/0 is up, line protocol is upSerial4/1 is up, line protocol is upSerial4/2 is administratively down, line protocol is downSerial4/3 is administratively down, line protocol is down

Understanding CLI Error MessagesYou may encounter some error messages while using the CLI. Table 5 shows the common CLI error messages.

For more system error messages, see the following document:

• Cisco IOS Release 12.4T System Message Guide

Saving Changes to a ConfigurationTo save changes that you made to the configuration of a device, you must issue the copy running-config startup-config command or the copy system:running-config nvram:startup-config command. When you issue these commands, the configuration changes that you made are saved to the startup configuration and saved when the software reloads or power to the device is turned off or interrupted. The following example shows the syntax of the copy running-config startup-config command:

Router# copy running-config startup-configDestination filename [startup-config]?

You press Enter to accept the startup-config filename (the default), or type a new filename and then press Enter to accept that name. The following output is displayed indicating that the configuration was saved.

Table 5 Common CLI Error Messages

Error Message Meaning How to Get Help

% Ambiguous command: “show con”

You did not enter enough characters for the command to be recognized.

Reenter the command followed by a space and a question mark (?). The keywords that you are allowed to enter for the command appear.

% Incomplete command. You did not enter all the keywords or values required by the command.

Reenter the command followed by a space and a question mark (?). The keywords that you are allowed to enter for the command appear.

% Invalid input detected at “^” marker.

You entered the command in-correctly. The caret (^) marks the point of the error.

Enter a question mark (?) to display all the commands that are available in this command mode. The keywords that you are allowed to enter for the command appear.

http://www.cisco.com/en/US/docs/ios/12_4t/system/messages/124tsms.html

Using the Command-Line Interface in Cisco IOS SoftwareAdditional Information

xii

Building configuration...[OK]Router#

On most platforms, the configuration is saved to NVRAM. On platforms with a Class A flash file system, the configuration is saved to the location specified by the CONFIG_FILE environment variable. The CONFIG_FILE variable defaults to NVRAM.

Additional Information • “Using the Cisco IOS Command-Line Interface” section of the Cisco IOS Configuration

Fundamentals Configuration Guide


• Cisco Product/Technology Support


• Support area on Cisco.com (also search for documentation by task or product)

http://www.cisco.com/en/US/support/index.html

• Software Download Center (downloads; tools; licensing, registration, advisory, and general information) (requires Cisco.com user ID and password)

http://www.cisco.com/kobayashi/sw-center/

• Error Message Decoder, a tool to help you research and resolve error messages for Cisco IOS software

http://www.cisco.com/pcgi-bin/Support/Errordecoder/index.cgi

• Command Lookup Tool, a tool to help you find detailed descriptions of Cisco IOS commands (requires Cisco.com user ID and password)


• Output Interpreter, a troubleshooting tool that analyzes command output of supported show commands

https://www.cisco.com/pcgi-bin/Support/OutputInterpreter/home.pl







http://www.cisco.com/en/US/support/index.html

http://www.cisco.com/kobayashi/sw-center/

http://www.cisco.com/pcgi-bin/Support/Errordecoder/index.cgi


https://www.cisco.com/pcgi-bin/Support/OutputInterpreter/home.pl

Americas Headquarters:Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA

Configuring Routing Information Protocol

First Published: February 27, 2006Last Updated: April 23, 2010

Routing Information Protocol (RIP) is a commonly used routing protocol in small to medium TCP/IP networks. It is a stable protocol that uses a distance-vector algorithm to calculate routes.

Finding Feature InformationYour software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the “Feature Information for Configuring RIP” section on page 29.


Contents• Prerequisites for Configuring RIP, page 2

• Restrictions for Configuring RIP, page 2

• Information About Configuring RIP, page 2

• How to Configure RIP, page 8

• Configuration Examples for RIP, page 23

• Additional References, page 27

• Feature Information for Configuring RIP, page 29

• Glossary, page 31


Configuring Routing Information Protocol Prerequisites for Configuring RIP

2

Prerequisites for Configuring RIPBefore configuring RIP, the ip routing command is configured. For more information about configuring the ip routing command, see the Cisco IOS IP Routing: RIP Command Reference.

Restrictions for Configuring RIPThe metric that RIP uses to rate the value of different routes is hop count. The hop count is the number of routers that can be traversed in a route. A directly connected network has a metric of zero; an unreachable network has a metric of 16. This small range of metrics makes RIP an unsuitable routing protocol for large networks.

Information About Configuring RIPTo configure the Routing Information Protocol (RIP), you should understand the following concepts:

• RIP Overview, page 2

• RIP Routing Updates, page 3

• RIP Routing Metric, page 3

• RIP Version 2 and Enabling Authentication, page 3

• Exchange of Routing Information, page 4

• RIP Route Summarization, page 4

• Split Horizon Mechanism, page 5

• Interpacket Delay for RIP Updates, page 6

• RIP Optimization over WAN Circuits, page 6

• Source IP Addresses, page 6

• Neighbor Router Authentication, page 6

• IP-RIP Delay Start, page 7

RIP OverviewRouting Information Protocol uses broadcast User Datagram Protocol (UDP) data packets to exchange routing information. Cisco IOS software sends routing information updates every 30 seconds, which is termed advertising. If a router does not receive an update from another router for 180 seconds or more, it marks the routes served by the nonupdating router as being unusable. If there is still no update after 240 seconds, the router removes all routing table entries for the nonupdating router.

A router that is running RIP can receive a default network via an update from another router that is running RIP, or the router can source (generate) the default network itself with RIP. In both cases, the default network is advertised through RIP to other RIP neighbors.

The Cisco implementation of RIP Version 2 supports plain text and Message Digest 5 (MD5) authentication, route summarization, classless interdomain routing (CIDR), and variable-length subnet masks (VLSMs).

http://www.cisco.com/en/US/docs/ios/iproute_rip/command/reference/irr_book.html

Configuring Routing Information Protocol Information About Configuring RIP

3

RIP Routing UpdatesRIP sends routing-update messages at regular intervals and when the network topology changes. When a router receives a RIP routing update that includes changes to an entry, the router updates its routing table to reflect the new route. The metric value for the path is increased by 1, and the sender is indicated as the next hop. RIP routers maintain only the best route (the route with the lowest metric value) to a destination. After updating its routing table, the router immediately begins transmitting RIP routing updates to inform other network routers of the change. These updates are sent independently of the regularly scheduled updates that RIP routers send.

RIP Routing MetricRIP uses a single routing metric (hop count) to measure the distance between the source and a destination network. Each hop in a path from source to destination is assigned a hop count value, which is typically 1. When a router receives a routing update that contains a new or changed destination network entry, the router adds 1 to the metric value indicated in the update and enters the network in the routing table. The IP address of the sender is used as the next hop. If the network of an interface network is not specified, it will not be advertised in any RIP update.

RIP Version 2 and Enabling AuthenticationThe Cisco implementation of RIP Version 2 supports authentication, key management, route summarization, CIDR, and VLSMs. For more information about managing authentication keys see the “Managing Authentication Keys” section of the “Configuring IP Routing Protocol-Independent Features” module.

By default, the software receives RIP Version 1 and Version 2 packets, but sends only Version 1 packets. You can configure the software to receive and send only Version 1 packets. Alternatively, you can configure the software to receive and send only Version 2 packets. To override the default behavior, you can configure which RIP version an interface sends. Similarly, you can also control how packets received from an interface are processed.

RIP Version 1 does not support authentication. If you are sending and receiving RIP Version 2 packets, you can enable RIP authentication on an interface.

The key chain determines the set of keys that can be used on the interface. If a key chain is not configured, no authentication is performed on that interface, not even the default authentication. Therefore, you must also perform the tasks in the section “Managing Authentication Keys” in the “Configuring IP Routing Protocol-Independent Features” module.

We support two modes of authentication on an interface for which RIP authentication is enabled: plain text authentication and MD5 authentication. The default authentication in every RIP Version 2 packet is plain text authentication.

Note Do not use plain text authentication in RIP packets for security purposes, because the unencrypted authentication key is sent in every RIP Version 2 packet. Use plain text authentication when security is not an issue, for example, to ensure that misconfigured hosts do not participate in routing.

http://cisco.com/en/US/docs/ios/iproute_pi/configuration/guide/iri_ip_prot_indep.html




4

Exchange of Routing InformationRIP is normally a broadcast protocol, and in order for RIP routing updates to reach nonbroadcast networks, you must configure the Cisco IOS software to permit this exchange of routing information.

To control the set of interfaces with which you want to exchange routing updates, you can disable the sending of routing updates on specified interfaces by configuring the passive-interface router configuration command. See the discussion on filtering in the “Filter Routing Information” section in the “Configuring IP Routing Protocol-Independent Features” module.

An offset list is the mechanism for increasing incoming and outgoing metrics to routes learned via RIP. Optionally, you can limit the offset list with either an access list or an interface. To increase the value of routing metrics, use the following command in router configuration mode:

Routing protocols use several timers that determine such variables as the frequency of routing updates, the length of time before a route becomes invalid, and other parameters. You can adjust these timers to tune routing protocol performance to better suit your internetwork needs. You can make the following timer adjustments:

• The rate (time in seconds between updates) at which routing updates are sent

• The interval of time (in seconds) after which a route is declared invalid

• The interval (in seconds) during which routing information regarding better paths is suppressed

• The amount of time (in seconds) that must pass before a route is removed from the routing table

• The amount of time for which routing updates will be postponed

It also is possible to tune the IP routing support in the software to enable faster convergence of the various IP routing algorithms, and, hence, quicker fallback to redundant routers. The total effect is to minimize disruptions to end users of the network in situations where quick recovery is essential

In addition, an address family can have explicitly specified timers that apply to that address-family (or VRF) only. The timers basic command must be specified for an address family or the system defaults for the timers basic command are used regardless of what is configured for RIP routing. The VRF does not inherit the timer values from the base RIP configuration. The VRF will always use the system default timers unless explicitly changed using the timers basic command.

See the “Address Family Timers: Example” section at the end of this chapter for examples of adjusting timers for an address family (VRF).

RIP Route SummarizationSummarizing routes in RIP Version 2 improves scalability and efficiency in large networks. Summarizing IP addresses means that there is no entry for child routes (routes that are created for any combination of the individual IP addresses contained within a summary address) in the RIP routing table, reducing the size of the table and allowing the router to handle more routes.

Summary IP address functions more efficiently than multiple individually advertised IP routes for the following reasons:

• The summarized routes in the RIP database are processed first.

• Any associated child routes that are included in a summarized route are skipped as RIP looks through the routing database, reducing the processing time required.



5

Cisco routers can summarize routes in two ways:

• Automatically, by summarizing subprefixes to the classful network boundary when crossing classful network boundaries (automatic summary).

Note Automatic summary is enabled by default.

• As specifically configured, advertising a summarized local IP address pool on the specified interface (on a network access server) so that the address pool can be provided to dialup clients.

When RIP determines that a summary address is required in the RIP database, a summary entry is created in the RIP routing database. As long as there are child routes for a summary address, the address remains in the routing database. When the last child route is removed, the summary entry also is removed from the database. This method of handling database entries reduces the number of entries in the database because each child route is not listed in an entry, and the aggregate entry itself is removed when there are no longer any valid child routes for it.

RIP Version 2 route summarization requires that the lowest metric of the “best route” of an aggregated entry, or the lowest metric of all current child routes, be advertised. The best metric for aggregated summarized routes is calculated at route initialization or when there are metric modifications of specific routes at advertisement time, and not at the time the aggregated routes are advertised.

The ip summary-address rip router configuration command causes the router to summarize a given set of routes learned via RIP Version 2 or redistributed into RIP Version 2. Host routes are especially applicable for summarization.

See the “Route Summarization: Example” section at the end of this chapter for examples of using split horizon.

You can verify which routes are summarized for an interface using the show ip protocols EXEC command. You can check summary address entries in the RIP database. These entries will appear in the database only if relevant child routes are being summarized. To display summary address entries in the RIP routing database entries if there are relevant routes being summarized based upon a summary address, use the show ip rip database command in EXEC mode. When the last child route for a summary address becomes invalid, the summary address is also removed from the routing table.

Split Horizon MechanismNormally, routers that are connected to broadcast-type IP networks and that use distance-vector routing protocols employ the split horizon mechanism to reduce the possibility of routing loops. Split horizon blocks information about routes from being advertised by a router out of any interface from which that information originated. This behavior usually optimizes communications among multiple routers, particularly when links are broken. However, with nonbroadcast networks (such as Frame Relay and Switched Multimegabit Digital System [SMDS]), situations can arise for which this behavior is less than ideal. For these situations, you may want to disable split horizon with RIP.

If an interface is configured with secondary IP addresses and split horizon is enabled, updates might not be sourced by the secondary address. One routing update is sourced per network number unless split horizon is disabled.


6

Interpacket Delay for RIP UpdatesBy default, the software adds no delay between packets in a multiple-packet RIP update being sent. If you have a high-end router sending to a low-speed router, you might want to add such interpacket delay to RIP updates, in the range of 8 to 50 milliseconds.

RIP Optimization over WAN CircuitsRouters are used on connection-oriented networks to allow potential connectivity to many remote destinations. Circuits on the WAN are established on demand and are relinquished when the traffic subsides. Depending on the application, the connection between any two sites for user data could be short and relatively infrequent.

Source IP AddressesBy default, the software validates the source IP address of incoming RIP routing updates. If that source address is not valid, the software discards the routing update. You might want to disable this feature if you have a router that is “off network” and you want to receive its updates. However, disabling this feature is not recommended under normal circumstances.

Neighbor Router AuthenticationYou can prevent your router from receiving fraudulent route updates by configuring neighbor router authentication. When configured, neighbor authentication occurs whenever routing updates are exchanged between neighbor routers. This authentication ensures that a router receives reliable routing information from a trusted source.

Without neighbor authentication, unauthorized or deliberately malicious routing updates could compromise the security of your network traffic. A security compromise could occur if an unfriendly party diverts or analyzes your network traffic. For example, an unauthorized router could send a fictitious routing update to convince your router to send traffic to an incorrect destination. This diverted traffic could be analyzed to learn confidential information about your organization or merely used to disrupt your organization’s ability to effectively communicate using the network. Neighbor authentication prevents any such fraudulent route updates from being received by your router.

When neighbor authentication has been configured on a router, the router authenticates the source of each routing update packet that it receives. This is accomplished by the exchange of an authenticating key (sometimes referred to as a password) that is known to both the sending and the receiving router.

There are two types of neighbor authentication used: plain text authentication and Message Digest Algorithm Version 5 (MD5) authentication. Both forms work in the same way, with the exception that MD5 sends a “message digest” instead of the authenticating key itself. The message digest is created using the key and a message, but the key itself is not sent, preventing it from being read while it is being transmitted. Plain text authentication sends the authenticating key itself over the wire.

Note Note that plain text authentication is not recommended for use as part of your security strategy. Its primary use is to avoid accidental changes to the routing infrastructure. Using MD5 authentication, however, is a recommended security practice.


7

In plain text authentication, each participating neighbor router must share an authenticating key. This key is specified at each router during configuration. Multiple keys can be specified with some protocols; each key must then be identified by a key number.

In general, when a routing update is sent, the following authentication sequence occurs:

Step 1 A router sends a routing update with a key and the corresponding key number to the neighbor router. In protocols that can have only one key, the key number is always zero.

The receiving (neighbor) router checks the received key against the same key stored in its own memory.

Step 2 If the two keys match, the receiving router accepts the routing update packet. If the two keys do not match, the routing update packet is rejected.

MD5 authentication works similarly to plain text authentication, except that the key is never sent over the wire. Instead, the router uses the MD5 algorithm to produce a “message digest” of the key (also called a “hash”). The message digest is then sent instead of the key itself. This ensures that nobody can eavesdrop on the line and learn keys during transmission.

Another form of neighbor router authentication is to configure key management using key chains. When you configure a key chain, you specify a series of keys with lifetimes, and the Cisco IOS software rotates through each of these keys. This decreases the likelihood that keys will be compromised. To find complete configuration information for key chains, refer to the “Managing Authentication Keys” section in the “Configuring IP Routing Protocol-Independent Features” module of the Cisco IOS IP Routing: Protocol-Independent Configuration Guide.

IP-RIP Delay StartThe IP-RIP Delay Start feature is used on Cisco routers to delay the initiation of RIPv2 neighbor sessions until the network connectivity between the neighbor routers is fully operational, thereby ensuring that the sequence number of the first MD5 packet that the router sends to the non-Cisco neighbor router is 0. The default behavior for a router configured to establish RIPv2 neighbor sessions with a neighbor router using MD5 authentication is to start sending MD5 packets when the physical interface is up.


Configuring Routing Information Protocol How to Configure RIP

8

How to Configure RIPThis section contains the following tasks:

• Enabling RIP and Configuring RIP Parameters, page 8 (Required)

• Specifying a RIP Version and Enabling Authentication, page 10 (Optional)

• Summarizing RIP Routes, page 11 (Optional)

• Enabling or Disabling Split Horizon, page 13 (Optional)

• Disabling the Validation of Source IP Addresses, page 14 (Optional)

• Configuring Interpacket Delay, page 15 (Optional)

• Optimizing RIP over WAN, page 16 (Optional)

• Configuring IP-RIP Delay Start for Routers Connected by a Frame Relay Network, page 18 (Required)

Enabling RIP and Configuring RIP ParametersPerform the steps in this section to enable RIP and to configure RIP parameters.

Offset-list

An offset list is the mechanism for increasing incoming and outgoing metrics to routes learned via RIP. This is done to provide a local mechanism for increasing the value of routing metrics. Optionally, you can limit the offset list with either an access list or an interface.

Timers

Routing protocols use several timers that determine such variables as the frequency of routing updates, the length of time before a route becomes invalid, and other parameters. You can adjust these timers to tune routing protocol performance to better suit your internetwork needs. You can make the following timer adjustments:

• The rate (time in seconds between updates) at which routing updates are sent

• The interval of time (in seconds) after which a route is declared invalid

• The interval (in seconds) during which routing information regarding better paths is suppressed

• The amount of time (in seconds) that must pass before a route is removed from the routing table

• The amount of time for which routing updates will be postponed

It also is possible to tune the IP routing support in the software to enable faster convergence of the various IP routing algorithms, and, hence, quicker fallback to redundant routers. The total effect is to minimize disruptions to end users of the network in situations where quick recovery is essential.

SUMMARY STEPS

1. enable

2. configure terminal

3. router rip


9

4. network ip-address

5. neighbor ip-address

6. offset-list [access-list-number | access-list-name] {in | out} offset [interface-type interface-number]

7. timers basic update invalid holddown flush [sleeptime]

8. end

DETAILED STEPS

Command or Action Purpose

Step 1 enable

Example:Router> enable

Enables privileged EXEC mode.

• Enter your password if prompted.

Step 2 configure terminal

Example:Router# configure terminal

Enters global configuration mode.

Step 3 router rip

Example:Router(config)# router rip

Enables a RIP routing process and enters router configuration mode.

Step 4 network ip-address

Example:Router(config-router)# network 10.1.1.0

Associates a network with a RIP routing process.

Step 5 neighbor ip-address

Example:Router(config-router)# neighbor 1.1.1.2

Defines a neighboring router with which to exchange routing information.

Step 6 offset-list [access-list-number | access-list-name] {in | out} offset [interface-type interface-number]

Example:Router(config-router)# offset-list 98 in 1 Ethernet 1/0

(Optional) Applies an offset to routing metrics.

Step 7 timers basic update invalid holddown flush [sleeptime]

Example:Router(config-router)# timers basic 1 2 3 4

(Optional) Adjusts routing protocol timers.

Step 8 end

Example:Router(config-router)# end

Exits router configuration mode and returns to privileged EXEC mode.


10

Specifying a RIP Version and Enabling AuthenticationPerform this task to specify a RIP version and enable authentication.

SUMMARY STEPS

1. enable


3. router rip

4. version {1 | 2}

5. exit

6. interface type number

7. ip rip send version [1] [2]

8. ip rip receive version [1] [2]

9. ip rip authentication key-chain name-of-chain

10. ip rip authentication mode {text | md5}

11. end

DETAILED STEPS


Step 1 enable







Step 3 router rip


Enters router configuration mode.

Step 4 version {1 | 2}

Example:Router(config-router)# version 1

Configures an interface to send only RIP Version 1 packets.

Step 5 exit

Example:Router(config-router)# exit

Exits the router configuration mode and enters the global configuration mode.


11

Summarizing RIP RoutesRIP Version 2 supports automatic route summarization by default. The software summarizes subprefixes to the classful network boundary when classful network boundaries are crossed.

If you have disconnected subnets, disable automatic route summarization to advertise the subnets. When route summarization is disabled, the software sends subnet and host routing information across classful network boundaries. To disable automatic summarization, use the no auto-summary command in router configuration mode.

Restrictions

Supernet advertisement (advertising any network prefix less than its classful major network) is not allowed in RIP route summarization, other than advertising a supernet learned in the routing tables. Supernets learned on any interface that is subject to configuration are still learned.

For example, the following summarization is invalid: (invalid supernet summarization)

Router(config)# interface Ethernet 1 Router(config-if)# ip summary-address rip 10.0.0.0 252.0.0.0 ..

Step 6 interface type number

Example:Router(config)# interface Ethernet 3/0

Enters interface configuration mode.

Step 7 ip rip send version [1] [2]

Example:Router(config-if)# ip rip send version 1

Configures an interface to send only RIP Version 1 packets.

Step 8 ip rip receive version [1] [2]

Example:Router(config-if)# ip rip receive version 1

Configures an interface to accept only RIP Version 1 packets.

Step 9 ip rip authentication key-chain name-of-chain

Example:Router(config-if)# ip rip authentication key-chain chainname

Enables RIP authentication.

Step 10 ip rip authentication mode {text | md5}

Example:Router(config-if)# ip rip authentication mode md5

Configures the interface to use MD5 digest authentication (or let it default to plain text authentication).

Step 11 end

Example:Router(config-if)# end

Exits interface configuration mode and returns to privileged EXEC mode.



12

.

Each route summarization on an interface must have a unique major network, even if the subnet mask is unique. For example, the following is not permitted:

Router(config)# interface Ethernet 1 Router(config)# ip summary-address rip 10.1.0.0 255.255.0.0 Router(config)# ip summary-address rip 10.2.2.0 255.255.255.0 ...

SUMMARY STEPS

1. enable



4. ip summary-address rip ip-address network-mask

5. exit

6. rip router

7. no auto-summary

8. end

DETAILED STEPS


Step 1 enable









Enters the interface configuration mode.

Step 4 ip summary-address rip ip-address network-mask

Example:Router(config-if)# ip summary-address rip 10.2.0.0 255.255.0.0

Specifies the IP address and network mask that identify the routes to be summarized.

Step 5 exit

Example:Router(config-if)# exit

Exits the interface configuration mode.


13

Enabling or Disabling Split HorizonTo enable or disable split horizon, use the following commands in interface configuration mode, as needed.

SUMMARY STEPS

1. enable



4. ip split-horizon

5. no ip split-horizon

6. end

DETAILED STEPS

Step 6 router rip


Enters the router configuration mode.

Step 7 no auto-summary

Example:Router(config-router)# no auto-summary

Used in router configuration mode, disables automatic summarization.

Step 8 end





Step 1 enable











14

Disabling the Validation of Source IP AddressesPerform this task to disable the default function that validates the source IP addresses of incoming routing updates.

Restrictions

Split horizon for Frame Relay and SMDS encapsulation is disabled by default. Split horizon is not disabled by default for interfaces using any of the X.25 encapsulations. For all other encapsulations, split horizon is enabled by default.

Note In general, changing the state of the default is not recommended unless you are certain that your application requires making a change in order to advertise routes properly. Remember that if split horizon is disabled on a serial interface (and that interface is attached to a packet-switched network), you must disable split horizon for all routers in any relevant multicast groups on that network.

Note Summarized network will not be advertised when split horizon is enabled.

SUMMARY STEPS

1. enable



4. ip split-horizon

5. exit

6. router rip

7. no validate-update-source

8. end

Step 4 ip split-horizon

Example:Router(config-if)# ip split-horizon

Enables split horizon.

Step 5 no ip split-horizon

Example:Router(config-if)# no ip split-horizon

Disables split horizon.

Step 6 end


Exits interface configuration mode and returns to privileged EXEC mode.



15

DETAILED STEPS

Configuring Interpacket DelayPerform this to configure interpacket delay.

SUMMARY STEPS

1. enable




Step 1 enable










Step 4 ip split-horizon

Example:Router(config-if)# ip split-horizon

Enables split horizon.

Step 5 exit


Exits interface configuration mode.

Step 6 router rip



Step 7 no validate-update-source

Example:Router(config-router)# no validate-update-source

Disables the validation of the source IP address of incoming RIP routing updates.

Step 8 end




16

4. exit

5. router rip

6. output-delay milliseconds

7. end

DETAILED STEPS

Optimizing RIP over WANThere are two problems when RIP is not optimized:

• Periodic broadcasting by RIP generally prevents WAN circuits from being closed.

• Even on fixed, point-to-point links, the overhead of periodic RIP transmissions could seriously interrupt normal data transfer because of the quantity of information that passes through the line every 30 seconds.


Step 1 enable










Step 4 exit



Step 5 router rip



Step 6 output-delay milliseconds

Example:Router(config-router)# output-delay 8

Configures interpacket delay for outbound RIP updates.

Step 7 end




17

To overcome these limitations, triggered extensions to RIP cause RIP to send information on the WAN only when there has been an update to the routing database. Periodic update packets are suppressed over the interface on which this feature is enabled. RIP routing traffic is reduced on point-to-point, serial interfaces. Therefore, you can save money on an on-demand circuit for which you are charged for usage. Triggered extensions to RIP partially support RFC 2091, Triggered Extensions to RIP to Support Demand Circuits.

Perform the following task to enable triggered extensions to RIP and to display the contents of the RIP private database.

SUMMARY STEPS

1. enable


3. interface serial controller-number

4. ip rip triggered

5. end

6. show ip rip database [prefix mask]

DETAILED STEPS


Step 1 enable







Step 3 interface serial controller-number

Example:Router(config)# interface serial3/0

Configures a serial interface.

Step 4 ip rip triggered

Example:Router(config-if)# ip rip triggered

Enables triggered extensions to RIP.

Step 5 end


Returns to privileged EXEC mode.

Step 6 show ip rip database [prefix mask]

Example:Router# show ip rip database

Displays the contents of the RIP private database.


18

Configuring IP-RIP Delay Start for Routers Connected by a Frame Relay Network

The tasks in this section explain how to configure a router to use the IP-RIP Delay Start feature on a Frame Relay interface.

• Configuring RIPv2, page 19 (required)

• Configuring Frame Relay on a Serial Subinterface, page 20 (required)

• Configuring IP, MD5 Authentication for RIPv2 and the IP-RIP Delay Start Feature on a Frame Relay Subinterface, page 21 (required)

The IP-RIP Delay Start feature is often used when a Cisco router is configured to establish a RIPv2 neighbor relationship using MD5 authentication with a non-Cisco device over a Frame Relay network. When RIPv2 neighbors are connected over Frame Relay, it is possible for the serial interface connected to the Frame Relay network to be up while the underlying Frame Relay circuits are not yet ready to transmit and receive data. When a serial interface is up and the Frame Relay circuits are not yet operational, any MD5 packets that the router attempts to transmit over the serial interface are dropped. When MD5 packets are dropped because the Frame Relay circuits over which the packets need to be transmitted are not yet operational, the sequence number of the first MD5 packet received by the neighbor router after the Frame Relay circuits become active will be greater than 0. Some non-Cisco routers will not allow an MD5-authenticated RIPv2 neighbor session to start when the sequence number of the first MD5 packet received from the other router is greater than 0.

The differences in vendor implementations of MD5 authentication for RIPv2 are probably a result of the ambiguity of the relevant RFC (RFC 2082) with regards to packet loss. RFC 2082 suggests that routers should be ready to accept either a sequence number of 0 or a sequence number higher than the last sequence number received. For more information about MD5 message reception for RIPv2, see section 3.2.2 of RFC 2082 at the following url: http://www.ietf.org/rfc/rfc2082.txt.

Timesaver Cisco routers allow an MD5-authenticated RIPv2 neighbor session to start when the sequence number of the first MD5 packet received from the other router is greater than 0. If you are using only Cisco routers in your network, you do not need to use the IP-RIP Delay Start feature.

Note The IP-RIP Delay Start feature is supported over other interface types such as Fast Ethernet and Gigabit Ethernet. If your Cisco router cannot establish RIPv2 neighbor sessions using MD5 authentication with a non-Cisco device, the IP-RIP Delay Start feature might resolve the problem.

Prerequisites

Your router must be running Cisco IOS Release 12.4(12) or a later release.

Restrictions

The IP-RIP Delay Start feature is required only when your Cisco router is configured to establish a RIPv2 neighbor relationship with a non-Cisco device and you want to use MD5 neighbor authentication.

http://www.ietf.org/rfc/rfc2082.txt


19

Configuring RIPv2

This required task configures RIPv2 on the router.

This task provides instructions for only one of the many possible permutations for configuring RIPv2 on your router.

SUMMARY STEPS

1. enable


3. router rip

4. network ip-network

5. version {1 | 2}

6. [no] auto-summary

DETAILED STEPS


Step 1 enable







Step 3 router rip


Enables a RIP routing process, which places you in router configuration mode.

Step 4 network ip-network


Associates a network with a RIP routing process.


Example:Router (config-router)# version 2

Configures the software to receive and send only RIP Version 1 or only RIP Version 2 packets.

Step 6 [no] auto-summary

Example:Router(config-router)# no auto-summary

Disables or restores the default behavior of automatic summarization of subnet routes into network-level routes.


20

Configuring Frame Relay on a Serial Subinterface

This required task configures a serial subinterface for Frame Relay.

Note This task provides instructions for only one of the many possible permutations for configuring Frame Relay on a subinterface. For more information about and instructions for configuring Frame Relay, see the “Configuring Frame Relay” part of the Cisco IOS Wide-Area Networking Configuration Guide.

SUMMARY STEPS

1. enable



4. no ip address

5. encapsulation frame-relay [mfr number | ietf]

6. frame-relay lmi-type {cisco | ansi | q933a}

7. exit

8. interface type number/subinterface-number {point-to-point | multipoint}

9. frame-relay interface-dlci dlci [ietf | cisco]

DETAILED STEPS


Step 1 enable








Example:Router(config)# interface serial3/0

Specifies an interface and enters interface configuration mode.

Step 4 no ip address

Example:Router(config-if)# no ip address

Removes a previously configured IP address from the interface.

Step 5 encapsulation frame-relay [mfr number | ietf]

Example:Router(config-if)# encapsulation frame-relay ietf

Specifies the type of Frame Relay encapsulation for the interface.

http://www.cisco.com/en/US/docs/ios/wan/configuration/guide/wan_cfg_frm_rly.html


21

Configuring IP, MD5 Authentication for RIPv2 and the IP-RIP Delay Start Feature on a Frame Relay Subinterface

This required task configures IP, MD5 authentication for RIPv2 and the IP-RIP Delay Start feature on a Frame Relay subinterface.

SUMMARY STEPS

1. enable


3. key chain name-of-chain

4. key number

5. key-string string

6. exit

7. exit

8. interface type number/subinterface-number

9. no cdp enable

10. ip address ip-address subnet-mask

11. ip rip authentication mode {text | md5}

12. ip rip authentication key-chain name-of-chain

13. ip rip initial-delay delay

14. end

Step 6 frame-relay lmi-type {cisco | ansi | q933a}

Example:Router(config-if)# frame-relay lmi-type ansi

Specifies the type of Frame Relay local management interface (LMI) for the interface.

Step 7 exit



Step 8 interface type number/subinterface-number {point-to-point | multipoint}

Example:Router(config)# interface serial3/0.1 point-to-point

Specifies a subinterface and the connection type for the subinterface and enters subinterface configuration mode.

Step 9 frame-relay interface-dlci dlci [ietf | cisco]

Example:Router(config-subif)# frame-relay interface-dlci 100 ietf

Assigns a data-link connection identifier (DLCI) to a Frame Relay subinterface.



22

DETAILED STEPS


Step 1 enable







Step 3 key chain name-of-chain

Example:Router(config)# key chain rip-md5

Specifies the name of a key chain and enters key chain configuration mode.

Step 4 key number

Example:Router(config-keychain)# key 123456

Specifies the key identifier and enters key chain key configuration mode. Range: 0 to 2147483647.

Step 5 key-string string

Example:Router(config-keychain-key)# key-string abcde

Configures the key string.

Step 6 exit

Example:Router(config-keychain-key)# exit

Exits key chain key configuration mode.

Step 7 exit

Example:Router(config-keychain)# exit

Exits key chain configuration mode.

Step 8 interface type number/subinterface-number

Example:Router(config)# interface serial3/0.1

Specifies a subinterface and enters subinterface configuration mode.

Note The connection type keyword is not required for this step in this task because the connection type for this subinterface was specified in the previous task.

Step 9 no cdp enable

Example:Router(config-subif)# no cdp enable

Disables Cisco Discovery Protocol (CDP) options on the interface.

Note CDP is not supported by non-Cisco devices; and the IP-RIP Delay Start feature is required only when you are connecting to a non-Cisco router. Therefore, you should disable CDP on any interfaces on which you want to configure the IP-RIP Delay Start feature.

Configuring Routing Information Protocol Configuration Examples for RIP

23

Configuration Examples for RIPThis section provides the following RIP configuration examples:

• Route Summarization: Example, page 23

• Split Horizon: Examples, page 24

• Address Family Timers: Example, page 25

• IP-RIP Delay Start on a Frame Relay Interface: Examples, page 26

Route Summarization: ExampleThe following example shows how the ip summary-address rip router configuration command can be used to configure summarization on an interface. In this example, the subnets 10.1.3.0/25, 10.1.3.128/25, 10.2.1.0/24, 10.2.2.0/24, 10.1.2.0/24 and 10.1.1.0/24 can be summarized as shown below while sending the updates over an interface.

Router(config)#interface GigabitEthernet 0/2Router(config-if)#ip summary-address rip 10.1.0.0 255.255.0.0Router(config-if)#ip summary-address rip 10.2.0.0 255.255.0.0Router(config-if)#ip summary-address rip 10.3.0.0 255.255.0.0

Step 10 ip address ip-address subnet-mask

Example:Router (config-subif)# ip address 172.16.10.1 255.255.255.0

Configures an IP address for the Frame Relay subinterface.

Step 11 ip rip authentication mode {text | md5}

Example:Router(config-subif)# ip rip authentication mode md5

Specifies the mode for RIPv2 authentication.

Step 12 ip rip authentication key-chain name-of-chain

Example:Router (config-subif)# ip rip authentication key-chain rip-md5

Specifies a previously configured key chain for RIPv2 MD5 authentication.

Step 13 ip rip initial-delay delay

Example:Router(config-subif)# ip rip initial-delay 45

Configures the IP-RIP Delay Start feature on the interface. The router will delay sending the first MD5 authentication packet to the RIPv2 neighbor for the number of seconds specified by the delay argument. Range: 0 to 1800.

Step 14 end

Example:Router(config-subif)# end

Exits the sub-interface configuration mode and returns to privileged EXEC mode.



24

Split Horizon: ExamplesTwo examples of configuring split horizon are provided.

Example 1

The following configuration shows a simple example of disabling split horizon on a serial link. In this example, the serial link is connected to an X.25 network.

Router(config)# interface Serial 0 Router(config-if)# encapsulation x25 Router(config-if)# no ip split-horizon

Example 2

In the next example, Figure 1 illustrates a typical situation in which the no ip split-horizon interface configuration command would be useful. This figure depicts two IP subnets that are both accessible via a serial interface on Router C (connected to a Frame Relay network). In this example, the serial interface on Router C accommodates one of the subnets via the assignment of a secondary IP address.

The Ethernet interfaces for Router A, Router B, and Router C (connected to IP networks 10.13.50.0, 10.155.120.0, and 10.20.40.0, respectively all have split horizon enabled by default, while the serial interfaces connected to networks 172.16.1.0 and 192.168.1.0 all have split horizon disabled with the no ip split-horizon command. Figure 1 shows the topology and interfaces.

Figure 1 Disabled Split Horizon Example for Frame Relay Network

In this example, split horizon is disabled on all serial interfaces. Split horizon must be disabled on Router C in order for network 172.16.0.0 to be advertised into network 192.168.0.0 and vice versa. These subnets overlap at Router C, interface S0. If split horizon were enabled on serial interface S0, it would not advertise a route back into the Frame Relay network for either of these networks.

Configuration for Router Ainterface ethernet 1 ip address 10.13.50.1

Router BRouter C

Router A

E1

E0

S1

Interface address:192.168.1.2


Secondary interface address: 192.168.1.1


S0

E2

S2Network address:

10.13.50.0


Network address:10.20.40.0


Network address:10.155.120.0


S10

69a

Frame Relaynetwork

Networkaddress:

172.16.1.0

Networkaddress:

192.168.1.0


25

!interface serial 1 ip address 172.16.2.2 encapsulation frame-relay no ip split-horizon

Configuration for Router Binterface ethernet 2 ip address 10.155.120.1!interface serial 2 ip address 192.168.1.2 encapsulation frame-relay no ip split-horizon

Configuration for Router Cinterface ethernet 0ip address 10.20.40.1

!interface serial 0ip address 172.16.1.1ip address 192.168.1.1 secondaryencapsulation frame-relay no ip split-horizon

Address Family Timers: ExampleThe following example shows how to adjust individual address family timers. Note that the address family “notusingtimers” will use the system defaults of 30, 180, 180, and 240 even though timer values of 5, 10, 15, and 20 are used under the general RIP configuration. Address family timers are not inherited from the general RIP configuration.

Router(config)# router ripRouter(config-router)# version 2Router(config-router)# timers basic 5 10 15 20Router(config-router)# redistribute connectedRouter(config-router)# network 5.0.0.0Router(config-router)# default-metric 10Router(config-router)# no auto-summaryRouter(config-router)#Router(config-router)# address-family ipv4 vrf abcRouter(config-router-af)# timers basic 10 20 20 20Router(config-router-af)# redistribute connectedRouter(config-router-af)# network 10.0.0.0Router(config-router-af)# default-metric 5Router(config-router-af)# no auto-summaryRouter(config-router-af)# version 2Router(config-router-af)# exit-address-familyRouter(config-router)# Router(config-router)# address-family ipv4 vrf xyzRouter(config-router-af)# timers basic 20 40 60 80Router(config-router-af)# redistribute connectedRouter(config-router-af)# network 20.0.0.0Router(config-router-af)# default-metric 2Router(config-router-af)# no auto-summaryRouter(config-router-af)# version 2Router(config-router-af)# exit-address-familyRouter(config-router)#Router(config-router)# address-family ipv4 vrf notusingtimers


26

Router(config-router-af)# redistribute connected Router(config-router-af)# network 20.0.0.0 Router(config-router-af)# default-metric 2 Router(config-router-af)# no auto-summary Router(config-router-af)# version 2 Router(config-router-af)# exit-address-family Router(config-router)#

IP-RIP Delay Start on a Frame Relay Interface: ExamplesThis excerpt from a router configuration file contains the minimum commands required to configure the IP-RIP Delay Start feature on your router.

!key chain rip-md5 key 123456 key-string abcde!router rip version 2 network 172.16.0.0 no auto-summary

Configuring Routing Information Protocol Additional References

27

!interface Serial3/0 no ip address encapsulation frame-relay ietf frame-relay lmi-type ansi!interface Serial3/0.1 point-to-point ip address 172.16.10.1 255.255.255.0 ip rip initial-delay 45 ip rip authentication mode md5 ip rip authentication key-chain rip-md5 frame-relay interface-dlci 100!

Additional ReferencesThe following sections provide references related to configuring Routing Information Protocol.

Related Documents

Standards

MIBs

Related Topic Document Title

Protocol-independent features, filtering RIP information, key management (available in RIP Version 2), and VLSM

Configuring IP Routing Protocol-Independent Features

RIP commands: complete command syntax, command mode, command history, defaults, usage guidelines, and examples

Cisco IOS IP Routing: RIP Command Reference

Configuring Frame Relay Cisco IOS Wide-Area Networking Configuration Guide

Standard Title

None —

MIB MIBs Link

No new or modified MIBS are supported and support for existing MIBs has not been modified.

To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:





http://www.cisco.com/en/US/docs/ios/iproute_pi/configuration/guide/iri_prot_indep.html

Configuring Routing Information Protocol Additional References

28

RFCs

Technical Assistance

RFC Title

RFC 1058 Routing Information Protocol

RFC 2082 RIP-2 MD5 Authentication

RFC 2091 Triggered Extensions to RIP to Support Demand Circuits

RFC 2453 RIP version 2

Description Link

The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.

To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.

Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.

http://www.cisco.com/cisco/web/support/index.html

Configuring Routing Information Protocol Feature Information for Configuring RIP

29

Feature Information for Configuring RIPTable 1 lists the features in this module and provides links to specific configuration information.

Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Note Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.

Table 1 Feature Information for Configuring Routing Information Protocol

Feature Name Releases Feature Information

IP-RIP Delay Start 12.4(12)15.0(1)M12.2(33)SRE

The IP-RIP Delay Start feature is used on Cisco routers to delay the initiation of RIPv2 neighbor sessions until the network connectivity between the neighbor routers is fully operational, thereby ensuring that the sequence number of the first MD5 packet that the router sends to the non-Cisco neighbor router is 0. The default behavior for a router configured to establish RIPv2 neighbor sessions with a neighbor router using MD5 authentication is to start sending MD5 packets when the physical interface is up.

The following sections provide information about this feature:

• Neighbor Router Authentication, page 6

• IP-RIP Delay Start, page 7

The following commands were introduced or modified: ip rip initial-delay delay.


Configuring Routing Information Protocol Feature Information for Configuring RIP

30

IP Summary Address for RIPv2 12.0(7)T12.1(3)T12.1(14)12.2(2)T12.2(27)SBB15.0(1)M12.2(33)SRE

The IP Summary Adddress for RIPv2 feature introduced the ability to summarize routes. Summarizing routes in RIP Version 2 improves scalability and efficiency in large networks. Summarizing IP addresses means that there is no entry for child routes (routes that are created for any combination of the individual IP addresses contained within a summary address) in the RIP routing table, reducing the size of the table and allowing the router to handle more routes.


• RIP Route Summarization, page 4

• Summarizing RIP Routes, page 11

• Route Summarization: Example, page 23

The following commands were introduced or modified by this feature: ip summary-address rip.

Routing Information Protocol 12.2(27)SBB15.0(1)M12.2(33)SRE

Routing Information Protocol (RIP) is a commonly used routing protocol in small to medium TCP/IP networks. It is a stable protocol that uses a distance-vector algorithm to calculate routes.

Triggered RIP 12.0(1)T15.0(1)M12.2(33)SRE

Triggered RIP was introduced to overcome constant RIP updates over expensive circuit-based WAN links. Triggered extensions to RIP cause RIP to send information on the WAN only when there has been an update to the routing database. Periodic update packets are suppressed over the interface on which this feature is enabled. RIP routing traffic is reduced on point-to-point, serial interfaces.


• Optimizing RIP over WAN, page 16

The following commands were introduced or modified: ip rip triggered, show ip rip database.

Table 1 Feature Information for Configuring Routing Information Protocol (continued)


Configuring Routing Information Protocol Glossary

31

Glossaryaddress family—A group of network protocols that share a common format of network address. Address families are defined by RFC 1700.

IS-IS—Intermediate System-to-Intermediate System. OSI link-state hierarchical routing protocol based on DECnet Phase V routing, where routers exchange routing information based on a single metric, to determine network topology.

RIP—Routing Information Protocol.RIP is a dynamic routing protocol used in local and wide area networks.

VRF—VPN routing and forwarding instance. A VRF consists of an IP routing table, a derived forwarding table, a set of interfaces that use the forwarding table, and a set of rules and routing protocols that determine what goes into the forwarding table. In general, a VRF includes the routing information that defines a customer VPN site that is attached to a PE router.

CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco and/or its affiliates in the United States and certain other countries.




Configuring Routing Information Protocol Glossary

32

Americas Headquarters:Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA

Advanced RIP Features

First Published: December 17, 2007Last Updated: November 20, 2009

The Advanced RIP Features contained in this configuration module cover the implementation of RFC 1724, which allows you to monitor RIPv2 using SNMP, and the information about configuring the cable modem HFC RIP Relay feature.

Finding Feature InformationYour Cisco IOS software release may not support all of the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. 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 Advanced RIP Features” section on page 19.


Contents• Information About Advanced RIP Features, page 2

• How to Configure Advanced RIP Features, page 5

• Configuration Examples for Advanced RIP Features, page 13

• Additional References, page 16

• Feature Information for Advanced RIP Features, page 19

• Glossary, page 20


Advanced RIP Features Information About Advanced RIP Features

2

Information About Advanced RIP FeaturesThis section consists of the following subsection:

• Cable HFC, page 2

• HFC RIP Relay, page 2

• Benefits of the RIPv2 MIB, page 3

• RIPv2 MIB, page 3

Cable HFCCable technology has been adapting to the deployment of fiber since 1994, leading to hybrid solutions known as hybrid fiber-coaxial (HFC). HFC networks contain both optical-fiber and coaxial cable lines. Optical fiber is deployed from the cable headend to cable operator subscribers with up to 2000 subscribers. Coaxial cable is deployed from the optical-fiber feeders to each subscriber. Hybrid networks provide the bandwidth and reliability of optical fiber at a lower cost than a pure fiber network.

HFC RIP RelayThe cable modem HFC RIP Relay feature allows the delivery of Routing Information Protocol (RIP) messages from a Cisco IOS router containing an integrated cable modem to the hybrid fiber-coaxial (HFC) cable modem termination system (CMTS) when they are on different subnets. The integrated cable modem may be physically integrated into the router or via a cable modem high-speed WAN interface card (HWIC). In previous Cisco IOS releases, RIP messages were rejected by the CMTS because the interface on the Cisco IOS router was in a different subnet from the CMTS. The solution involves trapping and handling RIP messages by the cable modem and ensuring that the RIP messages are forwarded to the router. The cable modem HFC RIP Relay feature enhances the scalability, security, and certification requirements of cable operators who require RIP to provision and manage customer cable modems.

In the provisioning systems used by some cable operators, when a Cisco IOS router containing an integrated cable modem is connected to a CMTS, RIP messages are rejected because the IP address derived from a DHCP request for the router is from a different pool of IP addresses than for the cable modems. The RIP messages are rejected by the CMTS because the interface on the Cisco IOS router is in a different subnet from the CMTS. Without requiring additional configuration on the CMTS, the HFC RIP Relay feature enables the cable modem to bridge the RIP messages between the Cisco IOS router and the CMTS.

The cable modem HFC RIP Relay feature is implemented in Cisco IOS Release 12.4(15)XY, 12.4(20)T, and later releases. The feature requires the cable modem firmware version filename of C21031014bFU07192007.CDF in the United States or the cable modem firmware version filename of C21041014bFU07192007.CDF in Europe and Japan, and the feature is turned off by default. To enable HFC RIP relay, use the new service-module ip rip relay command-line interface (CLI) command.

Support is added for configuring a static IP address on the cable modem interface. Configuring a static IP address for the Cisco IOS router with an integrated cable modem is also supported in Cisco IOS Release 12.4(15)XY, 12.4(20)T, and later releases using the ip address command.


3

Benefits of the RIPv2 MIBThe 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.

RIPv2 MIBThis document describes the Cisco IOS implementation of RFC 1724, RIP Version 2 MIB Extensions. RIPv2 using Simple Network Management Protocol (SNMP).

This section describes the MIB objects that are provided by RFC 1724 definitions. The RIPv2 MIB consists of the following managed objects:

• Global counters—Used to keep track of changing routes or neighbor changes.

• Interface status table—Defines objects that are used to keep track of statistics specific to interfaces.

• Interface configuration table—Defines objects that are used to keep track of interface configuration statistics.

• Peer table—Defined to monitor neighbor relationships. This object is not implemented in Cisco IOS software.

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 Network Management Station (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 objects 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 1 RFC 1724 RIPv2 MIB Global Counters Objects

Global Counter Object Description

rip2Globals rip2GlobalRouteChanges Number of route changes made to the IP route database by RIP. The number is incremented when a route is modified.

rip2GlobalQueries Number of responses sent to RIP queries from other systems. The number is incremented when RIP responds to a query from another system.


4

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 using the show ip protocol commands. All objects in the RIPv2 MIB interface table are implemented read-only.

Table 2 RFC 1724 RIPv2 MIB Interface Table Objects

Sequence Name Object Description

Rip2IfStatEntry rip2IfStatAddress The IP address of this system on the indicated subnet. For unnumbered interfaces, the value of 0.0.0.N, where the least significant 24 bits (N) are the ifIndex for the IP interface in network byte order.

rip2IfStatRcvBadPackets The number of RIP response packets received by the RIP process that were subsequently discarded for any reason. For example, a version 0 packet or an unknown command type.

rip2IfStatRcvBadRoutes The number of routes, in valid RIP packets, that were ignored for any reason. This is incremented when:

• The address family identifier does not equal AF_INET.

• A RIP v2 update is received and the address is not a RIP multicast address (244.0.0.0) or RIP broadcast address (255.255.255.255).

• A RIP v2 update is received and the address is a martian address.

rip2IfStatSentUpdates The number of triggered RIP updates actually sent on this interface. This explicitly does not include full updates sent containing new information.

rip2IfStatStatus This value is always set to 1.

Advanced RIP Features How to Configure Advanced RIP Features

5

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.

How to Configure Advanced RIP FeaturesConfiguring advanced RIP features consists of the following tasks:

• Configuring HFC RIP Relay, page 6

• Enabling RIPv2 Monitoring with SNMP Using the RIPv2: RFC 1724 MIB Extensions, page 11

Table 3 RFC 1724 RIPv2 MIB Interface Configuration Table Object Types

Sequence Name Object Type Description

rip2IfConfEntry rip2IfConfAddress The IP address of this system on the indicated subnet. For unnumbered interfaces, the value 0.0.0.N, where the least significant 24 bits (N) are the ifIndex for the IP interface in network byte order.

rip2IfConfDomain This value is always equal to "".

rip2IfConfAuthType The type of authentication used on this interface.

rip2IfConfAuthKey The value to be used as the authentication key whenever the corresponding instance of rip2IfConfAuthType has a value other than no authentication.

rip2IfConfSend The version of RIP updates that are sent on this interface.

rip2IfConfReceive The version of RIP updates that are accepted on this interface.

rip2IfConfDefaultMetric This variable indicates the metric that is used for the default route entry in RIP updates originated on this interface.

rip2IfConfStatus This value is always set to 1.

rip2IfConfSrcAddress The IP address that this system will use as a source address on this interface. If it is a numbered interface, this must be the same value as rip2IfConfAddress. On unnumbered interfaces, it must be the value of rip2IfConfAddress for some interface on the system.


6

Configuring HFC RIP RelayThis section contains the following tasks:

• Enabling HFC RIP Relay, page 6

• Enabling HFC RIP Relay for a Single Subnet and Disabling Split-Horizon, page 8

• Verifying the Configuration of HFC RIP Relay, page 10(optional)

Prerequisites

The HFC RIP Relay feature requires an Integrated Services Router (ISR) with an integrated cable modem and Cisco IOS Release 12.4(15)XY, 12.4(20)T, or later release and one of the following:

• Cable modem firmware version filename of C21031014bFU07192007.CDF in the United States

• Cable modem firmware version filename of C21041014bFU07192007.CDF in Europe and Japan

ISR cable products include the Cisco 815, Cisco 1805, and the cable modem HWIC in the Cisco 1800, 2800, and 3800 series routers.

Restrictions

The HFC RIP Relay feature does not support multiple cable modem HWICs in a single router.

Enabling HFC RIP Relay

Perform this task to enable RIP relay on an integrated cable modem. In this task, a static IP address is configured for the cable modem interface and RIP relay is enabled on the interface. Validation of the source IP address of incoming RIP routing updates is disabled to allow RIP updates from unknown sources. RIP is defined as the routing protocol to be used on all interfaces that are connected to networks 10.0.0.0 and 172.18.0.0.

SUMMARY STEPS

1. enable



4. ip address ip-address mask [secondary]

5. service-module ip rip relay

6. exit

7. router rip

8. version {1 | 2}




12. end


7

DETAILED STEPS


Step 1 enable








Example:Router(config)# interface cable-modem 0/3/0

Configures an interface type and enters interface configuration mode.

• In this example, cable-modem interface 0/3/0 is configured.

Step 4 ip address ip-address mask [secondary]

Example:Router(config-if)# ip address 10.5.5.5 255.255.255.0

Sets a primary or secondary IP address for an interface.

• In this example, the static IP address of 10.5.5.5 is configured under the cable-modem interface.

Step 5 service-module ip rip relay

Example:Router(config-if)# service-module ip rip relay

Enables RIP relay in the ISR cable-modem driver.

Step 6 exit


Exits interface configuration mode and returns to global configuration mode.

Step 7 router rip


Enters router configuration mode for the specified routing process.

• In this example, a RIP routing process is configured.



Specifies a RIP version used globally by the router.

• In this example, the software sends and receives RIP version 2 packets.




• When the validation check is enabled, the software ensures that the source IP address of incoming routing updates is on the same IP network as one of the addresses defined for the receiving interface.

• In this example, the router is configured not to perform validation checks on the source IP address of incoming RIP updates.


8

Enabling HFC RIP Relay for a Single Subnet and Disabling Split-Horizon

Perform this task to enable RIP relay on an ISR cable modem. In this task, a static IP address is configured for the cable-modem interface and RIP relay is enabled on the interface. Split-horizon is disabled, and RIP is defined as the routing protocol to be used on all interfaces connected to network 10.0.0.0.

SUMMARY STEPS

1. enable



4. ip address ip-address mask [secondary]

5. service-module ip rip relay

6. no ip split-horizon

7. exit

8. router rip

9. version {1 | 2}



12. end



Specifies a list of networks for the RIP routing process.

• In this example, RIP is defined as the routing protocol to be used on all interfaces connected to network 10.0.0.0.





Step 12 end





9

DETAILED STEPS


Step 1 enable








Example:Router(config)# interface cable-modem 0/3/0

Configures an interface type and enters interface configuration mode.

• In this example, cable-modem interface 0/3/0 is configured.

Step 4 ip address ip-address mask [secondary]

Example:Router(config-if)# ip address 10.5.5.5 255.255.255.0

Sets a primary or secondary IP address for an interface.

• In this example, a static IP address of 10.5.5.5 is configured under the cable-modem interface.

Step 5 service-module ip rip relay

Example:Router(config-if)# service-module ip rip relay

Enables RIP relay in the ISR cable-modem driver.

Step 6 no ip split-horizon

Example:Router(config-if)# no ip split-horizon

Disables split horizon, allowing routing updates to be sent from the interface over which the route was learned.

Step 7 exit


Exits interface configuration mode and returns to global configuration mode.

Step 8 router rip


Enters router configuration mode for the specified routing process.

• In this example, a RIP routing process is configured.



Specifies a RIP version used globally by the router.

• In this example, the software sends and receives RIP version 2 packets.


10

Verifying the Configuration of HFC RIP Relay

Use the following steps to verify the local configuration of HFC RIP relay on a router.

SUMMARY STEPS

1. enable

2. show running-config [options]

DETAILED STEPS

Step 1 enable

Enables privileged EXEC mode. Enter your password if prompted.

Router> enable

Step 2 show running-config [options]

Displays the running configuration on the local router. The output will display the configuration of the service-module ip rip relay command in the cable-modem interface section and of the RIP commands under the RIP protocol section.

Router# show running-config

.

.

.interface Cable-Modem0/3/0 ip address 172.20.0.2 255.255.255.0 service-module ip rip relay no ip split-horizon..




• When the validation check is enabled, the software ensures that the source IP address of incoming routing updates is on the same IP network as one of the addresses defined for the receiving interface.

• In this example, the router is configured not to perform validation checks on the source IP address of incoming RIP updates.





Step 12 end





11

.router rip version 2 no validate-update-source network 10.0.0.0 network 172.18.0.0...

Enabling RIPv2 Monitoring with SNMP Using the RIPv2: RFC 1724 MIB Extensions

This section contains the following tasks:

• Enabling SNMP Read-Only Access on the Router, page 11 (required)

• Verifying the Status of the RIPv2: RFC 1724 MIB Extensions on the Router and Your Network Management Station, page 13 (optional)

Prerequisites

• RIPv2 must be configured on the router.

• Your SNMP NMS must have the RFC 1724 RIPv2 MIB installed.

• Your SNMP NMS must have the following MIBs installed because RFC 1724 imports data types and object identifiers (OIDs) from them:

– SNMPv2-SMI

– SNMPv2-TC

– SNMPv2-CONF

– RFC1213-MIB

Restrictions

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 command in RIP router configuration mode are tracked. Global data is tracked only for changes to the main routing table.

Enabling SNMP Read-Only Access on the Router

There are no router configuration tasks required for the RIPv2: RFC 1724 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 When you configure an SNMP server read-only community string on the router, you are granting SNMP read-only access to the objects that support read-only access in all MIBs that are available in the version of Cisco IOS software that is running on the router.


12

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 If you already have an SNMP read-only community string configured on your router you do not need to perform this task. After you load Cisco IOS Release 12.4(6)T or a later release on your router, you can use SNMP commands on your NMS to query the RFC 1724 RIPv2 MIB on your router

SUMMARY STEPS

1. enable


3. snmp-server community string1 ro

4. end

DETAILED STEPS


Step 1 enable







Step 3 snmp-server community string1 ro

Example:Router(config)# snmp-server community T8vCx3 ro

Enables SNMP read-only access to the objects in the MIBs that are included in the version of Cisco IOS software that is running on the router.

Note For security purposes, do not use the standard default value of public for your read-only community string. Use a combination of uppercase and lowercase letters and numbers for the password.

Step 4 end

Example:Router(config)# end

Ends your configuration session and returns to privileged EXEC mode.

Advanced RIP Features Configuration Examples for Advanced RIP Features

13

Verifying the Status of the RIPv2: RFC 1724 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 This task uses the NET-SNMP toolset that is available in the public domain. The step that is documented uses a terminal session on an NMS that is running Linux. Substitute the SNMP command from the SNMP toolset on your NMS as appropriate when you perform this task.

Prerequisites

Your NMS must have the RFC 1724 MIB installed.

SUMMARY STEPS

1. snmpwalk -m all -v2c ip-address -c read-only-community-string rip2Globals

DETAILED STEPS

Step 1 snmpwalk -m all -v2c ip-address -c read-only-community-string rip2Globals

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 rip2Globals

RIPv2-MIB::rip2GlobalRouteChanges.0 = Counter32: 5RIPv2-MIB::rip2GlobalQueries.0 = Counter32: 1$

Configuration Examples for Advanced RIP FeaturesThis section contains the following configuration examples:

• Configuration Examples for HFC RIP Relay, page 13

• Configuration Examples for RIPv2 Monitoring with SNMP Using the RIPv2: RFC1724 MIB Extensions, page 14

Configuration Examples for HFC RIP RelayThis section contains the following examples:

• Enabling HFC RIP Relay: Example, page 14

• Enabling HFC RIP Relay for a Single Subnet and Disabling Split-Horizon: Example, page 14


14

Enabling HFC RIP Relay: Example

The following example enables RIP relay on an ISR cable modem. A static IP address is configured for the cable-modem interface, and RIP relay is enabled on the interface. Validation of the source IP address of incoming RIP routing updates is disabled to allow RIP updates from unknown sources. RIP is defined as the routing protocol to be used on all interfaces connected to networks 10.0.0.0 and 172.18.0.0.

interface Cable-Modem0/3/0 ip address 10.5.5.5 255.255.255.0 service-module ip rip relay exit router rip version 2 no validate-update-source network 10.0.0.0 network 172.18.0.0

Enabling HFC RIP Relay for a Single Subnet and Disabling Split-Horizon: Example

The following example enables RIP relay on an ISR cable modem. A static IP address is configured for the cable-modem interface, and RIP relay is enabled on the interface. Validation of the source IP address of incoming RIP routing updates is disabled to allow RIP updates from unknown sources, and split-horizon is disabled. RIP is defined as the routing protocol to be used on all interfaces connected to network 172.20.0.0.

interface Cable-Modem0/3/0 ip address 172.20.0.2 255.255.255.0 service-module ip rip relay no ip split-horizon exit router rip version 2 no validate-update-source network 172.20.0.0

Configuration Examples for RIPv2 Monitoring with SNMP Using the RIPv2: RFC1724 MIB Extensions

This section contains the following examples:

• Querying the RIP Interface Status Table Objects: Example, page 14

• Querying the RIP Interface Configuration Table Objects: Example, page 15

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 Rip2IfStatEntry

RIPv2-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: 0


15

RIPv2-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 the interfaces in the RIP interface status table using the snmpwalk command.

$ snmpwalk -m all -v2c 10.0.0.253 -c T8vCx3 rip2IfStatStatus

RIPv2-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.253

RIPv2-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 rip2IfConfEntry

RIPv2-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 = ""

Advanced RIP Features Additional References

16

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 rip2IfConfAddress

RIPv2-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$

Additional ReferencesThe following sections provide references related to advanced RIP configuration.


17

Related Documents

Standards

MIBs

RFCs

Related Topic Document Title

Configuring RIP Configuring Routing Information Protocol

Configuring protocol-independent routing features Configuring IP Routing Protocol-Independent Features

Configuring Frame Relay Configuring Frame Relay

Cable modem HWIC card configuration Cisco Cable Modem High-Speed WAN Interface Cards Configuration Guide

RIP commands: complete command syntax, command mode, defaults, command history, usage guidelines, and examples

Cisco IOS IP Routing: RIP Command Reference

SNMP configuration Configuring SNMP Support

SNMP commands Cisco IOS Network Management Command Reference

Standard Title

No new or modified standards are supported. and support for existing standards has not been modified.

—

MIB MIBs Link

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:


RFC Title

RFC 1724 RIP Version 2 MIB Extensions

RFC 2082 RIP-2 MD5 Authentication

RFC 2453 RIP Version 2


http://www.cisco.com/en/US/docs/ios/iproute/configuration/guide/irp_cfg_info_prot.html

http://www.cisco.com/en/US/docs/ios/iproute_pi/configuration/guide/iri_ip_prot_indep.html


http://www.cisco.com/en/US/docs/ios/12_4/12_4x/12_4_6xe/snwshoe1.html


http://www.cisco.com/en/US/docs/ios/netmgmt/configuration/guide/nm_cfg_snmp_sup.html

http://www.cisco.com/en/US/docs/ios/netmgmt/command/reference/nm_book.html


18

Technical Assistance

Description Link

The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.

To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.

Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.

http://www.cisco.com/techsupport

http://www.cisco.com/public/support/tac/home.shtml

Advanced RIP Features Feature Information for Advanced RIP Features

19

Feature Information for Advanced RIP FeaturesTable 4 lists the release historyfor this feature.

Table 4 Only features that were introduced or modified in Cisco IOS Release 12.2(1) or 12.0(3)S or a later release appear in the table.

Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Note Table 4 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.

Table 4 Feature Information for Advanced RIP Features


HFC RIP Relay 12.4(15)XY12.4(20)T15.0(1)M12.2(33)SRE

The HFC RIP Relay feature allows the delivery of Routing Information Protocol (RIP) messages from a Cisco IOS router containing a cable HWIC to the HFC CMTS when they are on different subnets. Configuring a static IP address is now also supported on a cable modem interface.


• HFC RIP Relay, page 2

• Configuring HFC RIP Relay, page 6

• Enabling HFC RIP Relay, page 6

• Enabling HFC RIP Relay for a Single Subnet and Disabling Split-Horizon, page 8

• Configuration Examples for HFC RIP Relay, page 13

The following command was introduced by this feature: service-module ip rip relay.

RIPv2: RFC 1724 MIB Extension 12.4(6)T15.0(1)M12.2(33)SRE

This feature introduces the Cisco IOS implementation of RFC 1724, RIP Version 2 MIB Extensions. RFC 1724 defines MIB objects that allow the management and limited control of RIPv2 using SNMP.


• Benefits of the RIPv2 MIB, page 3

• RIPv2 MIB, page 3

• Enabling RIPv2 Monitoring with SNMP Using the RIPv2: RFC 1724 MIB Extensions, page 11

• Configuration Examples for RIPv2 Monitoring with SNMP Using the RIPv2: RFC1724 MIB Extensions, page 14.


Advanced RIP Features Glossary

20

GlossaryOID—object identifier. A managed object within the object tree.

SNMP—Simple Network Management Protocol. Aprotocol used to monitor and manage networking devices.

snmpget—An SNMP command to query statistics from a specific OID in the MIB.

snmpwalk—An SNMP command to query statistics from a branch in the MIB.





Cisco IOS IP Routing: RIP Configuration Guide...cisco ios ip routing: rip configuration guide...

Documents

Transcript of Cisco IOS IP Routing: RIP Configuration Guide...cisco ios ip routing: rip configuration guide...