RIP Overview

This section provides an overview of RIP configuration.

Enabling RIP on the device starts the RIP process which then begins populating its routing table and sending and receiving routing updates. Use the router rip command in configuration command mode to both enable RIP on the device and enter RIP configuration command mode.

Within RIP configuration command mode:

• Attach one or more networks to the RIP process specifying the IP address of the directly connected network, followed by the wildcard mask for this network. RIP network wildcard masks are reverse networks (use 1‘s for don‘t care bits). Use the network command to attach one or more networks to this RIP process.
• Optionally assign ACLs to a distribution list to filter networks received and to suppress networks from being advertised in RIP updates. Use the distribute-list command to assign an ACL to the list, specifying an IP routing configured VLAN and whether the affected routing updates are incoming or outgoing.
• Optionally change the preference value for using RIP as the routing protocol for this device by changing the RIP administrative distance value using the distance command.
• Optionally specify interfaces which will not transmit any RIP update packets using the passive-interface command.
• Optionally adjust routing timers associated with:
  • The frequency of routing updates by specifying the interval, in seconds, at which routing updates are sent
  • The expiration of routes by specifying the interval, in seconds, from the point of the last update after which a route times out and is marked as expired
  • The deletion of routes by specifying the interval in seconds from the point of a routes expiration after which a route is deleted from the routing table

    Using the timers command. Use the show ip protocols command to display RIP timer values.

• Specify route types that can be redistributed in RIP update messages using the redistribute command. The S- K- and 7100-Series supports redistribution of connected and static routes, optionally specifying the hop count metric for these routes, or specifying OSPF using the process ID to redistribute.