In a VPN Option A scenario, disabling DN bit setting in OSPFv3 LSAs allows PEs in different ASs to communicate with each other.
Figure 1 shows a VPN Option A scenario where an OSPFv3 neighbor relationship is established between ASBR1 and ASBR2. Each of the ASBRs imports BGP routes from the connected PE to the OSPFv3 process, generates LSAs, and advertises the LSAs to the peer ASBR. The ASBRs, however, cannot use the received LSAs to generate OSPFv3 routes. This is because LSAs with the DN bit set cannot be used for route calculation, as defined in a standard protocol. Consequently, no OSPFv3 routes will be imported into BGP processes on the ASBRs, and no BGP routes will be advertised to the connected PEs, causing traffic loss. To prevent this issue, you can disable DN bit checking in OSPFv3 LSAs on both the ASBRs, allowing them to use the received LSAs to calculate routes as normal.
The system view is displayed.
An OSPFv3 process bound to the existing VPN instance is started, and the view of the OSPFv3 process is displayed.
An OSPFv3 process can be bound to only one VPN instance. If an OSPFv3 process is not bound to any VPN instance before being started, this process is a public network process. The public network OSPFv3 process cannot be bound to a VPN instance.
Deleting a VPN instance or disabling the IPv6 address family in the VPN instance will delete all the associated OSPFv3 processes.
A router ID is configured.
A router ID uniquely identifies an OSPFv3 process in an AS. If no router ID is configured, the OSPFv3 process cannot run.
OSPFv3 is enabled to import BGP routes.
The OSPFv3 device is disabled from setting the DN bit in LSAs.
The configuration is committed.