Configuring OSPFv3 Virtual Links
In certain cases, the direct physical connection between a backbone area and a non-backbone area can hardly be realized. Thus, you can configure virtual links for the ABR that is not directly connected to the backbone area. Virtual links are mainly used for redundancy backups. The other ends of virtual links also need corresponding configurations.
Context
Similar to OSPFv2, OSPFv3 defines that the route information of non-backbone areas must be transmitted through backbone areas. To configure OSPFv3, comply with the following principles:
- All non-backbone areas are connected with backbone areas.
- The connectivity of the backbone area must be kept.
In actual applications, the previous principles cannot be complied with due to various restrictions. In this case, you can solve this problem by configuring virtual links.
- Connecting an area to the backbone area through the non-backbone area
- Connecting to the segmented backbone area through the non-backbone area
To configure virtual links, comply with the following principles:
- Virtual links must be configured between two ABRs.
- The Transmit area cannot be the Stub area.
Procedure
- Access the system view.
- Access the OSPFv3 process view.
ospfv3 [ process-id ]
- Access the OSPFv3 area view.
area area-id
- Configure a virtual link.
vlink-peervlink-peer neighbor-id [ hello hello-interval | retransmit retransmit-interval | trans-delay trans-delay-interval | dead dead-interval | authentication-mode { hmac-sha256 key-id key-id { plain plain-text | [ cipher ] cipher-text } | keychain keychain-name } | instance instance-id ] *