Knowing when and how to create an OSPF virtual link is an essential skill for BSCI and CCNP exam success, not to mention how important it can be on your job! As a CCNA and CCNP candidate, you know the theory of virtual links, so let’s take a look at how to configure a virtual link, as well as some real-world tips that many CCNA and CCNP study guides leave out!\nIn this configuration, no router with an interface in Area 4 has a physical interface in Area 0. This means a logical connection to Area 0, a virtual link, must be built.\nIn the following example, R1 and R3 are adjacent and both have interfaces in Area 0. R4 has an adjacency with R3 via Area 34, but R4 has no physical interface in Area 0 and is advertising its loopback 220.127.116.11 into OSPF. R1 doesn’t have the route to that loopback.\nR1#show ip route ospf\n18.104.22.168\/32 is subnetted, 1 subnets\nO 22.214.171.124 via 10.1.1.5, 01:05:45, Ethernet0\n172.23.0.0\/27 is subnetted, 1 subnets\nO IA 172.23.23.0 via 126.96.36.199, 00:04:14, Serial0\n188.8.131.52\/32 is subnetted, 1 subnets\nO 184.108.40.206 via 10.1.1.5, 01:05:45, Ethernet0\nTo resolve this, a virtual link will be built between R3 and R4 through Area 34. The area through which the virtual link is built, the transit area, cannot be a stub area of any kind.\nR4(config)#router ospf 1\nR4(config-router)#area 34 virtual-link 220.127.116.11\nR3(config)#router ospf 1\n2d07h: %OSPF-4-ERRRCV: Received invalid packet: mismatch area ID, from backbone area must be virtual-link but not found from 172.23.23.4, Ethernet0\nR3(config)#router ospf 1\nR3(config-router)#area 34 virtual-link 18.104.22.168\nR3(config-router)#^Z\n2d07h: %OSPF-5-ADJCHG: Process 1, Nbr 22.214.171.124 on OSPF_VL0 from LOADING to FULL, Loading Done\nA few details worth noting… the virtual link command uses the remote device’s RID, not necessarily the IP address on the interface that’s in the transit area. Also, don’t worry about that error message you see in the output from R3 that is normal and you’ll see it until you finish building the virtual link.\nAlways confirm the virtual link with show ip ospf virtual-link. If you’ve configured it correctly, the VL should come up in a matter of seconds.\nR3#show ip ospf virtual-link\nVirtual Link OSPF_VL0 to router 126.96.36.199 is up\nRun as demand circuit\nDoNotAge LSA allowed.\nTransit area 34, via interface Ethernet0, Cost of using 10\nTransmit Delay is 1 sec, State POINT_TO_POINT,\nTimer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5\nHello due in 00:00:00\nAdjacency State FULL (Hello suppressed)\nIndex 2\/4, retransmission queue length 1, number of retransmission 1\nFirst 0x2C8F8E(15)\/0x0(0) Next 0x2C8F8E(15)\/0x0(0)\nLast retransmission scan length is 1, maximum is 1\nLast retransmission scan time is 0 msec, maximum is 0 msec\nLink State retransmission due in 3044 msec\nVirtual links are actually simple to configure, but for some reason they seem to intimidate people. It’s my experience that the error message highlighted in R3’s output above causes a lot of panic, but the only thing that message means is that you’re not finished configuring the virtual link yet.\nThere are three main misconfigurations that cause 99% of virtual link configuration issues:\nUsing the wrong OSPF RID value\nTrying to use a stub area as the transit area\nFailure to configure link authentication on the virtual link when Area 0 is running authentication\nThat last one is the one that gets forgotten! A virtual link is really an extension of Area 0, and if Area 0 is running link authentication, the virtual link must be configured for it as well. Pay attention to the details. don’t panic when you see the error message on the second router you configure with the virtual link, and you’ll be ready for any virtual link situation on the job or in the CCNA \/ CCNP exam room!