Technical data
BLADE OS 5.1 Application Guide
BMD00136, November 2009 Chapter 11: OSPF
163
Example 2: Virtual Links
In the example shown in Figure 27, area 2 is not physically connected to the backbone as is usually
required. Instead, area 2 will be connected to the backbone via a virtual link through area 1. The
virtual link must be configured at each endpoint.
Figure 27 Configuring a Virtual Link
Configuring OSPF for a Virtual Link on Switch #1
1. Configure IP interfaces on each network that will be attached to the switch.
In this example, two IP interfaces are needed:
Interface 1 for the backbone network on 10.10.7.0/24
Interface 2 for the transit area network on 10.10.12.0/24
2. Configure the router ID.
A router ID is required when configuring virtual links. Later, when configuring the other end of the
virtual link on Switch 2, the router ID specified here will be used as the target virtual neighbor
(nbr) address.
Switch 2
Switch 2
Switch 1
Switch 1
>> # interface ip 1
>> (config-ip-if)# ip address 10.10.7.1
>> (config-ip-if)# ip netmask 255.255.255.0
>> (config-ip-if)# enable
>> (config-ip-if)# exit
>> # interface ip 2
>> (config-ip-if)# ip address 10.10.12.1
>> (config-ip-if)# ip netmask 255.255.255.0
>> (config-ip-if)# enable
>> (config-ip-if)# exit
>> # ip router-id 10.10.10.1