Configuring RIP to Import Routes

Procedure

1. Run system-view

   The system view is displayed.

2. Run rip [ process-id ]

   The RIP view is displayed.

3. (Optional) Run default-cost cost

   The default metric for imported routes is set.

   If the metric of imported routes is not specified in step 4, the default metric is used.

4. Run import-route bgp [ permit-ibgp ] [ cost { cost | transparent } | route-policy route-policy-name ] ^* or import-route { { static | direct | unr } | { { rip | ospf | isis } [ process-id ] } } [ cost cost | route-policy route-policy-name ] ^*

   External routes are imported to RIP.

   

   When RIP imports IBGP routes, routing loops may occur. Configure this function with caution.

5. (Optional) Run filter-policy { acl-number | acl-name acl-name | ip-prefix ip-prefix-name } export [ protocol [ process-id ] | interface-type interface-number ]

   The imported routes are filtered before being advertised.

   The routing information advertised by RIP may contain the routing information imported from other protocols. You can use the protocol parameter to filter the routing information imported from a specified routing protocol. If the protocol parameter is not used, all the routes advertised by RIP are filtered, including the imported routes and the local routes (direct routes).

   

   RIP-2 defines a 16-bit tag, while other routing protocols define 32-bit tags. If the routes of other protocols are imported to RIP and the tag is used in the routing policy, the tag value cannot exceed 65535. If the tag value exceeds 65535, the routing policy becomes invalid or the matching result is incorrect.