17 mins read

OSPF Virtual Link

1. Intro

For backbone areas only, create a virtual link to use in place of an actual physical link. All area border routers and other routing devices on the backbone must be contiguous. If this is not possible and there is a break in OSPF connectivity, use virtual links to create connectivity to the OSPF backbone. When configuring virtual links, you must configure links on the two routing devices that form the end points of the link, and both of these routing devices must be area border routers.

You cannot configure links through stub areas.

2. OSPF Initial Topology

We will modify a little the topology so that R2 is not directly connected to Area 0, as follows:

Let’s check the config on R1 and R2.

Same as in the diagram, R2 is in Area 5, it has a session to R1 (Area 1), but no neighbors to Area 0.

This has an impact on the OSPF database and the routing table. Area 5 and Area 0 can’t see each other:

We can see the same in the routing table. To be explicit:

  • we are missing R3, R4, R5, … (and so on) loopbacks
  • we are missing the 10.1.x.x, 10.2.x.x and 10.3.x.x routes
  • Even if we have the LSA in the OSPF database, we are even missing the External routes 2.2.x.x, 3.3.x.x, 4.4.x.x routes

Same on R3, we are missing R2 loopback and 10.1.2.x, 10.1.3.x routes:

3. OSPF Virtual Link configuration:

First we must already have a router-id, which we have: set routing-options router-id 17.0.0.x.

We will configure a virtual link from R1 (Area 5 ABR) to R3 (Area 0 ABR).

Now we can see that we have an OSPF neighborship on the virtual link:

And finally the OSPF database and routing table now are ok:


External Resources: