To guide traffic forwarding in SRv6 scenarios, OSPFv3 can be configured to advertise a locator route.
Currently, only IS-IS can be used to implement SRv6 BE. In scenarios that use OSPFv3 on the public network (for example, an SRv6 BE scenario), OSPFv3 needs to be configured to advertise a locator route. After this is configured, OSPFv3 can advertise intra-area LSAs carrying information about the IPv6 prefix configured for the locator, and deliver the route with this IPv6 prefix to the local routing table to guide traffic forwarding.
The system view is displayed.
SRv6 is enabled.
An SRv6 locator is configured.
Exit the SRv6 locator view.
Exit the SRv6 view.
The OSPFv3 process view is displayed.
A router ID is configured.
This router ID must be unique in an AS. The common practice is to select the IP address of an interface on the device as the router ID.
The router ID for each OSPFv3 process must be unique across the whole network. Otherwise, an OSPFv3 neighbor relationship cannot be established, and routing information is incorrect. You are advised to set a network-wide unique router ID for each OSPFv3 process on an OSPFv3 device.
OSPFv3 is enabled to advertise the locator route.
The configuration is committed.
Run the display ospfv3 [ process-id ] routing verbose command in any view to check information about an OSPFv3 routing table.