Lab-7- Implement Multi-Area OSPFv2

Name: _____________

Name:_____________

Name:_____________

Name:_____________

Name:_____________

Lab-7- Implement Multi-Area OSPFv2

Lab-7- Implement Multi-Area OSPFv2

Topology

Gig0/0 Gig0/1

Gig0/0
Gig0/0

Gig0/1 Gig0/1

FA0/11 FA0/11
Lab-7- Implement Multi-Area OSPFv2

Objectives
Part 1: Configure Basic Device Settings and Verify Connectivity
Part 2: Configure Multiarea OSPFv2
Part 3: Explore Link State Advertisements (LSAs)

Background / Scenario
To make dynamic routing more efficient and scalable, OSPF supports hierarchical routing using areas.
An OSPF area is a group of routers that share the same link-state information in their link-state databases (LSDBs).
When a large OSPF area is divided into smaller areas, it is called multiarea OSPF. Multi-area OSPF is useful in
larger network deployments to reduce processing and memory overhead.
In this lab you will configure multiarea OSPFv2 for IPv4.
Note: This lab is an exercise in developing, deploying, and verifying how OSPF operates and does not reflect networking
best practices.
Note: Loopback interfaces are used to simulate user networks and therefore require the ip ospf network point-
to-point interface config command.

Instructions

Part 1: Configure Basic Device Settings and Verify Connectivity

In Part 1, you will set up the network topology.

Step 1: Configure basic settings on R1, R2, R3, S1, and S2.

a. On each device, apply the following basic settings and interface addressing.

Router R1
hostname YOURNAME-R1
line con 0
logging sync
exec-time 0 0
!
interface GigabitEthernet0/0
description Link to R2
ip add 172.16.0.2 255.255.255.252
no shut
exit
!
interface GigabitEthernet0/1
description Link to S1
ip address 10.10.0.1 255.255.255.252
no shut
exit
!
line vty 0 4
privilege level 15
password cisco
login
transport input all
Lab-7- Implement Multi-Area OSPFv2

Router R2
hostname YOURNAME-R2
!
interface GigabitEthernet0/0
description Link to R1
ip add 172.16.0.1 255.255.255.252
no shut
exit
!
interface GigabitEthernet0/1
description Link to R3
ip address 172.16.1.1 255.255.255.252
no shut
exit
!
interface lo0
description Link to Internet
ip add 209.165.200.225 255.255.255.224
exit
!

line vty 0 4
privilege level 15
password cisco
login
transport input all
!
line con 0
logging sync
exec-time 0 0
exit

Router R3
hostname YOURNAME-R3
line con 0
logging sync
exec-time 0 0
exit
!
interface GigabitEthernet0/0
description Link to R2
ip add 172.16.1.2 255.255.255.252
no shut
exit
!
interface GigabitEthernet0/1
description Link to S2
ip address 10.10.4.1 255.255.255.252
no shut
exit
!
line vty 0 4
privilege level 15
password cisco
login
Lab-7- Implement Multi-Area OSPFv2

transport input all

Switch S1
hostname YOURNAME-S1
line con 0
exec-timeout 0 0
logging synchronous
!
interface fa0/11
description Link to R1
no switchport
ip address 10.10.0.2 255.255.255.252
no shut
exit
!
interface Lo0
description Simulates a LAN
ip address 10.10.1.1 255.255.255.0
ip ospf network point-to-point
exit
!
int Lo2
description Simulates a LAN
ip add 10.10.2.1 255.255.255.0
ip ospf network point-to-point
exit
!
int Lo3
description Simulates a LAN
ip add 10.10.3.1 255.255.255.0
ip ospf network point-to-point
exit
!
line vty 0 4
privilege level 15
password cisco
login
transport input all

Switch S2
hostname YOURNAME-S2
line con 0
logging sync
exec-time 0 0
!
interface fa0/11
description Link to R3
no switchport
ip address 10.10.4.2 255.255.255.252
no shut
exit
!
int Lo0
description Simulates a LAN
ip address 10.10.5.1 255.255.255.0
ip ospf network point-to-point
exit
Lab-7- Implement Multi-Area OSPFv2

!
int Lo16
description Simulates a LAN
ip add 10.10.16.1 255.255.255.0
ip ospf network point-to-point
exit
!
int Lo17
description Simulates a LAN
ip add 10.10.17.1 255.255.255.0
ip ospf network point-to-point
exit
!
int Lo18
description Simulates a LAN
ip add 10.10.18.1 255.255.255.0
ip ospf network point-to-point
exit
!
int Lo19
description Simulates a LAN
ip add 10.10.19.1 255.255.255.0
ip ospf network point-to-point
exit
!
int Lo20
description Simulates a LAN
ip add 10.10.20.1 255.255.255.0
ip ospf network point-to-point
exit
!
int Lo21
description Simulates a LAN
ip add 10.10.21.1 255.255.255.0
ip ospf network point-to-point
exit
!
int Lo22
description Simulates a LAN
ip add 10.10.22.1 255.255.255.0
ip ospf network point-to-point
exit
!
int Lo23
description Simulates a LAN
ip add 10.10.23.1 255.255.255.0
ip ospf network point-to-point
exit
!
line vty 0 4
privilege level 15
password cisco
login
transport input all
Lab-7- Implement Multi-Area OSPFv2

Step 2: Verify interfaces and direct connectivity between R1, R2, R3, S1, and S2.
a. On S1, verify the status of the configured interfaces.
S1#show ip int brief | include manual
FastEthernet0/11 10.10.0.2 YES manual up up
Loopback0 10.10.1.1 YES manual up up
Loopback2 10.10.2.1 YES manual up up
Loopback3 10.10.3.1 YES manual up up
S1#

Notice the loopback interfaces configured on S1. Theses interfaces were configured for lab purposes to simulate other
LANs.
Note: Loopback interfaces were numbered based on the network address (e.g., Lo2 = 10.10.2.0/24) for convenience
only.

b. On R1, R2, and R3, verify the status of the configured interfaces.
R1# show ip int brief | include manual
GigabitEthernet0/0 172.16.0.2 YES manual up up
GigabitEthernet0/1 10.10.0.1 YES manual up up
R1#

R2# show ip int brief | include manual

GigabitEthernet0/0 172.16.0.1 YES manual up up
GigabitEthernet0/1 172.16.1.1 YES manual up up
Loopback0 209.165.200.225 YES manual up up
R2#

R3# show ip int brief | include manual

GigabitEthernet0/1 10.10.4.1 YES manual up up
GigabitEthernet0/0 172.16.1.2 YES manual up up
R3#

c. On S2, verify the status of the configured interfaces.

S2# show ip int brief | include manual
FastEthernet0/11 10.10.4.2 YES manual up up
Loopback0 10.10.5.1 YES manual up up
Loopback16 10.10.16.1 YES manual up up
Loopback17 10.10.17.1 YES manual up up
Loopback18 10.10.18.1 YES manual up up
Loopback19 10.10.19.1 YES manual up up
Loopback20 10.10.20.1 YES manual up up
Loopback21 10.10.21.1 YES manual up up
Loopback22 10.10.22.1 YES manual up up
Loopback23 10.10.23.1 YES manual up up
S2#

Again, notice the loopback interfaces configured on S2. Theses interfaces were configured for lab purposes to
simulate other LANs.
Lab-7- Implement Multi-Area OSPFv2

d. On S1, verify direct connectivity with R1.

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

e. On R1, verify direct connectivity with R2.

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

f. On R2, verify direct connectivity with R3.

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

g. On R3, verify direct connectivity with S2.

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

All devices should be able to reach the other directly connected networks. Troubleshoot if necessary.
Lab-7- Implement Multi-Area OSPFv2

Part 2: Configure Multiarea OSPFv2

In this part, you will implement multiarea OSPF. Multi-area OSPF defines a two-layer area hierarchy using a backbone
area interconnecting regular areas. This is useful in larger network deployments to reduce processing and memory
overhead.
In this topology, OSPF has the following three areas defined:
 Area 0 – The backbone area. All regular areas should connect to the backbone area.
 Area 1 and Area 2 – Regular OSPF areas that connect to the backbone area. The
routers and switches in the topology are used in the following roles:
 Internal routers - R2 is an internal router in Area 0, S1 in Area 1, and S2 in Area 2.
 Backbone routers - R1, R2, and R3 are backbone routers as they all have interfaces in Area 0.
 Area Border routers (ABRs) – R1 and R3 are ABRs because they connect regular areas to Area 0.
 Autonomous System Boundary router (ASBR) – R2 is an ASBR as it connects to a non-OSPF net.
Recall that OSPF can be enabled using the traditional network router configuration command or by using the
ip ospf process-id area area-id interface configuration command. In this lab, we will implement multi-area OSPF
using wildcard masks.
You will now configure multiarea OSPF on all five devices starting with S1. You will also configure router IDs, reference
bandwidths, and default route propagation.
Note: The verification output displayed in the following part assumes that the devices have been configured in the
prescribed order. The output will vary if all devices are configured simultaneously.

Step 1: Implement OSPF on S1 using wildcard masks.

S1 will advertise its OSPF networks using the network router configuration command and wildcard masks. S1 is an
internal router in Area 1. Therefore, both network commands will be configured for Area 1.
On S1, configure:
 Enable IP routing
 OSPF process ID: 123
 Set the RID: 1.1.1.2
 Set the reference bandwidth to accommodate 1 Gbps links.
 Advertise the directly connected interfaces (i.e., Fa0/11 and the 3 loopbacks) using wildcards masks.

a. On S1, enable IP routing as shown.

S1(config)#ip routing
S1(config)#

b. On S1, enter OSPF router configuration mode using process ID 123, assign S1 the router ID 1.1.1.2, and set the
reference bandwidth to distinguish between Gigabit Ethernet and FastEthernet interfaces.
S1(config)#router ospf 123
S1(config-router)#router-id 1.1.1.2
S1(config-router)#auto-cost reference-bandwidth 1000
% OSPF: Reference bandwidth is changed.
Please ensure reference bandwidth is consistent across all routers.
Note: The reference bandwidth must be configured the same on all routers in the OSPF area.
Lab-7- Implement Multi-Area OSPFv2

c. On S1, advertise the FastEthernet 0/11 interface 10.10.0.0/30 network in OSPF Area 1 as shown.
Note: Deduct the subnet mask (i.e., /30 = 255.255.255.252) from 255.255.255.255, resulting in a wildcard mask of
0.0.0.3.
S1(config-router)#network 10.10.0.0 0.0.0.3 area 1
S1(config-router)#

d. On S1, advertise the Lo0 interface 10.10.1.0/24 network in OSPF Area 1 as shown.
S1(config-router)#network 10.10.1.0 0.0.0.255 area 1
S1(config-router)#end

e. On S1, advertise the Lo2 interface 10.10.2.0/24 and 10.10.3.0/24 networks in OSPF Area 1 as shown.
Note: Deduct the subnet mask (i.e., /23 = 255.255.254.0) from 255.255.255.255, resulting in a wildcard mask of
0.0.1.255.
S1(config-router)#network 10.10.2.0 0.0.1.255 area 1
S1(config-router)#end

f. On S1, verify the OSPF protocol settings using the show ip protocols command.
S1# show ip protocols | section ospf
Routing Protocol is "ospf 123"
Outgoing update filter list for all interfaces is not
set Incoming update filter list for all interfaces is
not set Router ID 1.1.1.2
Number of areas in this router is 1. 1 normal 0 stub 0
nssa Maximum path: 4
Routing for Networks:
10.10.0.0 0.0.0.3 area
1
10.10.1.0 0.0.0.255 area 1
10.10.2.0 0.0.1.255 area 1
Routing Information Sources:
Gateway Distance Last Update
Distance: (default is 110)

The output confirms the RID, the number of areas, and the networks advertised. Notice there are no Routing
Information Sources because there are no OSPF neighbors.

g. On S1, verify the OSPF interfaces using the show ip ospf interface brief command.
S1#show ip ospf interface brief
Interface PID Area IP Address/Mask Cost State Nbrs F/C
Lo0 123 1 10.10.1.1/24 1 P2P 0/0
Lo2 123 1 10.10.2.1/24 1 P2P 0/0
Lo3 123 1 10.10.3.1/24 1 P2P 0/0
Fa0/11 123 1 10.10.0.2/30 1 DR 1/1
S1#

The output confirms that both Fa0/11 and Loopback interfaces were correctly assigned to Area 1.
Lab-7- Implement Multi-Area OSPFv2

Step 2: Implement OSPF on R1.

Next, configure R1. R1 is an ABR with an interface in Area 1 and the other interface in the backbone. On R1,
configure:
 OSPF process ID: 123
 Set the RID: 1.1.1.1
 Set the reference bandwidth to accommodate 1 Gbps links.
 Advertise the G0/0 network (172.16.0.0/30) in Area 0 and the G0/1 network (10.10.0.0/30) in Area 1

a. On R1, configure OSPF as specified.

R1(config)#router ospf 123
R1(config-router)#router-id 1.1.1.1
R1(config-router)#auto-cost reference-bandwidth 1000
% OSPF: Reference bandwidth is changed.
Please ensure reference bandwidth is consistent across all routers.
R1(config-router)#
R1(config-router)#network 172.16.0.0 0.0.0.3 area 0
R1(config-router)#
R1(config-router)#network 10.10.0.0 0.0.0.3 area 1
R1(config-router)#end
Feb 15 10:21:48.411: %OSPF-5-ADJCHG: Process 123, Nbr 1.1.1.2 on
GigabitEthernet0/1 from LOADING to FULL, Loading
Done R1(config-router)#
Notice the informational message stating that a neighbor adjacency has been established with S1.

b. On R1, verify the OSPF configuration using the show ip protocols command.
R1# show ip protocols | begin ospf
Routing Protocol is "ospf 123"
Outgoing update filter list for all interfaces is not
set Incoming update filter list for all interfaces is
not set Router ID 1.1.1.1
It is an area border router
Number of areas in this router is 2. 2 normal 0 stub 0
nssa Maximum path: 4
Routing for Networks:
10.10.0.0 0.0.0.3 area
1
172.16.0.0 0.0.0.3 area 0
Routing Information Sources:
Gateway Distance Last Update
1.1.1.2 110 00:07:55
Distance: (default is 110)

Like the previous output of S1, this output confirms the router ID, and the networks advertised. However, notice
that it also explicitly states that R1 is an area border router (ABR), that it is in two areas, and that it has established
an adjacency and exchanged routing information with S2 (i.e., 1.1.1.2).
Lab-7- Implement Multi-Area OSPFv2

c. On R1, verify that the reference bandwidth has been changed using the show ip ospf | begin Ref
command.
R1#show ip ospf | begin Ref
Reference bandwidth unit is 1000
mbps Area BACKBONE(0) (Inactive)
Number of interfaces in this area is 1
Area has no authentication
SPF algorithm last executed 00:10:51.448 ago
SPF algorithm executed 3 times
Area ranges are
Number of LSA 3. Checksum Sum 0x019F16
Number of opaque link LSA 0. Checksum Sum 0x000000
Number of DCbitless LSA 0
Number of indication LSA
0 Number of DoNotAge LSA
0 Flood list length 0
Area 1
Number of interfaces in this area is 1
Area has no authentication

<Output omitted>

R1#

The output confirms that the reference bandwidth has been changed to distinguish GigabitEthernet interfaces. The
output also confirms that R1 is in two areas and has two link-state databases (LSDBs).
Note: Area 0 is currently inactive because there are no other peers configured.

d. On R1, verify the active OSPF interfaces using the show ip ospf interface brief command.
R1#show ip ospf interface brief
Interface PID Area IP Address/Mask Cost State Nbrs F/C
Gi0/0 123 0 172.16.0.2/30 1 DR 0/0
Gi0/1 123 1 10.10.0.1/30 1 BDR 1/1
R1#

The output confirms the interfaces, areas, and IP addresses.

Note: This lab is not concerned with DR/BDR elections therefore do not worry if the relationships do not match the
output.

e. On R1, verify which OSPF neighbors R1 has established an adjacency with using the show ip ospf
neighbor command.
R1#show ip ospf neighbor

Neighbor ID Pri State Dead Time Address Interface

1.1.1.2 1 FULL/DR 00:00:35 10.10.0.2 GigabitEthernet0/1
R1#

The output confirms that R1 has one neighbor (i.e., 1.1.1.2 = S1), they have a full adjacency established, the IP
address of S1 is 10.10.0.2, and R1 can reach S1 using its G0/1 interface.
Lab-7- Implement Multi-Area OSPFv2

f. On R1, use the show ip ospf neighbor detail command to get additional neighbor information.
R1# show ip ospf neighbor detail
Neighbor 1.1.1.2, interface address 10.10.0.2
In the area 1 via interface GigabitEthernet0/1
Neighbor priority is 1, State is FULL, 6 state changes
DR is 10.10.0.2 BDR is 10.10.0.1
Options is 0x12 in Hello (E-bit, L-bit)
Options is 0x52 in DBD (E-bit, L-bit, O-bit)
LLS Options is 0x1 (LR)
Dead timer due in 00:00:38
Neighbor is up for
00:16:37
Index 1/1/1, retransmission queue length 0, number of retransmission
0 First 0x0(0)/0x0(0)/0x0(0) Next 0x0(0)/0x0(0)/0x0(0)
Last retransmission scan length is 0, maximum is 0
Last retransmission scan time is 0 msec, maximum is 0 msec
R1#

As shown, the output confirms various information about the OSPF neighbor including DR and BDR status.

g. On R1, verify the OSPF routes in the routing table using the show ip route ospf command.
R1#show ip route ospf | begin Gateway
Gateway of last resort is not set

10.0.0.0/8 is variably subnetted, 3 subnets, 3 masks

O 10.10.1.0/24 [110/2] via 10.10.0.2, 00:24:43, GigabitEthernet0/1
O 10.10.2.0/24 [110/2] via 10.10.0.2, 00:07:59, GigabitEthernet0/1
O 10.10.3.0/24 [110/2] via 10.10.0.2, 00:07:59, GigabitEthernet0/1

The output displays entries for the S1 LANs. The O designation identifies these as OSPF internal routes.
Network routes learned from other OSPF routers in the same area are known as intra-area routes and are
identified in the IP routing table with an O.

h. On R1, get detailed information about the OSPF entry using the show ip route ospf 10.10.1.0 command.
R1#show ip route 10.10.1.0
Routing entry for 10.10.1.0/24
Known via "ospf 123", distance 110, metric 2, type intra area
Last update from 10.10.0.2 on GigabitEthernet0/1, 00:25:25
ago Routing Descriptor Blocks:
* 10.10.0.2, from 1.1.1.2, 00:25:25 ago, via GigabitEthernet0/1
Route metric is 11, traffic share count is 1

The output confirms that R1 learned about the intra-area route 10.10.1.0 from 10.10.0.2 with a router ID
of 1.1.1.2 in OSPF 123.
Lab-7- Implement Multi-Area OSPFv2

Step 3: Implement OSPF on R2.

Next, configure is R2. R2 is an internal backbone router and will become an ASBR. On R2,
configure:
 OSPF process ID: 123
 Set the RID: 2.2.2.1
 Set the reference bandwidth to accommodate 1 Gbps links.
 Advertise G0/0 (172.16.0.0/30) and G0/1 (172.16.1.0/30) in Area 0.

a. On R2, configure the OSPF settings as specified.

R2(config)#router ospf 123
R2(config-router)#router-id 2.2.2.1
R2(config-router)#auto-cost reference-bandwidth 1000
% OSPF: Reference bandwidth is changed.
Please ensure reference bandwidth is consistent across all routers.
R2(config-router)#
R2(config-router)#network 172.16.0.0 0.0.0.3 area 0
R2(config-router)#network 172.16.1.0 0.0.0.3 area 0
Feb 15 09:43:06.687: %OSPF-5-ADJCHG: Process 123, Nbr 1.1.1.1 on
GigabitEthernet0/0 from LOADING to FULL, Loading Done
R2(config-router)#
The output confirms that an adjacency has been established with R1 (i.e., 1.1.1.1).

b. On R2, propagate a default route to the internet. In our lab, Lo0 represents the internet.
R2(config-router)#default-information originate
R2(config-router)#exit
R2(config)#
R2(config)#ip route 0.0.0.0 0.0.0.0 lo0
%Default route without gateway, if not a point-to-point interface, may
impact performance
R2(config)# exit
R2#
Lab-7- Implement Multi-Area OSPFv2

c. On R2, verify the OSPF configuration using the show ip protocols command.
R2#show ip protocols | begin ospf
Routing Protocol is "ospf 123"
Outgoing update filter list for all interfaces is not
set Incoming update filter list for all interfaces is
not set Router ID 2.2.2.1
It is an autonomous system boundary
router Redistributing External Routes
from,
Number of areas in this router is 1. 1 normal 0 stub 0
nssa Maximum path: 4
Routing for Networks:
172.16.0.0 0.0.0.3 area 0
172.16.1.0 0.0.0.3 area 0
Routing Information Sources:
Gateway Distance Last Update
1.1.1.1 110 00:24:29
Distance: (default is 110)

Again, this output confirms the router ID chosen, number of areas R2 is in (i.e., 1), networks advertised, and that it
has established an adjacency and exchanged routing information with R1 (i.e., 1.1.1.1). R2 does not have an
adjacency with S1 because it is in another area.
Notice as well, that it explicitly states that R2 is an autonomous system boundary router (ASBR). This is because it is
now propagating a default route to all other routers in the OSPF domain.

d. On R2, verify that the reference bandwidth has been changed as shown.
R2#show ip ospf | begin Ref
Reference bandwidth unit is 1000
mbps Area BACKBONE(0)
Number of interfaces in this area is 2
Area has no authentication
SPF algorithm last executed 00:02:27.531 ago
SPF algorithm executed 5 times

<Output omitted>

The output confirms that the reference bandwidth has been changed and also confirms that R2 has two interfaces in its
link-state database (LSDB).

e. On R2, verify the active OSPF interfaces and assigned areas using the show ip ospf interface brief
command.
R2#show ip ospf interface brief
Interface PID Area IP Address/Mask Cost State Nbrs F/C
Gi0/1 123 0 172.16.1.1/30 1 DR 0/0
Gi0/0 123 0 172.16.0.1/30 1 BDR 1/1

The output confirms that the two interfaces are in Area 0, their IP addresses, state, and neighbors.
Lab-7- Implement Multi-Area OSPFv2

f. On R2, verify which OSPF neighbors have established an adjacency as shown

R2#show ip ospf neighbor

Neighbor ID Pri State Dead Time Address Interface

1.1.1.1 1 FULL/DR 00:00:36 172.16.0.2 GigabitEthernet0/0

The output confirms that R2 has one fully adjacent neighbor (i.e., 1.1.1.1 = R1).

g. On R2, use the show ip ospf neighbor detail command for more neighbor information.
R2#show ip ospf neigh detail
Neighbor 1.1.1.1, interface address 172.16.0.2, interface-id
5 In the area 0 via interface GigabitEthernet0/0
Neighbor priority is 1, State is FULL, 6 state changes
DR is 172.16.0.2 BDR is 172.16.0.1
Options is 0x12 in Hello (E-bit, L-bit)
<Output omitted>

The output confirms various information about the OSPF neighbor including DR and BDR status.

h. On R2, verify the OSPF routes in the routing table using the show ip route ospf command.
R2#show ip route ospf | begin Gateway

Gateway of last resort is 0.0.0.0 to network 0.0.0.0

10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks

O IA 10.10.0.0/30 [110/2] via 172.16.0.2, 00:28:19, GigabitEthernet0/0
O IA 10.10.1.0/24 [110/12] via 172.16.0.2, 00:28:19, GigabitEthernet0/0
O IA 10.10.2.0/24 [110/3] via 172.16.0.2, 00:10:02, GigabitEthernet0/0
O IA 10.10.3.0/24 [110/3] via 172.16.0.2, 00:10:02, GigabitEthernet0/0

The output displays that there is now a default gateway and two entries for the OSPF Area 1 networks. Notice how
these routes are identified as O IA which means they are routes from another area. Network routes learned from
OSPF routers in another area using an ABR are known as interarea routes as opposed to intra-area routes.

i. On R2, verify the static route entry in the routing table.

R2#show ip route static | begin Gateway
Gateway of last resort is 0.0.0.0 to network

0.0.0.0 S* 0.0.0.0/0 is directly connected,

Loopback0
Lab-7- Implement Multi-Area OSPFv2

Step 4: Implement OSPF on R3.

Next to configure is R3. Like R1, R3 is an ABR with an interface in Area 0 and one in Area 2. On R3,
configure:
 OSPF process ID: 123
 Set the RID: 3.3.3.1
 Set the reference bandwidth to accommodate 1 Gbps links.
 Advertise G0/1 (172.16.1.0/30) and G0/1 (10.10.4.0/30) in Area 2.

a. On R3, configure the OSPF settings as specified.

R3(config)#router ospf 123
R3(config-router)#router-id 3.3.3.1
R3(config-router)#auto-cost reference-bandwidth 1000
R3(config-router)#network 172.16.1.0 0.0.0.3 area 0
R3(config-router)#network 10.10.4.0 0.0.0.3 area 2
R3(config-router)#end
Feb 15 10:16:35.971: %OSPF-5-ADJCHG: Process 123, Nbr 2.2.2.1 on
GigabitEthernet0/2 from LOADING to FULL, Loading Done

b. On R3, verify the active OSPF interfaces using the show ip ospf interface brief command.
R3#show ip ospf interface brief
Interface PID Area IP Address/Mask Cost State Nbrs F/C
Gi0/0 123 0 172.16.1.2/30 10 BDR 1/1
Gi0/1 123 2 10.10.4.1/30 1 DR 0/0

The output confirms the interfaces, process ID, areas, IP addresses, cost, state, and neighbors.

c. On R3, verify the OSPF routes in the routing table using the show ip route ospf command.
R3#show ip route ospf | begin Gateway
Gateway of last resort is 172.16.1.1 to network 0.0.0.0

O*E2 0.0.0.0/0 [110/1] via 172.16.1.1, 00:03:22, GigabitEthernet0/0

10.0.0.0/8 is variably subnetted, 4 subnets, 3 masks
O IA 10.10.0.0/30 [110/12] via 172.16.1.1, 00:03:22, GigabitEthernet0/0
O IA 10.10.1.0/24 [110/13] via 172.16.1.1, 00:03:22,
GigabitEthernet0/0
O IA 10.10.2.0/24 [110/13] via 172.16.1.1, 00:11:59,
GigabitEthernet0/0
O IA 10.10.3.0/24 [110/13] via 172.16.1.1, 00:11:59, GigabitEthernet0/0
172.16.0.0/16 is variably subnetted, 3 subnets, 2 masks
O 172.16.0.0/30 [110/11] via 172.16.1.1, 00:03:22, GigabitEthernet0/0
R3#

The output verifies that R3 has received a default route from R2, 4 interarea routes (i.e., O IA routes) and one intra-
area OSPF route (i.e., O routes). The O*E2 route indicates that this is an external route that did not originate
in OSPF. The asterisk identifies this as a candidate default route.
Lab-7- Implement Multi-Area OSPFv2

Step 5: Implement OSPF on S2.

Last to configure is S2. Like S1, S2 is an internal router in Area 2. On S2, configure:
 Enable IP routing
 OSPF process ID: 123
 Set the RID: 3.3.3.2
 Set the reference bandwidth to accommodate 1 Gbps links.
 Advertise the G0/11 network (10.10.4.0/30) and the G0/1 network (10.10.0.0/30) in Area 2
 Advertise the 10.10.16.0 – 10.10.23.0 Loopbacks

a. On S2, configure the OSPF settings as specified.

S2(config)#ip routing
S2(config)#router ospf 123
S2(config-router)#router-id 3.3.3.2
S2(config-router)#auto-cost reference-bandwidth 1000
S2(config-router)#network 10.10.4.0 0.0.0.3 area 2
S2(config-router)#network 10.10.5.0 0.0.0.255 area 2
S2(config-router)#
Feb 15 10:35:39.877: %OSPF-5-ADJCHG: Process 123, Nbr 3.3.3.1 on
GigabitEthernet0/11 from LOADING to FULL, Loading Done

b. On S2, summarize the 10.10.16.0 – 10.10.23.0 networks as 10.10.16.0/19 configure an accommodating network
statement as shown.
S2(config-router)#network 10.10.16.0 0.0.7.255 area 2
S2(config-router)#end

c. On S2, verify the OSPF configuration on S2 using the show ip protocols command.
S2#show ip protocols | begin ospf
Routing Protocol is "ospf 123"
Outgoing update filter list for all interfaces is not
set Incoming update filter list for all interfaces is
not set Router ID 3.3.3.2
Number of areas in this router is 1. 1 normal 0 stub 0
nssa Maximum path: 4
Routing for Networks:
10.10.4.0 0.0.0.3 area 2
10.10.5.0 0.0.0.255 area 2
10.10.16.0 0.0.7.255 area
2 Routing Information
Sources:
Gateway Distance Last Update
3.3.3.1 110 00:00:41
2.2.2.1 110 00:00:42
Distance: (default is 110)

S2#
Lab-7- Implement Multi-Area OSPFv2

As expected, we can verify the router ID, number of areas, networks being advertised, and routing sources.
It may be surprising that R2 (i.e., 2.2.2.1) is displayed as a routing source. The reason is because it is the
source of the default route.

d. On S2, verify the active OSPF interfaces and assigned areas using the show ip ospf interface brief
command.
S2#show ip ospf int brief
Interface PID Area IP Address/Mask Cost State Nbrs F/C
Lo0 123 2 10.10.5.1/24 1 P2P 0/0
Lo16 123 2 10.10.16.1/24 1 P2P 0/0
Lo17 123 2 10.10.17.1/24 1 P2P 0/0
Lo18 123 2 10.10.18.1/24 1 P2P 0/0
Lo19 123 2 10.10.19.1/24 1 P2P 0/0
Lo20 123 2 10.10.20.1/24 1 P2P 0/0
Lo21 123 2 10.10.21.1/24 1 P2P 0/0
Lo22 123 2 10.10.22.1/24 1 P2P 0/0
Lo23 123 2 10.10.23.1/24 1 P2P 0/0
Fa0/11 123 2 10.10.4.2/30 1 BDR 1/1
S2#

The output confirms that all configured interfaces are in Area 2 and their IP addresses are correct.

e. On S2, verify adjacent OSPF neighbors using the show ip ospf neighbor command.
S2#show ip ospf neighbor
Neighbor ID Pri State Dead Time Address Interface
3.3.3.1 1 FULL/DR 00:00:37 10.10.4.1 FastEthernet0/11
S2#

The output confirms that S2 has one fully-adjacent neighbor (i.e., 3.3.3.1= R3).

f. On S2, verify the OSPF routes using the show ip route ospf command.
S2#show ip route ospf
172.16.0.0/30 is subnetted, 2 subnets
O IA 172.16.0.0 [110/12] via 10.10.4.1, 00:06:45, FastEthernet0/11
O IA 172.16.1.0 [110/11] via 10.10.4.1, 00:06:45, FastEthernet0/11
10.0.0.0/8 is variably subnetted, 12 subnets, 2 masks
O IA 10.10.0.0/30 [110/13] via 10.10.4.1, 00:06:45, FastEthernet0/11
O IA 10.10.1.0/24 [110/14] via 10.10.4.1, 00:06:45, FastEthernet0/11
O IA 10.10.2.0/24 [110/14] via 10.10.4.1, 00:13:11, FastEthernet0/11
O IA 10.10.3.0/24 [110/14] via 10.10.4.1, 00:13:11, FastEthernet0/11
O*E2 0.0.0.0/0 [110/1] via 10.10.4.1, 00:06:45,
FastEthernet0/11 S2#

The output displays 6 interarea routes (i.e., O IA routes) and the OSPF external route from 2.2.2.1(R2).
Lab-7- Implement Multi-Area OSPFv2

Step 6: Verify end-to-end connectivity.

The multiarea OSPF network is now completely configured. We now need to verify the operation of OSPF.
a. On S1, verify the routing table for OSPF routes.

S1#show ip route ospf | begin Gate

Gateway of last resort is 10.10.0.1 to network 0.0.0.0

O*E2 0.0.0.0/0 [110/1] via 10.10.0.1, 01:07:58, FastEthernet0/11

10.0.0.0/8 is variably subnetted, 18 subnets, 3 masks
O IA 10.10.4.0/30 [110/13] via 10.10.0.1, 00:34:29, FastEthernet0/11
O IA 10.10.5.0/24 [110/14] via 10.10.0.1, 00:15:17, FastEthernet0/11
O IA 10.10.16.0/24 [110/14] via 10.10.0.1, 00:10:39, FastEthernet0/11
O IA 10.10.17.0/24 [110/14] via 10.10.0.1, 00:10:39, FastEthernet0/11
O IA 10.10.18.0/24 [110/14] via 10.10.0.1, 00:10:39, FastEthernet0/11
O IA 10.10.19.0/24 [110/14] via 10.10.0.1, 00:10:39, FastEthernet0/11
O IA 10.10.20.0/24 [110/14] via 10.10.0.1, 00:10:39, FastEthernet0/11
O IA 10.10.21.0/24 [110/14] via 10.10.0.1, 00:10:39, FastEthernet0/11
O IA 10.10.22.0/24 [110/14] via 10.10.0.1, 00:10:39, FastEthernet0/11
O IA 10.10.23.0/24 [110/14] via 10.10.0.1, 00:10:39, FastEthernet0/11
172.16.0.0/30 is subnetted, 2 subnets
O IA 172.16.0.0 [110/2] via 10.10.0.1, 01:14:50, FastEthernet0/11
O IA 172.16.1.0 [110/12] via 10.10.0.1, 01:08:03, FastEthernet0/11
S1#

b. On S1, do an extended ping to the 10.10.23.1 network using the IP address of Lo2 as shown.
S1#ping 10.10.23.1 source lo2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.10.23.1, timeout is 2
seconds: Packet sent with a source address of 10.10.2.1
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/3/8
ms S1#

This confirms end-to-end connectivity.

Lab-7- Implement Multi-Area OSPFv2

Part 3: Explore Link State Advertisements (LSAs)

In this part, you will verify that the network has converged and explore how link-state advertisements (LSAs) are used
as the building blocks for the OSPF link-state database (LSDB).
OSPF routers create LSAs for every directly connected OSPF-enabled interface. It then sends those LSAs to OSPF peers
to form adjacencies. Individually, LSAs are database records providing specific OSPF network details. Combined, they
describe the entire topology of an OSPF area.

OSPF routers uses 5 main LSA types for IPv4 routing:

 Type 1, router LSA – All OSPF-enabled routers create and send type 1 LSAs. The LSAs are immediately
propagated within the area. An ABR does not forward the LSA outside the area.
 Type 2, network LSA - Only a DR generates and advertises a type 2 LSA. The type 2 network LSA lists each of
the attached routers that make up the transit network, including the DR itself, and the subnet mask that is used on
the link. The DR floods the LSA to all OSPF routers (i.e., 224.0.0.5) on the multiaccess network. The content of
the displayed type 2 LSA describes the network segment listing the DR address, the attached routers, and the used
subnet mask. This information is used by each router participating in OSPF to build the exact picture of the
described multiaccess segment, which cannot be fully described with just type 1 LSAs.
 Type 3, summary LSA - ABRs do not forward type 1 or type 2 LSAs into other areas. ABRs flood type 3 LSAs
to propagate network information to other areas. Type 3 summary LSAs describe networks that are in an area to the
rest of the areas in the OSPF autonomous system.
 Type 4, ASBR summary LSA – When there is an ASBR in the OSPF domain, it advertises itself using a special
type 1 LSA. When an ABR receives this type 1 LSA, it builds a type 4 LSA to advertise the existence of the ASBR
and floods it to other areas. Subsequent ABRs regenerate a type 4 LSA and flood it into their areas.
 Type 5, AS external LSA – ASBRs generate a type 5 external LSAs to advertise external OSPF routes to the
OSPF domain. Type 5 LSAs are originated by the ASBR and are flooded to the entire autonomous system.
Note: Other LSAs also exist but are out of scope of this lab.
The focus will be on LSA types 1, 2, and 3 which are used to identify intra-area and interarea routes.

Step 1: Verifying OSPF and Exploring LSAs on S1.

S1 is an internal router and generates type 1 LSAs. It is also the DR on the link connecting to R1 and therefore
generates type 2 LSAs.
a. On S1, display the list of neighbors using the show ip ospf neighbors command.
S1# show ip ospf neighbor

Neighbor ID Pri State Dead Time Address Interface

1.1.1.1 1 FULL/BDR 00:00:32 10.10.0.1 FastEthernet0/11

The output confirms that R1 (i.e., 1.1.1.1) is a neighbor and is the BDR on the link. Therefore, S1 must be the DR.
Lab-7- Implement Multi-Area OSPFv2

b. On S1, verify the contents of the LSDB using the show ip ospf database command.
S1# show ip ospf database

OSPF Router with ID (1.1.1.2) (Process ID 123)

Router Link States (Area 1)

Link ID ADV Router Age Seq# Checksum Link count

1.1.1.1 1.1.1.1 793 0x80000006 0x0038C1 1
1.1.1.2 1.1.1.2 896 0x8000000A 0x00A3DA 4

Net Link States (Area 1)

Link ID ADV Router Age Seq# Checksum

10.10.0.2 1.1.1.2 896 0x80000004 0x00B263

Summary Net Link States (Area 1)

Link ID ADV Router Age Seq# Checksum

10.10.4.0 1.1.1.1 548 0x80000003 0x00A66F
10.10.5.0 1.1.1.1 1289 0x80000002 0x00B958
10.10.16.0 1.1.1.1 1047 0x80000002 0x0040C6
10.10.17.0 1.1.1.1 1047 0x80000002 0x0035D0
10.10.18.0 1.1.1.1 1047 0x80000002 0x002ADA
10.10.19.0 1.1.1.1 1047 0x80000002 0x001FE4
10.10.20.0 1.1.1.1 1047 0x80000002 0x0014EE
10.10.21.0 1.1.1.1 1047 0x80000002 0x0009F8
10.10.22.0 1.1.1.1 1047 0x80000002 0x00FD03
10.10.23.0 1.1.1.1 1047 0x80000002 0x00F20D
172.16.0.0 1.1.1.1 793 0x80000004 0x00D7A3
172.16.1.0 1.1.1.1 548 0x80000004 0x00313F

Summary ASB Link States (Area 1)

Link ID ADV Router Age Seq# Checksum

2.2.2.1 1.1.1.1 548 0x80000004 0x000F1E

Type-5 AS External Link States

Link ID ADV Router Age Seq# Checksum Tag

0.0.0.0 2.2.2.1 335 0x80000004 0x009B92 123
S1#
Lab-7- Implement Multi-Area OSPFv2

Notice how the command output is divided into the following five sections:
o Router Link States – These are the type 1 LSAs received by S1 and they identify the routers (i.e.,
1.1.1.1 = R1, 1.1.1.2 = S1) in Area 1 that sent them, and the number of links that the routers have in the area.
Therefore, R1 only has one interface in Area 1 and S1 has 4 interfaces in Area 1.
o Net Link States – These are the type 2 LSAs generated by the DR. In our example, the DR is 1.1.1.2 (i.e.,
S1) on the link 10.10.0.2.
o Summary Net Link States – These are the type 3 LSAs describing remote networks (i.e., our O IA
networks or interarea routes) and the router that advertised them to S1.
o Summary ASB Link States – This is a type 4 LSA sent by the ABR (i.e., 1.1.1.1 = R1) advertising that
there is an ASBR in the network (i.e., 2.2.2.1).
o Type-5 AS External Link States – This is a type 5 LSA advertising a default route (i.e., 0.0.0.0) and the
router that is advertising it (i.e., 2.2.2.1).

Additional information about the Router Link States type 1 LSA can be gathered using the following show ip ospf
database command.

Step 2: Verifying OSPF and exploring LSAs on an ABR R1.

a. On R1, verify the OSPF LSDB as shown.
Note: R1 is an ABR with interfaces in Area 1 and Area 0 and will therefore have two LSDBs.

R1# show ip ospf database

OSPF Router with ID (1.1.1.1) (Process ID 123)

Router Link States (Area 0)

Link ID ADV Router Age Seq# Checksum Link count

1.1.1.1 1.1.1.1 1118 0x80000007 0x002C7A 1
2.2.2.1 2.2.2.1 905 0x80000006 0x0065A5 2
3.3.3.1 3.3.3.1 918 0x80000004 0x00682B 1

Net Link States (Area 0)

Link ID ADV Router Age Seq# Checksum

172.16.0.2 1.1.1.1 1118 0x80000004 0x004824
172.16.1.1 2.2.2.1 905 0x80000003 0x006DF6

Summary Net Link States (Area 0)

Link ID ADV Router Age Seq# Checksum

10.10.0.0 1.1.1.1 1363 0x80000004 0x0062C1
10.10.1.0 1.1.1.1 1363 0x80000004 0x0073AB
10.10.2.0 1.1.1.1 121 0x80000002 0x006CB3
10.10.3.0 1.1.1.1 121 0x80000002 0x0061BD
10.10.4.0 3.3.3.1 918 0x80000003 0x000813
10.10.5.0 3.3.3.1 1931 0x80000002 0x001BFB
10.10.16.0 3.3.3.1 1682 0x80000002 0x00A16A
10.10.17.0 3.3.3.1 1682 0x80000002 0x009674
Lab-7- Implement Multi-Area OSPFv2

10.10.18.0 3.3.3.1 1682 0x80000002 0x008B7E

10.10.19.0 3.3.3.1 1682 0x80000002 0x008088
10.10.20.0 3.3.3.1 1682 0x80000002 0x007592
10.10.21.0 3.3.3.1 1682 0x80000002 0x006A9C
10.10.22.0 3.3.3.1 1682 0x80000002 0x005FA6
10.10.23.0 3.3.3.1 1682 0x80000002 0x0054B0

Router Link States (Area 1)

Link ID ADV Router Age Seq# Checksum Link count

1.1.1.1 1.1.1.1 1363 0x80000006 0x0038C1 1
1.1.1.2 1.1.1.2 1467 0x8000000A 0x00A3DA 4

Net Link States (Area 1)

Link ID ADV Router Age Seq# Checksum

10.10.0.2 1.1.1.2 1467 0x80000004 0x00B263

Summary Net Link States (Area 1)

Link ID ADV Router Age Seq# Checksum

10.10.4.0 1.1.1.1 1118 0x80000003 0x00A66F
10.10.5.0 1.1.1.1 1858 0x80000002 0x00B958
10.10.16.0 1.1.1.1 1617 0x80000002 0x0040C6
10.10.17.0 1.1.1.1 1617 0x80000002 0x0035D0
10.10.18.0 1.1.1.1 1617 0x80000002 0x002ADA
10.10.19.0 1.1.1.1 1617 0x80000002 0x001FE4
10.10.20.0 1.1.1.1 1617 0x80000002 0x0014EE
10.10.21.0 1.1.1.1 1617 0x80000002 0x0009F8
10.10.22.0 1.1.1.1 1617 0x80000002 0x00FD03
10.10.23.0 1.1.1.1 1617 0x80000002 0x00F20D
172.16.0.0 1.1.1.1 1363 0x80000004 0x00D7A3
172.16.1.0 1.1.1.1 1118 0x80000004 0x00313F

Summary ASB Link States (Area 1)

Link ID ADV Router Age Seq# Checksum

2.2.2.1 1.1.1.1 1118 0x80000004 0x000F1E

Type-5 AS External Link States

Link ID ADV Router Age Seq# Checksum Tag

0.0.0.0 2.2.2.1 905 0x80000004 0x009B92 123
R1#

The output displays the type 1, 2, and 3 LSAs in Area 0, and then lists the type 1, 2, 3, and 4 LSAs in Area 1. The
last section displays the type 5 LSAs
Lab-7- Implement Multi-Area OSPFv2

Part 4: Lab DEMO and lab document submission

1- Copy and paste a Screen Shot output from your Setup to the Table below and Demo it
to your Instructor

2- Submit your Lab document to BrighTSpace with names of your team members

Show or ping
Node command Paste a Screen shot from your setup below
S1
(2.5
points show ip
) protocols |
begin ospf

S1
(2.5
show ip ospf
points
interface brief
)

S1
show ip ospf
(2.5
points neighbor
)

show ip route
S1 ospf
(2.5
points
)