Configuring OSPFv3 to Import External Routes
If not only OSPFv3, but also other routing protocols or OSPFv3 in other processes run on all FW, you can configure OSPFv3 to import the routes generated by other routing protocols, and advertise these routes using LSA.
Context
OSPFv3 is a routing protocol based on link status, the advertised LSAs cannot be filtered directly. Therefore, LSAs can only be filtered when OSPFv3 imports routes, and only the routes matching the conditions can be changed into LSAs and advertised.
Procedure
- Access the system view.
- Access the OSPFv3 process view.
ospfv3 [ process-id ]
- Import the default cost value of the route.
default { cost cost | tag tag | type type } *
By default, the cost value is 1, the tag value is 1, and the type value is Type2 for imported external routes.
- Import the external route.
import-route protocol [ process-id ] [ { cost cost | inherit-cost } | type type | tag tag | route-policy route-policy-name ] *
- cost: Indicates the cost of the imported route. The value is an integer ranging from 0 to 16777214.
- type: Indicates the type of the imported route. The value is 1 or 2.
- (Optional) Import IBGP routes in OSPFv3 process.
import-route bgp [ permit-ibgp ] [ { cost cost | inherit-cost } | type type | tag tag | route-policy route-policy-name ] *
Importing IBGP routes in OSPFv3 process can lead to routing loops.
- (Optional) Advertise default routes to the OSPFv3 route
area.
default-route-advertise [ always | cost cost | type type | tag tag | route-policy route-policy-name [ match-any ] ] *
- (Optional) Filter the imported external routing information.
filter-policy { acl6-number | ipv6-prefix ipv6-prefix-name } export [ protocol [ process-id ] ]
If the import-route command is executed on the OSPFv3 router to import external routing information, the OSPFv3 router turns into the ASBR.
You can specify parameter protocol to filter the routing information of a certain type. If parameter protocol is not specified, all the imported routing information of OSPFv3 is filtered.
The filter-policy export command only takes effect when the import-route command is executed on the local device to import routes (that is, when the local OSPFv3 router turns into the ASBR). The device filters the routes when OSPF imports them. The routes filtered out cannot be turned into LSAs and advertised by OSPF. If the import-route command is not executed to import external routes (including the OSPFv3 routes of different processes), the filter-policy export command is invalid.