GNS3 - OSPF Lab - Part 4

This is the fourth and last of four labs devoted to GNS3 OSPF. In our previous labs we configured area 0,
area 10 with the redistribution of EIGRP and area 23, and created a virtual link area connecting area 30
to area 0. In this lab we will learn how to configure OSPF to run on a Frame Relay network we will use a
Hub & Spoke topology to implement the frame-relay network.

The problem:
OSPF is a powerful but strict protocol. Mainly used to set up a LAN or point-to-point, it appears much
more skittish about a Frame Relay network, especially in a hub and spoke topology.

OSPF on a Frame Relay interface by default, definins the interface as a "non-broadcast network," which
makes sense ... because Frame Relay is a NBMA network type (Non Broadcast Multiple Access). Where
things get complicated is when the following is included:

 On a Non-Broadcast network:
 OSPF does not establish adjacency dynamically
 OSPF attempts to elect a DR (Designated Router) and BDR (Backup Designated Router).

The election of a DR and a BDR works perfectly if you are on a full-mesh topology that acts like an
Ethernet LAN. Here we have a hub and spoke topology, so no PVC between all routers, which implies
that we have to force ABR4 (who has a connection to other routers) to be the DR and prevent the other
two become BDR.

To recap, the DR is the router that serves as a centralized updates for OSPF on a network share. Each
router sending its updates to DR and it makes then follow all routers in the network share.

Task:
1. Start with configuring the router Hub "ABR4".

a. First thing, the configuration of the bandwidth of the Serial 0/2 interface. It uses two
PVCs each with a CIR of 128kbit / s, so we will assign a bandwidth of 128kbps so that
COST (which is the same for both is calculated based on this value).

ABR4 (config) # s0 / 2 interface

ABR4 (config-if) # bandwidth 128
ABR4 (config-if) # exit
ABR4 (config) #

b. Then we must enable OSPF on Serial0 / 2 interface.

ABR4 (config) # router ospf 1

ABR4 (config-router) # network 172.16.40.0 0.0.0.255 area 40
ABR4 (config-router) #
 c. Since the adjacencies will not form dynamically, you must configure static neighbors (R2
and R3).

ABR4 (config-router) # neighbor 172.16.40.2

ABR4 (config-router) # neighbor 172.16.40.3
ABR4 (config-router) # exit

d. To ensure that the DR is ABR4 shared network, better increase its priority (default 1).

ABR4 (config) # int s0 / 2

ABR4 (config-if) # ip ospf priority 127
ABR4 (config-if) # exit

e. That should be enough to ABR4, go to R2 and R3.

2. Let R2. As well as for ABR4, we will need to configure static neighbor (ABR4). By cons, so that the
topology works well, we must ensure that it does not attempt to become DR or BDR. That is to
set its priority to 0.

R2 (config) # interface serial 0/0

R2 (config-if) # bandwidth 128
R2 (config-if) # ip os
R2 (config-if) # ip ospf pr
R2 (config-if) # ip ospf priority
R2 (config-if) # ip ospf priority 0
R2 (config-if) # exit
R2 (config) # router ospf 1
R2 (config-router) # router-id 8.8.8.8
R2 (config-router) # network 172.16.40.0 0.0.0.255 area 40
R2 (config-router) # network 192.168.24.1 0.0.0.255 area 40
R2 (config-router) # neig
R2 (config-router) # neighbor 172.16.40.1
R2 (config-router) # exit
R2 (config) # exit

3. There are now more than R3 set in exactly the same way as R2.

R3 (config) # interface s0 / 0
R3 (config-if) # bandwidth 128
R3 (config-if) # ip ospf priority 0
R3 (config-if) # exit
R3 (config) # router ospf 1
R3 (config-router) # router-id 9.9.9.9
R3 (config-router) # network 172.16.40.0 0.0.0.255 area 40
R3 (config-router) # network 192.168.34.0 0.0.0.255 area 40
R3 (config-router) # neighbor 172.16.40.1
R3 (config-router) # exit
 R3 (config) # exit

4. At first everything seems to be in order, R3 seems to have a very complete routing table.

R3 # sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
O IA 192.168.30.0/24 [110/802] via 172.16.40.1, 0:01:09, Serial0 / 0
O 192.168.24.0/24 [110/791] via 172.16.40.2, 0:01:09, Serial0 / 0
192.168.10.0/30 is subnetted, 2 subnets
O IA 192.168.10.0 [110/1563] via 172.16.40.1, 0:01:09, Serial0 / 0
O IA 192.168.10.4 [110/2344] via 172.16.40.1, 0:01:09, Serial0 / 0
172.16.0.0/24 is subnetted, 1 subnets
C 172.16.40.0 is directly connected, Serial0 / 0
10.0.0.0 / 8 is variably subnetted, 5 subnets, 2 masks
O IA 10.0.1.8/30 [110/1562] via 172.16.40.1, 0:01:09, Serial0 / 0
O IA 10.0.1.12/30 [110/1562] via 172.16.40.1, 0:01:09, Serial0 / 0
O IA 10.0.0.0/24 [110/782] via 172.16.40.1, 0:01:09, Serial0 / 0
O IA 10.0.1.0/30 [110/1563] via 172.16.40.1, 0:01:09, Serial0 / 0
O IA 10.0.1.4/30 [110/1563] via 172.16.40.1, 0:01:09, Serial0 / 0
O IA 192.168.23.0/24 [110/792] via 172.16.40.1, 0:01:10, Serial0 / 0
C 192.168.34.0/24 is directly connected, FastEthernet0 / 0
O E1 192.168.100.0/24 [110/2345] via 172.16.40.1, 0:01:10, Serial0 / 0
R3 #

5. However, looking at the routing table near a problem arises. The 192.168.24.0/24 network (the
loopback of R2) is accessible via 172.16.40.2, address the same network as R3 ... but ... there is
no PVC between R2 and R3 and therefore no connectivity between the two routers!

R3 # ping 192.168.24.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.24.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
R3 #

Note: Since we are in a hub and spoke topology is not about creating a new PVC to link these two
routers. Therefore we will have to ask ABR4 relay frame-relay frames between R2 and R3 ... This just sets
a new mapping frame-relay.

6. R2 to reach R3, PVC is used which leads to R1 and R3 to R2 will also be used to join PVC leading
to R1.
 a. R2:

R2 (config) # interface s0 / 0
R2 (config-if) # frame-relay map ip 172.16.40.3 24 broadcast
R2 (config-if) # exit

b. R3:

R3 (config) # interface s0 / 0
R3 (config-if) # frame-relay map ip 172.16.40.2 34 broadcast
R3 (config-if) # exit

c. Verify:

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

7. To be on good behavior for OSPF, check the status of ABR4, it should be the DR of the frame-
relay network, and R2 and R3 are neither DR nor BDR should be seen as DROTHER.

a. ABR4:

ABR4 # sh ip ospf neighbor

Neighbor ID Pri State Dead Time Address Interface
3.3.3.3 0 FULL / - 0:00:32 10.0.1.14 Serial0 / 1
2.2.2.2 0 FULL / - 0:00:36 10.0.1.10 Serial0 / 0
1.1.1.1 1 FULL / BDR 0:00:34 10.0.0.1 FastEthernet0 / 0
2.2.2.2 1 FULL / DR 0:00:38 10.0.0.3 FastEthernet0 / 0
3.3.3.3 1 2WAY/DROTHER 0:00:36 10.0.0.4 FastEthernet0 / 0
8.8.8.8 0 FULL / DROTHER 0:01:32 172.16.40.2 Serial0 / 2
9.9.9.9 0 FULL / DROTHER 0:01:32 172.16.40.3 Serial0 / 2
ABR4 #

This concludes our OSPF lab. We have a functional backbone area 0 and two secondary areas 10 and 23
with area 10 being a Not So Totally stuby Area. We also have EIGRP being redistributed into OSPF and
finally we have a virtual link connecting area 30 and area 0. Additionally our lab now has area 40
connected via a NBMA hub & spoke frame-relay network