1. 1 © 2004, Cisco Systems, Inc. All rights reserved. CCNA 3 v3.1 Module 3 EIGRP

2. 222 © 2004, Cisco Systems, Inc. All rights reserved. Purpose of This PowerPoint This PowerPoint primarily consists of the Target Indicators (TIs) of this module in CCNA version 3.1. It was created to give instructors a PowerPoint to take and modify as their own. This PowerPoint is: NOT a study guide for the module final assessment. NOT a study guide for the CCNA certification exam. Please report any mistakes you find in this PowerPoint by using the Academy Connection Help link.

3. 333 © 2004, Cisco Systems, Inc. All rights reserved. To Locate Instructional Resource Materials on Academy Connection: Go to the Community FTP Center to locate materials created by the instructor community Go to the Tools section Go to the Alpha Preview section Go to the Community link under Resources See the resources available on the Class home page for classes you are offering Search http://www.cisco.comhttp://www.cisco.com Contact your parent academy!

4. 444 © 2004, Cisco Systems, Inc. All rights reserved. Objectives

5. 555 © 2004, Cisco Systems, Inc. All rights reserved. Comparing EIGRP with IGRP Comparisons between EIGRP and IGRP fall into the following major categories: Compatibility mode Metric calculation Hop count Automatic protocol redistribution Route tagging

6. 666 © 2004, Cisco Systems, Inc. All rights reserved. Using EIGRP with IGRP

7. 777 © 2004, Cisco Systems, Inc. All rights reserved. EIGRP and IGRP Metric Calculation

8. 888 © 2004, Cisco Systems, Inc. All rights reserved. Comparing show ip route for EIGRP and IGRP

9. 999 © 2004, Cisco Systems, Inc. All rights reserved. EIGRP Concepts The following three tables are maintained by EIGRP: Neighbor table Topology table Routing table

10. 10 © 2004, Cisco Systems, Inc. All rights reserved. The EIGRP Topology Table

11. 11 © 2004, Cisco Systems, Inc. All rights reserved. EIGRP Concepts Every EIGRP router maintains a topology table for each configured network protocol. All learned routes to a destination are maintained in the topology table.

12. 12 © 2004, Cisco Systems, Inc. All rights reserved. EIGRP Successors and Feasible Successors

13. 13 © 2004, Cisco Systems, Inc. All rights reserved. EIGRP Design Features

14. 14 © 2004, Cisco Systems, Inc. All rights reserved. EIGRP Technologies Neighbor discovery and recovery Reliable Transport Protocol DUAL finite-state machine algorithm Protocol-dependent modules By forming adjacencies, EIGRP routers: Dynamically learn of new routes that join their network Identify routers that become either unreachable or inoperable Rediscover routers that had previously been unreachable

15. 15 © 2004, Cisco Systems, Inc. All rights reserved. Data Structure The five EIGRP packet types are as follows:

16. 16 © 2004, Cisco Systems, Inc. All rights reserved. Default Hello Intervals and Hold Times for EIGRP

17. 17 © 2004, Cisco Systems, Inc. All rights reserved. Feasible Successor Route Selection Rules

18. 18 © 2004, Cisco Systems, Inc. All rights reserved. Configuring EIGRP

19. 19 © 2004, Cisco Systems, Inc. All rights reserved. EIGRP Automatically Summarizes Based on Class

20. 20 © 2004, Cisco Systems, Inc. All rights reserved. Manual Summarization with EIGRP

21. 21 © 2004, Cisco Systems, Inc. All rights reserved. Verifying EIGRP

22. 22 © 2004, Cisco Systems, Inc. All rights reserved. EIGRP debug Commands

23. 23 © 2004, Cisco Systems, Inc. All rights reserved. Building Neighbor Tables

24. 24 © 2004, Cisco Systems, Inc. All rights reserved. Discover Routes

25. 25 © 2004, Cisco Systems, Inc. All rights reserved. Select Routes If a link goes down, DUAL looks for an alternative route path, or feasible successor, in the topology table. If a feasible successor is not found, the route is flagged as Active, or unusable at present. Query packets are sent to neighboring routers requesting topology information. DUAL uses this information to recalculate successor and feasible successor routes to the destination.

26. 26 © 2004, Cisco Systems, Inc. All rights reserved. Troubleshooting Process 1.Analyze the network failure, make a clear problem statement. 2.Gather the facts needed to help isolate possible causes. 3.Consider possible problems based on the facts that have been gathered. 4.Create an action plan based on the remaining potential problems. 5.Implement the action plan, performing each step carefully while testing to see whether the symptom disappears. 6.Analyze the results to determine whether the problem has been resolved. If it has, the process is complete. 7.If the problem has not been resolved, create an action plan based on the next most likely problem in the list. Return to Step 4, change one variable at a time, and repeat the process until the problem is solved. 8.Once the actual cause of the problem is identified, try to solve it.

27. 27 © 2004, Cisco Systems, Inc. All rights reserved. Use show Commands and TCP/IP Tools

28. 28 © 2004, Cisco Systems, Inc. All rights reserved. Troubleshooting RIP Configuration Layer 1 or Layer 2 connectivity issues exist. VLSM subnetting is configured. VLSM subnetting cannot be used with RIPv1 Mismatched RIPv1 and RIPv2 routing configurations exist. Network statements are missing or incorrectly assigned. The outgoing interface is down. The advertised network interface is down.

29. 29 © 2004, Cisco Systems, Inc. All rights reserved. Troubleshooting IGRP Configuration

30. 30 © 2004, Cisco Systems, Inc. All rights reserved. Troubleshooting EIGRP Configuration

31. 31 © 2004, Cisco Systems, Inc. All rights reserved. Troubleshooting EIGRP Configuration

32. 32 © 2004, Cisco Systems, Inc. All rights reserved. Troubleshooting OSPF Configuration

33. 33 © 2004, Cisco Systems, Inc. All rights reserved. Summary