Configuring OSPFv3 to Import External Routes

Importing the routes discovered by other routing protocols can enrich OSPFv3 routing information.

Context

OSPFv3 is a link state-based routing protocol and cannot filter LSAs to be advertised. Therefore, OSPFv3 must filter routes when importing them so that only the filtered routes can be advertised.

Perform the following steps on the router that runs OSPFv3:

Procedure

Run system-view
The system view is displayed.
Run ospfv3 [ process-id ]
The OSPFv3 view is displayed.
Run default { cost costvalue | tag tagvalue | type typevalue } ^*
The default cost is set for imported routes.
Run import-route { bgp [ permit-ibgp ] | direct | static | unr } [ { cost cost | inherit-cost } | tag tag | type type | { route-policy route-policy-name | route-filter route-filter-name } ] ^*
External routes are imported.

The import-route command cannot be used to import the default route from another AS.
(Optional) Run import-route limit limit-number [ threshold-alarm { upper-limit upper-limit-value | lower-limit lower-limit-value } ^* ]
A limit is configured on the number of LSAs generated when an OSPFv3 process imports external routes.

If OSPFv3 imports a large number of external routes and advertises them to a device with a smaller routing table capacity, the device may restart unexpectedly. To address this problem, run the import-route limit command to configure a limit on the number of LSAs generated when an OSPFv3 process imports external routes.

Ensure that upper-limit-value is greater than or equal to lower-limit-value.
Run commit
The configuration is committed.