Install guide

32 Redistributing BGP Routes into RIP Release Note
Software Version 2.7.6
C613-10462-00 REV A
Redistributing BGP Routes into RIP
Software Release 2.7.6 enables you to configure RIP to redistribute BGP routes.
You can redistribute up to 500 BGP routes as RIP routes, by using the
command:
add ip rip redistribute protocol=bgp [limit=1..500]
[metric=0..16] [routemap=routemap]
[subnet={on|off|yes|no|true|false}]
This command enables you to set the RIP metric for the imported routes,
choose whether to import subnet routes, specify the number of routes to
import, and filter routes through a route map.
To change the settings for redistributing routes, use the command:
set ip rip redistribute protocol=bgp [limit=1..500]
[metric=0..16] [routemap=routemap]
[subnet={on|off|yes|no|true|false}]
To display the settings for redistributing BGP routes, and the number of BGP
routes that RIP is currently redistributing, use the command:
show ip rip redistribute
To stop RIP from redistributing BGP routes, use the command:
delete ip rip redistribute protocol=bgp
The number of routes that RIP can redistribute is limited because RIP is not
designed to process large numbers of routes. By default, the limit is set to 50.
When the limit is reached, routes are no longer imported until existing routes
are removed. Because they are BGP routes, BGP controls when the routes
disappear. To ensure RIP imports the routes it needs to, we recommend you:
■ minimise the number of routes in the BGP route table by configuring
automatic summarising
■ use a route map to select an appropriate subset of the BGP routes, as
described in the next section
Filtering BGP Routes When Redistributing
To select the most appropriate routes for importing into BGP, you can apply a
route map, using one of the commands:
add ip rip redistribute protocol=bgp [routemap=routemap]
[other-options...]
set ip rip redistribute protocol=bgp [routemap=routemap]
[other-options...]
The router or switch can use the route map to:
■ accept or reject update messages on the basis of origin, community, AS
path, next hop or Multi Exit Discriminator (MED)
■ accept or reject particular routes, by comparing the update message’s
routes with a prefix list
■ alter matching routes’ metric and tag