Cisco Live OSPF Lessons

Troubleshooting OSPF and
EIGRP Routing Protocols

Ruchir Jain, Technical Leader Services
Agenda
• Troubleshooting Methodology
• OSPF Overview
• Troubleshooting OSPF
• EIGRP Overview
• Troubleshooting EIGRP
Troubleshooting
Methodology
Troubleshooting Methodology
Build the Protocol Run Routing

Database Algorithm
Form Neighbour Populate the IP

Relationship Routing Table
OSPF Overview
OSPF Areas
• Link State protocol
• Uses a 2 level hierarchical model Area 3
• Areas defined with 32 bit number

Defined in IP address format or single
decimal value (i.e., Area 0.0.0.0, or Area 0) Area 0
• 0.0.0.0 (0) reserved for the Area 2

backbone area Area 1
• Area 0 has to contiguous
OSPF LSAs – OSPFv2
• Router and Network LSA’s within an
area (Type 1 and Type 2) Area 3
• Summary LSA Type 3 outside the
area. Generated by ABR.
• Summary LSA Type 4 generated by Area 0
ABR to describe route to ASBR
Area 2
• Type 5 for redistributed routes Area 1
generated by ASBR
• Partial SPF for summary and
External LSA’s
Area 3
OSPF LSAs – OSPFv3

Area 0
• Router and Network LSA’s within an area Area 2
(Type 1 and Type 2). Do not carry prefix information. Area 1
• Link LSA Type 8 have link local scope. Used to notify neighbour
about the attached addresses on that link.
• Intra-area Prefix LSA Type 9. Advertises Router itself, attached stub
networks and transit network segments.
• Inter-area prefix LSA Type 3 outside the area. Generated by ABR.
• Inter-area router LSA Type 4. Generated by ABR to describe route to
ASBR.
• AS-External LSA Type 5 for redistributed routes generated by ASBR.
OSPF Neighbour Adjacency Process
10.1.1.1 10.2.2.2
R1 R2
Hello
• Init
{ RID =10.1.1.1
Hello
RID =10.2.2.2
Init on R2
Init on R1
Hello
{ 2-Way on R2
RID =10.1.1.1
N =10.2.2.2
• 2-Way
Hello
RID =10.2.2.2
2-Way on R1
N =10.1.1.1
10.1.1.1 10.2.2.2
R1 R2
DBD
• EXSTART MTU = 1500
Flag = 0x7
Seq = 0x2499
DBD
• EXCHANGE MTU = 1500
Flag = 0x3
Seq = 0x837
10.1.1.1 10.2.2.2
R1 R2
LS Request
LS Type
• LOADING Link State ID
Advertising Router
LS Update
# LSA’s
• FULL LSA’s
LSA ..
Troubleshooting
OSPF/OSPFv3
Lifecycle View of the OSPF Routing Process
Build the OSPF LSA

Database Run OSPF SPF
Routing Algorithm
Form OSPF Neighbour Populate the IP

Adjacency Is Not Coming Up
OSPF not enabled on the interface
R1#show ip/ipv6 ospf neighbor
R1# In 12.0:
R1#show ip/ipv6 ospf interface eth 0/0 R1#show ip/ipv6 ospf interface eth0/0
Ethernet0/0 is up, line protocol is up R1#
OSPF not enabled on this interface
Check for wrong network statement / For OSPFv3, check interface configuration
for missing “ipv6 ospf area” command
• Mismatched subnet mask (OSPFv2 only) / Hello - Dead Interval
10.1.1.1 10.2.2.2
10.0.0.2/26
10.0.0.1/24
Area 2 Area 2
R1 R2

R1#
R1#debug ip/ipv6 ospf hello

OSPF adjacency events debugging is on
OSPF: Mismatched hello parameters from 10.0.0.2

Dead R 40 C 40, Hello R 10 C 10 Mask R 255.255.255.192 C 255.255.255.0
• Mismatched area ID
10.1.1.1 10.2.2.2
10.0.0.2
10.0.0.1
Area 2
Area 0
R1 R2
R1#debug ip/ipv6 ospf adj

OSPF: Rcv pkt from 10.0.0.2, Et0/0, area 0.0.0.0 mismatch area 0.0.0.2 in the header
On R2:
%OSPF-4-ERRRCV: Received invalid packet: mismatch area ID, from backbone area
must be virtual-link but not found from 10.0.0.1, Ethernet0/0
• Mismatched transit/stub/NSSA option
10.1.1.1 10.2.2.2
10.0.0.2
10.0.0.1
Area 2 NSSA
Area 2
R1 R2
R1#debug ip/ipv6 ospf hello

OSPF-1 HELLO Et0/0: Rcv hello from 10.2.2.2 area 2 10.0.0.2
OSPF-1 HELLO Et0/0: Hello from 10.0.0.2 with mismatched NSSA option bit
Adjacency Is Not Coming Up – OSPFv3 Only
• Mismatched instance-ID
10.1.1.1 10.2.2.2
Area 1 Area 1
R1 R2
R1#show ipv6 ospf neighbor

R1#
R1#sh ipv6 ospf int e0/0 | inc Instance
Area 1, Process ID 1, Instance ID 2, Router ID 10.1.1.1
R2#sh ipv6 ospf int e0/0 | inc Instance
Area 1, Process ID 1, Instance ID 0, Router ID 10.2.2.2
Either change R2 instance ID to 2 or change R1 instance ID back to 0

Adjacency Is Not Coming Up – OSPFv3 Only
• No IPv6 address on the interface
10.1.1.1 10.2.2.2
Area 1 Area 1
R1 R2
R1#show ipv6 ospf neighbor

R2#
R1#sh ipv6 int e0/0
OSPFv3 runs over link local address. Link local or unicast global address
is required to be configured on interface.
Stuck in INIT
• One side is blocking the hello packet with access-list
• One side is translating (NAT) OSPF hello
• One side multicast capabilities is broken (Layer 2)
• OSPF authentication mismatch (only IPv4)
Stuck in 2-WAY
• Normal in Broadcast Network
• All OSPF Routers have 0 priority

Adjacency stuck in Exchange/Exstart
10.1.1.1 10.2.2.2
• MTU mismatch— Stuck in EXCHANGE/EXSTART
R1 R2
• Neighbour RID is same as ours— Stuck in
EXSTART DBD
MTU = 1500
Flag = 0x7
• Unicast is broken—Stuck in EXCHANGE/EXSTART Seq = 0x2499
a. Wrong VC/DLCI mapping

b. MTU problem DBD
c. Access-list blocking unicast MTU = 1500

Flag = 0x3
Seq = 0x837
Router LSA Router IDs
R1: 10.1.1.1
10.1.24.0/24 10.1.45.0/24 R2: 10.2.2.2
2001:1:24::/64 2001:45::/64
10.1.123.0/24 10.20.1.0/24
10.10.10.10/32 R1 R2 R3: 10.3.3.3
2001:1:123::/64 R4 R5 2001:20:1::/64
2001:10:10::10/128 Area 2 R4: 10.4.4.4
Area 0
Area 1 10.1.5.0/24 / 2001:1:5::/64 R5: 10.5.5.5
R3
LS Type: Router Links LS age: 1342

Link State ID: 10.1.1.1 IPv4 Options: (V6-Bit, E-Bit, R-bit, DC-Bit) IPv6
Advertising Router: 10.1.1.1 LS Type: Router Links
LS Seq Number: 80000003 Link State ID: 0
Checksum: 0x3C1 Advertising Router: 10.1.1.1
Length: 48 LS Seq Number: 80000002
Number of Links: 2 Checksum: 0x8D46
Length: 40
Link connected to: a Stub Network Number of Links: 1
(Link ID) Network/subnet number: 10.10.10.10
(Link Data) Network Mask: 255.255.255.255 Link connected to: a Transit Network
Number of MTID metrics: 0 Link Metric: 10
TOS 0 Metrics: 1 Local Interface ID: 2
Neighbor (DR) Interface ID: 2
Link connected to: a Transit Network Neighbor (DR) Router ID: 10.2.2.2
(Link ID) Designated Router address: 10.1.123.2
(Link Data) Router Interface address: 10.1.123.1
Number of MTID metrics: 0
TOS 0 Metrics: 10
Network LSA Router IDs
R1: 10.1.1.1
10.1.24.0/24 10.1.45.0/24 R2: 10.2.2.2
2001:1:24::/64 2001:45::/64
10.1.123.0/24 10.20.1.0/24
10.10.10.10/32 R1 R2 R3: 10.3.3.3
2001:1:123::/64 R4 R5 2001:20:1::/64
2001:10:10::10/128 Area 2 R4: 10.4.4.4
Area 0
Area 1 10.1.5.0/24 / 2001:1:5::/64 R5: 10.5.5.5
R3
R1#sh ip ospf database network adv-router 10.2.2.2 R1#sh ipv6 ospf database network adv-router 10.2.2.2
IPv4 IPv6
OSPF Router with ID (10.1.1.1) (Process ID 1) OSPFv3 Router with ID (10.1.1.1) (Process ID 1)
Net Link States (Area 1) Net Link States (Area 1)
Routing Bit Set on this LSA in topology Base with MTID 0 LS age: 1656
LS age: 1548 Options: (V6-Bit, E-Bit, R-bit, DC-Bit)
Options: (No TOS-capability, DC) LS Type: Network Links
LS Type: Network Links Link State ID: 2 (Interface ID of Designated Router)
Link State ID: 10.1.123.2 (address of Designated Router) Advertising Router: 10.2.2.2
Advertising Router: 10.2.2.2 LS Seq Number: 80000002
LS Seq Number: 80000002 Checksum: 0xA021
Checksum: 0x72F9 Length: 36
Length: 36 Attached Router: 10.2.2.2
Network Mask: /24 Attached Router: 10.1.1.1
Attached Router: 10.2.2.2 Attached Router: 10.3.3.3
Attached Router: 10.1.1.1
Attached Router: 10.3.3.3
Summary LSA / Inter-area Prefix LSA Router IDs
R1: 10.1.1.1
10.1.24.0/24 10.1.45.0/24 R2: 10.2.2.2
2001:1:24::/64 2001:45::/64
10.1.123.0/24 10.20.1.0/24
10.10.10.10/32 R1 R2 R3: 10.3.3.3
2001:1:123::/64 R4 R5 2001:20:1::/64
2001:10:10::10/128 Area 2 R4: 10.4.4.4
Area 0
Area 1 10.1.5.0/24 / 2001:1:5::/64 R5: 10.5.5.5
R3
R1#sh ip ospf database summary 10.1.5.0 R1#show ipv6 ospf database inter-area prefix 2001:1:5::/64
IPv4 IPv6
Summary Net Link States (Area 1) Routing Bit Set on this LSA
LS age: 1655
Routing Bit Set on this LSA in topology Base with MTID 0 LS Type: Inter Area Prefix Links
LS age: 1445 Link State ID: 3
Options: (No TOS-capability, DC, Upward) Advertising Router: 10.2.2.2
LS Type: Summary Links(Network) LS Seq Number: 80000001
Link State ID: 10.1.5.0 (summary Network Number) Checksum: 0x9CCB
Advertising Router: 10.2.2.2 Length: 36
LS Seq Number: 80000001 Metric: 84
Checksum: 0x8A3E Prefix Address: 2001:1:5::
Length: 28 Prefix Length: 64, Options: None
Network Mask: /24
MTID: 0 Metric: 84
Summary ASBR LSA / Inter-area Router LSA Router IDs
R1: 10.1.1.1
10.1.24.0/24 10.1.45.0/24 R2: 10.2.2.2
2001:1:24::/64 2001:45::/64
10.1.123.0/24 10.20.1.0/24
10.10.10.10/32 R1 R2 R3: 10.3.3.3
2001:1:123::/64 R4 R5 2001:20:1::/64
2001:10:10::10/128 Area 2 R4: 10.4.4.4
Area 0
Area 1 10.1.5.0/24 / 2001:1:5::/64 R5: 10.5.5.5
R3
R1#sh ip ospf database asbr-summary adv-router 10.2.2.2 R1#sh ipv6 ospf database inter-area router adv-router 10.2.2.2
IPv4 IPv6
Summary ASB Link States (Area 1) Inter Area Router Link States (Area 1)
Routing Bit Set on this LSA in topology Base with MTID 0 Routing Bit Set on this LSA
LS age: 316 LS age: 355
Options: (No TOS-capability, DC, Upward) Options: (V6-Bit, E-Bit, R-bit, DC-Bit)
LS Type: Summary Links(AS Boundary Router) LS Type: Inter Area Router Links
Link State ID: 10.5.5.5 (AS Boundary Router address) Link State ID: 168101125
Advertising Router: 10.2.2.2 Advertising Router: 10.2.2.2
LS Seq Number: 80000002 LS Seq Number: 80000002
Checksum: 0xB314 Checksum: 0x3F3A
Length: 28 Length: 32
Network Mask: /0 Metric: 74
MTID: 0 Metric: 74 Destination Router ID: 10.5.5.5
AS External LSA Router IDs
R1: 10.1.1.1
10.1.24.0/24 10.1.45.0/24 R2: 10.2.2.2
2001:1:24::/64 2001:45::/64
10.1.123.0/24 10.20.1.0/24
10.10.10.10/32 R1 R2 R3: 10.3.3.3
2001:1:123::/64 R4 R5 2001:20:1::/64
2001:10:10::10/128 Area 2 R4: 10.4.4.4
Area 0
Area 1 10.1.5.0/24 / 2001:1:5::/64 R5: 10.5.5.5
R3
R1#show ip ospf database external 10.20.1.0 R1#show ipv6 ospf database external 2001:20:1::/64
IPv4 IPv6
Routing Bit Set on this LSA in topology Base with MTID 0 Type-5 AS External Link States
LS age: 586
Options: (No TOS-capability, DC, Upward) Routing Bit Set on this LSA
LS Type: AS External Link LS age: 761
Link State ID: 10.20.1.0 (External Network Number ) LS Type: AS External Link
Advertising Router: 10.5.5.5 Link State ID: 0
LS Seq Number: 80000002 Advertising Router: 10.5.5.5
Checksum: 0xA3C3 LS Seq Number: 80000002
Length: 36 Checksum: 0x79E6
Network Mask: /24 Length: 36
Metric Type: 2 (Larger than any link state path) Prefix Address: 2001:20:1::
MTID: 0 Prefix Length: 64, Options: None
Metric: 20 Metric Type: 2 (Larger than any link state path)
Forward Address: 0.0.0.0 Metric: 20
External Route Tag: 0
OSPFv3 Only - Link States – Type 8 Router IDs
R1: 10.1.1.1
10.1.24.0/24 10.1.45.0/24 R2: 10.2.2.2
2001:1:24::/64 2001:45::/64
10.1.123.0/24 10.20.1.0/24
10.10.10.10/32 R1 R2 R3: 10.3.3.3
2001:1:123::/64 R4 R5 2001:20:1::/64
2001:10:10::10/128 Area 2 R4: 10.4.4.4
Area 0
Area 1 10.1.5.0/24 / 2001:1:5::/64 R5: 10.5.5.5
R3
R1#show ipv6 ospf database R1#show ipv6 ospf database link adv-router 10.2.2.2
OSPFv3 Router with ID (10.1.1.1) (Process ID 1) OSPFv3 Router with ID (10.1.1.1) (Process ID 1)
<output omitted> Link (Type-8) Link States (Area 1)
Link (Type-8) Link States (Area 1) LS age: 1566

Options: (V6-Bit, E-Bit, R-bit, DC-Bit)
ADV Router Age Seq# Link ID Interface LS Type: Link-LSA (Interface: Ethernet0/0)
10.1.1.1 1559 0x80000003 2 Et0/0 Link State ID: 2 (Interface ID)
10.2.2.2 1438 0x80000003 2 Et0/0 Advertising Router: 10.2.2.2
10.3.3.3 1302 0x80000003 2 Et0/0 LS Seq Number: 80000003
Checksum: 0x7B41
Length: 56
Router Priority: 1
Link Local Address: FE80::A8BB:CCFF:FE00:200
Number of Prefixes: 1
Prefix Address: 2001:1:123::
Prefix Length: 64, Options: None
OSPFv3 Only - Intra Area Prefix LSA – Type 9 Router IDs
R1: 10.1.1.1
10.1.24.0/24 10.1.45.0/24 R2: 10.2.2.2
2001:1:24::/64 2001:45::/64
10.1.123.0/24 10.20.1.0/24
10.10.10.10/32 R1 R2 R3: 10.3.3.3
2001:1:123::/64 R4 R5 2001:20:1::/64
2001:10:10::10/128 Area 2 R4: 10.4.4.4
Area 0
Area 1 10.1.5.0/24 / 2001:1:5::/64 R5: 10.5.5.5
R3
R1#show ipv6 ospf database R1#show ipv6 ospf database prefix adv-router 10.1.1.1
OSPFv3 Router with ID (10.1.1.1) (Process ID 1) OSPFv3 Router with ID (10.1.1.1) (Process ID 1)
<output omitted> Intra Area Prefix Link States (Area 1)

Routing Bit Set on this LSA
Intra Area Prefix Link States (Area 1) LS age: 1991
LS Type: Intra-Area-Prefix-LSA
ADV Router Age Seq# Link ID Ref-lstype Ref-LSID Link State ID: 0
10.1.1.1 1767 0x80000004 0 0x2001 0 Advertising Router: 10.1.1.1
10.2.2.2 1647 0x80000002 2048 0x2002 2 LS Seq Number: 80000004
Checksum: 0x719C
Length: 52
Referenced LSA Type: 2001
Referenced Link State ID: 0
Referenced Advertising Router: 10.1.1.1
Number of Prefixes: 1
Prefix Address: 2001:10:10::10
Prefix Length: 128, Options: LA, Metric: 0
SPF Running Constantly
Reasons
• LSA Flaps due to:
•Duplicate RID/IP address

•Constant link flapping in an area
R1#show ip/ipv6 ospf statistic
Area 0: SPF algorithm executed 42 times
SPF calculation time
Delta T Intra D-Intra Summ D-Summ Ext D-Ext Total Reason
00:22:00 0 0 0 0 0 0 0 R, N, SN,
00:21:44 0 0 4 0 0 0 4 R, SN, X
00:21:34 0 0 4 0 0 0 4 R, SN, X
00:21:24 0 0 0 4 0 0 4 R, SN, X
00:21:14 0 0 0 0 0 0 0 R,
00:21:04 0 0 0 0 0 0 0 R, N, SN,
00:20:54 0 0 0 0 0 0 0 X
00:20:44 0 0 4 0 0 0 4 R, SN, X
00:20:34 0 0 0 0 0 0 0 X
00:00:17 4 0 0 0 0 0 4 R, N, SN, SA, X
...
R=Router LSA; N=NetworkLSA; SN=Summary Network LSA; SA=Summary ASBR LSA; X=External
LSA
R1#show ip/ipv6 ospf statistic detail
OSPF process ID 100
------------------------------------------
SPF 1 executed 1w0d ago, SPF type Full

SPF calculation time (in msec):
SPT Intra D-Intr Summ D-Summ Ext7 D-Ext7 Total
0 0 0 0 0 0 0 0
LSIDs processed R:1 N:0 Stub:1 SN:0 SA:0 X7:0
Change record R,
LSIDs changed 1
Last 10 LSIDs:
10.2.2.2(R)
Summary OSPF SPF statistic
SPF calculation time
Delta T Intra D-Intra Summ D-Summ Ext D-Ext Total Reason
1w0d 0 0 0 0 0 0 0 R,
R2#debug ip/ipv6 ospf monitor
OSPF: Schedule SPF in area 1
Change in LS ID 10.1.1.1, LSA type R,
OSPF: schedule SPF: spf_time 0ms wait_interval 861421816s
OSPF: Begin SPF at 0x33585480ms, process time 752ms spf_time 0ms, wait_interval 861421816s
OSPF: End SPF at 0x33585488ms, Total elapsed time 8ms
Intra: 4ms, Inter: 0ms, External: 0ms
R2#debug ip/ipv6 ospf spf

OSPFv3-1-IPv6 SPF : Changed LSA 10.1.1.1/0, type 2009, area 0
OSPFv3-1-IPv6 SPF : Detect MAXAGE in LSA 10.1.1.1/0, type 2009
OSPFv3-1-IPv6 SPF : reset throttling to 5000ms next wait-interval 10000ms
OSPFv3-1-IPv6 INTRA: Running SPF for area 0, cause P
OSPFv3-1-IPv6 INTRA: Intra-Area SPF (Prefix), Area 0
OSPFv3-1-IPv6 INTRA: Process Prefix LSAs
R1#show ip/ipv6 ospf database
OSPF Router with ID (10.1.1.1) (Process ID 1)
Router Link States (Area 1)
Link ID ADV Router Age Seq# Checksum Link count

10.1.1.1 10.1.1.1 2 0x80000006 0x00FCC4 2
10.2.2.2 10.2.2.2 1742 0x80000008 0x00CF21 1
10.3.3.3 10.3.3.3 1873 0x80000004 0x00AC42 1
Net Link States (Area 1)
Link ID ADV Router Age Seq# Checksum

10.1.123.2 10.2.2.2 5 0x80000004 0x006EFB
OSPF Traffic Statistics Summary traffic statistics for process ID 1:
OSPF packets received/sent
Type Packets Bytes

RX Invalid 0 0
show ip/ipv6 ospf <process_id> traffic RX Hello 8 384
RX DB des 8 496
RX LS req 2 72
RX LS upd 8 740
RX LS ack 4 236
RX Total 30 1928
TX Failed 0 0
TX Hello 10 792
TX DB des 6 624
TX LS req 2 112
TX LS upd 8 708
TX LS ack 5 460
TX Total 31 2696
OSPF header errors

Length 0, Checksum 0, Version 0, Bad Source 0,
No Virtual Link 0, Area Mismatch 0, No Sham Link 0,
Self Originated 0, Duplicate ID 0, Hello 0,
MTU Mismatch 0, Nbr Ignored 0, LLS 0,
Authentication 0, TTL Check Fail 0,
OSPF LSA errors

Type 0, Length 0, Data 0, Checksum 0,
OSPF Routing Table
Prefix in Database but not in the Routing Table
R1#sh ip ospf nei
Neighbor ID Pri State Dead Time Address Interface
10.2.2.2 0 FULL/ - 00:00:30 10.0.0.2 Serial0/0
R2#sh ip ospf nei

Neighbor ID Pri State Dead Time Address Interface
10.1.1.1 1 FULL/BDR 00:00:30 10.0.0.1 Serial0/0
R1#sh ip route ospf

R1#
10.2.2.2
10.1.1.1 Area 0
R1 R2
10.0.0.1/30 10.0.0.2/30
OSPF Routing Table
R1#sh ip ospf data router 10.2.2.2 R2#sh ip ospf data router 10.1.1.1
OSPF Router with ID (10.1.1.1) (Process ID 1) OSPF Router with ID (10.2.2.2) (Process ID 1)
Adv Router is not-reachable Adv Router is not-reachable
LS age: 1254 LS age: 1670
Options: (No TOS-capability, DC) Options: (No TOS-capability, DC)
LS Type: Router Links LS Type: Router Links
Link State ID: 10.2.2.2 Link State ID: 10.1.1.1
Advertising Router: 10.2.2.2 Advertising Router: 10.1.1.1
Link connected to: a Transit Network Link connected to: a Stub Network
(Link ID) Designated Router address: 10.0.0.2 (Link ID) Network/subnet number: 10.0.0.0
(Link Data) Router Interface address: 10.0.0.2 (Link Data) Network Mask: 255.255.255.252
Number of TOS metrics: 0 Number of TOS metrics: 0
TOS 0 Metrics: 10 TOS 0 Metrics: 10
10.2.2.2
10.1.1.1 Area 0
R1 R2
10.0.0.1/30 10.0.0.2/30
Quiz Time
OSPF Neigbourship is stuck in Exstart between 2 routers. MTU is same

on both sides while Router ID is different. What could be a problem?
Unicast connectivity is broken
What are 2 new LSA for OSPFv3?

Type 8 - Link LSA
Type 9 – Intra Area Prefix LSA
EIGRP Overview
EIGRP Basics
• Advanced distance vector, TLV based
protocol
• Uses DUAL algorithm
• Runs directly on top of IP/IPv6 protocol
88
• Uses multicast capabilities(Neighbour
relationship &Updates) EIGRP AS 1
• Support unequal cost path load
balancing
• Metric is based on the bandwidth and
delay
EIGRP Neighbour Process
• Hello process used for neighbour discovery and maintenance
Hello Types
K-value A
AS number should match
IP subnet (only IPv4)
• Multicast hellos (by default) Hello

224.0.0.10 / FF02::A B
• IPv6 uses Link Local address to form neighbourship

• Hello Interval
60 seconds for low-speed NBMA
5 seconds for all other interfaces
41
EIGRP Reliable Communication
Reliable Transport Protocol (RTP)
• Purpose of RTP
– To transmit and receive EIGRP packets
• Characteristics of RTP
– Reliable & unreliable delivery:
 Reliable delivery requires acknowledgment from destination
 Unreliable delivery does not require an acknowledgement from destination
– Packets can be
 Unicast
 Multicast
42
EIGRP DUAL Routing Algorithm Concepts
• Feasible Distance (FD): minimum distance (metric) to a destination network.
• Reported distance (RD): distance (metric) towards a destination advertised

by upstream neighbour.
• A neighbour meets the feasibility condition (FC) if the RD is smaller than the
FD of this router.
EIGRP DUAL Routing Algorithm
• Finite-State-Machine
Track all routes
Select a Successor
Remember Feasible Successors
If Successor lost
Use Feasible Successor
If no Feasible Successor exists
Query Neighbours and Recompute new Successor
Troubleshooting EIGRP
Lifecycle View of the EIGRP Routing Process
Build the EIGRP

Topology Database Run EIGRP Dual
Routing Algorithm
Form EIGRP Neighbour Populate the IP

EIGRPNeighbour
EIGRP Neighbours
Process
R1#show ip/ipv6 eigrp neighbors
IP-EIGRP neighbors for process 1
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
2 10.0.0.2 Et0 12 6d16h 20 200 0 233
1 10.8.0.5 Et1 13 2w2d 87 522 0 452
0 10.9.0.7 Et1 10 2w2d 85 510 0 3
Seconds before declaring neighbour down

How long since the last time neighbour was discovered
How long it takes for neighbour to respond to reliable packets
How long we’ll wait before retransmitting if no acknowledgement
* Normal to have 5000 during the startup
Number of EIGRP packets unacknowledged by the neighbour
EIGRP Neighbour Problems
• The hold time expires when an EIGRP
packet is not received during hold time
A
• Ping the multicast Address (224.0.0.10 /

FF02::A) from the Other Router Ping 224.0.0.10
Hello
• Other checks:
B
• Access-lists
• Debug EIGRP packet hello
• Ping neighbour with small & large packets
• Interface errors
Neighbour 10.1.1.1 (Ethernet0) is
• Sniffer Captures – external or internal down: holding time expired
• Configure neighbour statements (IPv4 only)
EIGRP Neighbour Problems
• Manual configuration changes can also reset EIGRP neighbours:

• Summary changes (manual and auto)
• Route filter changes
• Graceful restart to resynchronise neighbour relationships

clear ip/ipv6 eigrp neighbor <address> soft
EIGRP Different Log Messages
eigrp log-neighbor-changes must be enabled under EIGRP process
Example logs
Neighbor 10.0.0.2 (Ethernet0) is down: peer restarted
Neighbor 10.0.0.2 (Ethernet0) is down: holding time expired
Neighbor 10.0.0.2 (Ethernet0) is down: retry limit exceeded
Neighbor 10.0.0.2 (Ethernet0) is down: route filter changed (old)
Neighbor 10.0.0.2 (Ethernet0) is down: K-value mismatch
Neighbor 10.0.0.2 (Ethernet0) is down: manually cleared
Neighbor 10.0.0.2 (Ethernet0) is down: Interface Goodbye received
Neighbor 10.0.0.2 (Ethernet0) is resync: route configuration changed

Neighbor 10.0.0.2 (Ethernet0) is resync: manually cleared
Neighbor 10.0.0.2 (Ethernet0) is resync: peer graceful-restart
There are others, but not seen very often…

R1
EIGRP Topology Exchange
Packet
• Reliable packets: re-sent after Retransmit Time Out Ack
R2
(Typically RTO = 6 X SRTT)
• Minimum 200 ms and maximum 5000 ms
Neighbour 10.0.0.1 (Ethernet0) is
• After 16 retransmissions: re-initialise the neighbour down: retry limit exceeded
R1#show ip eigrp neighbors

IP-EIGRP neighbors for process 1
(sec) (ms) Cnt Num
1 10.0.0.1 Et0/0 14 00:00:15 0 5000 4 0
R1#sh ipv6 eigrp neighbors
EIGRP-IPv6 Neighbors for AS(1)
(sec) (ms) Cnt Num
1 Link-local address: Et0/0 12 00:00:16 1 100 3 7
FE80::A8BB:CCFF:FE00:300
• Ping the neighbour’s unicast address
- Vary the packet size
- Try large numbers of packets
R1
• This Ping Can Be Issued from Either

Neighbour
R2
• Common causes
- Mismatched MTU R2# ping
- Unidirectional link Protocol[ip]:
- Dirty link Target IP address: 10.0.0.1
- Bad Hardware
Repeat count [5]: 100
Datagram Size: 1500
Timeout in seconds[2]:
Extended commands[n]: y
R1#show ip eigrp events Lo0: 10.1.1.1
Event information for AS 1:
R1
...
10 13:20:43.289 Rcv update met/succmet: 409600 128256 .1
11 13:20:43.289 Rcv update dest/nh: 10.2.2.0/24 10.0.0.2

10.0.0.0/24
R1#show ipv6 eigrp events Update .2

Event information for AS 1:
R2
...
Lo0: 10.2.2.2
13 15:37:13.791 Rcv update met/succmet: metric(2221056)
metric(2195456)
14 15:37:13.791 Rcv update dest/nh: 2001:1:45::/64
FE80::A8BB:CCFF:FE00:200
EIGRP Event Log
• Always running
• Separate event log for each Autonomous System
• Default 500 lines (configurable):

eigrp event-log-size ## (where ## are number of lines)
size 0 will disable log
• Most recent events at top.
• Clearing the event log:

clear ip eigrp event
Lo0: 10.1.1.1
R1#debug ip/ipv6 eigrp
IP-EIGRP Route Events debugging is on R1
.1
R2#debug ip/ipv6 eigrp 10 10.2.2.0 255.255.255.0
IP-EIGRP AS Target Events debugging is on 10.0.0.0/24
IP-EIGRP(Default-IP-Routing-Table:10): Processing incoming UPDATE packet

IP-EIGRP(Default-IP-Routing-Table:10): Int 10.2.2.0/24 M 409600 – 256000 153600 SM
Update .2
128256 - 256 128000 R2
Lo0: 10.2.2.2
DUAL FD, RD, FS and Successor
A-B-E = 20+30 = 50 B
A-C-E = 20+40 = 60
10.200.1.0
20 Se1/1 RD=40
A-D-E = 20+70 = 90 20 RD=20
A C E
FD = 50
D
RtrA#show ip/ipv6 eigrp topology

IP-EIGRP Topology Table for AS(1)/ID(10.1.1.1)
..snip…..
P 10.200.1.0/24, 1 successors, FD is 50 Feasible Distance
via 10.1.1.2 (50 / 30), Serial1/0 Successor (A-B-E)
via 10.1.2.2 (60 / 40), Serial1/1 Feasible Successor (A-C-E)
Computed Reported
Distance Distance
Show IP EIGRP Topology All-Links
Show ip eigrp topology all-links B
displays a list of All neighbours
10.200.1.0
.1 .2 .1 .2
56k 128k
A C E
RtrA#show ip/ipv6 eigrp topology all-links

…..snip…..
P 10.200.1.0/24, 1 successors, FD is 21026560
via 10.1.1.2 (21026560/20514560), Serial1/0 Successor
via 10.1.2.2 (46740736/20514560), Serial1/1 Feasible Successor
via 10.1.3.2 (46740736/46228736), Serial1/2 Possible Successor
Reported
Distance
57
Show IP EIGRP Topology Summary
Total number of routes in the local topology table
Number of queries this router is waiting on replies for
Internal data structures
R1#sh ip/ipv6 eigrp topology sum

Head serial 1, next serial 1526
589 routes, 0 pending replies, 0 dummies
IP-EIGRP(0) enabled on 12 interfaces, neighbors present on 4 interfaces
Quiescent interfaces: Po3 Po6 Po2 Gi8/5
Interfaces with no outstanding packets to be sent or acknowledged

• Normal state of a route is passive
• Going active is the normal during convergence

• Successor is lost and no feasible successors
• It means sending Queries to neighbours
• SIA timer is 180 seconds
%DUAL-3-SIA: Route 10.64.5.0 255.255.255.192

stuck-in-active state in IP-EIGRP 1. Cleaning up
• Two (probably) unrelated causes of the problem stuck and active

Need to troubleshoot both parts
Cause of active often easier to find
Cause of stuck more important to find
Troubleshoot Stuck in Active
Show ip/ipv6 eigrp topology active (useful only during problem)
R1#show ip eigrp topology active
A 10.200.1.0/24, 1 successors, FD is Inaccessible
1 replies, active 00:01:17, query-origin: Local origin
via Connected (Infinity/Infinity), Ethernet1/0
Remaining replies:
via 10.0.0.2, r, Ethernet0/0
R1 is waiting on reply from 10.0.0.2
1. Primary path goes down / No Feasible Successor
10.0.0.0/24 10.10.0.0/24 10.20.0.0/24 10.30.0.0/24

10.200.1.0/24
R1 R2 R3 R4 R5
2. Query sent to R2 3. Query sent to R3 4. Query sent to R4.
Drops in between
5. SIA-Query sent to R2
after 1.5 mins
6. SIA-Reply from R2 R3 resets neighbourship with R4 after 3 mins

EIGRP Likely Causes for Stuck-in-Active
• Bad or congested links
• Query range is too long - Reduce Scope (stub routers) or Summarise
• Excessive redundancy
• Overloaded router (high CPU)
• Router memory shortage
• Software defects (seldom)
Problem with External Routes
• EIGRP not installing external routes
10.1.1.0/24
via RIP
• The first thing to check is: A

- default metric configured router eigrp 100
redistribute rip
- metric tied to the redistribution statement ....
• default-metric What metric

should I use?
• redistribute .... <metric> B C#show ip route 10.1.1.0
C#
C
B#show ip route 10.1.1.0
B#
Problem with External Routes
• We’ve resolved the metric issue, and B 10.1.1.0/24

picked the route up, but C didn’t—why? via RIP
A
router eigrp 100
redistribute rip metric 1000 1 255 1 1500
....
C
B#show ip route 10.1.1.0 C#show ip route 10.1.1.0
.... C#
10.1.1.0/24 via [A]
Problem with External Routes 10.1.1.0/24
via RIP
A
• We’ve resolved the metric issue, and B
picked the route up, but C didn’t—why?
• B’s topology table show originating
router ID field in the external route is B
set to 192.168.1.1
192.168.1.1
• But, that’s Router C’s loopback C
B#show ip eigrp topology 10.1.1.0
address! 10.10.1.0/24
....
External data:
Originating router is 192.168.1.1
Problem indicated in event log:
1 02:30:18.591 Ignored route, metric: 192.168.1.0 2297856
2 02:30:18.591 Ignored route, neighbor info: 10.1.1.0/24 Serial0/3
3 02:30:18.591 Ignored route, dup router: 192.168.1.1
IPv6 Unique Issues
• IPv6 Router-ID: Uses the same router-id selection process as IPv4. If IPv4
address is not available manually set the router-ID.
• EIGRP does not use a network statement to specify its IPv6 interfaces
Two different methods exist:
• Classic mode uses the “ipv6 eigrp <AS>” command on each interface
• Named mode defaults to having all interfaces enabled
• Need to “shutdown” under af-interface <interface>
• Router process was defined to be shutdown by default in earlier versions.

Classic and Named Mode
Classic Mode Named mode
R2#conf t R1# conf t

Enter configuration commands, one per line. End Enter configuration commands, one per line. End
with CNTL/Z. with CNTL/Z.
R2(config)#ipv6 router eigrp 1 R1(config)#router eigrp foo
R2(config-rtr)#interface Serial4/0 R1(config-router)#address-family ipv6 unicast auto 1
R2(config-if)#ipv6 eigrp 1
R1#sh run | section router eigrp
R2#sh run interface Serial4/0 router eigrp foo
Interface Serial4/0 !
ipv6 address 1:2::2/64 address-family ipv6 unicast autonomous-system 1
ipv6 eigrp 1 !
end af-interface Serial4/0
exit-af-interface
R2#sh run | section ipv6 router !
ipv6 router eigrp 1 topology base
exit-af-topology
R2#sh ipv6 eigrp topology exit-address-family
P 1:2::/64, 1 successors, FD is 2169856
via Connected, Serial4/0 R1#sh eigrp address-family ipv6 topology
P 1:1::/64, 1 successors, FD is 1735175958
via Connected, Serial4/0
Quiz Time
What does non zero Q CNT means?
Router is waiting for neighbor to acknowledge the packets.
Router is configured only for IPv6. EIGRP has been enabled but EIGRP
does not seem to be working. What could be a problem?
Router ID is not available.

Q&A
Complete Your Online Session Evaluation
Give us your feedback and receive a
Cisco 2016 T-Shirt by completing the
Overall Event Survey and 5 Session
Evaluations.
– Directly from your mobile device on the Cisco Live
Mobile App
– By visiting the Cisco Live Mobile Site
http://showcase.genie-connect.com/ciscolivemelbourne2016/
– Visit any Cisco Live Internet Station located
throughout the venue
Learn online with Cisco Live!
T-Shirts can be collected Friday 11 March Visit us online after the conference
for full access to session videos and
at Registration presentations.
www.CiscoLiveAPAC.com
Thank you

Cisco Live OSPF Lessons

Uploaded by

Document Information

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

Cisco Live OSPF Lessons

Uploaded by

Copyright:

Available Formats

Troubleshooting OSPF and

EIGRP Routing Protocols

Build the Protocol Run Routing

Form Neighbour Populate the IP

• Areas defined with 32 bit number

• 0.0.0.0 (0) reserved for the Area 2

OSPF LSAs – OSPFv3

• Router and Network LSA’s within an area Area 2

(Type 1 and Type 2). Do not carry prefix information. Area 1

Build the OSPF LSA

Form OSPF Neighbour Populate the IP

R1#show ip/ipv6 ospf neighbor

R1#debug ip/ipv6 ospf hello

OSPF: Mismatched hello parameters from 10.0.0.2

R1#debug ip/ipv6 ospf adj

R1#show ip/ipv6 ospf neighbor

R1#debug ip/ipv6 ospf hello

R1#show ipv6 ospf neighbor

Either change R2 instance ID to 2 or change R1 instance ID back to 0

R1#show ipv6 ospf neighbor

R1#sh ipv6 int e0/0

• All OSPF Routers have 0 priority

a. Wrong VC/DLCI mapping

c. Access-list blocking unicast MTU = 1500

LS Type: Router Links LS age: 1342

Net Link States (Area 1) Net Link States (Area 1)

<output omitted> Link (Type-8) Link States (Area 1)

Link (Type-8) Link States (Area 1) LS age: 1566

<output omitted> Intra Area Prefix Link States (Area 1)

•Duplicate RID/IP address

SPF 1 executed 1w0d ago, SPF type Full

R2#debug ip/ipv6 ospf spf

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

Router Link States (Area 1)

Link ID ADV Router Age Seq# Checksum Link count

Net Link States (Area 1)

Link ID ADV Router Age Seq# Checksum

OSPF packets received/sent

Type Packets Bytes

OSPF header errors

OSPF LSA errors

R2#sh ip ospf nei

R1#sh ip route ospf

OSPF Neigbourship is stuck in Exstart between 2 routers. MTU is same

Unicast connectivity is broken

What are 2 new LSA for OSPFv3?

IP subnet (only IPv4)

• Multicast hellos (by default) Hello

• IPv6 uses Link Local address to form neighbourship

• Feasible Distance (FD): minimum distance (metric) to a destination network.

• Reported distance (RD): distance (metric) towards a destination advertised

Build the EIGRP

Form EIGRP Neighbour Populate the IP

Seconds before declaring neighbour down

• Ping the multicast Address (224.0.0.10 /

• Manual configuration changes can also reset EIGRP neighbours:

• Graceful restart to resynchronise neighbour relationships

Neighbor 10.0.0.2 (Ethernet0) is resync: route configuration changed

There are others, but not seen very often…

R1#show ip eigrp neighbors

• This Ping Can Be Issued from Either

11 13:20:43.289 Rcv update dest/nh: 10.2.2.0/24 10.0.0.2

R1#show ipv6 eigrp events Update .2

• Separate event log for each Autonomous System