www.howtonetwork.org

CCNA & CCNP Certifcation Training

  • About
  • Contact
  • FAQ
  • Join
  • Home
  • CCNA
    • ICND1
    • ICND2
    • 101 CCNA LABS
  • CCNP
    • ROUTE
    • SWITCH
    • TSHOOT
    • 101 CCNP LABS
  • CompTIA
    • Security+
    • Network+
  • Design
    • CCDA
    • CCDP
You are here: Home / ROUTE / Module 3 / OSPF – OSPF Virtual Links

OSPF – OSPF Virtual Links

A virtual link is a logical extension of the OSPF backbone. As we learned earlier in this chapter, when implementing a multi-area OSPF network, one area must be designated as the backbone area and all non-backbone areas must be connected to the backbone area. In most cases, a physical link is used to connect the non-backbone area to the backbone area; however, this is not always possible or feasible. In addition to being used to connect areas that have no physical connection to the OSPF backbone, virtual links can also be used for redundancy as well as connecting a discontinuous or partitioned backbone.

Connecting to the Backbone

In multi-area OSPF networks, virtual links are primarily used to connect disconnected non-backbone areas to the backbone. Consider the topology illustrated in Figure 3-23:

3-23

 

Fig. 3-23. Connecting to the Backbone

Figure 3-23 shows a multi-area OSPF network comprised of three areas, which are area 0, area 1 and area 2. Area 1 is physically connected to the backbone; however, area 2 is not. Given the OSPF requirement that all non-backbone areas must be connected to the backbone, a virtual link is required to logically connect area 2 to the backbone. There are two conditions that must be met before the virtual link is configured. These conditions are:

  • One area must be connected to the backbone area before the virtual link can be created
  • The transit area must be a common area between the two endpoint routers

Because a virtual link is a logical extension of area 0, the area across which the virtual link is configured must be connected to the backbone as well. If that area was not connected to the backbone, then it too would require a virtual link to connect it to the backbone. The second condition is that the area across which the virtual link traverses (the transit area) must be a common area between the two endpoints of the virtual link. In other words, if R3 and R6 resided in different areas, then the virtual link could not be configured between the two endpoints. This would apply even if R6 was in an area that was connected to the backbone.

The simplest way of remembering what a virtual link is to simply think of it as just a tunnel between two endpoints that joins disconnected areas to the backbone. As a matter of fact, virtual links do operate in a tunnel-like manner, as will be described shortly.
Referencing Figure 3-23, the virtual vink across the transit area (area 1) would be configured between R3 and R6. R3 is the ABR connected to the backbone and R6 is the router that is connected to the disconnected area (area 2). It is important to understand that until the virtual link is established, R4 is not considered an ABR. Before we move ahead, it is important to take a moment to understand this statement.

Recall, at the beginning of this chapter, we learned that an ABR is an OSPF router that connects one or more OSPF areas to the OSPF backbone. This means that it must have at least one interface in area 0 and another interface, or interfaces, within a different OSPF area. Based on this definition, even though R6 is connected to both area 1 and area 2, it is technically not an ABR because it has no interfaces in the backbone area.

Because R6 is not an ABR it cannot generate Type 3 LSAs for the intra-area, i.e. the Type 1 and Type 2, routes in either area and flood those to the adjacent areas as inter-area, i.e. Type 3 LSAs. Given this, area 1 and area 0 are oblivious of area 2 and vice-versa as areas 1 and 0 have no inter-area routes for area 2 and area 2 has no inter-area routes for areas 1 and 0. At this point, the OSPF network is considered broken and these different areas cannot communicate.

When the virtual vink is established between R3 and R6, area 0 is extended to R6. Once R6 has this logical connection to the backbone, it considers itself an ABR. R6 therefore generates Type 3 LSAs for all areas it is connected to and floods them to adjacent areas. Areas 0, 1, and 2 now have inter-area routes for all other areas and all subnets in all networks have full connectivity between each other. The network is no longer broken and connectivity is complete restored.

When a virtual link is established, OSPF uses Unicast, not Multicast to send routing updates between the virtual link endpoints. For example, referencing Figure 3-23, routing updates across the virtual link from R3 to R6 would be tunneled across the virtual link and be sourced from the FastEthernet0/0 interface of R3, which has the IP address 10.1.1.3, and would have a destination address of 10.1.1.6, which is the FastEthernet0/0 interface of R6.

realworldReal World Implementation 

When configuring virtual links in production networks, if there is a firewall in the transit area, it is important to ensure that the firewall rules are configured to allow traffic between the two Virtual Link endpoints. In most cases, simply allowing IP protocol 89 (OSPF) between the two endpoint addresses will suffice; however, depending on the firewall type, more configuration may be required. Make sure you remember this, as it can save you a lot of troubleshooting and heartache in the real world.

While routing protocol updates are tunneled, it is important to know that normal traffic is not tunneled and is not subject to any tunneling overhead. This is the primary advantage of using Virtual Links. The configuration of virtual links in Cisco IOS software is a straightforward process. This is performed using the area [transit area] virtual-link [router-id] [hello-interval <seconds>] [retransmit-interval <seconds>] [transmit-delay <seconds>] [dead-interval <seconds>] [ttl-security hops <hop-count>] router configuration command on the ABR and the router connected to the disconnected area.

When using the area…virtual-link router configuration command, the transit area refers to the common transit area that the Virtual Link will traverse. Referencing the topology illustrated in Figure 3-23, the transit area would be area 1.

The router-id specifies the router ID of the end of the virtual link. This address is the actual OSPF RID as seen in the output of the show ip protocols or any of the show ip ospf commands and not the interface address of the remote endpoint. The specified router ID does not have to reachable as the virtual link packets are tunneled using the physical interface addresses as source and destination addresses in the routing protocol updates. Because intra-area routes exist for these interfaces already, the router ID does not have to be reachable.

As an example, even if the router ID was configured using the router-id <address> router configuration command, the same value should be used when configuring the virtual link between the routers. If you use the interface address, the Virtual Link will not be established between the routers. This is often a point of confusion. Ensure that you remember when you are configuring virtual links in Cisco IOS software.

The hello-interval <seconds> keyword can be used to specify a Hello interval for the Virtual Link endpoints. This value must match on both routers. If this keyword is not used, OSPF will send Hello packets across the virtual link every ten (10) seconds by default.

The retransmit-interval <seconds> keyword is used to specify the time between Link State Advertisement (LSA) retransmissions and the transmit-delay <seconds>keyword specifies the estimated time seconds) required to send a link-state update packet on the interface. These advanced configurations are beyond the scope of the ROUTE exam and are not illustrated in the following configuration examples.

The dead-interval <seconds> keyword specifies the time after which the neighbor is declared down if a Hello packet has not been received in the value specified. If this is configured, it must be the same on all routers. If not, it defaults to four times the Hello interval, which is forty (40) seconds. The timer automatically changes when the Hello time is changed.

The ttl-security hops <hop-count> keyword configures Time-to-Live (TTL) security on a virtual link. TTL security is used to configure a TTL value for incoming IP packets received from the neighbor. The implementation of this virtual link configuration is beyond the scope of the ROUTE exam and is not illustrated in the following configuration examples.

To reinforce the virtual link fundamentals, the topology illustrated in Figure 3-24 will be used to demonstrate both the configuration and validation of virtual links.

3-24

Fig. 3-24. Configuring Virtual Links

Assuming that OSPF has been correctly configured on all routers, we will begin by looking at the contents of the Link State Databases on all routers included in the topology. The LSDB on R1 shows the intra-area routes for area 0 and the inter-area routes for area 1, which were flooded into the area by the ABR (R2):

R1#show ip ospf databaseOSPF Router with ID (1.1.1.1) (Process ID 1)Router Link States (Area 0)

Link ID         ADV Router      Age         Seq#       Checksum Link count
1.1.1.1         1.1.1.1         384         0x80000001 0x0096AC 4
2.2.2.2         2.2.2.2         384         0x80000003 0x00185F 2

Summary Net Link States (Area 0)

Link ID         ADV Router      Age         Seq#       Checksum
2.2.2.2         2.2.2.2         419         0x80000001 0x00FA31
3.3.3.3         2.2.2.2         370         0x80000001 0x00D650
10.0.1.0        2.2.2.2         374         0x80000003 0x00C561

The LSDB on R2 shows the intra-area routes for area 0 as well as the inter-area routes, which R2 flooded into the area. We can also see the intra-area routes for area 1, as well as the inter-area (area 0) routes that R2 has flooded into area 1.

R2#show ip ospf databaseOSPF Router with ID (2.2.2.2) (Process ID 2)Router Link States (Area 0)

Link ID         ADV Router      Age         Seq#       Checksum Link count
1.1.1.1         1.1.1.1         506         0x80000001 0x0096AC 4
2.2.2.2         2.2.2.2         505         0x80000003 0x00185F 2

Summary Net Link States (Area 0)

Link ID         ADV Router      Age         Seq#       Checksum
2.2.2.2         2.2.2.2         540         0x80000001 0x00FA31
3.3.3.3         2.2.2.2         490         0x80000001 0x00D650
10.0.1.0        2.2.2.2         494         0x80000003 0x00C561

Router Link States (Area 1)

Link ID         ADV Router      Age         Seq#       Checksum Link count
2.2.2.2         2.2.2.2         500         0x80000002 0x006488 2
3.3.3.3         3.3.3.3         500         0x80000002 0x00518F 2

Net Link States (Area 1)

Link ID         ADV Router      Age         Seq#       Checksum
10.0.1.3        3.3.3.3         501         0x80000001 0x0064A7

Summary Net Link States (Area 1)

Link ID         ADV Router      Age         Seq#       Checksum
1.1.1.1         2.2.2.2         501         0x80000001 0x00AB44
10.0.0.0        2.2.2.2         547         0x80000001 0x004D9D
11.1.1.0        2.2.2.2         501         0x80000001 0x008D50

The LSDB on R3 shows the intra-area routes for area 1 as well as the inter-area routes, which R2 flooded into the area. We can also see the intra-area routes for area 1, as well as the inter-area (area 0) routes that R2 has flooded into area 1. In addition to this, the LSDB also shows the intra-area routes for area 2.

However, because R3 is not an ABR, i.e. has no connection to the backbone, it does not generate a flood Summary LSAs (inter-area) for these routes into area 1 nor can it generate a Summary LSA for the intra-area routes in area 2 and flood it into area 1. This means that neither R2 nor R1 is aware of area 2 and R4 is not aware of area 1 or area 0.

R3#show ip ospf databaseOSPF Router with ID (3.3.3.3) (Process ID 3)Router Link States (Area 1)

Link ID         ADV Router      Age         Seq#       Checksum Link count
2.2.2.2         2.2.2.2         736         0x80000002 0x006488 2
3.3.3.3         3.3.3.3         735         0x80000002 0x00518F 2

Net Link States (Area 1)

Link ID         ADV Router      Age         Seq#       Checksum
10.0.1.3        3.3.3.3         735         0x80000001 0x0064A7

Summary Net Link States (Area 1)

Link ID         ADV Router      Age         Seq#       Checksum
1.1.1.1         2.2.2.2         735         0x80000001 0x00AB44
10.0.0.0        2.2.2.2         780         0x80000001 0x004D9D
11.1.1.0        2.2.2.2         735         0x80000001 0x008D50

Router Link States (Area 2)

Link ID         ADV Router      Age         Seq#       Checksum Link count
3.3.3.3         3.3.3.3         815         0x80000003 0x0081DD 2
4.4.4.4         4.4.4.4         866         0x80000003 0x00B043 4

And finally, The LSDB on R4 shows only the intra-area routes in area 2 because there is no ABR to create and flood Summary LSAs into the area.

R4#show ip ospf databaseOSPF Router with ID (4.4.4.4) (Process ID 4)Router Link States (Area 2)

Link ID         ADV Router      Age         Seq#       Checksum Link count
3.3.3.3         3.3.3.3         1135        0x80000003 0x0081DD 2
4.4.4.4         4.4.4.4         1183        0x80000003 0x00B043 4

The configuration of the virtual link connecting area 2 to the backbone would be implemented on R2 and R3. This configuration would be performed as follows:

R2(config)#router ospf 2
R2(config-router)#area 1 virtual-link 3.3.3.3
R2(config-router)#exit

 

R3(config)#router ospf 3
R3(config-router)#area 1 virtual-link 2.2.2.2
R3(config-router)#exit

When the virtual link has been successfully configured, an adjacency is established between R2 and R3. This adjacency is similar to a typical OSPF adjacency and is included in the output of the show ip ospf neighborcommand as illustrated below:

R3#show ip ospf neighborNeighbor ID    Pri   State        Dead Time   Address     Interface
2.2.2.2          0   FULL/  –        –        10.0.1.2    OSPF_VL0
2.2.2.2          1   FULL/BDR     00:00:39    10.0.1.2    FastEthernet0/0
4.4.4.4          0   FULL/  –     00:00:35    10.0.2.4    Serial0/0

Adding the detail keyword to the show ip ospf neighbor command prints detailed information about the Virtual Link as illustrated in the output below:

R3#show ip ospf neighbor detail
Neighbor 2.2.2.2, interface address 10.0.1.2
In the area 0 via interface OSPF_VL0
Neighbor priority is 0, State is FULL, 6 state changes
DR is 0.0.0.0 BDR is 0.0.0.0
Options is 0x32 in Hello (E-bit L-bit DC-bit )
    Options is 0x72 in DBD (E-bit L-bit DC-bit O-bit)
LLS Options is 0x1 (LR)
Neighbor is up for 00:03:19
Index 1/3, retransmission queue length 0, number of retransmission 1
First 0x0(0)/0x0(0) Next 0x0(0)/0x0(0)
Last retransmission scan length is 1, maximum is 1
Last retransmission scan time is 0 msec, maximum is 0 msec

Referencing the sections in bold above, the output of the show ip ospf neighbor detail command for the Virtual Link includes the neighbor router ID and the interface address that will be used to source routing protocol packets. The state of the neighbor is also included in this output. This state should always be FULL.

The command also includes options included in the Hello and DBD packets for the virtual link. The different options in Hello and DBD packets were described earlier in this chapter. The Virtual Link Hello and DBD packets include the following options:

  • The DC bit, which indicates that it supports Demand Circuits mentioned in RFC 1793
  • The L bit, which indicates that it supports Link Local Signaling or LLS
  • The E Bit, which indicates that it supports External LSAs
  • The O Bit, which indicates that it supports Opaque LSAs mentioned in RFC 2370

Based on RFC 1793 demand circuits are defined as ‘network segments whose cost depends on either connect time and/or usage (expressed in terms of bytes or packets). Examples include ISDN circuits and X.25 SVCs.’ OSPF demand circuits have two main characteristics:

  • Periodic Hellos are suppressed
  • Periodic LSA refreshes are suppressed

The original school of thought that resulted in virtual links being considered demand circuits was because of the concern of the routing protocol overhead when virtual links were used across low-bandwidth links. The suppression of the period Hello packets and LSA refreshes was recommended to reduce this overhead.

When a link is configured as a demand circuit, period Hellos are suppressed only if it is a point-to-point or point-to-multipoint network types. However, Hellos are not suppressed for other network types. As stated earlier in this chapter, by default, OSPF re-floods all LSAs every 30 minutes (1800 seconds). When the virtual link is established, if the DC bit is supported by routers, the DoNotAge (DNA) is set in the LSA age, effectively preventing LSAs received across the demand circuit from being aged out.

NOTE: The Link State Age field states the time (in seconds) since the Link State Advertisement was originated. Within this field, the DNA bit is the most significant bit. When this bit is set, the LSA stops aging, and no periodic updates are sent. However, even for an OSPF demand circuit period refresh will occur when there is a change to the network topology. This exception is used to ensure the accuracy of routing information when Virtual Links are used.

The L bit indicates Link Local Signaling support. This is beyond the scope of the ROUTE exam and is not described in this guide. The E bit indicates External (Type 5) LSA support. In other words, External LSAs can also be flooded across the virtual link. The O bit indicates Opaque LSA support. Type 9, 10, and 11 LSAs are Opaque LSAs.

Type 9 Opaque LSAs have a link-local flooding scope and are not flooded beyond the local link or local network. Type 10 Opaque LSAs have an area flooding scope and are not flooded beyond their area. Type 11 Opaque LSAs are similar to Type 5 LSAs in that they have a domain flooding scope. In addition to this, these LSAs are not flooded into stub areas. Opaque LSAs allow for upgrades to OSPF for application-specific purposes and are included for the future extensibility of the protocol. Going into further detail on these LSAs is beyond the scope of the ROUTE exam. These LSAs will not be described in any further detail in this guide.

The show ip ospf virtual-links command can be used to view additional information about the Virtual Link. The output printed by this command is shown below:

R3#show ip ospf virtual-links
Virtual Link OSPF_VL0 to router 2.2.2.2 is up
Run as demand circuit
  DoNotAge LSA allowed.
Transit area 1, via interface FastEthernet0/0, Cost of using 1
Transmit Delay is 1 sec, State POINT_TO_POINT,
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Hello due in 00:00:06
Adjacency State FULL (Hello suppressed)
Index 1/3, retransmission queue length 0, number of retransmission 1
First 0x0(0)/0x0(0) Next 0x0(0)/0x0(0)
Last retransmission scan length is 1, maximum is 1
Last retransmission scan time is 0 msec, maximum is 0 msec

Referencing the sections in bold above, the output of the show ip ospf virtual-links command shows that the virtual link is configured as a demand circuit. This means periodic Hellos and LSA refreshes are suppressed across the virtual link and the DNA bit is set in the Link State Age field for all LSAs received across the virtual link. This can be validated by looking at the LSDB on the ABR (R3) as shown below:

R3#show ip ospf databaseOSPF Router with ID (3.3.3.3) (Process ID 3)Router Link States (Area 0)

Link ID         ADV Router      Age         Seq#       Checksum Link count
1.1.1.1         1.1.1.1         1285  (DNA) 0x80000001 0x0096AC 4
2.2.2.2         2.2.2.2         1     (DNA) 0x80000004 0x00EF5B 3
3.3.3.3         3.3.3.3         1003        0x80000004 0x000CF2 1

Summary Net Link States (Area 0)

Link ID         ADV Router      Age         Seq#       Checksum
2.2.2.2         2.2.2.2         1320  (DNA) 0x80000001 0x00FA31
2.2.2.2         3.3.3.3         1003        0x80000003 0x00E242
3.3.3.3         2.2.2.2         1269  (DNA) 0x80000001 0x00D650
3.3.3.3         3.3.3.3         1003        0x80000003 0x00AA77
4.4.4.4         3.3.3.3         1003        0x80000003 0x00FEDE
10.0.1.0        2.2.2.2         1274  (DNA) 0x80000003 0x00C561
10.0.1.0        3.3.3.3         1003        0x80000003 0x00A77B
10.0.2.0        3.3.3.3         1003        0x80000003 0x0015CD
44.4.4.0        3.3.3.3         1003        0x80000003 0x001D9C

Router Link States (Area 1)

Link ID         ADV Router      Age         Seq#       Checksum Link count
2.2.2.2         2.2.2.2         188         0x80000005 0x005E8B 2
3.3.3.3         3.3.3.3         1005        0x80000006 0x00587F 2

Net Link States (Area 1)

Link ID         ADV Router      Age         Seq#       Checksum
10.0.1.3        3.3.3.3         249         0x80000004 0x005EAA

Summary Net Link States (Area 1)

Link ID         ADV Router      Age         Seq#       Checksum
1.1.1.1         2.2.2.2         190         0x80000004 0x00A547
4.4.4.4         2.2.2.2         951         0x80000003 0x0027B9
4.4.4.4         3.3.3.3         1005        0x80000003 0x00FEDE
10.0.0.0        2.2.2.2         190         0x80000004 0x0047A0
10.0.2.0        2.2.2.2         951         0x80000003 0x003DA8
10.0.2.0        3.3.3.3         1005        0x80000003 0x0015CD
11.1.1.0        2.2.2.2         190         0x80000004 0x008753
44.4.4.0        2.2.2.2         951         0x80000003 0x004577
44.4.4.0        3.3.3.3         1005        0x80000003 0x001D9C

Router Link States (Area 2)

Link ID         ADV Router      Age         Seq#       Checksum Link count
3.3.3.3         3.3.3.3         1005        0x80000006 0x007EDC 2
4.4.4.4         4.4.4.4         311         0x80000006 0x00AA46 4

                Summary Net Link States (Area 2)

Link ID         ADV Router      Age         Seq#       Checksum
1.1.1.1         3.3.3.3         1008        0x80000003 0x009355
2.2.2.2         3.3.3.3         1008        0x80000003 0x00E242
3.3.3.3         3.3.3.3         1008        0x80000003 0x00AA77
10.0.0.0        3.3.3.3         1008        0x80000003 0x0035AE
10.0.1.0        3.3.3.3         1008        0x80000003 0x00A77B
11.1.1.0        3.3.3.3         1008        0x80000003 0x007561

In the output above, following the establishment of the virtual link, R3 now has intra-area and inter-area routes for area 0. Only the LSAs received across the virtual link will have the DNA bit set. The LSAs generated and flooded to adjacent areas by R3 will not. This is illustrated in the output below:

R3#show ip ospf database summary 2.2.2.2OSPF Router with ID (3.3.3.3) (Process ID 3)Summary Net Link States (Area 0)

LS age: 1320 (DoNotAge)
Options: (No TOS-capability, DC, Upward)
LS Type: Summary Links(Network)
  Link State ID: 2.2.2.2 (summary Network Number)
  Advertising Router: 2.2.2.2
LS Seq Number: 80000001
Checksum: 0xFA31
Length: 28
Network Mask: /32
TOS: 0  Metric: 1

LS age: 898
Options: (No TOS-capability, DC, Upward)
LS Type: Summary Links(Network)
  Link State ID: 2.2.2.2 (summary Network Number)
  Advertising Router: 3.3.3.3
LS Seq Number: 80000003
Checksum: 0xE242
Length: 28
Network Mask: /32
TOS: 0  Metric: 2

Going back to the output of the show ip ospf virtual-links command, the transit area is also printed, including the interface used to reach the remote endpoint and the cost of the Virtual Link. This is the cumulative cost between the local router and the remote endpoint. In the topology illustrated in Figure 3-24, R2 and R3 are connected via a FastEthernet link. If additional routers were in the path between these two endpoints, the Virtual Link cost value would reflect the cumulative metric between the two endpoints.

And finally, the last bolded section in the output of the show ip ospf virtual-links command shows that the adjacency state is FULL and Hello packets are being suppressed, which is the default for demand circuits.

Going back to the topology used in the virtual link configuration example, R4 now has both intra-area and inter-area routes in its Link State Database. The inter-area (Type 3) routes are flooded into the area by the ABR (R3) as illustrated in the following output:

R4#show ip ospf databaseOSPF Router with ID (4.4.4.4) (Process ID 4)Router Link States (Area 2)

Link ID         ADV Router      Age         Seq#       Checksum Link count
3.3.3.3         3.3.3.3         1633        0x80000006 0x007EDC 2
4.4.4.4         4.4.4.4         934         0x80000006 0x00AA46 4

                Summary Net Link States (Area 2)

Link ID         ADV Router      Age         Seq#       Checksum
1.1.1.1         3.3.3.3         1633        0x80000003 0x009355
2.2.2.2         3.3.3.3         1633        0x80000003 0x00E242
3.3.3.3         3.3.3.3         1633        0x80000003 0x00AA77
10.0.0.0        3.3.3.3         1633        0x80000003 0x0035AE
10.0.1.0        3.3.3.3         1633        0x80000003 0x00A77B
11.1.1.0        3.3.3.3         1633        0x80000003 0x007561

NOTE: Connectivity to other routers can be performed using a simple ping as follows:

R4#ping 1.1.1.1Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/4 ms

While virtual links provide a flexible way of connecting disconnected areas to the backbone, the major disadvantage to using them is that they cannot be configured over stub areas. If the transit area is configured as a stub area, then a tunnel must be used instead of a virtual link. Again referencing the topology illustrated in Figure 3-24, if area 1 was a stub area, a tunnel must be configured between R2 and R3.

The tunnel is configured in a similar manner to a physical interface. This tunnel interface must then be placed into area 0 using either the ip ospf [process ID] area 0 interface configuration command or the network x.x.x.x y.y.y.y area 0 router configuration command. Tunnel interface configuration is described in detail later in this guide.

Using Virtual Links for Redundancy

In addition to being used to connect disconnected areas to the backbone, virtual links may also be used to provide redundancy. Consider the network illustrated in Figure 3-25:

3-25

Fig. 3-25. Using Virtual Links for Redundancy

Figure 3-25 illustrates a basic multi-area OSPF network. R1 and R2 are connected to area 0 and to routers R3 and R5 in areas 1 and 2, respectively. R4 is connected to area 1 and area 2. Although virtual links would not be required in this implementation, they can be configured to provide redundancy in the event that area 1 or area 2 lost its connection to the backbone. Figure 3-26 illustrates how the OSPF network would be broken if the connection between R3 and R1, for example, was removed due to a link or other failure:

3-26

Fig. 3-26. Using Virtual Links for Redundancy

Following the failure of the link between R1 and R3, as illustrated in Figure 3-26, area 1 will no longer be connected to the backbone. The same would be applicable to area 2 if the connection between R2 and R5 failed. In this case, virtual links can be configured ahead of time to ensure that these areas have a connection to the backbone in the event of a link failure. The virtual link would be configured between R1 and R4 and between R2 and R4 for areas 1 and 2 respectively.

In addition to being used for redundant connectivity for non-backbone areas, virtual links can also be configured to provide redundancy in the event of a link failure that would result in the backbone area being portioned or disconnected. This is illustrated in Figure 3-27:

3-27

Fig. 3-27. Using Virtual Links for Redundancy

Referencing the network diagram in Figure 3-27, a link failure between R1 and R2 would result in the breakup or partitioning of the OSPF backbone. While a partitioned backbone is allowed when implementing multi-area OSPF, the two separate backbones must be connected using a virtual link. To avoid the portioning of the backbone in the network in Figure 3-26, a virtual link would be configured between R1 and R2, using area 1 as the transit area. This allows normal OSPF operation in the event of the failure of the link or connection between R1 and R2.

Connecting Partitioned Backbones

A partitioned backbone is an OSPF backbone that has been split in two. This is similar to what would happen in the event of a link failure between R1 and R2 in Figure 3-27. Sometimes, a portioned backbone is necessary to connect two different OSPF networks. These two OSPF networks may need to be joined together following an acquisition or merger, for example as illustrated in Figure 3-28:

3-28

Fig. 3-28. Connecting Partitioned Backbones

In Figure 3-28, two companies have recently merged and are in the process of integrating their networks. The two companies are using OSPF as the IGP of choice. To merge the two OSPF networks, a common area would need to be configured between the two backbone areas belonging to each individual area. A virtual link would then be configured across this common area to join the two backbone areas.

Following virtual link implementation rules, the transit area between the two networks should not be configured as a stub area. If it must be configured as a stub area, a tunnel would need to be used instead of a virtual link. In addition to connecting the two backbones, general design verifications such as ensuring there are no overlapping areas or IP address space would also be undertaken. These issues cannot be resolved simply by implementing a virtual link.

There are some significant differences in the operation of virtual links and tunnels that you should remember when choosing when to use one over the other when connecting disconnected areas to the backbone or connecting a portioned backbone. These differences are listed in Table 3-4:

Characteristic When using a Tunnel When using a Virtual Link
OSPF Network Type Defaults to point-to-point Defaults to point-to-point
Demand Circuit No Yes
DoNotAge Bit Set No Yes
Hellos Suppressed No Yes
Routing Updates Tunneled between endpoints Tunneled between endpoints
Normal User Data Tunneled between endpoints Not tunneled; sent natively
Cost (Metric) Based on Tunnel bandwidth Cumulative between endpoints
Can transit Stub area Yes No

Tab. 3-3. Comparing Virtual Links and Tunnels

Prev

Next

About Us

This is a free bonus site for members of www.howtonetwork.com

Copyright

The content on this copyright Reality Press Ltd.
Copyright Reality Press Ltd.