Configuring RIP to Import External Routes
RIP can import routes from other processes or routing protocols to enrich the RIP routing table.
Context
On a large-scale network, multiple routing protocols may be configured for devices in different areas. In this situation, configure RIP to import routes from other processes or routing protocols to implement inter-area communication.
Procedure
- Run system-view
The system view is displayed.
- Run rip [ process-id ]
A RIP process is created, and the RIP view is displayed.
- (Optional) Run default-cost cost
The default cost is set for imported routes.
If you do not specify the cost for external routes, the value 0 takes effect.
- Import external routes.
- To import direct, static, IS-IS, or OSPF routes, or routes of other RIP processes, run the import-route { static | direct | bgp | unr | { isis | ospf | rip } [ process-id ] } [ cost cost | { route-policy route-policy-name | route-filter route-filter-name } ] * command.
- To import IBGP routes, run the import-route bgp permit-ibgp [ cost cost | { route-policy route-policy-name | route-filter route-filter-name } ] * command or the import-route bgp [ permit-ibgp ] { cost transparent { route-policy route-policy-name | route-filter route-filter-name } | { route-policy route-policy-name | route-filter route-filter-name } cost transparent | cost transparent } command.
Import of routes of other protocols may lead to routing loops. Therefore, exercise caution when running the import-route command.
- Run commit
The configuration is committed.