Troubleshoo*ng OSPF

Topology

Ini+al Configura+on Commands``

R1:

enable
conf t
logging console
host R1
no ip domain-lookup
line con 0
exec-timeout 0 0
logging synchronous
int gig 0/1
ip address 192.168.1.1 255.255.255.0
ipv6 address 2000:1::1/64
no shutdown
int gig 0/2
ip address 192.0.2.1 255.255.255.252
ip address 192.0.2.1 255.255.255.252
ip mtu 1478
ip ospf 1 area 0
ipv6 address 2000:2::1/64
no shutdown
router ospf 1
passive-interface GigabitEthernet0/1
network 192.168.1.0 0.0.0.255 area 0

Copyright 2024, Kevin Wallace Training, LLC

end
copy run star

R2:

enable
conf t
logging console
host R2
no ip domain-lookup
line con 0
exec-timeout 0 0
logging synchronous
int gig 0/1
ip address 192.0.2.2 255.255.255.252
ip ospf hello-interval 20
ipv6 address 2000:2::2/64
no shutdown
int gig 0/2
ip address 203.0.113.1 255.255.255.252
ipv6 address 2000:3::1/64
no shutdown
router ospf 2
network 192.0.2.0 0.0.0.3 area 0
network 203.0.113.0 0.0.0.3 area 1
end
copy run star

R3:

enable
conf t
logging console
host R3
no ip domain-lookup
line con 0
exec-timeout 0 0
logging synchronous
int gig 0/1
ip address 203.0.113.2 255.255.255.252

Copyright 2024, Kevin Wallace Training, LLC

ipv6 address 2000:3::2/64
no shutdown
int gig 0/2
ip address 172.16.1.1 255.255.255.0
ipv6 address 2000:4::1/64
no shutdown
router ospf 1
passive-interface GigabitEthernet0/1
network 0.0.0.0 255.255.255.255 area 0
end
copy run star

Troubleshoo+ng Challenge

• None of the routers are learning OSPF routes.

• Examine and correct the exisFng OSPF configuraFon on each router such that each
router has full visibility to all networks.

Solu+on

Step 1: Let’s begin by making sure we’re correctly interpreFng the issue and that we cannot see
any OSPF-learned routes on any of our routers.

R1:
R1#show ip route
Codes: L - local, 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, H - NHRP, l - LISP
a - application route
+ - replicated route, % - next hop override, p - overrides from PfR

Gateway of last resort is not set

192.0.2.0/24 is variably subnetted, 2 subnets, 2 masks

C 192.0.2.0/30 is directly connected, GigabitEthernet0/2
L 192.0.2.1/32 is directly connected, GigabitEthernet0/2
192.168.1.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.1.0/24 is directly connected, GigabitEthernet0/1
L 192.168.1.1/32 is directly connected, GigabitEthernet0/1
R1#

R2:
R2#show ip route

Copyright 2024, Kevin Wallace Training, LLC

Codes: L - local, 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, H - NHRP, l - LISP
a - application route
+ - replicated route, % - next hop override, p - overrides from PfR

Gateway of last resort is not set

192.0.2.0/24 is variably subnetted, 2 subnets, 2 masks

C 192.0.2.0/30 is directly connected, GigabitEthernet0/1
L 192.0.2.2/32 is directly connected, GigabitEthernet0/1
203.0.113.0/24 is variably subnetted, 2 subnets, 2 masks
C 203.0.113.0/30 is directly connected, GigabitEthernet0/2
L 203.0.113.1/32 is directly connected, GigabitEthernet0/2
R2#

R3:
R3#show ip route
Codes: L - local, 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, H - NHRP, l - LISP
a - application route
+ - replicated route, % - next hop override, p - overrides from PfR

Gateway of last resort is not set

172.16.0.0/16 is variably subnetted, 2 subnets, 2 masks

C 172.16.1.0/24 is directly connected, GigabitEthernet0/2
L 172.16.1.1/32 is directly connected, GigabitEthernet0/2
203.0.113.0/24 is variably subnetted, 2 subnets, 2 masks
C 203.0.113.0/30 is directly connected, GigabitEthernet0/1
L 203.0.113.2/32 is directly connected, GigabitEthernet0/1
R3#

The output from the show ip route command indicates we haven’t learned any routes via
OSPF, or any other rouFng protocol.

Step 2: To begin our troubleshooFng, let’s make sure that OSPF is indeed configured on R1.

R1:
R1#show ip protocols
*** IP Routing is NSF aware ***

Routing Protocol is "application"

Sending updates every 0 seconds
Invalid after 0 seconds, hold down 0, flushed after 0
Outgoing update filter list for all interfaces is not set

Copyright 2024, Kevin Wallace Training, LLC

 Incoming update filter list for all interfaces is not set
Maximum path: 32
Routing for Networks:
Routing Information Sources:
Gateway Distance Last Update
Distance: (default is 4)

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 192.168.1.1
Number of areas in this router is 1. 1 normal 0 stub 0 nssa
Maximum path: 4
Routing for Networks:
192.168.1.0 0.0.0.255 area 0
Routing on Interfaces Configured Explicitly (Area 0):
GigabitEthernet0/2
Passive Interface(s):
GigabitEthernet0/1
Routing Information Sources:
Gateway Distance Last Update
Distance: (default is 110)

R1#

Let’s get a closer look at our OSPF configuraFon by examining our running configuraFon.

R1#show run | s router ospf

router ospf 1
passive-interface GigabitEthernet0/1
network 192.168.1.0 0.0.0.255 area 0
R1#

We see that interface Gig 0/1 is a passive interface. Is that ok?

Yes. Since we aren’t trying to form an OSPF neighborship off of interface Gig 0/1, we can make it
a passive interface to suppress the sending of OSPF Hello messages, while sFll adverFsing the
network off of Gig 0/1 via OSPF to any neighbors that we do have.

Also, noFce that we have a single network statement, that’s adverFsing the network off of Gig
0/1. There’s not a network statement that’s used to adverFse the network off of Gig 0/1. Is that
a problem?

Not necessarily. We could tell an interface to parFcipate in OSPF. Let’s see if that’s the case
here.

R1#show run | s interface

interface GigabitEthernet0/0
no ip address

Copyright 2024, Kevin Wallace Training, LLC

 shutdown
duplex auto
speed auto
media-type rj45
interface GigabitEthernet0/1
ip address 192.168.1.1 255.255.255.0
duplex auto
speed auto
media-type rj45
ipv6 address 2000:1::1/64
interface GigabitEthernet0/2
ip address 192.0.2.1 255.255.255.252
ip mtu 1478
ip ospf 1 area 0
duplex auto
speed auto
media-type rj45
ipv6 address 2000:2::1/64
interface GigabitEthernet0/3
no ip address
shutdown
duplex auto
speed auto
media-type rj45
passive-interface GigabitEthernet0/1
R1#

From the output, we see that we’re telling interface Gig 0/2 that we want it to parFcipate in
OSPF process ID 1 as a member of area 0, which means we’re going to adverFse the network off
of this interface (i.e., 192.0.2.0 /30) via OSPF.

Step 3: Now that we’ve confirmed that OSPF is configured ton router R1, let’s check out router
R2.

R2:
R2#show ip protocols
*** IP Routing is NSF aware ***

Routing Protocol is "application"

Sending updates every 0 seconds
Invalid after 0 seconds, hold down 0, flushed after 0
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Maximum path: 32
Routing for Networks:
Routing Information Sources:
Gateway Distance Last Update
Distance: (default is 4)

Copyright 2024, Kevin Wallace Training, LLC

Routing Protocol is "ospf 2"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Router ID 203.0.113.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:
192.0.2.0 0.0.0.3 area 0
203.0.113.0 0.0.0.3 area 1
Routing Information Sources:
Gateway Distance Last Update
Distance: (default is 110)

R2#

This output shows us that router R2’s OSPF configuraFon is using Process ID 2, while router R1’s
OSPF configuraFon is using Process ID 1. Is that a problem?

Actually, no. Unlike EIGRP Autonomous System numbers, with OSPF, Process IDs are locally-
significant and don’t need to match on neighboring routers.

Let’s make sure we’re adverFsing the two networks connected to router R2 via OSPF.

R2#show run | s router

router ospf 2
network 192.0.2.0 0.0.0.3 area 0
network 203.0.113.0 0.0.0.3 area 1
R2#

Next, let us examine the OSPF configuraFon of router R3.

Step 4: Next, let us examine the OSPF configuraFon of router R3.

R3:
R3#show ip protocols
*** IP Routing is NSF aware ***

Routing Protocol is "application"

Sending updates every 0 seconds
Invalid after 0 seconds, hold down 0, flushed after 0
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Maximum path: 32
Routing for Networks:
Routing Information Sources:
Gateway Distance Last Update
Distance: (default is 4)

Copyright 2024, Kevin Wallace Training, LLC

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 203.0.113.2
Number of areas in this router is 1. 1 normal 0 stub 0 nssa
Maximum path: 4
Routing for Networks:
0.0.0.0 255.255.255.255 area 0
Passive Interface(s):
GigabitEthernet0/1
Routing Information Sources:
Gateway Distance Last Update
Distance: (default is 110)

R3#show run | s router

router ospf 1
passive-interface GigabitEthernet0/1
network 0.0.0.0 255.255.255.255 area 0
R3#

Output from these commands indicates we are running OSPF Process ID 1, but we’re only using
a single network statement. Is that an issue?

No, it’s not. The reason is, the network statement isn’t actually telling OSPF to adverFse the
specified network. Rather that network statement is specifying an IP address space, and if
that router has an interface that is up and has an IP address that falls within the specified
address space, then OSPF should adverFse the network connected to that interface.

In this case, the network statement is specifying an IP address space that encompasses all
IPv4 addresses. Therefore, the IP addresses of both interface Gig 0/1 and interface Gig 0/2 fall
within that address space (of all possible IPv4 addresses). As a result, OSPF is being told to
adverFse the networks connected to each interface.

However, there is an issue with this configuraFon. Even though we do have an opportunity for
router R3 to have a passive interface, that passive interface should be off of Gig 0/2, not Gig
0/1. So, that passive-interface statement would prevent R3 from forming a
neighborship with R2.

Let’s fix that.

R3#conf term
R3(config)#router ospf 1
R3(config-router)#no passive-interface GigabitEthernet0/1
R3(config-router)#passive-interface gig 0/2
R3(config-router)#end
R3#

Now, let’s see if we’ve formed, or are in the process of forming, an OSPF neighborship with R2.

Copyright 2024, Kevin Wallace Training, LLC

R3#show ip ospf neighbor
R3#

No, we’re not. Next, let’s take a look at the running configuraFon to see if we spot anything
suspicious.

R3#show run | s interface

interface GigabitEthernet0/0
no ip address
shutdown
duplex auto
speed auto
media-type rj45
interface GigabitEthernet0/1
ip address 203.0.113.2 255.255.255.252
duplex auto
speed auto
media-type rj45
ipv6 address 2000:3::2/64
interface GigabitEthernet0/2
ip address 172.16.1.1 255.255.255.0
duplex auto
speed auto
media-type rj45
ipv6 address 2000:4::1/64
interface GigabitEthernet0/3
no ip address
shutdown
duplex auto
speed auto
media-type rj45
passive-interface GigabitEthernet0/2
R3#

Step 5: Everything looks normal there, so let’s go back to router R2 and take a closer look at its
configuraFon.

R2:
R2#
*Nov 6 19:18:50.595: %OSPF-4-ERRRCV: Received invalid packet:
mismatched area ID from backbone area from 203.0.113.2,
GigabitEthernet0/2
R2#
*Nov 6 19:18:59.787: %OSPF-4-ERRRCV: Received invalid packet:
mismatched area ID from backbone area from 203.0.113.2,
GigabitEthernet0/2
R2#

Copyright 2024, Kevin Wallace Training, LLC

As soon as we go back to router R2, we see a series of Syslog error messages indicaFng that we
have an Area mismatch between R2 and R3. According to our topology, interface Gig 0/2 on R2
and interface Gig 0/1 on R3 should be in Area 1. Let’s make sure the network off of Gig 0/2 on
R2 is indeed configured for Area 1.

R2#show run | s router

router ospf 2
network 192.0.2.0 0.0.0.3 area 0
network 203.0.113.0 0.0.0.3 area 1
R2#

Step 6: Things seem to be correctly configured on R2. Let’s see if that’s the case for router R3.

R3:
R3#show run | s router
router ospf 1
passive-interface GigabitEthernet0/2
network 0.0.0.0 255.255.255.255 area 0
R3#

And now we’ve spo]ed our second issue. Specifically, the network statement in R3’s OSPF
configuraFon is specifying Area 0 rather than Area 1.

Let’s fix that.

R3#conf term
R3(config)#router ospf 1
R3(config-router)#no network 0.0.0.0 255.255.255.255 area 0
R3(config-router)#network 0.0.0.0 255.255.255.255 area 1
R3(config-router)#end
R3#
*Nov 6 19:26:46.929: %SYS-5-CONFIG_I: Configured from console by
console
R3#
*Nov 6 19:26:48.517: %OSPF-5-ADJCHG: Process 1, Nbr 203.0.113.1 on
GigabitEthernet0/1 from LOADING to FULL, Loading Done
R3#

We seem to now have an OSPF neighborship between R3 and R2. Let’s confirm that.

R3#show ip ospf neighbor

Neighbor ID Pri State Dead Time Address Interface

203.0.113.1 1 FULL/DR 00:00:36 203.0.113.1 GigabitEthernet0/1
R3#
R3#show ip route
Codes: L - local, 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

Copyright 2024, Kevin Wallace Training, LLC

 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, H - NHRP, l - LISP
a - application route
+ - replicated route, % - next hop override, p - overrides from PfR

Gateway of last resort is not set

172.16.0.0/16 is variably subnetted, 2 subnets, 2 masks

C 172.16.1.0/24 is directly connected, GigabitEthernet0/2
L 172.16.1.1/32 is directly connected, GigabitEthernet0/2
192.0.2.0/30 is subnetted, 1 subnets
O IA 192.0.2.0 [110/2] via 203.0.113.1, 00:06:10, GigabitEthernet0/1
203.0.113.0/24 is variably subnetted, 2 subnets, 2 masks
C 203.0.113.0/30 is directly connected, GigabitEthernet0/1
L 203.0.113.2/32 is directly connected, GigabitEthernet0/1
R3#

Great news! R3 has not only formed a neighborship with R2, R3 has learned about the OSPF
Inter Area route of 192.0.2.0 /30.

Step 7: Now that we have an OSPF neighborship between R2 and R3, and we’re able to
exchange OSPF routes, let’s go back to R2 and troubleshoot is connecFon with R1.

To begin, let’s take a closer look at the OSPF configuraFon for the interface connecFng over to
R1.

R2:
R2#show ip ospf interface gig 0/1
GigabitEthernet0/1 is up, line protocol is up
Internet Address 192.0.2.2/30, Area 0, Attached via Network
Statement
Process ID 2, Router ID 203.0.113.1, Network Type BROADCAST, Cost: 1
Topology-MTID Cost Disabled Shutdown Topology Name
0 1 no no Base
Transmit Delay is 1 sec, State DR, Priority 1
Designated Router (ID) 203.0.113.1, Interface address 192.0.2.2
No backup designated router on this network
Timer intervals configured, Hello 20, Dead 80, Wait 80, Retransmit 5
oob-resync timeout 80
Hello due in 00:00:06
Supports Link-local Signaling (LLS)
Cisco NSF helper support enabled
IETF NSF helper support enabled
Index 1/1/1, flood queue length 0
Next 0x0(0)/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)
R2#

Copyright 2024, Kevin Wallace Training, LLC

NoFce that we have a non-default Hello Fmer (and therefor a non-default Dead Fmer) for
interface Gig 0/1. Normally, the Hello Fmer would be 10 seconds, not 20 seconds, and Fmers
need to match between OSPF neighbors.

Let’s check to see if we have a non-default Fmer configured, and if we do, let’s fix it.

R2#show run | s interface

interface GigabitEthernet0/0
no ip address
shutdown
duplex auto
speed auto
media-type rj45
interface GigabitEthernet0/1
ip address 192.0.2.2 255.255.255.252
ip ospf hello-interval 20
duplex auto
speed auto
media-type rj45
ipv6 address 2000:2::2/64
interface GigabitEthernet0/2
ip address 203.0.113.1 255.255.255.252
duplex auto
speed auto
media-type rj45
ipv6 address 2000:3::1/64
interface GigabitEthernet0/3
no ip address
shutdown
duplex auto
speed auto
media-type rj45
R2#
R2#conf t
Enter configuration commands, one per line. End with CNTL/Z.
R2(config)#int gig 0/1
R2(config-if)#ip ospf hello-interval 10
R2(config-if)#end
R2#
*Nov 6 19:43:40.438: %SYS-5-CONFIG_I: Configured from console by console
R2#show ip ospf interface gig 0/1
GigabitEthernet0/1 is up, line protocol is up
Internet Address 192.0.2.2/30, Area 0, Attached via Network Statement
Process ID 2, Router ID 203.0.113.1, Network Type BROADCAST, Cost: 1
Topology-MTID Cost Disabled Shutdown Topology Name
0 1 no no Base
Transmit Delay is 1 sec, State DR, Priority 1
Designated Router (ID) 203.0.113.1, Interface address 192.0.2.2
Backup Designated router (ID) 192.168.1.1, Interface address 192.0.2.1
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
oob-resync timeout 40
Hello due in 00:00:04
Supports Link-local Signaling (LLS)
Cisco NSF helper support enabled
IETF NSF helper support enabled
Index 1/1/1, flood queue length 0
Next 0x0(0)/0x0(0)/0x0(0)
Last flood scan length is 0, maximum is 0
Last flood scan time is 0 msec, maximum is 0 msec

Copyright 2024, Kevin Wallace Training, LLC

 Neighbor Count is 1, Adjacent neighbor count is 0
Suppress hello for 0 neighbor(s)
R2#show ip ospf neigh

Neighbor ID Pri State Dead Time Address Interface

192.168.1.1 1 EXSTART/BDR 00:00:39 192.0.2.1 GigabitEthernet0/1
203.0.113.2 1 FULL/BDR 00:00:34 203.0.113.2 GigabitEthernet0/2
R2#

We’ve fixed the Fmer, and we’re a]empFng to form a neighborship with R1, but we appear to
be stuck in the EXSTART state. That’s o`en an indicaFon of a mismatched Maximum
Transmission Unit (MTU) value.
R2#show ip int gig 0/1
GigabitEthernet0/1 is up, line protocol is up
Internet address is 192.0.2.2/30
Broadcast address is 255.255.255.255
Address determined by setup command
MTU is 1500 bytes
Helper address is not set
...OUTPUT OMITTED...

It looks like we have a default MTU of 1500 Bytes on the R2 side of the connecFon. So, let’s
check out R1.

Step 8: It looks like we have a default MTU of 1500 Bytes on the R2 side of the connecFon. So,
let’s check out R1.

R1:
R1#show ip int gig 0/2
GigabitEthernet0/2 is up, line protocol is up
Internet address is 192.0.2.1/30
Broadcast address is 255.255.255.255
Address determined by setup command
MTU is 1478 bytes
Helper address is not set
...OUTPUT OMITTED...

It appears that router R1’s Gig 0/2 interface has a non-default MTU, and the MTU values must
match between OSPF adjacencies. So, let’s fix that.

R1#conf t
R1(config)#int gig 0/2
R1(config-if)#default ip mtu
R1(config-if)#end
R1#
*Nov 6 19:53:15.937: %OSPF-5-ADJCHG: Process 1, Nbr 203.0.113.1 on GigabitEthernet0/2
from LOADING to FULL, Loading Done
R1#
R1#show ip ospf neighbor

Neighbor ID Pri State Dead Time Address Interface

203.0.113.1 1 FULL/DR 00:00:32 192.0.2.2 GigabitEthernet0/2
R1#show ip route

Copyright 2024, Kevin Wallace Training, LLC

Codes: L - local, 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, H - NHRP, l - LISP
a - application route
+ - replicated route, % - next hop override, p - overrides from PfR

Gateway of last resort is not set

172.16.0.0/24 is subnetted, 1 subnets

O IA 172.16.1.0 [110/3] via 192.0.2.2, 00:00:56, GigabitEthernet0/2
192.0.2.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.0.2.0/30 is directly connected, GigabitEthernet0/2
L 192.0.2.1/32 is directly connected, GigabitEthernet0/2
192.168.1.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.1.0/24 is directly connected, GigabitEthernet0/1
L 192.168.1.1/32 is directly connected, GigabitEthernet0/1
203.0.113.0/30 is subnetted, 1 subnets
O IA 203.0.113.0 [110/2] via 192.0.2.2, 00:00:56, GigabitEthernet0/2
R1#

A`er fixing the MTU issue, an OSPF neighborship was formed, and R1 now has full visibility to
all networks in the topology.

Step 9: Let’s confirm that routers R2 and R3 can also see all the networks in the topology.

R2:
R2#show ip route
Codes: L - local, 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, H - NHRP, l - LISP
a - application route
+ - replicated route, % - next hop override, p - overrides from PfR

Gateway of last resort is not set

172.16.0.0/24 is subnetted, 1 subnets

O 172.16.1.0 [110/2] via 203.0.113.2, 00:29:26, GigabitEthernet0/2
192.0.2.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.0.2.0/30 is directly connected, GigabitEthernet0/1
L 192.0.2.2/32 is directly connected, GigabitEthernet0/1
O 192.168.1.0/24 [110/2] via 192.0.2.1, 00:03:03, GigabitEthernet0/1
203.0.113.0/24 is variably subnetted, 2 subnets, 2 masks
C 203.0.113.0/30 is directly connected, GigabitEthernet0/2
L 203.0.113.1/32 is directly connected, GigabitEthernet0/2
R2#
R3:
R3#show ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP

Copyright 2024, Kevin Wallace Training, LLC

 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, H - NHRP, l - LISP
a - application route
+ - replicated route, % - next hop override, p - overrides from PfR

Gateway of last resort is not set

172.16.0.0/16 is variably subnetted, 2 subnets, 2 masks

C 172.16.1.0/24 is directly connected, GigabitEthernet0/2
L 172.16.1.1/32 is directly connected, GigabitEthernet0/2
192.0.2.0/30 is subnetted, 1 subnets
O IA 192.0.2.0 [110/2] via 203.0.113.1, 00:30:13, GigabitEthernet0/1
O IA 192.168.1.0/24 [110/3] via 203.0.113.1, 00:03:47, GigabitEthernet0/1
203.0.113.0/24 is variably subnetted, 2 subnets, 2 masks
C 203.0.113.0/30 is directly connected, GigabitEthernet0/1
L 203.0.113.2/32 is directly connected, GigabitEthernet0/1
R3#

Success! We’ve met the goal of the troubleshooFng exercise, to allow all routers to see all
networks in the topology. To review, we encountered the following troubleshooFng issues:

• Incorrect passive interface

• Incorrect area
• Mismatched Hello Fmers
• Mismatched MTU values

If you enjoyed this training, check out our All-Access Pass where you can access all
our on-demand courses for one yearly subscrip;on payment.

h"ps://kwtrain.com/all-access

Copyright 2024, Kevin Wallace Training, LLC