1 / 21

Configure and Troubleshoot IP Routing Protocols - EIGRP & OSPF

Configure and Troubleshoot IP Routing Protocols - EIGRP & OSPF. Cisco Support Community. Technology. Process. Manas R Moothedath Sumit Kothiyal. IP Routing Protocols – Part 2. Manas Moothedath and Sumit Kothiyal. Cisco Systems (India) Pvt Limited. 26 th Mar 2014. EIGRP.

zaria
Download Presentation

Configure and Troubleshoot IP Routing Protocols - EIGRP & OSPF

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Configure and Troubleshoot IP Routing Protocols - EIGRP & OSPF Cisco Support Community Technology Process Manas R Moothedath SumitKothiyal

  2. IP Routing Protocols – Part 2 Manas Moothedath and SumitKothiyal Cisco Systems (India) Pvt Limited 26th Mar 2014 EIGRP

  3. EIGRP

  4. AGENDA • EIGRP packets – a quick recap • Basic troubleshooting of EIGRP issues.  • A closer look at typical EIGRP error messages • Practical view of EIGRP failure scenarios • Best practices in EIGRP 

  5. EIGRP Packets – A Quick Recap The Hello Hello R1 R2 Hello Network command ENABLES EIGRP.

  6. EIGRP Packets – A Quick Recap The Update Update R1 R2

  7. EIGRP Packets – A Quick Recap Reply The Query The Reply R3 X R1 R2 Query

  8. Troubleshooting EIGRP – Effect to cause… Typical EIGRP error messages – neighborship flapping continuously: EIGRP Hold time expired Retry Limit Exceeded Peer restarted

  9. The EIGRP – STUCK IN ACTIVE Revisiting the EIGRP Query “show ipeigrp topology active”

  10. Understanding the ‘EIGRP Topology’ router B# show ipeigrp topology 170.16.0.0 255.255.0.0 IP-EIGRP topology entry for 172.16.0.0/16 State is Passive, Query origin flag is 1, 1 Successor(s), FD is 3757056 Routing Descriptor Blocks: 12.1.2.2 (Serial1), from 12.1.2.2, Send flag is 0x0 Composite metric is (3757056/3245056), Route is External Vector metric: Minimum bandwidth is 1544 Kbit Total delay is 82000 microseconds Reliability is 255/255 Load is 1/255 Minimum MTU is 1500 Hop count is 7 External data: Originating router is 192.168.1.1 AS number of routes is 0 External protocol is OSPF, external metric is 64 Administrator tag is 0

  11. Typical EIGRP Failures scenarios: One way link Mismatched Parameters Query boundary too large Duplicate router-id Hello ping 224.0.0.10

  12. EIGRP Caveats: Discontiguous Classful Boundary • auto-summary • Enabled/Disabled? • Redistribution metric into EIGRP • MUST be specified • Routes advertised to a neighbor • Only if EIGRP in Routing Table • Only the best routes 192.168.1.0/24 172.16.1.0/24 172.16.2.0/24 172.16.3.0/24

  13. OSPF

  14. AGENDA • OSPF Hello • OSPF Neighborship States • Troubleshooting Neighborship Issues • Common Misconceptions • Common Issues.

  15. OSPF Hello • Hello Interval • Dead Interval • Subnet Mask • Area ID • Authentication • Optional Capabilities - eg. Stub

  16. Neighborship states • Down • INIT - Initiated (Multicast) • 2-WAY - See ourself in the neighbor Hello (Multicast) • Exstart - Master/Slave (Unicast) • Exchange - Exchanging DBD (Unicast) • Loading - LSR - LSU - Exchange LSA’s (Unicast) • Full

  17. Lab Topology: R4 R2 R1 R5 R3 R6 R7

  18. Neighborship Issue • Neighbor not seen – • Hello Parameters mismatch. • Multicast Issues. • Neighbor stuck in Exstart– • MTU mismatch. • Unicast Issue.

  19. Common Caveats: • Summary LSA is not summarisation. • Distribute-list out doesn’t work. • Checking the LSA in the wrong database • (checking intra-area route in show ipospf database)

  20. Other issues: • 2-way with all the neighbors (no DR) • Not full will all the neighbors • expected, DR-BDR are full with all the neighbors. • DROthersare only full with DR-BDR • Advertising router is not reachable (not pingable) • could be expected if RID is not advertised. • - RID is just a name.

More Related