Example 2: Virtual Links; Configuring Ospf For A Virtual Link On Switch #1 - Lenovo ThinkSystem NE2552E Application Manual

Example 2: Virtual Links

Configuring OSPF for a Virtual Link on Switch #1

1. Configure IP interfaces on each network that will be attached to the switch.
2. Configure the router ID.
3. Enable OSPF.
4. Define the backbone.
© Copyright Lenovo 2018
In the example shown in Figure
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 46. Configuring a Virtual Link
Backbone
Application
Area 0
Switch 1
(0.0.0.0)
IF 1
10.10.7.1
Router ID:
10.10.7.0/24
10.10.10.1
Network
Note:
OSPFv2 supports IPv4 only. IPv6 is supported in OSPFv3 (see "OSPFv3
Implementation in Lenovo ENOS" on page
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

NE2552E(config)# interface ip 1
NE2552E(config-ip-if)# ip address 10.10.7.1 255.255.255.0 enable
NE2552E(config-ip-if)# exit
NE2552E(config)# interface ip 2
NE2552E(config-ip-if)# ip address 10.10.12.1 255.255.255.0 enable
NE2552E(config-ip-if)# exit
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.
NE2552E(config)# ip router-id 10.10.10.1
NE2552E(config)# router ospf
NE2552E(config-router-ospf)# enable
NE2552E(config-router-ospf)# area 0 area-id 0.0.0.0
NE2552E(config-router-ospf)# area 0 type transit
NE2552E(config-router-ospf)# area 0 enable
46, area 2 is not physically connected to the
Transit Area
Area 1
(0.0.0.1)
BladeCenter
IF 2 IF 1
10.10.12.1 10.10.12.2
Virtual Link 1
10.10.12.0/24
10.10.14.1
Network
413).
Stub Area
Area 2
Switch 2
(0.0.0.2)
IF 1
10.10.24.1
Router ID:
10.10.24.0/24
Network
Chapter 28: OSPF
407