Table Of Contents
Implementing RIP on Cisco IOS XR Software
Contents
Information About Implementing RIP on Cisco IOS XR Software
Prerequisites for Implementing RIP on Cisco IOS XR Software
RIP Functional Overview
Split Horizon for RIP
Route Timers for RIP
Route Redistribution for RIP
Default Administrative Distances for RIP
Routing Policy Options for RIP
How to Implement RIP on Cisco IOS XR Software
Enabling RIP
Prerequisites
Customize RIP
Control Routing Information
Creating a Route Policy for RIP
Configuration Examples for Implementing RIP on Cisco IOS XR Software
Configuring a Basic RIP Configuration: Example
Configuring RIP on the Provider Edge: Example
Adjusting RIP Timers for each VRF Instance: Example
Configuring Redistribution for RIP: Example
Configuring Route Policies for RIP: Example
Configuring Passive Interfaces and Explicit Neighbors for RIP: Example
Controlling RIP Routes: Example
Additional References
Related Documents
Standards
MIBs
RFCs
Technical Assistance
Implementing RIP on Cisco IOS XR Software
The Routing Information Protocol (RIP) is a classic distance vector Interior Gateway Protocol (IGP) designed to exchange information within an autonomous system (AS) of a small network.
This module describes the concepts and tasks you need to implement basic RIP routing on your router. Cisco IOS XR software supports a standard implementation of RIP Version 2 (RIPv2) that supports backward compatibility with RIP Version 1 (RIPv1) as specified by RFC2453.
For RIP configuration information related to the following features, see the "Related Documents" section of this module.
•
Multiprotocol Label Switching (MPLS) Layer 3 Virtual Private Network (VPN)
•Site of Origin (SoO) Support
Note For more information about RIP on the Cisco IOS XR software and complete descriptions of the RIP commands listed in this module, see the "Related Documents" section of this module. To locate documentation for other commands that might appear while performing a configuration task, search online in the Cisco IOS XR software master command index.
Feature History for Implementing RIP on Cisco IOS XR Software
Release
|
Modification
|
Release 3.3.0
|
This feature was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
|
Release 3.4.0
|
No modification.
|
Release 3.5.0
|
Four-byte autonomous system (AS) number support was added.
|
Contents
•Information About Implementing RIP on Cisco IOS XR Software
•How to Implement RIP on Cisco IOS XR Software
•Configuration Examples for Implementing RIP on Cisco IOS XR Software
•Additional References
Information About Implementing RIP on Cisco IOS XR Software
•Prerequisites for Implementing RIP on Cisco IOS XR Software
•RIP Functional Overview
•Split Horizon for RIP
•Route Timers for RIP
•Route Redistribution for RIP
•Default Administrative Distances for RIP
•Routing Policy Options for RIP
Prerequisites for Implementing RIP on Cisco IOS XR Software
The following prerequisite must be met for implementing RIP on Cisco IOS XR software. You must be in a user group associated with a task group that includes the proper task IDs for RIP commands. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
RIP Functional Overview
RIP Version 1 (RIP v1) is a classful, distance-vector protocol that is considered the easiest routing protocol to implement. Unlike OSPF, RIP broadcasts User Datagram Protocol (UDP) data packets to exchange routing information in internetworks that are flat rather than hierarchical. Network complexity and network management time is reduced. However, as a classful routing protocol, RIP v1 allows only contiguous blocks of hosts, subnets or networks to be represented by a single route, severely limiting its usefulness.
RIP v2 allows more information carried in RIP update packets, such as support for:
•Route summarization
•Classless interdomain routing (CIDR)
•Variable-length subnet masks (VLSMs)
•Autonomous systems and the use of redistribution
•Multicast address 224.0.0.9 for RIP advertisements
The 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.
Routing information updates are advertised every 30 seconds by default, and new updates discovered from neighbor routers are stored in a routing table.
Only RIP Version 2 (RIP v2), as specified in RFC 2453, is supported on Cisco IOS XR software and, by default, the software only sends and receives RIP v2 packets. However, you can configure the software to send, or receive, or both, only Version 1 packets or only Version 2 packets or both version type packets per interface.
Here are some good reasons to use RIP:
•Compatible with diverse network devices
•Best for small networks, because there is very little overhead, in terms of bandwidth used, configuration, and management time.
•Support for legacy host systems
Because of RIP's ease of use, it is implemented in networks worldwide.
Split Horizon for RIP
Normally, 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.
If an interface is configured with secondary IP addresses and split horizon is enabled, updates might not be sourced by every secondary address. One routing update is sourced per network number unless split horizon is disabled.
Note The split horizon feature is enabled by default. In general, we recommend that you do not change the default state of split horizon unless you are certain that your operation requires the change in order to properly advertise routes.
Route Timers for RIP
RIP uses 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, by making the following timer adjustments to:
•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 RIP topology table
•The amount of time delay between RIP update packets
The first four timer adjustments are configurable by the timers basic command. The output-delay command changes the amount of time delay between RIP update packets. See the "Customize RIP" section for configuration details.
It also is possible to tune the IP routing support in the software to enable faster convergence of the various IP routing algorithms and quickly drop back to redundant routers, if necessary. The total result is to minimize disruptions to end users of the network in situations in which quick recovery is essential.
Route Redistribution for RIP
Redistribution is a feature that allows different routing domains, to exchange routing information. Networking devices that route between different routing domains are called boundary routers, and it is these devices that inject the routes from one routing protocol into another. Routers within a routing domain only have knowledge of routes internal to the domain unless route redistribution is implemented on the boundary routers.
When running RIP in your routing domain, you might find it necessary to use multiple routing protocols within your internetwork and redistribute routes between them. Some common reasons are:
•To advertise routes from other protocols into RIP, such as static, connected, OSPF and BGP.
•To migrate from RIP to a new Interior Gateway Protocol (IGP) such as EIGRP.
•To retain routing protocol on some routers to support host systems, but upgrade routers for other department groups.
•To communicate among a mixed-router vendor environment. Basically, you might use a protocol specific to Cisco in one portion of your network and use RIP to communicate with devices other than Cisco devices.
Further, route redistribution gives a company the ability to run different routing protocols in work groups or areas in which each is particularly effective. By not restricting customers to using only a single routing protocol, Cisco IOS XR route redistribution is a powerful feature that minimizes cost, while maximizing technical advantage through diversity.
When it comes to implementing route redistribution in your internetwork, it can be very simple or very complex. An example of a simple one-way redistribution is to log into a router on which RIP is enabled and use the redistribute static command to advertise only the static connections to the backbone network to pass through the RIP network. For complex cases in which you must consider routing loops, incompatible routing information, and inconsistent convergence time, you must determine why these problems occur by examining how Cisco routers select the best path when more than one routing protocol is running administrative cost.
Default Administrative Distances for RIP
Administrative distance is used as a measure of the trustworthiness of the source of the IP routing information. When a dynamic routing protocol such as RIP is configured, and you want to use the redistribution feature to exchange routing information, it is important to know the default administrative distances for other route sources so that you can set the appropriate distance weight. See Table 4 for a list of the default administrative distances.
Table 4 Default Administrative Distances of Routing Protocols
Routing Protocols
|
Administrative Distance Value
|
Connected interface
|
0
|
Static route out an interface
|
0
|
Static route to next hop
|
1
|
EIGRP Summary Route
|
5
|
External BGP
|
20
|
Internal EIGRP
|
90
|
OSPF
|
110
|
IS-IS
|
115
|
RIP version 1 and 2
|
120
|
External EIGRP
|
170
|
Internal BGP
|
200
|
Unknown
|
255
|
An administrative distance is an integer from 0 to 255. In general, the higher the value, the lower the trust rating. An administrative distance of 255 means the routing information source cannot be trusted at all and should be ignored. Administrative distance values are subjective; there is no quantitative method for choosing them.
Routing Policy Options for RIP
Route policies comprise series of statements and expressions that are bracketed with the route-policy and end-policy keywords. Rather than a collection of individual commands (one for each line), the statements within a route policy have context relative to each other. Thus, instead of each line being an individual command, each policy or set is an independent configuration object that can be used, entered, and manipulated as a unit.
Each line of a policy configuration is a logical subunit. At least one new line must follow the then, else, and end-policy keywords. A new line must also follow the closing parenthesis of a parameter list and the name string in a reference to an AS path set, community set, extended community set, or prefix set. At least one new line must precede the definition of a route policy, AS path set, community set, extended community set, or prefix set. One or more new lines can follow an action statement. One or more new lines can follow a comma separator in a named AS path set, community set, extended community set, or prefix set. A new line must appear at the end of a logical unit of policy expression and may not appear anywhere else.
How to Implement RIP on Cisco IOS XR Software
This section contains instructions for the following tasks:
•Enabling RIP (required)
•Customize RIP (optional)
•Control Routing Information (optional)
•Creating a Route Policy for RIP (optional)
Note To save configuration changes, you must commit changes when the system prompts you.
Enabling RIP
This task enables RIP routing and establishes a RIP routing process.
Prerequisites
Although you can configure RIP before you configure an IP address, no RIP routing occurs until at least one IP address is configured.
SUMMARY STEPS
1. configure
2. router rip
3. neighbor ip-address
4. broadcast-for-v2
5. interface type instance
6. receive version {1 | 2 | 1 2}
7. send version {1 | 2 | 1 2}
8. end
or
commit
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
configure
Example:
RP/0/RP0/CPU0:router# configure
|
Enters global configuration mode.
|
Step 2
|
router rip
Example:
RP/0/RP0/CPU0:router(config)# router rip
|
Configures a RIP routing process.
|
Step 3
|
neighbor ip-address
Example:
RP/0/RP0/CPU0:router(config-rip)# neighbor
172.160.1.2
|
(Optional) Defines a neighboring router with which to exchange RIP protocol information.
|
Step 4
|
broadcast-for-v2
Example:
RP/0/RP0/CPU0:router(config-rip)#
broadcast-for-v2
|
(Optional) Configures RIP to send only Version 2 packets to the broadcast IP address rather than the RIP v2 multicast address (224.0.0.9). This command can be applied at the interface or global configuration level.
|
Step 5
|
interface type instance
Example:
RP/0/RP0/CPU0:router(config-rip)# interface pos
0/1/0/0
|
(Optional) Defines the interfaces on which the RIP routing protocol runs.
|
Step 6
|
receive version {1 | 2 | 1 2}
Example:
RP/0/RP0/CPU0:router(config-rip-if)# receive
version 1 2
|
(Optional) Configures an interface to accept packets that are:
•Only RIP v1
•Only RIP v2
•Both RIP v1 and RIP v2
|
Step 7
|
send version {1 | 2 | 1 2}
Example:
RP/0/RP0/CPU0:router(config-rip-if)# send
version 1 2
|
(Optional) Configures an interface to send packets that are:
•Only RIP v1
•Only RIP v2
•Both RIP v1 and RIP v2
|
Step 8
|
end
or
commit
Example:
RP/0/RP0/CPU0:router(config-rip-if)# end
or
RP/0/RP0/CPU0:router(config-rip-if)# commit
|
Saves configuration changes.
•When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before
exiting(yes/no/cancel)?
[cancel]:
–Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.
–Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.
–Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.
•Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.
|
Customize RIP
This task describes how to customize RIP for network timing and the acceptance of route entries.
SUMMARY STEPS
1. configure
2. router rip
3. auto-summary
4. timers basic update invalid holddown flush
5. output-delay delay
6. nsf
7. interface type instance
8. metric-zero-accept
9. split-horizon disable
10. poison-reverse
11. end
or
commit
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
configure
Example:
RP/0/RP0/CPU0:router# configure
|
Enters global configuration mode.
|
Step 2
|
router rip
Example:
RP/0/RP0/CPU0:router(config)# router rip
|
Configures a RIP routing process.
|
Step 3
|
auto-summary
Example:
RP/0/RP0/CPU0:router(config-rip)# auto-summary
|
(Optional) Enables automatic route summarization of subnet routes into network-level routes.
•By default, auto-summary is disabled.
Note If you have disconnected subnets, use the no keyword to disable automatic route summarization and permit software to send subnet and host routing information across classful network boundaries.
|
Step 4
|
timers basic update invalid holddown flush
Example:
RP/0/RP0/CPU0:router(config-rip)# timers basic 5
15 15 30
|
(Optional) Adjusts RIP network timers.
Note To view the current and default timer values, view output from the show rip command.
|
Step 5
|
output-delay delay
Example:
RP/0/RP0/CPU0:router(config-rip)# output-delay 10
|
(Optional) Changes the interpacket delay for the RIP updates sent.
Note Use this command if you have a high-end router sending at high speed to a low-speed router that might not be able to receive at that fast a rate.
|
Step 6
|
nsf
Example:
RP/0/RP0/CPU0:router(config-rip)# nsf
|
(Optional) Configures NSF on RIP routes after a RIP process shutdown or restart.
|
Step 7
|
interface type instance
Example:
RP/0/RP0/CPU0:router(config-rip)# interface pos
0/1/0/0
|
(Optional) Defines the interfaces on which the RIP routing protocol runs.
|
Step 8
|
metric-zero-accept
Example:
RP/0/RP0/CPU0:router(config-rip-if)#
metro-zero-accept
|
(Optional) Allows the networking device to accept route entries received in update packets with a metric of zero (0). The received route entry is set to a metric of one (1).
|
Step 9
|
split-horizon disable
Example:
RP/0/RP0/CPU0:router(config-rip-if)#
split-horizon disable
|
(Optional) Disables the split horizon mechanism.
•By default, split horizon is enabled.
•In general, we do not recommend changing the state of the default for the split-horizon command, unless you are certain that your application requires a change to properly advertise routes. 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 networking devices in any relevant multicast groups on that network.
|
Step 10
|
poison-reverse
Example:
RP/0/RP0/CPU0:router(config-rip-if)#
poison-reverse
|
Enables poison reverse processing of RIP router updates.
|
Step 11
|
end
or
commit
Example:
RP/0/RP0/CPU0:router(config-rip-if)# end
or
RP/0/RP0/CPU0:router(config-rip-if)# commit
|
Saves configuration changes.
•When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before
exiting(yes/no/cancel)?
[cancel]:
–Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.
–Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.
–Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.
•Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.
|
Control Routing Information
This task describes how to control or prevent routing update exchange and propagation.
Some reasons to control or prevent routing updates are:
•To slow or stop the update traffic on a WAN link—If you do not control update traffic on an on-demand WAN link, the link remains up constantly. By default, RIP routing updates occur every 30 seconds.
•To prevent routing loops—If you have redundant paths or are redistributing routes into another routing domain, you may want to filter the propagation of one of the paths.
•To filter network received in updates — If you do not want other routers from learning a particular device's interpretation of one or more routes, you can suppress that information.
•To prevent other routers from processing routes dynamically— If you do not want to process routing updates entering the interface, you can suppress that information.
•To preserve bandwidth—You can ensure maximum bandwidth availability for data traffic by reducing unnecessary routing update traffic.
SUMMARY STEPS
1. configure
2. router rip
3. neighbor ip-address
4. interface type instance
5. passive-interface
6. exit
7. interface type instance
8. route-policy {in | out}
9. end
or
commit
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
configure
Example:
RP/0/RP0/CPU0:router# configure
|
Enters global configuration mode.
|
Step 2
|
router rip
Example:
RP/0/RP0/CPU0:router(config)# router rip
|
Configures a RIP routing process.
|
Step 3
|
neighbor ip-address
Example:
RP/0/RP0/CPU0:router(config-rip)# neighbor
172.160.1.2
|
(Optional) Defines a neighboring router with which to exchange RIP protocol information.
|
Step 4
|
interface type instance
Example:
RP/0/RP0/CPU0:router(config-rip)# interface pos
0/1/0/0
|
(Optional) Defines the interfaces on which the RIP routing protocol runs.
|
Step 5
|
passive-interface
Example:
RP/0/RP0/CPU0:router(config-rip-if)#
passive-interface
|
(Optional) Suppresses the sending of RIP updates on an interface, but not to explicitly configured neighbors.
|
Step 6
|
exit
Example:
RP/0/RP0/CPU0:router(config-rip-if)# exit
|
(Optional) Returns the router to the next higher configuration mode.
|
Step 7
|
interface type instance
Example:
RP/0/RP0/CPU0:router(config-rip)# interface pos
0/2/0/0
|
(Optional) Defines the interfaces on which the RIP routing protocol runs.
|
Step 8
|
route-policy {in | out}
Example:
RP/0/RP0/CPU0:router(config-rip-if)# route-policy
out
|
(Optional) Applies a routing policy to updates advertised to or received from a RIP neighbor.
|
Step 9
|
end
or
commit
Example:
RP/0/RP0/CPU0:router(config-rip-if)# end
or
RP/0/RP0/CPU0:router(config-rip-if)# commit
|
Saves configuration changes.
•When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before
exiting(yes/no/cancel)?
[cancel]:
–Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.
–Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.
–Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.
•Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.
|
Creating a Route Policy for RIP
This task defines a route policy and shows how to attach it to an instance of a RIP process. Route policies can be used to:
•Control routes sent and received
•Control which routes are redistributed
•Control origination of the default route
A route policy definition consists of the route-policy command and name argument followed by a sequence of optional policy statements, and then closes with the end-policy command.
A route policy is not useful until it is applied to routes of a routing protocol.
SUMMARY STEPS
1. configure
2. route-policy name
3. set rip-metric number
4. end-policy
5. end
or
commit
6. configure
7. router rip
8. route-policy route-policy-name {in | out}
9. end
or
commit]
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
configure
Example:
RP/0/RP0/CPU0:router# configure
|
Enters global configuration mode.
|
Step 2
|
route-policy name
Example:
RP/0/RP0/CPU0:router(config)# route-policy
IN-IPv4
|
Defines a route policy and enters route-policy configuration mode.
|
Step 3
|
set rip-metric number
RP/0/RP0/CPU0:router(config-rpl)# set rip
metric 42
|
(Optional) Sets the RIP metric attribute.
|
Step 4
|
end-policy
Example:
RP/0/RP0/CPU0:router(config-rpl)# end-policy
|
Ends the definition of a route policy and exits route-policy configuration mode.
|
Step 5
|
end
or
commit
Example:
RP/0/RP0/CPU0:router(config-rpl)# end
or
RP/0/RP0/CPU0:router(config-rpl)# commit
|
Saves configuration changes.
•When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before
exiting(yes/no/cancel)?
[cancel]:
–Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.
–Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.
–Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.
•Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.
|
Step 6
|
configure
Example:
RP/0/RP0/CPU0:router# configure
|
Enters global configuration mode.
|
Step 7
|
router rip
Example:
RP/0/RP0/CPU0:router(config)# router rip
|
Configures a RIP routing process.
|
Step 8
|
route-policy route-policy-name {in | out}
Example:
RP/0/RP0/CPU0:router(config-rip)# route-policy
IN in
|
Applies a routing policy to updates advertised to or received from an RIP neighbor.
|
Step 9
|
end
or
commit
Example:
RP/0/RP0/CPU0:router(config-rip)# end
or
RP/0/RP0/CPU0:router(config-rip)# commit
|
Saves configuration changes.
•When you issue the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before
exiting(yes/no/cancel)?
[cancel]:
–Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.
–Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.
–Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.
•Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.
|
Configuration Examples for Implementing RIP on Cisco IOS XR Software
This section provides the following configuration examples:
•Configuring a Basic RIP Configuration: Example
•Configuring RIP on the Provider Edge: Example
•Adjusting RIP Timers for each VRF Instance: Example
•Configuring Redistribution for RIP: Example
•Configuring Route Policies for RIP: Example
•Configuring Passive Interfaces and Explicit Neighbors for RIP: Example
•Controlling RIP Routes: Example
Configuring a Basic RIP Configuration: Example
The following example shows two Gigabit Ethernet interfaces configured with RIP.
interface GigabitEthernet0/6/0/0
ipv4 address 172.16.0.1 255.255.255.0
interface GigabitEthernet0/6/0/2
ipv4 address 172.16.2.12 255.255.255.0
interface GigabitEthernet0/6/0/0
interface GigabitEthernet0/6/0/2
Configuring RIP on the Provider Edge: Example
The following example shows how to configure basic RIP on the PE with two VPN routing and forwarding (VRF) instances.
interface GigabitEthernet0/6/0/0
interface GigabitEthernet0/6/0/2
interface GigabitEthernet0/6/0/3
Adjusting RIP Timers for each VRF Instance: Example
The following example shows how to adjust RIP timers for each VPN routing and forwarding (VRF) instance.
For VRF instance vpn0, the timers basic command sets updates to be broadcast every 10 seconds. If a router is not heard from in 30 seconds, the route is declared unusable. Further information is suppressed for an additional 30 seconds. At the end of the flush period (45 seconds), the route is flushed from the routing table.
For VRF instance vpn1, timers are adjusted differently: 20, 60, 60, and 70 seconds.
The output-delay command changes the interpacket delay for RIP updates to 10 milliseconds on vpn1. The default is that interpacket delay is turned off.
interface GigabitEthernet0/6/0/0
interface GigabitEthernet0/6/0/2
interface GigabitEthernet0/6/0/3
Configuring Redistribution for RIP: Example
The following example shows how to redistribute Border Gateway Protocol (BGP) and static routes into RIP.
The RIP metric used for redistributed routes is determined by the route policy. If a route policy is not configured or the route policy does not set RIP metric, the metric is determined based on the redistributed protocol. For VPNv4 routes redistributed by BGP, the RIP metric set at the remote PE router is used, if valid.
In all other cases (BGP, IS-IS, OSPF, EIGRP, connected, static), the metric set by the default-metric command is used. If a valid metric cannot be determined, then redistribution does not happen.
interface GigabitEthernet0/6/0/2
interface GigabitEthernet0/6/0/3
redistribute bgp 100 route-policy ripred
Configuring Route Policies for RIP: Example
The following example shows how to configure inbound and outbound route policies that are used to control which route updates are received by a RIP interface or sent out from a RIP interface.
if destination in pf1 then
if destination in pf2 then
interface GigabitEthernet0/6/0/0
route-policy policy_in in
interface GigabitEthernet0/6/0/2
route-policy pass-all out
Configuring Passive Interfaces and Explicit Neighbors for RIP: Example
The following example shows how to configure passive interfaces and explicit neighbors. When an interface is passive, it only accepts routing updates. In other words, no updates are sent out of an interface except to neighbors configured explicitly.
interface GigabitEthernet0/6/0/0
interface GigabitEthernet0/6/0/2
Controlling RIP Routes: Example
The following example shows how to use the distance command to install RIP routes in the Routing Information Base (RIB). The maximum-paths command controls the number of maximum paths allowed per RIP route.
interface GigabitEthernet0/6/0/0
Additional References
The following sections provide references related to implementing RIP on Cisco IOS XR software.
Related Documents
Related Topic
|
Document Title
|
RIP commands: complete command syntax, command modes, command history, defaults, usage guidelines, and examples
|
Cisco IOS XR Routing Command Reference, Release 3.5
|
MPLS VPN support for RIP feature information
|
Implementing MPLS Traffic Engineering on Cisco IOS XR Software module in Cisco IOS XR Multiprotocol Label Switching Configuration Guide, Release 3.5
|
Site of Origin (SoO) support for RIP feature information
|
Implementing MPLS Traffic Engineering on Cisco IOS XR Software module in Cisco IOS XR Multiprotocol Label Switching Configuration Guide, Release 3.5
|
Cisco CRS-1 router getting started material
|
Cisco CRS-1 Carrier Routing System Getting Started Guide, Release 3.5
|
Information about user groups and task IDs
|
Configuring AAA Services on Cisco IOS-XR Software module of Cisco IOS XR System Security Configuration Guide, Release 3.5
|
Standards
Standards
|
Title
|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
|
—
|
MIBs
RFCs
RFCs
|
Title
|
RFC 2453
|
RIP Version 2
|
Technical Assistance
Description
|
Link
|
The Cisco Technical Support website contains thousands of pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.
|
http://www.cisco.com/techsupport
|
