Configuring a RIPng Process to Import External Routes

A RIPng process can import the routes learned by other processes or routing protocols to enrich its routing information.

Run system-view
The system view is displayed.
Run ripng [ process-id ] [ vpn-instance vpn-instance-name ]
The RIPng view is displayed.
(Optional) Run default-cost cost
The default cost of external routes to be imported is set.

By default, the default cost of RIPng routes is 0.

If no cost is set for external routes to be imported, the default cost is used.

When a RIPng process imports IBGP routes, routing loops may occur. Therefore, exercise caution before you configure this function.
Run import-route { { ripng | isis | ospfv3 } [ process-id ] | bgp [ permit-ibgp ] | unr | direct | static } [ [ cost cost | inherit-cost ] | route-policy route-policy-name ] ^*
External routes are imported.
(Optional) Run filter-policy { acl6-number | acl6-name acl6-name | ipv6-prefix ipv6-prefix-name | route-policy route-policy-name } export [ protocol [ process-id ] ]
The RIPng process is configured to filter imported routes.

A RIPng process can use ACL6, route policy and IPv6 prefix lists to filter imported routes, allowing only the routes matching ACL6, route policy and IPv6 prefix lists to be advertised to RIPng neighbors. If protocol is not specified, the RIPng process filters all the routes to be advertised, including imported routes and local RIPng routes (similar to direct routes).