- Information About RIP
- Licensing Requirements for RIP
- Prerequisites for RIP
- Guidelines and Limitations
- Default Settings
- Configuring RIP
- Enabling the RIP Feature
- Creating a RIP Instance
- Restarting a RIP Instance
- Configuring RIP on an Interface
- Configuring RIP Authentication
- Configuring a Passive Interface
- Configuring Split Horizon with Poison Reverse
- Configuring Route Summarization
- Configuring Route Redistribution
- Configuring Virtualization
- Tuning RIP
- Verifying the RIP Configuration
- Displaying RIP Statistics
- Configuration Examples for RIP
- Related Topics
- Additional References
Configuring RIP
This chapter describes how to configure the Routing Information Protocol (RIP).
Information About RIP
This section includes the following topics:
- RIP Overview
- RIPv2 Authentication
- Split Horizon
- Route Filtering
- Route Summarization
- Route Redistribution
- Load Balancing
- Virtualization Support
RIP Overview
RIP uses User Datagram Protocol (UDP) data packets to exchange routing information in small internetworks. RIPv2 supports IPv4. RIPv2 uses an optional authentication feature supported by the RIPv2 protocol (see the “RIPv2 Authentication” section).
RIP uses the following two message types:
- Request—Sent to the multicast address 224.0.0.9 to request route updates from other RIP-enabled routers.
- Response—Sent every 30 seconds by default (see the “Verifying the RIP Configuration” section). The router also sends response messages after it receives a Request message. The response message contains the entire RIP route table. RIP sends multiple response packets for a request if the RIP routing table cannot fit in one response packet.
RIP uses a hop count for the routing metric. The hop count is the number of routers that a packet can traverse before reaching its destination. A directly connected network has a metric of 1; an unreachable network has a metric of 16. This small range of metrics makes RIP an unsuitable routing protocol for large networks.
RIPv2 Authentication
You can configure authentication on RIP messages to prevent unauthorized or invalid routing updates in your network. Cisco NX-OS supports a simple password or an MD5 authentication digest.
You can configure the RIP authentication per interface by using key-chain management for the authentication keys. Key-chain management allows you to control changes to the authentication keys used by an MD5 authentication digest or simple text password authentication. See the Cisco Nexus 5500 Series NX-OS Security Configuration Guide, Release 6.0, for more details about creating key-chains.
To use an MD5 authentication digest, you configure a password that is shared at the local router and all remote RIP neighbors. Cisco NX-OS creates an MD5 one-way message digest based on the message itself and the encrypted password and sends this digest with the RIP message (Request or Response). The receiving RIP neighbor validates the digest by using the same encrypted password. If the message has not changed, the calculation is identical and the RIP message is considered valid.
An MD5 authentication digest also includes a sequence number with each RIP message to ensure that no message is replayed in the network.
Split Horizon
You can use split horizon to ensure that RIP never advertises a route out of the interface where it was learned.
Split horizon is a method that controls the sending of RIP update and query packets. When you enable split horizon on an interface, Cisco NX-OS does not send update packets for destinations that were learned from this interface. Controlling update packets in this manner reduces the possibility of routing loops.
You can use split horizon with poison revers to configure an interface to advertise routes learned by RIP as unreachable over the interface that learned the routes. Figure 9-1 shows a sample RIP network with split horizon with poison reverse enabled.
Figure 9-1 RIP with Split Horizon Poison Reverse
Router C learns about route X and advertises that route to router B. Router B in turn advertises route X to router A, but sends a route X unreachable update back to router C.
Route Filtering
You can configure a route policy on a RIP-enabled interface to filter the RIP updates. Cisco NX-OS updates the route table with only those routes that the route policy allows.
Route Summarization
You can configure multiple summary aggregate addresses for a specified interface. Route summarization simplifies route tables by replacing a number of more-specific addresses with an address that represents all the specific addresses. For example, you can replace 10.1.1.0/24, 10.1.2.0/24, and 10.1.3.0/24 with one summary address, 10.1.0.0/16.
If more specific routes are in the routing table, RIP advertises the summary address from the interface with a metric equal to the maximum metric of the more specific routes.
Note Cisco NX-OS does not support automatic route summarization.
Route Redistribution
You can use RIP to redistribute static routes or routes from other protocols. When you configure redistribution, use a route policy to control which routes are passed into RIP. A route policy allows you to filter routes based on attributes such as the destination, origination protocol, route type, route tag, and so on. For more information, see Chapter13, “Configuring Route Policy Manager”
Whenever you redistribute routes into a RIP routing domain, by default Cisco NX-OS does not redistribute the default route into the RIP routing domain. You can generate a default route into RIP, which can be controlled by a route policy.
You also configure the default metric that is used for all imported routes into RIP.
Load Balancing
You can use load balancing to allow a router to distribute traffic over all the router network ports that are the same distance from the destination address. Load balancing increases the utilization of network segments and increases effective network bandwidth.
Cisco NX-OS supports the Equal Cost Multiple Paths (ECMP) feature with up to 16 equal-cost paths in the RIP route table and the unicast RIB. You can configure RIP to load balance traffic across some or all of those paths.
Virtualization Support
Cisco NX-OS supports multiple instances of the RIP protocol that runs on the same system. RIP supports Virtual Routing and Forwarding instances (VRFs).
By default, Cisco NX-OS places you in the default VRF unless you specifically configure another VRF. See Chapter11, “Configuring Layer 3 Virtualization”
Licensing Requirements for RIP
The following table shows the licensing requirements for this feature:
Prerequisites for RIP
RIP has the following prerequisites:
- You must enable the RIP feature (see the “Enabling the RIP Feature” section).
Guidelines and Limitations
RIP has the following configuration guidelines and limitations:
Default Settings
Table 9-1 lists the default settings for RIP parameters.
|
|
---|---|
Configuring RIP
This section includes the following topics:
- Enabling the RIP Feature
- Creating a RIP Instance
- Configuring RIP on an Interface
- Configuring a Passive Interface
- Configuring Route Summarization
- Configuring Route Summarization
- Configuring Route Redistribution
- Configuring Virtualization
- Tuning RIP
Note If you are familiar with the Cisco IOS CLI, be aware that the Cisco NX-OS commands for this feature might differ from the Cisco IOS commands that you would use.
Enabling the RIP Feature
You must enable the RIP feature before you can configure RIP.
SUMMARY STEPS
DETAILED STEPS
|
|
|
---|---|---|
Use the no feature rip command to disable the RIP feature and remove all associated configuration.
|
|
---|---|
Disables the RIP feature and removes all associated configuration. |
Creating a RIP Instance
You can create a RIP instance and configure the address family for that instance.
BEFORE YOU BEGIN
Ensure that you have enabled the RIP feature (see the “Enabling the RIP Feature” section).
SUMMARY STEPS
3. address-family ipv4 unicast
4. (Optional) show ip rip [ instance instance-tag ] [ vrf vrf-name ]
DETAILED STEPS
Use the no router rip command to remove the RIP instance and the associated configuration.
|
|
---|---|
Note You must also remove any RIP commands configured in interface mode.
You can configure the following optional parameters for RIP in address-family configuration mode:
|
|
---|---|
Sets the administrative distance for RIP. The range is from 1 to 255. The default is 120. See the “Administrative Distance” section. |
|
Configures the maximum number of equal-cost paths that RIP maintains in the route table. The range is from 1 to 16. The default is 16. |
This example shows how to create a RIP instance for IPv4 and set the number of equal-cost paths for load balancing:
switch(config)# router rip Enterprise
switch(config-router)# address-family ipv4 unicast
switch(config-router-af)# max-paths 10
switch(config-router-af)# copy running-config startup-config
Restarting a RIP Instance
You can restart a RIP instance. This clears all neighbors for the instance.
To restart an RIP instance and remove all associated neighbors, use the following command:
|
|
---|---|
Configuring RIP on an Interface
BEFORE YOU BEGIN
Ensure that you have enabled the RIP feature (see the “Enabling the RIP Feature” section).
SUMMARY STEPS
2. interface interface-type slot/port
5. (Optional) show ip rip [ instance instance-tag ] interface [ interface-type slot/port ] [ vrf vrf-name ] [ detail ]
DETAILED STEPS
This example shows how to add the Ethernet 1/2 interface to a RIP instance:
switch(config)# interface ethernet 1/2
switch(config-if)# no switchport
switch(config-if)# ip router rip Enterprise
switch(config)# copy running-config startup-config
Configuring RIP Authentication
You can configure authentication for RIP packets on an interface.
BEFORE YOU BEGIN
Ensure that you have enabled the RIP feature (see the “Enabling the RIP Feature” section).
Configure a key chain if necessary before enabling authentication. See the Cisco Nexus 5500 Series NX-OS Security Configuration Guide, Release 6.0, for details on implementing key chains.
SUMMARY STEPS
2. interface interface-type slot/port
4. ip rip authentication mode { text | md5 }
DETAILED STEPS
This example shows how to create a key chain and configure MD5 authentication on a RIP interface:
switch(config)# key chain RIPKey
switch(config)# key-string myrip
switch(config)# accept-lifetime 00:00:00 Jan 01 2000 infinite
switch(config)# send-lifetime 00:00:00 Jan 01 2000 infinite
switch(config)# interface ethernet 1/2
switch(config-if)# no switchport
switch(config-if)# ip rip authentication mode md5
switch(config-if)# ip rip authentication keychain RIPKey
switch(config-if)# copy running-config startup-config
Configuring a Passive Interface
You can configure a RIP interface to receive routes but not send route updates by setting the interface to passive mode.
To configure a RIP interface in passive mode, use the following command in interface configuration mode:
|
|
---|---|
Configuring Split Horizon with Poison Reverse
You can configure an interface to advertise routes learned by RIP as unreachable over the interface that learned the routes by enabling poison reverse.
To configure split horizon with poison reverse on an interface, use the following command in interface configuration mode:
|
|
---|---|
Enables split horizon with poison reverse. Split horizon with poison reverse is disabled by default. |
Configuring Route Summarization
You can create aggregate addresses that are represented in the routing table by a summary address. Cisco NX-OS advertises the summary address metric that is the smallest metric of all the more-specific routes.
To configure a summary address on an interface, use the following command in interface configuration mode:
|
|
---|---|
ip rip summary-address ip-prefix/mask-len switch(config-if)# ip router rip summary-address 192.0.2.0/24 |
Configuring Route Redistribution
You can configure RIP to accept routing information from another routing protocol and redistribute that information through the RIP network. Redistributed routes can optionally be assigned a default route.
Note Redistribution does not work if the access list is used as a match option in route-maps.
BEFORE YOU BEGIN
Ensure that you have enabled the RIP feature (see the “Enabling the RIP Feature” section).
Configure a route map before configuring redistribution. See the “Configuring Route Maps” section for details on configuring route maps.
SUMMARY STEPS
3. address-family ipv4 unicast
4. redistribute { bgp as | direct | eigrp | ospf | ospfv3 | rip } instance-tag | static } route-map map-name
5. (Optional) default-information originate [ always ] [ route-map map-name ]
6. (Optional) default-metric value
7. (Optional) show ip rip route [{ ip-prefix [ longer- prefixes | shorter-prefixes]] [ vrf vrf-name ] [ summary ]
DETAILED STEPS
|
|
|
---|---|---|
Creates a new RIP instance with the configured instance-tag. |
||
redistribute { bgp as | direct |{ eigrp | ospf | ospfv3 | rip } instance-tag | static } route-map map-name switch(config-router-af)# redistribute eigrp 201 route-map RIPmap |
Redistributes routes from other protocols into RIP. See the “Configuring Route Maps” section for more information about route maps. |
|
default-information originate [ always ] [ route-map map-name ] switch(config-router-af)# default-information originate always |
(Optional) Generates a default route into RIP, optionally controlled by a route map. |
|
(Optional) Sets the default metric for all redistributed routes. The range is from 1 to 15. The default is 1. |
||
show ip rip route [ ip-prefix [ longer-prefixes | shorter-prefixes ] [ vrf vrf-name] [ summary ] |
||
copy running-config startup-config switch(config-router-af)# copy running-config startup-config |
This example shows how to redistribute EIGRP into RIP:
switch(config)# router rip Enterprise
switch(config-router)# address-family ipv4 unicast
switch(config-router-af)# redistribute eigrp 201 route-map RIPmap
switch(config-router-af)# copy running-config startup-config
Configuring Virtualization
You can create multiple VRFs and use the same or multiple RIP instances in each VRF. You assign a RIP interface to a VRF.
Note Configure all other parameters for an interface after you configure the VRF for an interface. Configuring a VRF for an interface deletes all the configuration for that interface.
BEFORE YOU BEGIN
Ensure that you have enabled the RIP feature (see the “Enabling the RIP Feature” section).
SUMMARY STEPS
6. (Optional) address-family ipv4 unicast
7. (Optional) redistribute { bgp as | direct | { eigrp | ospf | ospfv3 | rip } instance-tag | static } route-map map-name
8. interface ethernet slot/port
11. ip-address ip-prefix/length
12. ip router rip instance-tag
13. (Optional) show ip rip [ instance instance-tag ] interface [ interface-type slot/port ] [ vrf vrf-name ]
DETAILED STEPS
|
|
|
---|---|---|
Creates a new RIP instance with the configured instance tag. |
||
(Optional) Configures the VRF address family for this RIP instance. |
||
redistribute { bgp as | direct | { eigrp | ospf | ospfv3 | rip } instance-tag | static } route-map map-name switch(config-router-vrf-af)# redistribute eigrp 201 route-map RIPmap |
(Optional) Redistributes routes from other protocols into RIP. See the “Configuring Route Maps” section for more information about route maps. |
|
Enters interface configuration mode. Note If this is a QSFP+ GEM, the slot/port syntax is slot/QSFP-module/port. |
||
Configures an IP address for this interface. You must do this step after you assign this interface to a VRF. |
||
show ip rip [ instance i nstance-tag ] interface [ interface-type slot/port ] [ vrf vrf-name ] |
(Optional) Displays RIP information for an interface. in a VRF. Note If this is a QSFP+ GEM, the slot/port syntax is slot/QSFP-module/port. |
|
This example shows how to create a VRF and add an interface to the VRF:
switch(config)# vrf context RemoteOfficeVRF
switch(config)# router rip Enterprise
switch(config-router)# vrf RemoteOfficeVRF
switch(config-router-vrf)# address-family ipv4 unicast
switch(config-router-vrf-af)# redistribute eigrp 201 route-map RIPmap
switch(config-router-vrf-af)# interface ethernet 1/2
switch(config-if)# no switchport
switch(config-if)# vrf member RemoteOfficeVRF
switch(config-if)# ip address 192.0.2.1/16
switch(config-if)# ip router rip Enterprise
switch(config-if)# copy running-config startup-config
Tuning RIP
You can tune RIP to match your network requirements. RIP uses several timers that determine 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.
Note You must configure the same values for the RIP timers on all RIP-enabled routers in your network.
You can use the following optional commands in address-family configuration mode to tune RIP:
You can use the following optional commands in interface configuration mode to tune RIP:
Verifying the RIP Configuration
To display the RIP configuration information, perform one of the following tasks:
Displaying RIP Statistics
To display the RIP statistics, use the following commands:
Use the clear ip rip policy command to clear policy statistics.
Use the clear ip rip statistics command to clear RIP statistics.
Configuration Examples for RIP
This example creates the Enterprise RIP instance in a VRF and adds Ethernet interface 1/2 to this RIP instance. The example also configures authentication for Ethernet interface 1/2 and redistributes EIGRP into this RIP domain.
redistribute eigrp 201 route-map RIPmap
ip rip authentication mode md5
Related Topics
See Chapter 13, “Configuring Route Policy Manager” for more information on route maps.
Additional References
For additional information related to implementing RIP, see the following sections:
Related Documents
|
|
---|---|
Cisco Nexus 5000 Series Command Reference, Cisco NX-OS Releases 4.x, 5.x |
Standards
|
|
---|---|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |