Filter
Top Products
Alteon OS Application Guide
Chapter 12: OSPF
20742C4911, January 2007
Example 2: Virtual Links
In the example shown in Figure 12-6, 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 12-6 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 on Switch #1: one for the backbone network on
10.10.7.0/24 and one 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.
3. Enable OSPF.
>> # /cfg/l3/if 1 (Select menu for IP interface 1)
>> IP Interface 1 # addr 10.10.7.1 (Set IP address on backbone network)
>> IP Interface 1 # mask 255.255.255.0 (Set IP mask on backbone network)
>> IP Interface 1 # enable (Enable IP interface 1)
>> IP Interface 1 # ../if 2 (Select menu for IP interface 2)
>> IP Interface 2 # addr 10.10.12.1 (Set IP address on transit area network)
>> IP Interface 2 # mask 255.255.255.0 (Set IP mask on transit area network)
>> IP Interface 2 # enable (Enable interface 2)
>> IP Interface 2 # /cfg/l3/rtrid 10.10.10.1
(Set static router ID on switch 1)
>> IP # /cfg/l3/ospf/on (Enable OSPF on switch 1)
BladeCenter
BladeCenter
Application
Switch 1
Application
Switch 1
Switch 2
Switch 2