Usage Scenario
After OSPF areas are defined, OSPF route updates between non-backbone areas are transmitted through a backbone area. Therefore, OSPF requires that all non-backbone areas maintain the connectivity with the backbone area and the backbone areas in different OSPF areas maintain the connectivity with each other. In real world situations, this requirement may not be met because of some restrictions. To resolve this problem, you can configure OSPF virtual links.
The display ospf vlink command displays OSPF virtual link information, which can help you troubleshoot OSPF virtual link faults.The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display ospf vlink OSPF Process 1 with Router ID 1.1.1.1 Virtual Links Virtual-link Neighbor-id -> 2.2.2.2, Neighbor-State: Full Interface: 10.1.1.1 (GigabitEthernet0/1/0) Cost: 1 State: P-2-P Type: Virtual Transit Area: 0.0.0.1 Timers: Hello 10 , Dead 40 , Retransmit 5 , Transmit Delay 1 GR State: Normal
Item | Description |
---|---|
Virtual-link Neighbor-id | ID of the neighboring router that is connected through the virtual link. |
Transit Area | Transit area ID if the current interface is a virtual link. |
GR State | GR status:
|
Neighbor-State | Neighbor status, such as Down, Init, 2-Way, ExStart, Exchange, Loading, and Full. |
Interface | Information about interfaces in the area, that is, IP address and name of the primary interface. |
Cost | Cost. |
State | Interface status. |
Type | Interface type. |
Timers | Interval for sending Hello messages, Dead time, polling interval (NBMA), retransmission interval, and transmission delay on the interface. |