Configuring OSPFv3 to Import External Routes

Context

Because OSPFv3 is a link-state routing protocol and cannot filter advertised LSAs directly, it must filter routes when importing them. After filtering, only the routes that pass the filtering criteria are advertised.

Perform the following operations on the switch that runs OSPFv3.

Procedure

Run system-view

The system view is displayed.
Run ospfv3 [ process-id ]

The OSPFv3 view is displayed.
Run default { cost cost | tag tag | type type }^*

Default parameters are set for imported routes.
Run import-route { bgp [ permit-ibgp ] | unr | direct | ripng help-process-id | static | isis help-process-id | ospfv3 help-process-id } [ { cost cost | inherit-cost } | type type | tag tag | route-policy route-policy-name ]^*

External routes are imported.

Importing IBGP routes in an OSPFv3 process may lead to routing loops.

After the import-route command is executed on an OSPFv3 switch to import external routes, the switch becomes an ASBR.
(Optional) Run default-route-advertise [ always | cost cost | type type | tag tag | route-policy route-policy-name ]^*

Default routes are advertised to the OSPFv3 routing area.
(Optional) Run filter-policy { acl6-number | acl6-name acl6-name | ipv6-prefix ipv6-prefix-name } export [ protocol [ process-id ] ]

Imported external routes are filtered.

To filter a certain type of route, you must specify protocol. Otherwise, OSPFv3 filters all imported routes.

The filter-policy command takes effect only for the routes imported by an ASBR using the import-route command. The ASBR filters routes when importing the routes. The routes that are filtered out do not generate LSAs and cannot be advertised by OSPFv3. If the import-route command is not run to import other external routes (including OSPFv3 routes in different processes), the filter-policy command does not take effect.