ROUTER RIP mode
passive-interface interface
Adding RIP Routes from Other Instances
In addition to filtering routes, you can add routes from other routing instances or protocols to the RIP
process.
With the redistribute command, you can include open shortest path first (OSPF), static, or directly
connected routes in the RIP process.
To add routes from other routing instances or protocols, use the following commands.
• Include directly connected or user-configured (static) routes in RIP.
ROUTER RIP mode
redistribute {connected | static} [metric metric-value] [route-map map-name]
–metric-value: the range is from 0 to 16.
–map-name: the name of a configured route map.
• Include specific OSPF routes in RIP.
ROUTER RIP mode
redistribute ospf process-id [match external {1 | 2} | match internal]
[metric value] [route-map map-name]
Configure the following parameters:
–process-id: the range is from 1 to 65535.
–metric: the range is from 0 to 16.
–map-name: the name of a configured route map.
To view the current RIP configuration, use the show running-config command in EXEC mode or the
show config command in ROUTER RIP mode.
Assigning a Prefix List to RIP Routes
Another method of controlling RIP (or any routing protocol) routing information is to filter the
information through a prefix list. A prefix list is applied to incoming or outgoing routes.
Those routes must meet the conditions of the prefix list; if not, the system drops the route. Prefix lists are
globally applied on all interfaces running RIP. Configure the prefix list in PREFIX LIST mode prior to
assigning it to the RIP process.
For configuration information about prefix lists, refer to Access Control Lists (ACLs).
To apply prefix lists to incoming or outgoing RIP routes, use the following commands.
• Assign a configured prefix list to all incoming RIP routes.
ROUTER RIP mode
distribute-list prefix-list-name in
• Assign a configured prefix list to all outgoing RIP routes.
ROUTER RIP mode
distribute-list prefix-list-name out
Routing Information Protocol (RIP) 755