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
Enter system view.
1.
Enter OSPFv3 view.
2.
Enter OSPFv3 area view.
3.
Configure a virtual link.
4.
Configuring OSPFv3 network types
OSPFv3 classifies networks into the following types by the link layer protocol:
By default, the 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 in the following cases:
•
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
Enter system view.
1.
Enter interface view.
2.
Configure a network type
3.
for the OSPFv3 interface.
Command
system-view
ospfv3 [ process-id ]
area area-id
vlink-peer router-id [ hello seconds | retransmit seconds |
trans-delay seconds | dead seconds | instance instance-id ]
*
Command
system-view
interface interface-type
interface-number
ospfv3 network-type
{ broadcast | nbma | p2mp
[ non-broadcast ] | p2p }
[ instance instance-id ]
273
Remarks
N/A
N/A
Optional.
The network type of an interface
depends on the media type of the
interface.