01 OSPF LAB Solution

Course Number
Course Title
Semester/Year
Instructor
Lab Assignment No 02
Assignment Title Open Shortest Path First (OSPF)
Submission Date
Due Date
Submitted by
TABLE OF CONTENTS
Page No.1 of 52
Topic Page No.
Introduction …………………………………………………………………………. 3
Part I. Configuring OSPF with Single Area ..……………………………………….. 3
Part II. Configuring a Multi-Area Routing Domain ......…………………………….. 21
Part III. Configuring Route Summarization ……….......……………………………. 30
Part IV. External Route …………………………….......……………………………. 35
Part V. Configuring Stub Areas ……………………......……………………………. 37
Part VI. Configuring Totally Stubby Areas ..………......……………………………. 41
Part VII. Configuring Virtual Link …………………......…………………………… 47
Conclusion …………………………………………………………………….......... 52
Introduction:
In this lab, we have configured OSPF with single area and have applied different OSPF commands to
observe the different important features of OSPF like neighbor discovery, the state of the neighbors,
Designated Router (DR) selection, initiation of HELLO packet, cost of the link etc.
Page No.2 of 52
In the second part of this lab, we have configured Multi-Area routing domain and studied the link-
state database and have observed the difference between the database of an ABR and the database of
an interior router.
In the next part, we have configured route summarization and observed the metric associated with
the subnets. Then we have configured external route and studied the LSA database. In the next part,
STUB Areas have been configured and examined the routing table before and after the stub-area
configuration.
We have also configured Totally Stubby Areas and monitored the changes in the database and finally
in the last of the lab, virtual link has been configured and have analyzed the link-state databases.
Part I: Configuring OSPF with Single Area
Physical Network Topology:
Logical Topology:
Page No.3 of 52
1. Assign appropriate IP address to the interface of your routers according to the following
table.
2. Set the bandwidth of the serial line to 1.544 Mbps.
3. Configure OSPF with single area (area 0) at your routers.
Design, Discussion and configuration for step 1-3:
We have configured the network topology based on frame-relay configuration at R7 and also we
ensured that the FastEthernet of R2, R5 and R7 were connected via S1, remaining in same VLAN
(here vlan 25). The configuration for Frame-relay and vlans were copied from the “Topology
conversion table”.
Page No.4 of 52
We have assigned the appropriate IP address to the interface of the routers according to the above
table and set the bandwidth of the serial link to 1.544 Mbps (1544 Kbps) and have configured OSPF
with single area (area 0) at the routers :
Running configuration of R1 Running configuration of R2

! !
hostname R1 hostname R2
! !
interface Serial0/1/0 interface FastEthernet0/0
bandwidth 1544 ip address 10.16.128.2 255.255.255.0
ip address 10.16.1.1 255.255.255.0 duplex auto
encapsulation frame-relay speed auto
ip ospf network point-to-point !
! !
interface Serial0/1/1 interface Serial0/1/0
bandwidth 1544 bandwidth 1544
ip address 10.16.2.2 255.255.255.0 ip address 10.16.2.1 255.255.255.0
encapsulation frame-relay encapsulation frame-relay
ip ospf network point-to-point ip ospf network point-to-point
! !
router ospf 1 interface Serial0/1/1
network 10.16.1.0 0.0.0.255 area 0 bandwidth 1544
network 10.16.2.0 0.0.0.255 area 0 ip address 10.16.3.2 255.255.255.0
! encapsulation frame-relay
ip ospf network point-to-point
!
router ospf 1
network 10.16.2.0 0.0.0.255 area 0
network 10.16.3.0 0.0.0.255 area 0
network 10.16.128.0 0.0.0.255 area 0
Running configuration of R3 Running configuration of R4
hostname R3 hostname R4
! !
Page No.5 of 52
! !
! !
router ospf 1 router ospf 1
network 10.16.1.0 0.0.0.255 area 0 network 10.16.4.0 0.0.0.255 area 0
network 10.16.3.0 0.0.0.255 area 0 network 10.16.5.0 0.0.0.255 area 0
!
The configuration was similar for rest of the Routers. After configuration we have checked the
connectivity by pinging and found each segment of network can reach any segment once when ospf
was enabled and also checked the frame-relay routes in active status.
R7#sh frame-relay route
Input Intf Input Dlci Output Intf Output Dlci Status

Serial0/0/0 103 Serial0/2/1 301 active
Serial0/3/0 406 Serial1/3 604 active
Serial0/3/1 405 Serial1/0 504 active
Serial1/0 504 Serial0/3/1 405 active
Serial1/1 506 Serial1/2 605 active
Serial1/2 605 Serial1/1 506 active
Serial1/3 604 Serial0/3/0 406 active
R1# ping 10.16.6.1
Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.16.6.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/57/60 ms
R1# ping 10.16.6.1
Page No.6 of 52
!!!!!
R1# ping 10.16.5.2

!!!!!
Our topology has been configured successfully.
4. Use show ip protocols and show ip route commands to verify that OSPF is enabled.
Command:
R1# show ip protocols
Routing Protocol is "ospf 1"

Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Router ID 10.16.2.2
Number of areas in this router is 1. 1 normal 0 stub 0 nssa
Maximum path: 4
Routing for Networks:
10.16.1.0 0.0.0.255 area 0
10.16.2.0 0.0.0.255 area 0
Reference bandwidth unit is 100 mbps
Routing Information Sources:
Gateway Distance Last Update
10.16.2.1 110 00:17:00
10.16.2.2 110 01:04:07
10.16.5.2 110 00:08:55
10.16.6.2 110 00:16:50
10.16.128.2 110 00:09:05
10.16.128.7 110 00:08:55
10.16.128.5 110 00:08:55
Distance: (default is 110)
R1# 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
Page No.7 of 52
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
10.0.0.0/24 is subnetted, 7 subnets

C 10.16.2.0 is directly connected, Serial0/1/1
O 10.16.3.0 [110/128] via 10.16.2.1, 00:02:56, Serial0/1/1
O 10.16.6.0 [110/129] via 10.16.2.1, 00:01:17, Serial0/1/1
O 10.16.4.0 [110/193] via 10.16.2.1, 00:00:13, Serial0/1/1
O 10.16.5.0 [110/129] via 10.16.2.1, 00:01:17, Serial0/1/1
O 10.16.128.0 [110/65] via 10.16.2.1, 00:02:13, Serial0/1/1
Ans: From the above result we can see that OSPF is enabled. All the subnets are known to the R1.
Two are directly connected and other five by OSPF routing protocol.
5. On your router, initiate the show ip ospf interface command and answer the following
questions:
• How many interface are configured for OSPF?
• What is the router ID used for each interface?
• Is there a DR for each configured network? If so, what is the DR IP address? If not, why not?
• How often are hello packets initiated?
• How many seconds will a router wait without receiving a hello packet before it considers the
neighbor as dead?
• What is the cost for each link that you have configured?
• What command can you use to modify the cost of the link?
Command:
R1# sh ip ospf interface
Serial0/1/1 is up, line protocol is up

Internet Address 10.16.2.2/24, Area 0
Process ID 1, Router ID 10.16.2.2, Network Type POINT_TO_POINT, Cost: 64
Transmit Delay is 1 sec, State POINT_TO_POINT
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
oob-resync timeout 40
Hello due in 00:00:03
Supports Link-local Signaling (LLS)
Cisco NSF helper support enabled
IETF NSF helper support enabled
Index 2/2, flood queue length 0
Page No.8 of 52
Next 0x0(0)/0x0(0)
Last flood scan length is 1, maximum is 1
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 10.16.128.2
Suppress hello for 0 neighbor(s)
Serial0/1/0 is up, line protocol is up
Internet Address 10.16.1.1/24, Area 0
Process ID 1, Router ID 10.16.2.2, Network Type POINT_TO_POINT, Cost: 64
Transmit Delay is 1 sec, State POINT_TO_POINT
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
oob-resync timeout 40
Hello due in 00:00:00
Index 1/1, flood queue length 0
Next 0x0(0)/0x0(0)
Last flood scan length is 0, maximum is 0
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 0, Adjacent neighbor count is 0
Suppress hello for 0 neighbor(s)
• How many interface are configured for OSPF?

• What is the router ID used for each interface?
Ans: Two interfaces (Serial0/1/0, Serial0/1/1) are configured for OSPF and the Router ID
is10.16.2.2. It is mentionable that we did not configure any loop back address, so the highest
interface among the up/up interfaces is selected as router ID. Again if we put Router ID x.x.x.x (into
OSPF configuration), then it will overwrite the router ID that was selected from loopback interface
(active) address.
• Is there a DR for each configured network? If so, what is the DR IP address? If not, why not?
Ans: In the topology R1 is connected to R2/R3 via “point to point network” connectivity. So there is
no DR.
DR is elected to reduce adjacency to half to the broadcast networks. In our topology R2, R5 and R7
are in a broadcast network, so the DR will be elected to that network.
As the priority for all three routers is 1(by default) so the tie will be broken by router ID. As the R7
has larger router ID (10.16.128.7), so it is selected as DR for that broadcast region of our topology.
• How often are hello packets initiated?
Page No.9 of 52
Ans: The hello time interval is 10 seconds (Default for point to point network)
Hello interval is configurable
R1(config-if)# ip ospf hello-interval <value in sec>
To be an OSPF neighbor, the hello interval of the peer routers must match.
• How many seconds will a router wait without receiving a hello packet before it considers the
neighbor as dead?
Ans: The dead time interval is 40 seconds (Default for point to point network), till 40 sec R1 will
consider R3 and R2 as neighbor if R3 or R2 don’t send hello.
Dead interval is configurable
R1(config-if)# ip ospf dead-interval <value in sec>
Like hello interval, dead interval of the peer routers must match to form OSPF neighbor relationship.
• What is the cost for each link that you have configured?
Ans: R1 is connected to R2 and R3 via serial link having BW of 1544 kbps. So the ospf cost is
64(ospf cost = 10^8/BW (in bps)).
• What command can you use to modify the cost of the link?
Command:
R1(config-if)# ip ospf cost ?
<1-65535> Cost
R1(config-if)# ip ospf cost <cost>
6. Initiate the show ip ospf neighbor detail command on your router and answer the following
question:
• How many neighbors do you have?
• What are your neighbors’ router IDs?
• What state do the neighbors have? What does the state mean to the routers?
Command:
R1# show ip ospf neighbor detail
Neighbor 10.16.3.1, interface address 10.16.1.2

In the area 0 via interface Serial0/1/0
Page No.10 of 52
Neighbor priority is 0, State is FULL, 6 state changes
DR is 0.0.0.0 BDR is 0.0.0.0
Options is 0x52
LLS Options is 0x1 (LR)
Dead timer due in 00:00:36
Neighbor is up for 01:50:02
Index 1/1, retransmission queue length 0, number of retransmission 1
First 0x0(0)/0x0(0) Next 0x0(0)/0x0(0)
Last retransmission scan length is 1, maximum is 1
Last retransmission scan time is 0 msec, maximum is 0 msec
Neighbor 10.16.128.2, interface address 10.16.2.1
In the area 0 via interface Serial0/1/0
Neighbor priority is 0, State is FULL, 6 state changes
DR is 0.0.0.0 BDR is 0.0.0.0
Options is 0x52
LLS Options is 0x1 (LR)
Dead timer due in 00:00:31
Neighbor is up for 00:41:32
Index 2/2, retransmission queue length 0, number of retransmission 1
First 0x0(0)/0x0(0) Next 0x0(0)/0x0(0)
Last retransmission scan length is 1, maximum is 1
Last retransmission scan time is 0 msec, maximum is 0 msec
• How many neighbors do you have?

Ans: For R1, it has two Neighbors (R2 and R3)
• What are your neighbors’ routers IDs?

Ans: The neighbors’ routers IDs 10.16.3.1 and 10.16.128.2.
Here, the highest active interface IP is considered as router ID as we did not configure any loopback
interface. If we put the folloging commands to any router then the router id would be x.x.x.x
regardless its loopback or IP interfaces it have.
R1(config)# router ospf 1

R1(config-router)# router-id x.x.x.x
• What state do the neighbors have? What does the state mean to the routers?
Ans: Both the neighbors are in FULL state; this means that the neighbors Link State database is fully
synchronized and for all outdated LSAs all updates have been received.
Moreover, we also observed the neighbors for other routers and found as we expect. Below the
neighbor brief for R2 is shown.
R2# sh ip ospf neighbor
Page No.11 of 52
Neighbor ID Pri State Dead Time Address Interface
10.16.128.5 1 FULL/BDR 00:00:31 10.16.128.5 FastEthernet0/0
10.16.128.7 1 FULL/DR 00:00:35 10.16.128.7 FastEthernet0/0
10.16.3.1 0 FULL/ - 00:00:32 10.16.3.1 Serial0/1/1
10.16.2.2 0 FULL/ - 00:00:39 10.16.2.2 Serial0/1/0
7. Verify that all the networks can be seen by your router by initiating the show ip ospf
database command.
Command:
R1# show ip ospf database
OSPF Router with ID (10.16.2.2) (Process ID 1)
Router Link States (Area 0)
Link ID ADV Router Age Seq# Checksum Link count

10.16.2.2 10.16.2.2 403 0x8000000F 0x002FE8 3
10.16.3.1 10.16.3.1 279 0x8000000E 0x0043D4 3
10.16.5.2 10.16.5.2 253 0x80000002 0x00D9AA 4
10.16.6.1 10.16.6.1 253 0x80000003 0x001170 4
10.16.128.2 10.16.128.2 283 0x80000008 0x00B411 5
10.16.128.5 10.16.128.5 252 0x80000006 0x006745 5
10.16.128.7 10.16.128.7 360 0x8000000D 0x00E5BA 1
Net Link States (Area 0)
Link ID ADV Router Age Seq# Checksum

10.16.128.7 10.16.128.7 307 0x80000004 0x00E72A
Observation: All the routers belong to same area (area 0), so there exist only one database. There
were all 7 routers links (type 1) and 1 network link (type 2) for transit network Advertised by DR.
8. Use sh ip ospf data router and sh ip ospf database network commands to show the details of
the LSAs.
We have used “show ip ospf database router” and “show ip ospf database network” to show the
router LSA, the LSA-1 and the network LSA, LSA-2. As we set only one single area, all the routers
had the same database and LSAs for R1:
Command:
R1# sh ip ospf database router

Link connected to: a Stub Network
OSPF Router with ID (10.16.2.2) (Process (Link ID) Network/subnet number: 10.16.6.0
Page No.12 of 52
ID 1) (Link Data) Network Mask: 255.255.255.0
Number of TOS metrics: 0
Router Link States (Area 0) TOS 0 Metrics: 64
LS age: 472 Link connected to: another Router (point-to-

Options: (No TOS-capability, DC) point)
LS Type: Router Links (Link ID) Neighboring Router ID: 10.16.5.2
Link State ID: 10.16.2.2 (Link Data) Router Interface address: 10.16.4.2
Advertising Router: 10.16.2.2 Number of TOS metrics: 0
LS Seq Number: 8000000F TOS 0 Metrics: 64
Checksum: 0x2FE8
Length: 72 Link connected to: a Stub Network
Number of Links: 4 (Link ID) Network/subnet number: 10.16.4.0
Link connected to: another Router (point-to-point) (Link Data) Network Mask: 255.255.255.0
(Link ID) Neighboring Router ID: 10.16.128.2 Number of TOS metrics: 0
(Link Data) Router Interface address: 10.16.2.2 TOS 0 Metrics: 64
TOS 0 Metrics: 64 LS age: 361
Options: (No TOS-capability, DC)
Link connected to: a Stub Network LS Type: Router Links
(Link ID) Network/subnet number: 10.16.2.0 Link State ID: 10.16.128.2
(Link Data) Network Mask: 255.255.255.0 Advertising Router: 10.16.128.2
Number of TOS metrics: 0 LS Seq Number: 80000008
TOS 0 Metrics: 64 Checksum: 0xB411
Length: 84
Link connected to: another Router (point-to-point) Number of Links: 5
(Link ID) Neighboring Router ID: 10.16.3.1
(Link Data) Router Interface address: 10.16.1.1 Link connected to: a Transit Network
Number of TOS metrics: 0 (Link ID) Designated Router address:
TOS 0 Metrics: 64 10.16.128.7
(Link Data) Router Interface address:
Link connected to: a Stub Network 10.16.128.2
(Link ID) Network/subnet number: 10.16.1.0 Number of TOS metrics: 0
(Link Data) Network Mask: 255.255.255.0 TOS 0 Metrics: 1
TOS 0 Metrics: 64 Link connected to: another Router (point-to-
point)
LS age: 351 (Link ID) Neighboring Router ID: 10.16.3.1
Options: (No TOS-capability, DC) (Link Data) Router Interface address: 10.16.3.2
LS Type: Router Links Number of TOS metrics: 0
Link State ID: 10.16.3.1 TOS 0 Metrics: 64
Advertising Router: 10.16.3.1
LS Seq Number: 8000000E Link connected to: a Stub Network
Checksum: 0x43D4 (Link ID) Network/subnet number: 10.16.3.0
Length: 72 (Link Data) Network Mask: 255.255.255.0
Number of Links: 4 Number of TOS metrics: 0
TOS 0 Metrics: 64
Link connected to: another Router (point-to-point)
(Link ID) Neighboring Router ID: 10.16.2.2 Link connected to: another Router (point-to-
(Link Data) Router Interface address: 10.16.1.2 point)
Number of TOS metrics: 0 (Link ID) Neighboring Router ID: 10.16.2.2
TOS 0 Metrics: 64 (Link Data) Router Interface address: 10.16.2.1
Page No.13 of 52
Link connected to: a Stub Network TOS 0 Metrics: 64
(Link ID) Network/subnet number: 10.16.1.0
(Link Data) Network Mask: 255.255.255.0 Link connected to: a Stub Network
Number of TOS metrics: 0 (Link ID) Network/subnet number: 10.16.2.0
TOS 0 Metrics: 64 (Link Data) Network Mask: 255.255.255.0
Link connected to: another Router (point-to-point) TOS 0 Metrics: 64
(Link Data) Router Interface address: 10.16.3.1
Number of TOS metrics: 0 LS age: 330
TOS 0 Metrics: 64 Options: (No TOS-capability, DC)
LS Type: Router Links
Link connected to: a Stub Network Link State ID: 10.16.128.5
(Link ID) Network/subnet number: 10.16.3.0 Advertising Router: 10.16.128.5
(Link Data) Network Mask: 255.255.255.0 LS Seq Number: 80000006
Number of TOS metrics: 0 Checksum: 0x6745
TOS 0 Metrics: 64 Length: 84
Number of Links: 5
LS age: 326
Options: (No TOS-capability, DC) Link connected to: a Transit Network
LS Type: Router Links (Link ID) Designated Router address:
Link State ID: 10.16.5.2 10.16.128.7
Advertising Router: 10.16.5.2 (Link Data) Router Interface address:
LS Seq Number: 80000002 10.16.128.5
Checksum: 0xD9AA Number of TOS metrics: 0
Length: 72 TOS 0 Metrics: 1
Number of Links: 4
Link connected to: another Router (point-to-
Link connected to: another Router (point-to- point)
point) (Link ID) Neighboring Router ID: 10.16.6.1
(Link ID) Neighboring Router ID: 10.16.128.5 (Link Data) Router Interface address: 10.16.6.2
(Link Data) Router Interface address: 10.16.5.2 Number of TOS metrics: 0
Number of TOS metrics: 0 TOS 0 Metrics: 64
TOS 0 Metrics: 64
Link connected to: a Stub Network (Link ID) Network/subnet number: 10.16.6.0
(Link ID) Network/subnet number: 10.16.5.0 (Link Data) Network Mask: 255.255.255.0
(Link Data) Network Mask: 255.255.255.0 Number of TOS metrics: 0
TOS 0 Metrics: 64
Link connected to: another Router (point-to-
Link connected to: another Router (point-to- point)
point) (Link ID) Neighboring Router ID: 10.16.5.2
(Link ID) Neighboring Router ID: 10.16.6.1 (Link Data) Router Interface address: 10.16.5.1
(Link Data) Router Interface address: 10.16.4.1 Number of TOS metrics: 0
TOS 0 Metrics: 64
Link connected to: a Stub Network (Link ID) Network/subnet number: 10.16.5.0
(Link ID) Network/subnet number: 10.16.4.0 (Link Data) Network Mask: 255.255.255.0
(Link Data) Network Mask: 255.255.255.0 Number of TOS metrics: 0
Page No.14 of 52
TOS 0 Metrics: 64
LS age: 327 LS age: 440

Options: (No TOS-capability, DC) Options: (No TOS-capability, DC)
LS Type: Router Links LS Type: Router Links
Link State ID: 10.16.6.1 Link State ID: 10.16.128.7
Advertising Router: 10.16.6.1 Advertising Router: 10.16.128.7
LS Seq Number: 80000003 LS Seq Number: 8000000D
Checksum: 0x1170 Checksum: 0xE5BA
Length: 72 Length: 36
Number of Links: 4 Number of Links: 1
Link connected to: another Router (point-to- Link connected to: a Transit Network
point) (Link ID) Designated Router address:
(Link ID) Neighboring Router ID: 10.16.128.5 10.16.128.7
(Link Data) Router Interface address: 10.16.6.1 (Link Data) Router Interface address:
Number of TOS metrics: 0 10.16.128.7
TOS 0 Metrics: 64 Number of TOS metrics: 0
TOS 0 Metrics: 1
Command:
R1# sh ip ospf database network
Routing Bit Set on this LSA

LS age: 420
LS Type: Network Links
Link State ID: 10.16.128.7 (address of Designated Router)
LS Seq Number: 80000004
Checksum: 0xE72A
Length: 36
Network Mask: /24
Attached Router: 10.16.128.7
Observation: All the routers advertised their associated router LSA, LSA-1 (point to point, point to
transient network, point to stub network) and only R7 advertised network LSA, LAS-2.
Page No.15 of 52
9. Study the LSA databases of PnR1 and PnR4. With the knowledge of the network topology,
identify the LSAs used to compute the shortest paths from PnR1 and PnR4 to the subnet
10.n.128.0/24. Compute the cost associated with these paths based on these LSAs. Verify your
computation by comparing your results with the entries of the routing table.
Ans:
From the data from “show ip ospf data router” the cost calculation is as below:
From R1 to 10.16.128.0/24: 65
(Cost of a serial0/1/0 of R1= 64, Cost of fa0/0 of R2=1)
From R4 to 10.16.128.0/24:74
(Cost of a serial0/1/1 of R4= 64, Cost of fa0/0 of R5=1)
Verify the computation from routing table:

Command:
R1# sh ip route


O 10.16.3.0 [110/128] via 10.16.2.1, 00:10:05, Serial0/1/1
O 10.16.6.0 [110/129] via 10.16.2.1, 00:08:26, Serial0/1/1
O 10.16.4.0 [110/193] via 10.16.2.1, 00:07:22, Serial0/1/1
O 10.16.5.0 [110/129] via 10.16.2.1, 00:08:26, Serial0/1/1
O 10.16.128.0 [110/65] via 10.16.2.1, 00:09:22, Serial0/1/1
R4# sh ip route

Page No.16 of 52

O 10.16.2.0 [110/129] via 10.16.5.1, 00:08:10, Serial0/1/1
O 10.16.3.0 [110/129] via 10.16.5.1, 00:08:10, Serial0/1/1
O 10.16.1.0 [110/193] via 10.16.5.1, 00:08:10, Serial0/1/1
O 10.16.6.0 [110/128] via 10.16.5.1, 00:08:10, Serial0/1/1
[110/128] via 10.16.4.2, 00:08:10, Serial0/1/0
O 10.16.128.0 [110/65] via 10.16.5.1, 00:08:10, Serial0/1/1
10. Identify the LSAs in your router for the point-to-point link between PnR3 and PnR2.
Ans: We have studied the router LSA at R1 as given on step 8. That point-to-point link was
advertised by R3 as router LSA and type was point-to-point. For verification relevant section of LSA
database is given as follows:
LS age: 351
Link State ID: 10.16.3.1
LS Seq Number: 8000000E
Checksum: 0x43D4
Length: 72
Number of Links: 4

TOS 0 Metrics: 64
11. Disable this point-to-point link. Check the LSAs in the database of your router again. Do
the LSAs reflect the change of the link state?
We have disabled the link by shutdown the related interface and verified the LSAdatabase at R2 by
“show ip ospf database router” command.
Command:
R2# config t
R2(config)# interface serial 0/1/1
R2(config-if)# shut
Page No.17 of 52
R2(config-if)# do sh ip ospf database router

OSPF Router with ID (10.16.128.2) (Process ID 1) (Link ID) Neighboring Router ID: 10.16.2.2
Router Link States (Area 0) Number of TOS metrics: 0
TOS 0 Metrics: 64
LS age: 1023
Options: (No TOS-capability, DC) Link connected to: a Stub Network
LS Type: Router Links (Link ID) Network/subnet number: 10.16.2.0
Link State ID: 10.16.2.2 (Link Data) Network Mask: 255.255.255.0
Advertising Router: 10.16.2.2 Number of TOS metrics: 0
LS Seq Number: 8000000F TOS 0 Metrics: 64
Checksum: 0x2FE8
Length: 60 LS age: 874
Number of Links: 3 Options: (No TOS-capability, DC)
Link connected to: another Router (point-to-point) Link State ID: 10.16.5.2
(Link ID) Neighboring Router ID: 10.16.128.2 Advertising Router: 10.16.5.2
(Link Data) Router Interface address: 10.16.2.2 LS Seq Number: 80000002
Number of TOS metrics: 0 Checksum: 0xD9AA
Number of Links: 4
(Link ID) Network/subnet number: 10.16.2.0 Link connected to: another Router (point-to-point)
(Link Data) Network Mask: 255.255.255.0 (Link ID) Neighboring Router ID: 10.16.128.5
Number of TOS metrics: 0 (Link Data) Router Interface address: 10.16.5.2
TOS 0 Metrics: 64
(Link ID) Network/subnet number: 10.16.1.0 Link connected to: a Stub Network
(Link Data) Network Mask: 255.255.255.0 (Link ID) Network/subnet number: 10.16.5.0
Number of TOS metrics: 0 (Link Data) Network Mask: 255.255.255.0
TOS 0 Metrics: 64
Adv Router is not-reachable Link connected to: another Router (point-to-point)

LS age: 899 (Link ID) Neighboring Router ID: 10.16.6.1
Options: (No TOS-capability, DC) (Link Data) Router Interface address: 10.16.4.1
LS Type: Router Links Number of TOS metrics: 0
Link State ID: 10.16.3.1 TOS 0 Metrics: 64
LS Seq Number: 8000000E Link connected to: a Stub Network
Checksum: 0x43D4 (Link ID) Network/subnet number: 10.16.4.0
Length: 60 (Link Data) Network Mask: 255.255.255.0
Number of Links: 3 Number of TOS metrics: 0
TOS 0 Metrics: 64
Number of TOS metrics: 0 LS age: 876
Page No.18 of 52
TOS 0 Metrics: 64 Options: (No TOS-capability, DC)
Link connected to: a Stub Network Link State ID: 10.16.128.5
(Link ID) Network/subnet number: 10.16.3.0 Advertising Router: 10.16.128.5
(Link Data) Network Mask: 255.255.255.0 LS Seq Number: 80000006
Number of TOS metrics: 0 Checksum: 0x6745
Number of Links: 5
(Link ID) Network/subnet number: 10.16.1.0 Link connected to: a Transit Network
(Link Data) Network Mask: 255.255.255.0 (Link ID) Designated Router address: 10.16.128.7
Number of TOS metrics: 0 (Link Data) Router Interface address: 10.16.128.5
LS age: 875 TOS 0 Metrics: 1
LS Type: Router Links Link connected to: another Router (point-to-point)
Link State ID: 10.16.6.1 (Link ID) Neighboring Router ID: 10.16.6.1
Advertising Router: 10.16.6.1 (Link Data) Router Interface address: 10.16.6.2
LS Seq Number: 80000003 Number of TOS metrics: 0
Checksum: 0x1170 TOS 0 Metrics: 64
Length: 72
Number of Links: 4 Link connected to: a Stub Network
TOS 0 Metrics: 64 Link connected to: another Router (point-to-point)
Link connected to: a Stub Network (Link Data) Router Interface address: 10.16.5.1
(Link ID) Network/subnet number: 10.16.6.0 Number of TOS metrics: 0
(Link Data) Network Mask: 255.255.255.0 TOS 0 Metrics: 64
TOS 0 Metrics: 64 Link connected to: a Stub Network
TOS 0 Metrics: 64
LS age: 985
Link connected to: a Stub Network Options: (No TOS-capability, DC)
(Link ID) Network/subnet number: 10.16.4.0 LS Type: Router Links
(Link Data) Network Mask: 255.255.255.0 Link State ID: 10.16.128.7
Number of TOS metrics: 0 Advertising Router: 10.16.128.7
TOS 0 Metrics: 64 LS Seq Number: 8000000D
Checksum: 0xE5BA
LS age: 206 Length: 36
Options: (No TOS-capability, DC) Number of Links: 1
Link State ID: 10.16.128.2 Link connected to: a Transit Network
Advertising Router: 10.16.128.2 (Link ID) Designated Router address: 10.16.128.7
Page No.19 of 52
LS Seq Number: 80000009 (Link Data) Router Interface address: 10.16.128.7
Checksum: 0x5D60 Number of TOS metrics: 0
Length: 60 TOS 0 Metrics: 1
Number of Links: 3
Link connected to: a Transit Network

(Link ID) Designated Router address: 10.16.128.7
TOS 0 Metrics: 1
Observation: After shutting down the link between R2 to R3 (interface serial 0/1/1 at R2), the result
was reflected on LSA database. Now R2 only advertised 3 “Router LSAs” which was 4 previously.
Also we can see the output.
Part II: Configuring a Multi-Area Routing Domain
1. Together with your pod members, configure the routers according to the following figure to
create a multi-area routing domain1.
Command:
R2# config t
R2(config-router)# network 10.16.2.0 0.0.0.255 area 1
Page No.20 of 52
Other routers also configured similarly as per topology
2. Use show ip protocol command to verify that ospf is enabled.
R1# show ip protocol

Router ID 10.16.2.2
Maximum path: 4
10.16.1.0 0.0.0.255 area 1
10.16.2.0 0.0.0.255 area 1
10.16.2.2 110 00:07:58
10.16.128.2 110 00:02:37
R2# sh ip protocols

Router ID 10.16.128.2
It is an area border router
Maximum path: 4
10.16.2.0 0.0.0.255 area 1
10.16.3.0 0.0.0.255 area 1
10.16.128.0 0.0.0.255 area 0
10.16.3.1 110 00:05:54
10.16.2.2 110 00:06:04
10.16.5.2 110 00:05:54
10.16.128.2 110 00:06:04
10.16.128.7 110 00:05:54
10.16.128.5 110 00:03:22
Page No.21 of 52
Observation: We have checked all the routers; routing protocol “ospf 1” is set to all the routers.
We also have checked the interfaces are in right area.
3. Use show ip ospf to verify that your router belongs to the right area(s).
Command:
R1# show ip ospf
Routing Process "ospf 1" with ID 10.16.2.2

------ output omitted -----------------------------
Area 1
Number of interfaces in this area is 2
Area has no authentication
SPF algorithm last executed 00:04:03.752 ago
SPF algorithm executed 6 times
Area ranges are
Number of LSA 7. Checksum Sum 0x025F7F
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
We also have checked the interfaces of different routers and found in exact area. The output is
given below:
R1# sh ip ospf interface brief

Interface PID Area IP Address/Mask Cost State Nbrs F/C
Se0/1/1 1 1 10.16.2.2/24 64 P2P 1/1
Se0/1/0 1 1 10.16.1.1/24 64 P2P 0/0
Fa0/0 1 0 10.16.128.2/24 1 BDR 2/2
Se0/1/1 1 1 10.16.3.2/24 64 P2P 1/1
Se0/1/0 1 1 10.16.2.1/24 64 P2P 1/1
Se0/1/0 1 1 10.16.3.1/24 64 P2P 1/1
Se0/1/1 1 1 10.16.1.1/24 64 P2P 0/0
Se0/1/1 1 2 10.16.5.2/24 64 P2P 1/1
Se0/1/0 1 2 10.16.4.1/24 64 P2P 1/1
Page No.22 of 52
Fa0/0 1 0 10.16.128.5/24 1 DROTH 2/2
Se0/1/1 1 2 10.16.6.2/24 64 P2P 1/1
Se0/1/0 1 2 10.16.5.1/24 64 P2P 1/1
Se0/1/0 1 2 10.16.6.1/24 64 P2P 1/1
Se0/1/1 1 2 10.16.4.2/24 64 P2P 1/1
Fa0/0 1 0 10.16.128.7/24 1 DR 2/2
4. Use show ip route to verify that your router has learned all the routers in the routing
domain.
Command:
R1# show ip route


O 10.16.3.0 [110/128] via 10.16.2.1, 00:03:32, Serial0/1/1
O IA 10.16.6.0 [110/129] via 10.16.2.1, 00:09:06, Serial0/1/1
O IA 10.16.4.0 [110/193] via 10.16.2.1, 00:08:19, Serial0/1/1
O IA 10.16.5.0 [110/129] via 10.16.2.1, 00:09:06, Serial0/1/1
O IA 10.16.128.0 [110/65] via 10.16.2.1, 00:10:51, Serial0/1/1
Observation: From the above output of “show ip route”, it is observed that all 7 subnets were
informed by R1. Two subnets are directly connected (denoted as C), one form same region (area 1,
denoted as O) and other four routes are from different region/s (area 0 and area 2, denoted as O IA)
Page No.23 of 52
5. Study the link-state database of an interior router in area 1 (area 2). What types of LSAs are
in the database?
Command:

10.16.2.2 10.16.2.2 766 0x80000002 0x0049DB 3
10.16.3.1 10.16.3.1 317 0x80000005 0x0055CB 3
10.16.128.2 10.16.128.2 313 0x80000006 0x0049CB 4
Summary Net Link States (Area 1)

10.16.4.0 10.16.128.2 600 0x80000001 0x00BE42
10.16.5.0 10.16.128.2 646 0x80000001 0x00310F
10.16.6.0 10.16.128.2 646 0x80000001 0x002619
10.16.128.0 10.16.128.2 752 0x80000001 0x0060A4
R4# sh ip ospf database

10.16.5.2 10.16.5.2 653 0x80000003 0x00D7AB 4
10.16.6.1 10.16.6.1 649 0x80000002 0x00136F 4
10.16.128.5 10.16.128.5 654 0x80000003 0x00FA05 4

10.16.1.0 10.16.128.5 731 0x80000001 0x00CD33
10.16.2.0 10.16.128.5 731 0x80000001 0x0040FF
10.16.3.0 10.16.128.5 398 0x80000001 0x00350A
10.16.128.0 10.16.128.5 731 0x80000001 0x004EB3
Answer to Question 5: From the above output of “show ip ospf database”, it is observed that a
router in a single area contains router LSA (LSA-1) and summary LSA (LSA-3) of that region.
Page No.24 of 52
6. Identify the LSAs used for the computation of the shortest path of an inter-area route from
the interior router in area 1 (area 2) to a subnet in area 2 (area 1).
Command:
R1# sh ip ospf database summary

LS age: 765
Options: (No TOS-capability, DC, Upward)
LS Type: Summary Links(Network)
Link State ID: 10.16.4.0 (summary Network Number)
Checksum: 0xBE42
Length: 28
Network Mask: /24
TOS: 0 Metric: 129

LS age: 811
Checksum: 0x310F
Length: 28
Network Mask: /24
TOS: 0 Metric: 65

LS age: 813
Checksum: 0x2619
Length: 28
Network Mask: /24
TOS: 0 Metric: 65
Page No.25 of 52
LS age: 919
Checksum: 0x60A4
Length: 28
Network Mask: /24
TOS: 0 Metric: 1

LS age: 854
Checksum: 0xCD33
Length: 28
Network Mask: /24
TOS: 0 Metric: 129

LS age: 854
Checksum: 0x40FF
Length: 28
Network Mask: /24
TOS: 0 Metric: 65

LS age: 522
Page No.26 of 52
Checksum: 0x350A
Length: 28
Network Mask: /24
TOS: 0 Metric: 65

LS age: 855
Checksum: 0x4EB3
Length: 28
Network Mask: /24
TOS: 0 Metric: 1
Observation: LSAs are used for the computation of the shortest path from one area to another area
have highlighted from “sh ip ospf database summary” output. It may be mentioned that from R1
there exists 4 Summary LSA (type - 3), three from area 2 and one for backbone. Again same is
applicable for an interior router in area 2 like R4.
7. Based on the LSAs, compute the cost of the inter-area route. Verify your computation by
comparing your result with the corresponding entry in the routing table.
Cost Calculation from R1 to different subnets of area0 and area 2:
Subnet Area Route Cost associated with Total cost

link
10.16.128.0 0 R1 to R2 to 64+1 65
10.16.4.0 2 R1 to R2 to R5 to 64+1+64+64 193
R4/R6 to
10.16.5.0 2 R1 to R2 to R5 to 64+1+64 129
10.16.6.0 2 R1 to R2 to R5 to 64+1+64 129
Verification from sh ip route:
Command:
R1# sh ip route
Page No.27 of 52

O 10.16.3.0 [110/128] via 10.16.2.1, 00:09:29, Serial0/1/1
O IA 10.16.6.0 [110/129] via 10.16.2.1, 00:15:02, Serial0/1/1
O IA 10.16.4.0 [110/193] via 10.16.2.1, 00:14:16, Serial0/1/1
O IA 10.16.5.0 [110/129] via 10.16.2.1, 00:15:02, Serial0/1/1
O IA 10.16.128.0 [110/65] via 10.16.2.1, 00:16:48, Serial0/1/1
Observation: From the above output, we can say that our calculation matched with SPF algorithm.
8. Study the link-state database of an area border router (ABR). What is the main difference
between the database of an ABR and the database of an interior router?
Command:

10.16.5.2 10.16.5.2 2243 0x80000002 0x00D9AA 4
10.16.6.1 10.16.6.1 2244 0x80000003 0x001170 4
10.16.128.2 10.16.128.2 1052 0x8000000E 0x00F0BC 1
10.16.128.5 10.16.128.5 945 0x80000007 0x00F8B2 1
10.16.128.7 10.16.128.7 461 0x8000000E 0x00E3BB 1

10.16.128.7 10.16.128.7 948 0x80000008 0x00DF2E

10.16.1.0 10.16.128.2 1055 0x80000001 0x00D52F
10.16.2.0 10.16.128.2 1055 0x80000001 0x0048FB
Page No.28 of 52
10.16.3.0 10.16.128.2 605 0x80000001 0x003D06
10.16.4.0 10.16.128.5 893 0x80000001 0x00A25C
10.16.5.0 10.16.128.5 952 0x80000001 0x001529
10.16.6.0 10.16.128.5 952 0x80000001 0x000A33

10.16.2.2 10.16.2.2 1063 0x80000002 0x0049DB 3
10.16.3.1 10.16.3.1 613 0x80000005 0x0055CB 3
10.16.128.2 10.16.128.2 608 0x80000006 0x0049CB 4

10.16.4.0 10.16.128.2 895 0x80000001 0x00BE42
10.16.5.0 10.16.128.2 941 0x80000001 0x00310F
10.16.6.0 10.16.128.2 941 0x80000001 0x002619
10.16.128.0 10.16.128.2 1047 0x80000001 0x0060A4

10.16.2.2 10.16.2.2 1083 0x80000002 0x0049DB 3
10.16.3.1 10.16.3.1 635 0x80000005 0x0055CB 3
10.16.128.2 10.16.128.2 630 0x80000006 0x0049CB 4

10.16.4.0 10.16.128.2 917 0x80000001 0x00BE42
10.16.5.0 10.16.128.2 964 0x80000001 0x00310F
10.16.6.0 10.16.128.2 964 0x80000001 0x002619
10.16.128.0 10.16.128.2 1070 0x80000001 0x0060A4
Answer: In the topology, R2 and R5 are Area Broader Router (ABR) as their interfaces are
connected in more than one area. From the output we saw that R2 (ABR) contains LSA of connected
2 areas (area1 and area 0) whereas, an interior router (having all interfaces in one area) like R1 exists
with LSA of its own region only.
Page No.29 of 52
Part III: Configuring Route Summarization
1. Together with your pod members determine a list of possible route summarizations for area
1 (area 2).
Route summarizations for Area 1:
Subnets in doted Binary conversion Summarised Address

decimal /mask
10.16.1.0 00001010 .00000100 .00000001 .0000000
0 10.16.0.0 /22
10.16.2.0 00001010 .00000100 .00000010 .0000000
0
10.16.3.0 00001010.
00000100 .00000011 .00000000
Summarised network 00001010.
00000100 .00000000 .00000000
Route summarizations for Area 2:
Subnets in doted Binary conversion Summarised Address

decimal /mask
10.16.4.0 00001010 .00000100 .
00000100 .00000000 10.16.4.0 /22
10.16.5.0 00001010 .00000100 .
00000101 .00000000
10.16.6.0 00001010. 00000100 .
00000110 .00000000
Summarised network 00001010. 00000100 .
00000100 .00000000
2. Configure the route summarization for area 1 (area 2) at the appropriate routers.
Command:
R2# config t
R2(config-router)# area 1 range 10.16.0.0 255.255.252.0
R5# config t
Page No.30 of 52
R5(config-router)# area 2 range 10.16.4.0 255.255.252.0
3. Use show ip route to verify that the route summarization is configured correctly.
Command:
R4# sh ip route

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

O IA 10.16.0.0/22 [110/129] via 10.16.5.1, 00:01:53, Serial0/1/1
O 10.16.6.0/24 [110/128] via 10.16.5.1, 00:19:33, Serial0/1/1
[110/128] via 10.16.4.2, 00:18:48, Serial0/1/0
C 10.16.4.0/24 is directly connected, Serial0/1/0
O IA 10.16.128.0/24 [110/65] via 10.16.5.1, 00:19:33, Serial0/1/1
R1# sh ip route


O 10.16.3.0/24 [110/128] via 10.16.2.1, 00:14:00, Serial0/1/1
O IA 10.16.4.0/22 [110/129] via 10.16.2.1, 00:00:21, Serial0/1/1
O IA 10.16.128.0/24 [110/65] via 10.16.2.1, 00:21:19, Serial0/1/1
Page No.31 of 52
Observation: After configuring summery address for area 1 and area2 in ABRs, R1 (in area1) is
getting summery address of area 2 routes and vice versa for R4.
4. Ping various routers in area 1 (area 2) to verify that PnR4 (PnR1) can reach all the networks
based on the summarized route entries at the routing table.
R1# ping 10.16.4.2

!!!!!
R1# ping 10.16.6.2

!!!!!
R1# ping 10.16.5.1

!!!!!
R1# ping 10.16.3.1

!!!!!
Observation: Pings from R1 to any destination of area 2 is successful.
5. Display the database of PnR4. Record the LSAs about the subnet in area 1. What is the
metric associated with the subnets in area 1. How this is metric devised.
Command:
Page No.32 of 52

LS age: 334
LS Type: Summary Links (Network)
Checksum: 0x47FD
Length: 28
Network Mask: /22
TOS: 0 Metric: 65

LS age: 1439
Checksum: 0x4EB3
Length: 28
Network Mask: /24
TOS: 0 Metric: 1
Observation: The R5 (10.16.128.5) advertises two summary LSAs, advertised for area0 having
cost 1 and for area 1 having cost 65 as highlighted above.
Answer to Step5:
The metric associated with the subnets in area 1 is 65 (Network Mask: /22, Metric: 65).
The Network Summary LSA advertised by R5 (10.16.128.5) which has Network Mask 22 and cost is
65. Here 65 = 64 +1 where 64 is the cost of serial link and 1 is the cost of Ethernet link associated
with R2.
6. Shut down the s0 interface of PnR2. Check the database again. Are there any changes on the
database? Why or why not?
Command:
R2# config t
R2(config)# interface s0/1/0
R2(config-if)# shutdown
Page No.33 of 52
R4#sh ip ospf database summary

LS age: 455
Checksum: 0x47FD
Length: 28
Network Mask: /22
TOS: 0 Metric: 65

LS age: 1560
Checksum: 0x4EB3
Length: 28
Network Mask: /24
TOS: 0 Metric: 1
Ans: There was no change in R4 (in area 2) summary LSA due to internal changes in area 1. Because
area 1 is summarized at R2. If any link goes down, R2 will keep sending the same summary without
change to area 2. So it will not affect database at another area.
Part IV: External Route
1. Ask your instructor to enable the core router external link. (To simulate External Links, you
can use Loop-Back interfaces)
Command:
R7# config t
R7(config)# interface loopback 0
Page No.34 of 52
R7(config-if)# ip address 200.200.200.200 255.255.255.0
R7(config-if)# exit
R7(config)# router rip
R7(config)# version 2
R7(config-router)# network 200.200.200.200
R7(config-router)# exit
R7(config-router)# redistribute rip subnets
2. Check if your interior routers have received the AS-External LSAs.
Command:
R1# show ip route

O E2 200.200.200.0/24 [110/20] via 10.16.2.1, 00:00:26, Serial0/1/1

O 10.16.3.0/24 [110/128] via 10.16.2.1, 00:05:45, Serial0/1/1
O IA 10.16.4.0/22 [110/129] via 10.16.2.1, 00:05:45, Serial0/1/1
O IA 10.16.128.0/24 [110/65] via 10.16.2.1, 00:05:45, Serial0/1/1
Observation: Interior router R1 has received the AS-External (LSA-5).
3. From the AS-External LSA, determine the router ID of the ASBR and the metric type.
Command:
R1# show ip ospf database external
Type-5 AS External Link States

LS age: 141
Page No.35 of 52
LS Type: AS External Link
Link State ID: 200.200.200.0 (External Network Number )
Checksum: 0x2381
Length: 36
Network Mask: /24
Metric Type: 2 (Larger than any link state path)
TOS: 0
Metric: 20
Forward Address: 0.0.0.0
External Route Tag: 0
Answer: The router ID of the ASBR is 10.16.128.7 and the Metric Type 2, (it is the default metric ,
the cost at any router is the cost advertised by the ASBR ).
4. Study the LSA database in an interior router; identify the LSAs used to determine the route
from the router to one of the external networks.
Command:

10.16.2.2 10.16.2.2 282 0x80000005 0x0043DE 3
10.16.3.1 10.16.3.1 1705 0x80000005 0x0055CB 3
10.16.128.2 10.16.128.2 423 0x80000009 0x0043CE 4

10.16.4.0 10.16.128.2 882 0x80000002 0x002B18
10.16.128.0 10.16.128.2 164 0x80000002 0x005EA5
Summary ASB Link States (Area 1)

10.16.128.7 10.16.128.2 105 0x80000001 0x000CF0
Link ID ADV Router Age Seq# Checksum Tag

200.200.200.0 10.16.128.7 110 0x80000001 0x002381 0
Page No.36 of 52
R1# sh ip ospf database external

LS age: 141
LS Type: AS External Link
Link State ID: 200.200.200.0 (External Network Number )
Checksum: 0x2381
Length: 36
Network Mask: /24
Metric Type: 2 (Larger than any link state path)
TOS: 0
Metric: 20
Forward Address: 0.0.0.0
External Route Tag: 0
R1# sh ip ospf database asbr-summary

LS age: 235
LS Type: Summary Links(AS Boundary Router)
Link State ID: 10.16.128.7 (AS Boundary Router address)
Checksum: 0xCF0
Length: 28
Network Mask: /0
TOS: 0 Metric: 1
Part V: Configuring Stub Areas
1. Record the size of the routing table in an interior router.
Command:
R1# sh ip route
Page No.37 of 52
O E2 200.200.200.0/24 [110/20] via 10.16.2.1, 00:00:26, Serial0/1/1

O 10.16.3.0/24 [110/128] via 10.16.2.1, 00:05:45, Serial0/1/1
O IA 10.16.4.0/22 [110/129] via 10.16.2.1, 00:05:45, Serial0/1/1
O IA 10.16.128.0/24 [110/65] via 10.16.2.1, 00:05:45, Serial0/1/1
2. Configure areas 1 and 2 as stub areas.
Configuring Stub Area:
Configuration R1, R2 and R3(for area 1) Configuration R4, R5 and R6(for area 2)
R1# config t R4# config t
R1(config)# router ospf 1 R4(config)# router ospf 1
R1(config-router)# area 1 stub R4(config-router)# area 2 stub
3. Use show ip ospf command to verify the configuration.
Command:
R1# sh ip ospf

Start time: 00:32:38.040, Time elapsed: 00:45:37.256
Supports only single TOS(TOS0) routes
Supports opaque LSA
Supports area transit capability
Router is not originating router-LSAs with maximum metric
Initial SPF schedule delay 5000 msecs
Minimum hold time between two consecutive SPFs 10000 msecs
Maximum wait time between two consecutive SPFs 10000 msecs
Incremental-SPF disabled
Minimum LSA interval 5 secs
Page No.38 of 52
Minimum LSA arrival 1000 msecs
LSA group pacing timer 240 secs
Interface flood pacing timer 33 msecs
Retransmission pacing timer 66 msecs
Number of external LSA 0. Checksum Sum 0x000000
Number of opaque AS LSA 0. Checksum Sum 0x000000
Number of DCbitless external and opaque AS LSA 0
Number of DoNotAge external and opaque AS LSA 0
Number of areas transit capable is 0
External flood list length 0
Area 1
It is a stub area
Area ranges are
Number of LSA 6. Checksum Sum 0x022511
Flood list length 0
R4# sh ip ospf

Supports opaque LSA
Page No.39 of 52
Area 2
It is a stub area
Area ranges are
Number of LSA 6. Checksum Sum 0x022CB9
Flood list length 0
4. Display the LSA database of the interior router. What types of LSAs are missing in
compared with the database before the stub-area configuration.
Before configuring area 1 stub After configuring area 1 stub

R1# sh ip ospf database R1# sh ip ospf database
OSPF Router with ID (10.16.2.2) (Process OSPF Router with ID (10.16.2.2) (Process
ID 1) ID 1)
Router Link States (Area 1) Router Link States (Area 1)
Link ID ADV Router Age Seq# Link ID ADV Router Age Seq#
Checksum Link count Checksum Link count
10.16.2.2 10.16.2.2 282 0x80000005 10.16.2.2 10.16.2.2 252 0x80000007
0x0043DE 3 0x005DC4 3
10.16.3.1 10.16.3.1 1705 0x80000005 10.16.3.1 10.16.3.1 248
0x0055CB 3 0x8000000A 0x0069B4 3
10.16.128.2 10.16.128.2 423 0x80000009 10.16.128.2 10.16.128.2 246 0x80000010
0x0043CE 4 0x0053B9 4
Summary Net Link States (Area 1) Summary Net Link States (Area 1)
Link ID ADV Router Age Seq# Link ID ADV Router Age Seq#
Checksum Checksum
10.16.4.0 10.16.128.2 882 0x80000002 0.0.0.0 10.16.128.2 256 0x80000001
0x002B18 0x00475A
10.16.128.0 10.16.128.2 164 0x80000002 10.16.4.0 10.16.128.2 256 0x80000003
Page No.40 of 52
0x005EA5 0x0047FC
10.16.128.0 10.16.128.2 256 0x80000003
Summary ASB Link States (Area 1) 0x007A8A
Link ID ADV Router Age Seq#

Checksum
10.16.128.7 10.16.128.2 105 0x80000001
0x000CF0
Link ID ADV Router Age Seq#

Checksum Tag
200.200.200.0 10.16.128.7 110
0x80000001 0x002381 0
Ans: AS-External LSA (LSA-5) and summary ASB LSA (LSA-4) were missing in the LSA
database.
5. Display the routing table of the interior router. Comment the difference between the routing
table before and after the stub-area configuration.
Command:
R1# sh ip route

Gateway of last resort is 10.16.2.1 to network 0.0.0.0

O 10.16.3.0/24 [110/128] via 10.16.2.1, 00:06:32, Serial0/1/1
O IA 10.16.4.0/22 [110/129] via 10.16.2.1, 00:06:32, Serial0/1/1
O IA 10.16.128.0/24 [110/65] via 10.16.2.1, 00:06:32, Serial0/1/1
O*IA 0.0.0.0/0 [110/65] via 10.16.2.1, 00:06:32, Serial0/1/1
Ans: At the internal router of stub area, external route were missing and default route was added in
stead.
Page No.41 of 52
Part VI: Configuring Totally Stubby Areas
1. Record the summary LSA (LSA type 3) and routing table of an interior router.
Command:

LS age: 482
Checksum: 0x475A
Length: 28
Network Mask: /0
TOS: 0 Metric: 1

LS age: 482
Checksum: 0x47FC
Length: 28
Network Mask: /22
TOS: 0 Metric: 65

LS age: 484
Checksum: 0x7A8A
Length: 28
Page No.42 of 52
Network Mask: /24
TOS: 0 Metric: 1
R1# sh ip route


O 10.16.3.0/24 [110/128] via 10.16.2.1, 00:06:32, Serial0/1/1
O IA 10.16.4.0/22 [110/129] via 10.16.2.1, 00:06:32, Serial0/1/1
O IA 10.16.128.0/24 [110/65] via 10.16.2.1, 00:06:32, Serial0/1/1
O*IA 0.0.0.0/0 [110/65] via 10.16.2.1, 00:06:32, Serial0/1/1
Observation: There was no difference in OSPF summary database as it was advertised by R2 about
networks of area 0 and area 2.
2. Disable the s0 interface of PnR2. Display the summary LSAs again. Note the difference
between the new and old LSAs and routing tables.
Command:
R2(config-if)# interface s0/1/0

LS age: 639
Page No.43 of 52
Checksum: 0x475A
Length: 28
Network Mask: /0
TOS: 0 Metric: 1
LS age: 639
Checksum: 0x47FC
Length: 28
Network Mask: /22
TOS: 0 Metric: 65
LS age: 640
Checksum: 0x7A8A
Length: 28
Network Mask: /24
TOS: 0 Metric: 1
R1# sh ip route

O 10.16.3.0/24 [110/128] via 10.16.2.1, 00:06:32, Serial0/1/1
O IA 10.16.4.0/22 [110/129] via 10.16.2.1, 00:06:32, Serial0/1/1
O IA 10.16.128.0/24 [110/65] via 10.16.2.1, 00:06:32, Serial0/1/1
O*IA 0.0.0.0/0 [110/65] via 10.16.2.1, 00:06:32, Serial0/1/1
Page No.44 of 52
Observation: In routing table of R1, directly connected network 10.16.2.0/24 is missing. There was
no difference in OSPF summary database as it was advertised by R2 about networks of area 0 and
area 2.
3. Configure areas 1 and 2 as totally stubby areas.
Configuration at R2 Configuration at R5
R2# config t R5# config t
R2(config-router)# area 1 stub no-summary R5(config-router)# area 2 stub no-summary
4. Use show ip ospf command to verify the configuration.

Command:
R1# sh ip ospf

Supports opaque LSA
Area 1
It is a stub area
Page No.45 of 52
Area ranges are
Number of LSA 4. Checksum Sum 0x015691
Flood list length 0

10.16.2.2 10.16.2.2 39 0x80000009 0x0059C6 3
10.16.3.1 10.16.3.1 902 0x8000000A 0x0069B4 3
10.16.128.2 10.16.128.2 40 0x80000013 0x004DBC 4

0.0.0.0 10.16.128.2 179 0x80000002 0x00455B
Observation: From output it is observed that R1 (under area 1, a stubby area) it has no inter area
summary, only has the default route.
5. How is the routing table compared with the routing table before the totally stubby-area
configuration?
Command:
R1# sh ip route

Page No.46 of 52
O 10.16.3.0 [110/128] via 10.16.2.1, 00:00:02, Serial0/1/1
O*IA 0.0.0.0/0 [110/65] via 10.16.2.1, 00:00:02, Serial0/1/1
Ans : The stubby area has inter-area routes and a default route for others. But totally stubby area
router did not have any inter area routes, it had only default route for other routes.
6. Now enable and disable the s0 interface of PnR2. Did you see any changes in the LSA
database and the routing table of the router?
Command:
R2# config t
R2(config)# interface s0/1/0
R2(config-if)# no shut
Observation: We have enabled and disabled s0/1/0 of R2 and observed that when the link is
enabled, on R2 the LSA database, the link count for link id 10.16.2.2 and 10.16.128.2 will be 4 and
10.16.2.0 network exists in routing table of R2. When the s0/1/0 of R2 is disabled, link count for
link id 10.16.2.2 and 10.16.128.2 will be 2 and in the routing table there is no entry for 10.16.2.2.
Part VII: Configuring Virtual Link
1. Configure Router PnR1 and PnR3 to make subnet 10.n.1.0/24 belong to area 3.
Command:
R1# config t
R3# config t
Verification of the configuration:
Command:
Page No.47 of 52
Se0/1/1 1 1 10.16.2.2/24 64 P2P 1/1
Se0/1/0 1 3 10.16.1.1/24 64 P2P 0/0

Se0/1/0 1 1 10.16.3.1/24 64 P2P 1/1
Se0/1/1 1 3 10.16.1.1/24 64 P2P 0/0
Note: before configuring this part, we have deleted the sub area / totally stubby area from all the
routers where it was configured.
2. Display the routing table to verify that the route to 10.n.1.0/24 is unknown to other routers.
Command:
R4# sh ip route

O E2 200.200.200.0/24 [110/20] via 10.16.5.1, 00:01:48, Serial0/1/1

O IA 10.16.2.0 [110/129] via 10.16.5.1, 00:01:48, Serial0/1/1
O IA 10.16.3.0 [110/129] via 10.16.5.1, 00:01:48, Serial0/1/1
O 10.16.6.0 [110/128] via 10.16.5.1, 00:01:58, Serial0/1/1
[110/128] via 10.16.4.2, 00:02:41, Serial0/1/0
O IA 10.16.128.0 [110/65] via 10.16.5.1, 00:01:49, Serial0/1/1
R2# sh ip route

Page No.48 of 52
O E2 200.200.200.0/24 [110/20] via 10.16.128.7, 00:04:24, FastEthernet0/0

O IA 10.16.6.0 [110/65] via 10.16.128.5, 00:02:36, FastEthernet0/0
C 10.16.128.0 is directly connected, FastEthernet0/0
Observation: The routing table of the other routers, there exist no entry for the subnet 10.16.1.0.
3. Configure a virtual link between Routers PnR1 and PnR2.
Virtual link configuration between area3 to area 0:
Configuration at R1 Configuration at R2
R1(config-router)# area 1 virtual-link 10.16.128.2 R2(config-router)# area 1 virtual-link 10.16.2.2
4. Display the routing table to verify that route 10.n.1.0/24 is now known to the other routers.
Command:
R2# sh ip route
O E2 200.200.200.0/24 [110/20] via 10.16.128.7, 00:07:54, FastEthernet0/0

O IA 10.16.1.0 [110/128] via 10.16.2.2, 00:00:43, Serial0/1/0
Page No.49 of 52
C 10.16.128.0 is directly connected, FastEthernet0/0
R4# sh ip route

O E2 200.200.200.0/24 [110/20] via 10.16.5.1, 00:06:27, Serial0/1/1

O IA 10.16.2.0 [110/129] via 10.16.5.1, 00:06:27, Serial0/1/1
O IA 10.16.3.0 [110/129] via 10.16.5.1, 00:06:27, Serial0/1/1
O IA 10.16.1.0 [110/193] via 10.16.5.1, 00:00:55, Serial0/1/1
O 10.16.6.0 [110/128] via 10.16.5.1, 00:06:37, Serial0/1/1
[110/128] via 10.16.4.2, 00:07:20, Serial0/1/0
O IA 10.16.128.0 [110/65] via 10.16.5.1, 00:06:27, Serial0/1/1
Observation: After configuring Virtual link, the area3 is logically connected to backbone area and
all the routers from different area can reach the network 10.16.1.0.
5. Use show ip ospf database to display and analyze the link-state databases of PnR1. Which
areas does PnR1 belong to?
Command:

10.16.2.2 10.16.2.2 168 0x80000002 0x00DF19 1
10.16.128.2 10.16.128.2 1 (DNA) 0x80000013 0x001903 2
10.16.128.5 10.16.128.5 326 (DNA) 0x8000000A 0x00F2B5 1
10.16.128.7 10.16.128.7 1398 (DNA) 0x80000012 0x00E1B7 1
Page No.50 of 52
10.16.128.7 10.16.128.7 329 (DNA) 0x8000000E 0x00D334

10.16.1.0 10.16.2.2 224 0x80000001 0x00C8FA
10.16.2.0 10.16.2.2 224 0x80000001 0x00BD05
10.16.2.0 10.16.128.2 436 (DNA) 0x80000001 0x0048FB
10.16.3.0 10.16.2.2 224 0x80000001 0x00354C
10.16.3.0 10.16.128.2 436 (DNA) 0x80000001 0x003D06
10.16.4.0 10.16.128.5 324 (DNA) 0x80000004 0x009C5F
10.16.5.0 10.16.128.5 329 (DNA) 0x80000001 0x001529
10.16.6.0 10.16.128.5 329 (DNA) 0x80000001 0x000A33

10.16.2.2 10.16.2.2 171 0x80000004 0x00DBAD 2
10.16.3.1 10.16.3.1 613 0x80000002 0x00E2AC 2
10.16.128.2 10.16.128.2 172 0x80000002 0x005DB7 4

10.16.1.0 10.16.2.2 227 0x80000001 0x00C8FA
10.16.4.0 10.16.128.2 491 0x80000001 0x00BE42
10.16.5.0 10.16.128.2 491 0x80000001 0x00310F
10.16.6.0 10.16.128.2 491 0x80000001 0x002619
10.16.128.0 10.16.128.2 598 0x80000001 0x0060A4

10.16.128.7 10.16.2.2 167 0x80000001 0x000437
10.16.128.7 10.16.128.2 599 0x80000001 0x000CF0

10.16.2.2 10.16.2.2 227 0x80000002 0x00DBBD 1
Page No.51 of 52
10.16.2.0 10.16.2.2 227 0x80000001 0x00BD05
10.16.3.0 10.16.2.2 227 0x80000001 0x00354C
10.16.4.0 10.16.2.2 167 0x80000001 0x00B688
10.16.5.0 10.16.2.2 167 0x80000001 0x002955
10.16.6.0 10.16.2.2 167 0x80000001 0x001E5F
10.16.128.0 10.16.2.2 167 0x80000001 0x0058EA

10.16.128.7 10.16.2.2 167 0x80000001 0x000437
Link ID ADV Router Age Seq# Checksum Tag

200.200.200.0 10.16.128.7 1571 0x80000002 0x002182 0
Analyzing link-state databases of R1: R1 is connected three different areas having following
LSAs:
Area Name of the LSA LSA

Type
Area 0 Router LSA 1
Network LSA 2
Summary LSA 3
Area 1 Router LSA 1
Summary LSA 3
Summary ASB LSA 4
Area 3 Router LSA 1
Summary LSA 3
Summary ASB LSA 4
AS External LSA 5
Area belongs to R1:
R1 is belonging to area 1(physically connected) area 3(physically connected) and area0 (connected
via virtual link). From the “sh ip ospf database” we have also observed that.
Conclusion
Page No.52 of 52
In this lab we have observed how the IP Routing Protocol, OSPF works. There are many significant
differences between IP Routing Protocol EIGRP and the OSPF. Every router in OSPF area maintains
a synchronized database which allows it to maintain a loop free routing. Moreover, several other
important features have allowed OSPF to become an outstanding IP Routing Protocol.
Page No.53 of 52

01 OSPF LAB Solution

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

01 OSPF LAB Solution

Uploaded by

Copyright:

Available Formats

Course Number

Part I. Configuring OSPF with Single Area ..……………………………………….. 3

Part II. Configuring a Multi-Area Routing Domain ......…………………………….. 21

Part III. Configuring Route Summarization ……….......……………………………. 30

Part IV. External Route …………………………….......……………………………. 35

Part V. Configuring Stub Areas ……………………......……………………………. 37

Part VI. Configuring Totally Stubby Areas ..………......……………………………. 41

Part VII. Configuring Virtual Link …………………......…………………………… 47

Part I: Configuring OSPF with Single Area

Physical Network Topology:

2. Set the bandwidth of the serial line to 1.544 Mbps.

3. Configure OSPF with single area (area 0) at your routers.

Design, Discussion and configuration for step 1-3:

Running configuration of R1 Running configuration of R2

R7#sh frame-relay route

Input Intf Input Dlci Output Intf Output Dlci Status

R1# ping 10.16.6.1

Type escape sequence to abort.

R1# ping 10.16.5.2

Type escape sequence to abort.

Our topology has been configured successfully.

R1# show ip protocols

Routing Protocol is "ospf 1"

Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP

Gateway of last resort is not set

10.0.0.0/24 is subnetted, 7 subnets

R1# sh ip ospf interface

Serial0/1/1 is up, line protocol is up

• How many interface are configured for OSPF?

• How often are hello packets initiated?

Hello interval is configurable

R1(config-if)# ip ospf hello-interval <value in sec>

Dead interval is configurable

R1(config-if)# ip ospf dead-interval <value in sec>

R1# show ip ospf neighbor detail

Neighbor 10.16.3.1, interface address 10.16.1.2

• How many neighbors do you have?

• What are your neighbors’ routers IDs?

R1(config)# router ospf 1

R2# sh ip ospf neighbor

R1# show ip ospf database

OSPF Router with ID (10.16.2.2) (Process ID 1)

Router Link States (Area 0)

Link ID ADV Router Age Seq# Checksum Link count

Net Link States (Area 0)

Link ID ADV Router Age Seq# Checksum

R1# sh ip ospf database router

LS age: 472 Link connected to: another Router (point-to-

LS age: 327 LS age: 440

R1# sh ip ospf database network

OSPF Router with ID (10.16.2.2) (Process ID 1)

Net Link States (Area 0)

Routing Bit Set on this LSA

Verify the computation from routing table:

Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP

Gateway of last resort is not set

10.0.0.0/24 is subnetted, 7 subnets

Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP

10.0.0.0/24 is subnetted, 7 subnets

Link connected to: another Router (point-to-point)

Link connected to: another Router (point-to-point)

Adv Router is not-reachable Link connected to: another Router (point-to-point)