CCNA 2 v3.1 Module 7 Distance Vector Routing Protocols

1© 2004, Cisco Systems, Inc. All rights reserved.

CCNA 2 v3.1 Module 7 Distance Vector Routing

Protocols

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.

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.com • Contact your parent academy!

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

Objectives

555© 2004, Cisco Systems, Inc. All rights reserved.

Distance Vector Updates

666© 2004, Cisco Systems, Inc. All rights reserved.

Problem: Routing Loops

• Routing loops can occur when inconsistent routing tables are not updated due to slow convergence in a changing network.

777© 2004, Cisco Systems, Inc. All rights reserved.

Problem: Counting to Infinity

888© 2004, Cisco Systems, Inc. All rights reserved.

Solution: Defining a Maximum for Infinity

999© 2004, Cisco Systems, Inc. All rights reserved.

Solution: Split Horizon

101010© 2004, Cisco Systems, Inc. All rights reserved.

Solution: Route Poisoning

111111© 2004, Cisco Systems, Inc. All rights reserved.

Solution: Triggered Updates

121212© 2004, Cisco Systems, Inc. All rights reserved.

Solution: Holddown Timers

131313© 2004, Cisco Systems, Inc. All rights reserved.

Key Characteristics of RIP

141414© 2004, Cisco Systems, Inc. All rights reserved.

RIP Commands

• Using router rip and network commands to Enable RIP

• Enabling RIP on an IP-addressed network• Monitoring IP packet flow using the show ip protocol command

• The show ip route command

151515© 2004, Cisco Systems, Inc. All rights reserved.

Configuring RIP

161616© 2004, Cisco Systems, Inc. All rights reserved.

Using the ip classless Command

171717© 2004, Cisco Systems, Inc. All rights reserved.

The show ip protocols Command

181818© 2004, Cisco Systems, Inc. All rights reserved.

The show ip route Command

191919© 2004, Cisco Systems, Inc. All rights reserved.

Troubleshooting RIP Update Issues

• debug ip rip

• show ip protocols {summary} • show ip route • debug ip rip {events} • show ip interface brief

202020© 2004, Cisco Systems, Inc. All rights reserved.

Preventing Routing Updates through an Interface

212121© 2004, Cisco Systems, Inc. All rights reserved.

Load Balancing with RIP

222222© 2004, Cisco Systems, Inc. All rights reserved.

Administrative Distance

232323© 2004, Cisco Systems, Inc. All rights reserved.

Integrating Static Route with RIP

• A router running RIP can receive a default route via an update from another router running RIP.

• Another option is for the router to generate the default route itself.

• The administrator can override a static route with dynamic routing information by adjusting the administrative distance values.

242424© 2004, Cisco Systems, Inc. All rights reserved.

Integrating Static Route with RIP

• Static routes that point out an interface will be advertised by the RIP router that owns the static route and propagated throughout the internetwork. This is because static routes that point to an interface are considered in the routing table to be connected and thus lose their static nature in the update. If a static route is assigned to an interface that is not defined in a network command, a redistribute static command must be specified in the RIP process before RIP will advertise the route.

252525© 2004, Cisco Systems, Inc. All rights reserved.

IGRP Features

262626© 2004, Cisco Systems, Inc. All rights reserved.

IGRP Commands

• Using router igrp and network commands to enable IGRP

• Enabling IGRP on an IP-addressed network• Monitoring IP packet flow using the show ip protocol command

• The show ip interfaces command• The show ip route command• The debug ip rip command

272727© 2004, Cisco Systems, Inc. All rights reserved.

IGRP Metrics

• Bandwidth – The lowest bandwidth value in the path • Delay – The cumulative interface delay along the

path • Reliability – The reliability on the link towards the

destination as determined by the exchange of keepalives

• Load – The load on a link towards the destination based on bits per second

282828© 2004, Cisco Systems, Inc. All rights reserved.

IGRP Routes: Interior, System, & Exterior

292929© 2004, Cisco Systems, Inc. All rights reserved.

IGRP Stability Features

• Holddowns, Split horizons, & Poison-reverse updates

303030© 2004, Cisco Systems, Inc. All rights reserved.

Configuring IGRP

313131© 2004, Cisco Systems, Inc. All rights reserved.

Migrating RIP to IGRP

1. Verify existing routing protocol (RIP) on the routers to be converted.

2. Configure IGRP on RouterA and RouterB 3. Enter show ip protocols on RouterA

and RouterB 4. Enter show ip route on RouterA and

RouterB

323232© 2004, Cisco Systems, Inc. All rights reserved.

Migrating RIP to IGRP

333333© 2004, Cisco Systems, Inc. All rights reserved.

Verifying IGRP Configuration

• Some commands for checking IGRP configuration are as follows: show interface interface show running-config show running-config interface interface show running-config | begin interface interface show running-config | begin igrp show ip protocols

343434© 2004, Cisco Systems, Inc. All rights reserved.

Troubleshooting IGRP

• The following commands are useful when troubleshooting IGRP: show ip protocols {summary} show ip route debug ip igrp events IGRP protocol events debug ip igrp transactions IGRP protocol transactions ping traceroute

353535© 2004, Cisco Systems, Inc. All rights reserved.

Summary