ca ex s2m07 ripv2.ppt [compatibility mode]

8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]

1/66

Chapter 7: RIPv2

CCNA Ex loration version 4.0

1


2/66

Overview

Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 2


3/66

RIPv1 Limitations



4/66

Lab Topology



5/66

VLSM



6/66

Lab Topology: Private Address



7/66

Lab Topology: Loopback interface



8/66

RIPv1 Topology Limitations

Static Routes and Null Interfaces



9/66

Null interface

The address space represented by the staticsummary route 192.168.0.0/16 does not actually

exist. In order to simulate this static route, we use a nullinterface as the exit interface.


or configure the null interface. It is always up butdoes not forward or receive traffic. Traffic sent tothe null interface is discarded.

For our purposes, the null interface will serve asthe exit interface for our static route.


10/66

Extra : Null interface

The Cisco IOS software supports a "null" interface.This pseudo-interface functions similarly to the null

devices available on most operating systems. This interface is always up and can never forwardor receive traffic; encapsulation always fails. The


specify for the null interface is no ipunreachables.

The null interface provides an alternative method

of filtering traffic. You can avoid the overheadinvolved with using access lists by directingundesired network traffic to the null interface.


11/66

Extra: Using discard routes



12/66


Verifying and Testing Connectivity



13/66


Verifying and Testing Connectivity



14/66

Lab 7.1.2.3: RIPv1 Topology Limitations


Use the Packet Tracer Activity to practice your router configuration skills,including RIPv1 configurations.


15/66

RIPv1: Discontiguous Networks


RIPv1 is a classful routing protocol. It does not include the subnet masks in its routing

updates.Therefore, RIPv1 cannot support discontiguous

networks, VLSM, or Classless Inter-Domain Routing(CIDR) supernets.


16/66



Because the subnet mask is not included in the update, RIPv1and other classful routing protocols must summarize networks atmajor network boundaries.


17/66




18/66




19/66




20/66

RIPv1: No VLSM Support



21/66

RIPv1: No CIDR support



22/66

RIPv1: No CIDR support



23/66

Lab 7.1.5.2: RIPv1-No CIDR support


Use the Packet Tracer Activity in Simulation mode to see that updates are notsent across classful network boundaries with RIPv1. In RealTime mode, verify non-convergence with the

show ip route ping

debug ip rip.


24/66

Configuring RIPv2



25/66

Enabling and Verifying RIPv2



26/66

Extra: Next Hop



27/66




28/66




29/66




30/66

Auto-summary and RIPv2


By default, RIPv2 automatically summarizes networks at majornetwork boundaries, just like RIPv1.


31/66




32/66




33/66




34/66

Disabling Auto-summay in RIPv2



35/66

Verifying RIPv2 Updates



36/66

Verifying RIPv2 Updates



37/66

Lab 7.2.4.2: Verifying RIPv2 Updates


Use the Packet Tracer Activity to configure RIPv2, disableautomatic summarization, and verify your configurations.


38/66

Compatibility with RIP v1

NewYork

interface fastethernet0/0

ip address 192.168.50.129 255.255.255.192

ip rip send version 1

ip rip receive version 1


RIPv2


ip address 172.25.150.193 255.255.255.240ip rip send version 1 2


ip address 172.25.150.225 225.255.255.240

router rip

version 2

network 172.25.0.0

network 192.168.50.0

Interface FastEthernet0/0 isconfigured to send and receiveRIP v1 updates.

FastEthernet0/1 is configuredto send both version 1 and 2

updates. FastEthernet0/2 has no special

configuration and thereforesends and receives version 2by default.


39/66


ip rip send version {1 | 2}

ip rip receive version {1 | 2}



40/66

Adding a default Routes to RIPv2

ISP

192.168.4.20/30

Internet

s0 s1

192.168.4.24/30

.21.25

10.0.0.0/8

e0.1.1

static route to

207.0.0.0/8

207.0.0.0/16

207.1.0.0/16

207.2.0.0/16

207.3.0.0/16

etc.ISP

router rip

redistribute staticnetwork 10.0.0.0

network 192.168.4.0

version 2


e0

SantaCruz2SantaCruz1

172.30.1.0/24

s0 s0

172.30.100.0/24

e0

.22.26

.1.1

Lo0Lo0

172.30.110.0/24172.30.2.0/24

.1.1

`172.30.200.16/28

172.30.200.32/28

Lo1

Lo2

no auto-summary

default-information originate

ip route 207.0.0.0 255.0.0.0 null0

ip route 0.0.0.0 0.0.0.0 10.0.0.2

etherenet0


41/66

router rip

redistribute static



42/66

VLSM and CIDR


RIP 2 d VLSM


43/66

RIPv2 and VLSM


RIP 2 d CIDR


44/66

RIPv2 and CIDR


One of the goals of Classless Inter-Domain Routing (CIDR) asstated by RFC 1519 is "to provide a mechanism for the

aggregation of routing information." This goal includes theconcept of supernetting.

A supernet is a block of contiguous classful networks that isaddressed as a single network.

RIPv2 and CIDR


45/66

RIPv2 and CIDR



46/66

Verifying and Troubleshooting RIPv2


Verification and Troubleshooting Commands


47/66





48/66


It is always best to begin with the basics:1. Make sure all of the links (interfaces)

are up and operational.2. Check the cabling.


.

correct IP address and subnet maskon each interface.

4. Remove any unnecessary

configuration commands that are nolonger necessary or have beenreplaced by other commands.



49/66


Router#show ip route

172.30.0.0/16 is variably subnetted, 6 subnets, 2 masksC 172.30.200.32/28 is directly connected, Loopback2C 172.30.200.16/28 is directly connected, Loopback1R 172.30.2.0/24 [120/2] via 192.168.4.21, 00:00:21, Serial0


. . . . . . , ,C 172.30.100.0/24 is directly connected, Ethernet0

C 172.30.110.0/24 is directly connected, Loopback0192.168.4.0/30 is subnetted, 2 subnets

R 192.168.4.24 [120/1] via 192.168.4.21, 00:00:21, Serial0C 192.168.4.20 is directly connected, Serial0

R 10.0.0.0/8 [120/1] via 192.168.4.21, 00:00:21, Serial0R 207.0.0.0/8 [120/1] via 192.168.4.21, 00:00:21, Serial0

Supernet, classless routing protcolswill route supernets (CIDR)



50/66





51/66





52/66


Router#debug ip rip

RIP protocol debugging is on

Router#01:23:34: RIP: received v2 update from 192.168.4.22 on Serial101:23:34: 172.30.100.0/24 -> 0.0.0.0 in 1 hops

01:23:34: 172.30.110.0/24 -> 0.0.0.0 in 1 hops

Router#

Includes mask


. . .

01:23:38: 172.30.2.0/24 -> 0.0.0.0 in 1 hops

01:23:38: 172.30.1.0/24 -> 0.0.0.0 in 1 hops

Router#

01:24:31: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (10.0.0.1)

01:24:31: 172.30.2.0/24 -> 0.0.0.0, metric 2, tag 0

01:24:31: 172.30.1.0/24 -> 0.0.0.0, metric 2, tag 0

01:24:31: 172.30.100.0/24 -> 0.0.0.0, metric 2, tag 001:24:31: 172.30.110.0/24 -> 0.0.0.0, metric 2, tag 0

01:24:31: 192.168.4.24/30 -> 0.0.0.0, metric 1, tag 0

01:24:31: 192.168.4.20/30 -> 0.0.0.0, metric 1, tag 0

multicast



53/66





54/66





55/66


Router# show ip rip database

172.19.0.0/16 auto-summary

172.19.64.0/24 directly connected, Ethernet0172.19.65.0/24


. . . , ,

[2] via 172.19.67.38, 00:00:25, Serial0172.19.67.0/24 directly connected, Serial0

172.19.67.38/32 directly connected, Serial0

172.19.70.0/24 directly connected, Serial1172.19.86.0/24[1] via 172.19.67.38, 00:00:25, Serial0

[1] via 172.19.70.36, 00:00:17, Serial1

Common RIPv2 issues


56/66

Common RIPv2 issues


The network statement does 2 things:

1. It enables the routing protocol to send and receiveupdates on any local interfaces that belong to thatnetwork.

2. It includes that network in its routing updates to its

neighboring routers.

Authentication


57/66


Configuring authentication


58/66

g g




59/66

g g

Router(config)#key chain Romeo

Router(config-keychain)#key 1Router(config-keychain-key)#key-string Juliet

The password must be the same on both routers (Juliet), but the


.

Router(config)#interface fastethernet 0/0Router(config-if)#ip rip authentication key-chain Romeo

(option) Router(config-if)#ip rip authentication mode md5



60/66

g g


Clear Text Authentication


61/66


MD5 Authentication


62/66


RIPv2 redistribution


63/66

Planning Redistribution

Locate the boundary router between two routing processes. Determine which routing process is the core or backbone

process

Determine which routing process is the edge or migrationprocess

Select a method for injecting the required edge protocol routesinto the core.

63Hc vin mng Bach Khoa - Website: www.bkacad.com

Configuring Redistribution into RIP


64/66

Use this command to redistribute routes into RIP: Router(config-router)# redistribute protocol[process-id]

[match route-type] [metric metric-value] [route-map map-tag]

RtrA(config)# router rip

RtrA(config-router)# redistribute ospf ?

-

64

RtrA(config-router)# redistribute ospf 1 ?

match Redistribution of OSPF routes

metric Metric for redistributed routes

route-map Route map reference

Default metric is infinity.

The redistribute command parameters for RIP


65/66

Parameter Description

protocol Source protocol from which routes are being redistributed.

process-idThis value is an AS number. For OSPF, this value is an OSPFprocess ID.

(Optional) Command parameter used for redistributing OSPF

65

match route-type. ,

which OSPF routes are redistributed into other routing

domains.

metric metric-value

(Optional) Parameter used to specify the RIP seed metric forthe redistributed route. When you are redistributing into RIP,this value is not specified and no value is specified using thedefault-metric router configuration command, then the default

metric is 0, which is interpreted as infinity, and routes will notbe redistributed. The metric for RIP is the hop count.

route-map map-tag(Optional) Identifier of a configured route map to beinterrogated to filter the importation of routes from this sourcerouting protocol to the current routing protocol.

Summary


66/66


ca ex s2m07 ripv2.ppt [compatibility mode]

Documents