280
Configuring an OSPFv3 virtual link
You can configure a virtual link to maintain connectivity between a non-backbone area and the
backbone, or in the backbone itself.
IMPORTANT:
•
Both ends of a virtual link are ABRs that must be configured with the
vlink-peer
command.
•
Do not configure virtual links in the areas of a GR-capable process.
To configure a virtual link:
Step Command
1.
Enter system view.
system-view
2.
Enter OSPFv3 view.
ospfv3
[
process-id
]
3.
Enter OSPFv3 area view.
area
area-id
4.
Configure a virtual link.
vlink-peer
router-id
[
hello
seconds
|
retransmit
seconds
|
trans-delay
seconds
|
dead
seconds
|
instance
instance-id
] *
Configuring OSPFv3 network types
OSPFv3 classifies networks into the following types by the link layer protocol.
By default, the default OSPFv3 interface network types vary with the link layer protocols of the interfaces:
•
When the link layer protocol is PPP, OSPFv3 considers the network type as P2P by default.
•
When the link layer protocol is Ethernet, OSPFv3 considers the network type as broadcast by
default.
You can change the network type of an OSPFv3 interface as needed. For example:
•
An NBMA network must be fully connected. Any two routers in the network must be directly
reachable to each other through a virtual circuit. If no such direct link is available, you must change
the network type through a command.
•
If direct connections are not available between some routers in an NBMA network, the type of
interfaces associated must be configured as P2MP, or as P2P for interfaces with only one neighbor.
Configuration prerequisites
Before you configure OSPFv3 network types, complete the following tasks:
•
Configure IPv6 functions.
•
Configure OSPFv3 basic functions.
Configuring the OSPFv3 network type for an interface
Step Command
Remarks
1.
Enter system view.
system-view
N/A
