The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter contains the following sections:
Your software release might not support all the features documented in this module. For the latest caveats and feature information, see the Bug Search Tool at https://tools.cisco.com/bugsearch/ and the release notes for your 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 "New and Changed Information"chapter or the Feature History table in this chapter.
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.
 Note |
Cisco NX-OS does not support IPv6 for RIP. |
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. 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.
You can configure authentication on RIP messages to prevent unauthorized or invalid routing updates in your network.Cisco NX-OSsupports 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 7000 Series NX-OS Security Configuration Guide, 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.
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 reverse to configure an interface to advertise routes learned by RIP as unreachable over the interface that learned the routes.
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.
By default, split horizon is enabled on all interfaces.
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.
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. |
You can use RIP to redistribute static routes or routes from other protocols. You must configure a route map with the redistribution 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 Configuring Route Policy Manager.
Whenever you redistribute routes into a RIP routing domain, Cisco NX-OS does not, by default, 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.
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 usage 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.
Cisco NX-OS supports stateless restarts for RIP. After a reboot or supervisor switchover, Cisco NX-OS applies the running configuration and RIP immediately sends request packets to repopulate its routing table.
Cisco NX-OS supports multiple instances of the RIP protocol that run on the same system. RIP supports virtual routing and forwarding (VRF) instances. VRFs exist within virtual device contexts (VDCs).
You can configure up to four RIP instances on a VDC. By default, Cisco NX-OS places you in the default VDC and default VRF unless you specifically configure another VDC and VRF.
See the Cisco Nexus 7000 Series NX-OS Virtual Device Context Configuration Guide.
You must enable RIP.
Cisco NX-OS does not support RIPv1. if Cisco NX-OS receives a RIPv1 packet, it logs a message and drops the packet.
Cisco NX-OS does not establish adjacencies with RIPv1 routers.
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.
| Parameters | Default |
|---|---|
|
Maximum paths for load balancing |
8 |
|
RIP feature |
Disabled |
|
Split horizon |
Enabled |
Configuring RIP
Confirm that you are in the correct VDC. To change the VDC, use the switchto vdc command.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
switch# configure terminal |
Enters global configuration mode. |
|
Step 2 |
switch(config)# [no] feature rip |
Enables the RIP feature. Use the no form of this command to disable this feature. |
|
Step 3 |
(Optional) switch(config)# copy running-config startup-config |
(Optional)
Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. |
|
Step 4 |
(Optional) switch(config)# show feature |
(Optional)
Displays enables and disabled features. |
The following example enables RIP:
switch # configure terminal
switch(config)# feature rip
switch(config)# copy running-config startup-configYou can create a RIP instance and configure the address family for that instance.
You must enable RIP.
Ensure that you are in the correct VDC (or use the switchto vdc command).
| Command or Action | Purpose | |||
|---|---|---|---|---|
|
Step 1 |
switch# configure terminal |
Enters global configuration mode. |
||
|
Step 2 |
switch(config)# [no] router rip instance-tag |
Creates a new RIP instance with the configured instance-tag. Use the no form of this command to disable this feature.
|
||
|
Step 3 |
switch(config-router)# address-family ipv4 unicast |
Configures the address family for this RIP instance and enters address-family configuration mode. |
||
|
Step 4 |
(Optional) switch(config-router-af)# show ip rip [instance instance-tag] [vrf vrf-name] |
(Optional)
Displays a summary of RIP information for all RIP instances. |
||
|
Step 5 |
(Optional) switch(config-router-af)# distance value |
(Optional)
Sets the administrative distance for RIP, in address-family configuration mode. The range is from 1 to 255. |
||
|
Step 6 |
(Optional) switch(config-router-af)# maximum-paths number |
(Optional)
Configures the maximum number of equal-cost paths that RIP maintains in the route table, in address-family configuration mode. The range is from 1 to 16. |
||
|
Step 7 |
(Optional) switch(config-router-af)# copy running-config startup-config |
(Optional)
Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. |
The following example creates a RIP instance for IPv4 and sets the number of equal-cost paths for load balancing:
switch# configure terminal
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-configYou can restart a RIP instance and remove all associated neighbors for the instance.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
switch# configure terminal |
Enters global configuration mode. |
|
Step 2 |
switch(config)# restart rip instance-tag |
Restarts the RIP instance and removes all neighbors. |
|
Step 3 |
(Optional) switch(config)# copy running-config startup-config |
(Optional)
Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. |
The following example restarts a RIP instance:
switch # configure terminal
switch(config)# restart rip Enterprise
switch(config)# copy running-config startup-configYou must enable RIP.
Confirm that you are in the correct VDC. To change the VDC, use the switchto vdc command.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
switch# configure terminal |
Enters global configuration mode. |
|
Step 2 |
switch(config)# interface interface-type slot/port |
Enters interface configuration mode. |
|
Step 3 |
switch(config-if)# ip router rip instance-tag |
Associates this interface with a RIP instance. |
|
Step 4 |
(Optional) switch(config-if)# copy running-config startup-config |
(Optional)
Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. |
|
Step 5 |
(Optional) switch(config-if)# show ip rip [instance instance-tag] interface [interface-type slot/port] [vrf vrf-name] [detail] |
(Optional)
Displays RIP information for an interface. |
The following example configures RIP on an Ethernet interface:
switch # configure terminal
switch(config)# interface ethernet 1/2
switch(config-if)# no switchport
switch(config-if)# ip router rip Enterprise
switch(config-if)# show ip rip Enterprise ethernet 1/2
switch(config-if)# copy running-config startup-config
You can configure authentication for RIP packets on an interface.
You must enable RIP.
Ensure that you are in the correct VDC (or use the switchto vdc command).
Configure a keychain if necessary before enabling authentication. For details about implementing key chains, see the Cisco Nexus 7000 Series NX-OS Security Configuration Guide.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
switch# configure terminal |
Enters global configuration mode. |
|
Step 2 |
switch(config)# interface interface-type slot/port |
Enters interface configuration mode. |
|
Step 3 |
switch(config-if)# ip rip authentication mode {text | md5} |
Sets the authentication type for RIP on this interface as cleartext or MD5 authentication digest. |
|
Step 4 |
switch(config-if)# ip rip authentication keychain key |
Configures the authentication key used for RIP on this interface. |
|
Step 5 |
(Optional) switch(config-if)# copy running-config startup-config |
(Optional)
Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. |
The following example creates a key chain and configures MD5 authentication on a RIP interface:
switch# configure terminal
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)# ip rip authentication mode md5
switch(config-if)# ip rip authentication keychain RIPKey
switch(config-if)# copy running-config startup-configYou can configure a RIP interface to receive routes but not send route updates by setting the interfaces to passive mode. You can configure a RIP interface in passive mode in the interface configuration mode.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
switch# configure terminal |
Enters global configuration mode. |
|
Step 2 |
switch(config)# interface interface-type slot/port |
Enters interface configuration mode. |
|
Step 3 |
switch(config-if)# ip rip passive-interface |
Sets the interface into passive mode. |
|
Step 4 |
(Optional) switch(config-if)# copy running-config startup-config |
(Optional)
Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. |
The following example configures a RIP interface in passive mode:
switch # configure terminal
switch(config)# interface ethernet 1/2
switch(config-if)# ip rip passive-interface
switch(config-if)# copy running-config startup-configYou can configure an interface to advertise routes learned by RIP as unreachable over the interface that learned the routes by enabling poison reverse. You can configure split horizon with poison reverse on an interface using the interface configuration mode.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
switch# configure terminal |
Enters global configuration mode. |
|
Step 2 |
switch(config)# interface interface-type slot/port |
Enters interface configuration mode. |
|
Step 3 |
switch(config-if)# ip rip poison-reverse |
Enables split horizon with poison reverse. Split horizon with poison reverse is disabled by default. |
|
Step 4 |
(Optional) switch(config-if)# copy running-config startup-config |
(Optional)
Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. |
The following example restarts a RIP instance:
switch # configure terminal
switch(config)# interface ethernet 1/2
switch(config-if)# ip rip poison-reverse
switch(config-if)# copy running-config startup-configYou 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 interface configuration mode.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
switch# configure terminal |
Enters global configuration mode. |
|
Step 2 |
switch(config)# interface interface-type slot/port |
Enters interface configuration mode. |
|
Step 3 |
switch(config-if)# ip rip summary-address ip-prefix/mask-len |
Configured a summary address for RIP for IPv4 addresses. |
|
Step 4 |
(Optional) switch(config-if)# copy running-config startup-config |
(Optional)
Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. |
The following example restarts a RIP instance:
switch# configure terminal
switch(config)# interface ethernet 1/2
switch(config-if)# ip router rip summary-address 192.0.2.0/24
switch(config-if)# copy running-config startup-configYou 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.
You must enable RIP.
Ensure that you are in the correct VDC (or use the switchto vdc command).
Configure a route map before configuring redistribution.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
switch# configure terminal |
Enters global configuration mode. |
|
Step 2 |
switch(config)# router rip instance-tag |
Creates a new RIP instance with the configured instance-tag. |
|
Step 3 |
switch(config-router)# address-family ipv4 unicast |
Enters address family configuration mode. |
|
Step 4 |
switch(config-router-af)# redistribute {bgp as | direct | eigrp | isis | ospf | ospfv3 | rip} instance-tag | static} route-map map-name |
Redistributes routes from other protocols into RIP. |
|
Step 5 |
(Optional) switch(config-router-af)# default-information originate [always] [route-map map-name] |
(Optional)
Generates a default route into RIP, optionally controlled by a route map. |
|
Step 6 |
(Optional) switch(config-router-af)# default-metric value |
(Optional)
Sets the default metric for all redistributed routes. The range is from 1 to 15. The default is 1. |
|
Step 7 |
(Optional) switch(config-router-af)# copy running-config startup-config |
(Optional)
Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. |
|
Step 8 |
(Optional) switch(config-router-af)# show ip rip route [ip-prefix [longer-prefixes | shorter-prefixes]] [vrf vrf-name] [summary] |
(Optional)
Shows the routes in RIP. |
The following example shows how to redistribute EIGRP into RIP:
switch# configure terminal
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-configBeginning with Cisco NX-OS Release 6.1, you can configure Cisco NX-OS RIP to behave like Cisco IOS RIP in the way that routes are advertised and processed.
Directly connected routes are treated with cost 1 in Cisco NX-OS RIP and with cost 0 in Cisco IOS RIP. When routes are advertised in Cisco NX-OS RIP, the receiving device adds a minimum cost of +1 to all received routes and installs the routes in its routing table. In Cisco IOS RIP, this cost increment is done on the sending router, and the receiving router installs the routes without any modification. This difference in behavior can cause issues when both Cisco NX-OS and Cisco IOS devices are working together. You can prevent these compatibility issues by configuring Cisco NX-OS RIP to advertise and process routes like Cisco IOS RIP
You must enable RIP.
Ensure that you are in the correct VDC (or use the switchto vdc command).
| Command or Action | Purpose | |||
|---|---|---|---|---|
|
Step 1 |
switch# configure terminal |
Enters global configuration mode. |
||
|
Step 2 |
switch(config)# router rip instance-tag |
Creates a new RIP instance with the configured instance-tag. You can enter 100, 201, or up to 20 alphanumeric chapters for the instance tag. |
||
|
Step 3 |
switch(config-router)# [no] metric direct 0 |
Configures all directly connected routes with cost 0 instead of the default of cost 1 in order to make Cisco NX-OS RIP compatible with Cisco IOS RIP in the way that routes are advertised and processed.
|
||
|
Step 4 |
(Optional) switch(config-router)# show running-config rip |
(Optional)
Displays the current running RIP configuration. |
||
|
Step 5 |
(Optional) switch(config-router)# copy running-config startup config |
(Optional)
Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration |
The following example shows how to disable NX-OS RIP compatibility with Cisco IOS RIP by returning all direct routes from cost 0 to cost 1:
switch# configure terminal
switch(config)# router rip 100
switch(config-router)# no metric direct 0
switch(config-router)# show running-config rip
switch(config-router)# copy running-config startup-configYou can configure multiple RIP instances in each VDC. You can also create multiple VRFs within each VDC 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 configurations for an interface. |
You must enable RIP.
Create the VDCs.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
switch# configure terminal |
Enters global configuration mode. |
|
Step 2 |
switch(config)# vrf vrf-name |
Creates a new VRF. |
|
Step 3 |
switch(config-vrf)# exit |
Exits VRF configuration mode. |
|
Step 4 |
switch(config)# router rip instance-tag |
Creates a new RIP instance with the configured instance tag. |
|
Step 5 |
switch(config-router)# vrf vrf-name |
Creates a new VRF and enters VRF configuration mode. |
|
Step 6 |
(Optional) switch(config-router-vrf)# address-family ipv4 unicast |
(Optional)
(Optional) Configures the VRF address family for this RIP instance. |
|
Step 7 |
(Optional) switch(-router-vrf-af)# redistribute {bgp as | direct | {eigrp | isis | ospf | ospfv3 | rip} instance-tag | static} route-map map-name |
(Optional)
Redistributes routes from other protocols into RIP. |
|
Step 8 |
switch(config-router-vrf-af)# interface ethernet slot/port |
Enters interface configuration mode. |
|
Step 9 |
switch(config-if)# no switchport |
Configures the interface as a Layer 3 routed interface. |
|
Step 10 |
switch(config-if)# vrf member vrf-name |
Adds this interface to a VRF. |
|
Step 11 |
switch(config-if)# ip-address ip-prefix/length |
Configures an IP address for this interface. You must perform this step after you assign this interface to a VRF. |
|
Step 12 |
switch(config-if)# ip router rip instance-tag |
Associates this interface with a RIP instance. |
|
Step 13 |
(Optional) switch(config-if)# copy running-config startup-config |
(Optional)
Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. |
|
Step 14 |
(Optional) switch(config-if)# show ip rip [instance instance-tag] interface [interface-type slot/port] [vrf vrf-name] |
(Optional)
Displays RIP information for an interface in a VRF. |
The following example shows how to create a VRF and add an interface to the VRF:
switch# configure terminal
switch(config)# vrf context RemoteOfficeVRF
switch(config-vrf)# exit
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)# 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-configYou 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 internet work needs.
Note |
You must configure the same values for the RIP timers on all RIP-enabled routers in your network. |
| Command or Action | Purpose | |||
|---|---|---|---|---|
|
Step 1 |
(Optional) switch(config-router-af)# timers basic update timeout holddown garbage-collection |
(Optional)
|
||
|
Step 2 |
switch(config-router-af)# exit |
Exits address-family configuration mode. |
||
|
Step 3 |
switch(config-router)# exit |
Exits router configuration mode. |
||
|
Step 4 |
switch(config)# interface type number |
Enters interface configuration mode. |
||
|
Step 5 |
(Optional) switch(config-if)# ip rip metric-offset value |
(Optional)
Adds a value to the metric for every router received on this interface. The range is from 1 to 15. The default is 1. |
||
|
Step 6 |
(Optional) switch(config-if)# ip rip route-filter {prefix-list list-name | route-map map-name | [in | out] |
(Optional)
Specifies a route map to filter incoming or outgoing RIP updates. |
switch(config-router-af)# timers basic 40 120 120 100
switch(config-router-af)# exit
switch(config-router)# exit
switch(config)# exit
switch(config)# interface ethernet 1/2
switch(config-if)# ip rip metric-offset 10
switch(config-if)# ip rip route-filter route-map InputMap inUse one of the following commands to verify the configuration:
|
Command |
Purpose |
|---|---|
| show ip rip instance [instance-tag] [vrf vrf-name] |
Displays the status for an instance of RIP. |
| show ip rip [instance instance-tag] interface slot/port detail [vrf vrf-name] |
Displays the RIP status for an interface |
| show ip rip [instance instance-tag] neighbor [interface-type number] [vrf vrf-name] |
Displays the RIP neighbor table |
| show ip rip [instance instance-tag] route [ip-prefix/length [longer-prefixes | shorter-prefixes]] [summary] [vrf vrf-name] |
Displays the RIP route table |
| show running-configuration rip |
Displays the current running RIP configuration. |
Use one of the following commands to display RIP statistics:
|
Command |
Purpose |
|---|---|
|
show ip rip [instance instance-tag] policy statistics redistribute {bgp as | direct | {eigrp | isis | ospf | ospfv3 | rip} instance-tag | static} [vrf vrf-name] |
Displays the RIP policy status. Use the clear ip rip policy command to clear policy statistics. |
| show ip rip [instance instance-tag] statistics interface-type number] [vrf vrf-name] |
Displays the RIP statistics. Use the clear ip rip statistics command to clear RIP statistics. |
Use the clear ip rip policy command to clear policy statistics.
Use the clear ip rip statistics command to clear RIP statistics.
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.
vrf context NewVRF
!
feature rip
router rip Enterprise
vrf NewVRF
address-family ip unicast
redistribute eigrp 201 route-map RIPmap
max-paths 10
!
interface ethernet 1/2
vrf NewVRF
ip address 192.0.2.1/16
ip router rip Enterprise
ip rip authentication mode md5
ip rip authentication keychain RIPKey|
Related Topic |
Document Title |
|---|---|
|
RIP CLI |
Cisco Nexus 7000 Series NX-OS Unicast Routing Command Reference |
|
VDCs and VRFs |
Cisco Nexus 7000 Series NX-OS Virtual Device Context Configuration Guide |
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
This table includes only the updates for those releases that have resulted in additions or changes to the feature.
|
Feature Name |
Releases |
Feature Information |
|---|---|---|
|
RIP |
6.1(1) |
Added the ability to configure Cisco NX-OS RIP to be behaviorally compatible with Cisco IOS RIP in the way that routes are advertised and processed. |
|
RIP |
4.0(1) |
This feature was introduced. |
Feedback