ccna exp2 - chapter07 - ripv2

8/3/2019 CCNA Exp2 - Chapter07 - RIPv2

1/44

1

Module 7- RIPv2

CCNA Exploration 4.0


2/44

2

Overview

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


3/44


4/44


5/44


6/44

6

RIPv1: Discontiguous Networks

Because the subnet mask is not included in the update, RIPv1 and otherclassful routing protocols must summarize networks at major networkboundaries.



7/447

Configuring RIPv2



8/448

Enabling and Verifying RIPv2

The Next Hop address is used to identify a better next-hop address - if oneexists - than the address of the sending router.

If the field is set to all zeros (0.0.0.0), the address of the sending router is thebest next-hop address.



9/44


10/4410

Auto-summary and RIPv2

By default, RIPv2 automatically summarizes networks at major networkboundaries, just like RIPv1.



11/4411




12/4412




13/4413


Remember, the 192.168.0.0/16 route could not be distributed with RIPv1because the subnet mask was less than the classful mask.

Because the mask is not included in RIPv1 updates, there was no way for theRIPv1 router to determine what that mask should be. Therefore, the update

was never sent.Hc vin mng Bach Khoa - Website: www.bkacad.com


14/4414

Disabling Auto-summay in RIPv2



15/4415

Verifying RIPv2 Updates



16/4416

Verifying RIPv2 Updates



17/4417

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


ip address 172.25.150.193 255.255.255.240

ip 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 2updates.

FastEthernet0/2 has no specialconfiguration and thereforesends and receives version 2by default.

RIPv2



18/4418

Propagating a default Routes in RIPv2

e0

ISP

SantaCruz2SantaCruz1

192.168.4.20/30

172.30.1.0/24

Internet

s0

s0 s0

s1

172.30.100.0/24

e0

192.168.4.24/30

.21

.22

.25

.26

10.0.0.0/8

e0.1

.1.1

Lo0Lo0

172.30.110.0/24172.30.2.0/24

.1.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.

172.30.200.16/28

172.30.200.32/28

Lo1

Lo2

ISP

router rip

redistribute staticnetwork 10.0.0.0

network 192.168.4.0

version 2

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.2etherenet0


Two steps to propagate default route into RIPv2:

Create default route in propagator. Implement default-information originate in router mode.


19/4419

VLSM and CIDR



20/4420

RIPv2 and VLSM



21/4421

RIPv2 and CIDR

One of the goals of Classless Inter-Domain Routing (CIDR) as stated

by RFC 1519 is "to provide a mechanism for the aggregation of routing

information." This goal includes the concept of supernetting.

A supernet is a block of contiguous classful networks that is addressed

as a single network.



22/44


23/4423

Authentication

Whatever the reason, it is good practice to authenticate routing information transmittedbetween routers.

RIPv2, EIGRP, OSPF, IS-IS, and BGP can be configured to authenticate routinginformation.

This practice ensures routers will only accept routing information from other routers thathave been configured with the same password or authentication information.

Note: Authentication does not encrypt the routing table.



24/4424

Configuring authentication

Router(config)#key chain RomeoRouter(config-keychain)#key 1

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

The password must be the same on both routers (Juliet), but the name of the key(Romeo) can be different.

Router(config)#interface fastethernet 0/0

Router(config-if)#ip rip authentication key-chain Romeo

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

If the command ip rip authentication mode md5 is not added, the interface will use thedefault clear text authentication. Although clear text authentication may be necessary tocommunicate with some RIP v2 implementations, for security concerns use the moresecure MD5 authentication whenever possible.



25/44

RIPv2 redistribution

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.

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


26/44

Configuring Redistribution into RIP

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]

26

RtrA(config)# router rip

RtrA(config-router)# redistribute ospf ?

Process ID

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.


27/44

The redistribute command parameters for RIP

27

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.

match route-type(Optional) Command parameter used for redistributing OSPFroutes into another routing protocol. For OSPF, the criterion bywhich OSPF routes are redistributed into other routingdomains.

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 defaultmetric 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.


28/44

28

Verifying and Troubleshooting RIPv2



29/44

29

Verification and Troubleshooting Commands

There are several ways to verify and troubleshoot RIPv2. Many of the same commandsused for RIPv2 can be used to verify and troubleshoot other routing protocols.

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.

3. Check to make sure you have the correct IP address and subnet mask on eachinterface.

4. Remove any unnecessary configuration commands that are no longer necessaryor have been replaced by other commands.



30/44

30


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, Loopback1

R 172.30.2.0/24 [120/2] via 192.168.4.21, 00:00:21, Serial0R 172.30.1.0/24 [120/2] via 192.168.4.21, 00:00:21, Serial0C 172.30.100.0/24 is directly connected, Ethernet0C 172.30.110.0/24 is directly connected, Loopback0

192.168.4.0/30 is subnetted, 2 subnetsR 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 protcols will route supernets (CIDR)



31/44

31




32/44

32




33/44

33




34/44

34


Router#debug ip rip

RIP protocol debugging is on

Router#01:23:34: RIP: received v2 update from 192.168.4.22 on Serial1

01: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#

01:23:38: RIP: received v2 update from 192.168.4.26 on Serial0

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 0

01: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

Router(config)# line console 0

Router(config-line)# logging synchronous

multicast

Includes mask



35/44

35




36/44

36




37/44

37


Router# show ip rip database

172.19.0.0/16 auto-summary172.19.64.0/24 directly connected, Ethernet0

172.19.65.0/24

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

[2] via 172.19.67.38, 00:00:25, Serial0

172.19.67.0/24 directly connected, Serial0



172.19.86.0/24[1] via 172.19.67.38, 00:00:25, Serial0

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

The show ip rip database command to check summary address entries in theRIP database. These entries will appear in the database if there are only relevant child or

specific routes being summarized.

When the last child route for a summary address becomes invalid, thesummary address is also removed from the routing table.



38/44

38

Common RIPv2 issues

The network statement does two things: It enables the routing protocol to send and receive updates on any local

interfaces that belong to that network.

It includes that network in its routing updates to its neighboring routers.


S


39/44

39

Summary

RIPv2 is a classless, distance vector routing protocol, that is defined in

RFC 1723. Because RIPv2 is a classless routing protocol, it includes the subnet

mask with the network addresses in the routing updates.

As with other classless routing protocols, RIPv2 supports CIDRsupernets, VLSM and discontiguous networks.



40/44


41/44

41


42/44

42


43/44

43


44/44

ccna exp2 - chapter07 - ripv2

Documents