W&L Page 1 CCNA 200-120 CCNA 200-120 Training Jose Luis Flores / Amel Walkinshaw Aug, 2015.
14 CCNA 200-120 RIPV2
-
Upload
chetan666123 -
Category
Documents
-
view
259 -
download
0
description
Transcript of 14 CCNA 200-120 RIPV2
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 1/61
Cisco certification training
Instructor:- ASHOK TAMBE
Contactus:-9930157345ashoktambe
Trainingfor
CCNA,CCNP,CCNASECURITY
CCIP,
MPLS,BGP,IPV6
NETWORK+,SEURITY+
Instructor:- ASHOK TAMBE
Cisco certification training
Copyright©2015NETworkingWANschool
CCNA200-120
https://www.facebook.com/Networkingwanschool
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 2/61
Copyright©2015NETworkingWANschool
CCNA200-120
Instructor:- ASHOK TAMBE
RIP version 2
Contactno:-9930157345
https://www.facebook.com/ashok.tambe.733
https://www.facebook.com/groups/networkingwanschool/
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 3/61
RIPv1 Limitations
RIPv1: Topology Limitations
RIPv1: Discontiguous Networks RIPv1: No VLSM Support
RIPv1: No CIDR Support
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 4/61
Note on Classful Routing Protocols, RIPv1 limitations
The first part of this presentation discusses the limitations of classful
routing protocols such as RIPv1. RIPv1 is used as an example, so we can see how RIPv2 a classless
routing protocol does not have these same limitations.
Classful routing protocols have three major limitations:
Does not support discontiguous networks.
Does not support VLSM
Does not support CIDR
Instead of just “memorizing” these facts, we will demonstrate and
“understand” why a classful routing protocol has these limitations.
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 5/61
RIPv1: Distance Vector, Classless Routing Protocol
RIP Version 2 (RIPv2) is defined in RFC 1723.
Classless routing protocol Less popular than EIGRP, OSPF and IS-IS.
RIPv2 is ideal for explaining the differences between a classful
routing protocol (RIPv1) and a classless routing protocol (RIPv2).
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 6/61
RIPv1 and RIPv2
RIPv2 enhancements over RIPv1:
Next-hop addresses included in the routing updates
Multicast addresses in sending updates
Authentication option available
Both versions of RIP share the following features and limitations:
Use of hold-down and other timers Use of split horizon and split horizon with poison reverse
Use of triggered updates
Maximum hop count of 15 hops
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 7/61
In a discontiguous network, a classful major network address, such as
172.30.0.0/16, is separated by one or more other major networks.
Classful routing protocols do not include enough routing information to
route properly for discontiguous networks.
RIPv1 Limitations
172.30.0.0/16172.30.0.0/16
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 8/61
R2: static summary route to the 192.168.0.0/16 network.
Redistr ibut ion - Inject static route(s) into routing protocol updates.
R2(config)# router rip
R2(config-router)# redistribute static
This summary route will cause problems with RIPv1 because:
192.168.0.0/16 is a supernet (more later)
172.30.0.0/16172.30.0.0/16
R2(config)# ip route 192.168.0.0 255.255.0.0 null0
Summary Route
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 9/61
R1 and R3 contain:
Subnets of the 172.30.0.0/16 network
R3 contains VLSM networks
172.30.200.0/24 subnetted again:
172.30.200.16/28 and 172.30.200.32/28
172.30.0.0/16172.30.0.0/16
VLSM
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 10/61
R3: 172.30.200.0/24 subnetted again, using the first 4 bits for subnets and
the last 4 for hosts.
172.30.200.16/28 and 172.30.200.32/28
VLSM
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 11/61
Loop back inter face
Software-only interface
Used to emulate an interface
Ideal for simulating multiple networks attached to the same router.
172.30.0.0/16172.30.0.0/16
Loopback InterfacesR3(config)# interface Loopback0
R3(config-if)# ip address 172.30.110.1 255.255.255.0
R3(config)# interface Loopback1
R3(config-if)# ip address 172.30.200.17 255.255.255.240
R3(config)# interface Loopback2
R3(config-if)# ip address 172.30.200.33 255.255.255.240
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 12/61
RIPv1 Configurations
Configure RIPv1 for all three routers.
Configure a static summary route for 192.168.0.0/16 to null0 on R2.
R1(config)# router rip
R1(config-router)# network 172.30.0.0
R1(config-router)# network 209.165.200.0
R2(config)# ip route 192.168.0.0 255.255.0.0 null0
R2(config)# router rip
R2(config-router)# redistribute static
R2(config-router)# network 10.0.0.0
R2(config-router)# network 209.165.200.0
R3(config)# router rip
R3(config-router)# network 172.30.0.0
R3(config-router)# network 209.165.200.0
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 13/61
CIDR allows route aggregation.
A single high-level route entry with a subnet mask less than the classful maskcan be used to represent many lower level routes.
Fewer entries in the routing table.
Summarizes all 256 networks ranging from 192.168.0.0/24 to 192.168.255.0/24.
For Lab purposes:
The static summary route 192.168.0.0/16 does not actually exist.
R2(config)# ip route 192.168.0.0 255.255.0.0 Null0
Static Routes and Null Interfaces
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 14/61
Route Redistribution
Redistribution involves taking the routes from one routing source and sending thoseroutes to another routing source. ( more in CCNP route course )
Routes can only be redistributed into a dynamic routing protocol.
Between Dynamic routing protocol
Static routes
Directly connected networks
Want R2 to redistribute our static route (192.168.0.0/16) into RIPv1.
We will see whether this is indeed happening, and if not, why not.
R2(config)# ip route 192.168.0.0 255.255.0.0 null0
R2(config)# router rip
R2(config-router)# redistribute static
Is static route being sent via RIPv1
with other RIPv1 routes?
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 15/61
Verifying and Testing
Connectivity
Whenever R2 pings any of the 172.30.0.0 subnets on R1 or R3, only about
50 percent of the pings are successful.
R2# ping 172.30.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.30.1.1, timeout is 2 seconds:
!U!.!
Success rate is 60 percent (3/5), round-trip min/avg/max = 28/29/32 ms
R2# ping 172.30.100.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.30.100.1, timeout is 2 seconds:
!U!.!
Success rate is 60 percent (3/5), round-trip min/avg/max = 28/28/28 ms
R2#
172.30.0.0/16172.30.0.0/16
What do you expect will
happen?
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 16/61
Verifying and Testing
Connectivity
R1 is able to ping 10.1.0.1 but is unsuccessful when attempting to
ping the 172.30.100.1 interface on R3.
R1# ping 10.1.0.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5),round-trip min/avg/max = 28/28/28 ms
R1# ping 172.30.100.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.30.100.1, timeout is 2 seconds:
.....Success rate is 0 percent (0/5)
R1#
XWhat do you expect willhappen?
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 17/61
Verifying and Testing
Connectivity
R3# ping 10.1.0.1
Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 10.1.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5),round-trip min/avg/max = 28/28/28 ms
R3# ping 172.30.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.30.1.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
R3#
What do you expect will
happen? X
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 18/61
RIPv1: Discontiguous Networks
Because the subnet mask is not included in the update, RIPv1 and
other classful routing protocols must summarize networks at majornetwork boundaries.
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 19/61
RIPv1 on both Routers R1 and R3 summarize 172.30.0.0 in routing updates
to R2.
RIPv1: Discontiguous
Networks
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 20/61
Examining the Routing Tables
What do you expect to see for R2’s routing table?
R2 has two equal-cost routes to the 172.30.0.0/16 network.
R2# show ip route
R 172.30.0.0/16 [120/1] via 209.165.200.230, 00:00:09, Serial0/0/0
[120/1] via 209.165.200.234, 00:00:11, Serial0/0/1
209.165.200.0/30 is subnetted, 2 subnets
C 209.165.200.232 is directly connected, Serial0/0/1
C 209.165.200.228 is directly connected, Serial0/0/0
10.0.0.0/16 is subnetted, 1 subnets
C 10.1.0.0 is directly connected, FastEthernet0/0S 192.168.0.0/16 is directly connected, Null0
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 21/61
debug ip rip
Notice that the subnet mask is not included with the network
address in the update.
R2# debug ip rip
RIP: received v1 update from 209.165.200.230 on Serial0/0/0
172.30.0.0 in 1 hops
RIP: received v1 update from 209.165.200.234 on Serial0/0/1
172.30.0.0 in 1 hops
What do you expect to see?
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 22/61
show ip route
R1 has its own 172.30.0.0 routes:
172.30.2.0/24
172.30.1.0/24.
R1 does not send R2 those subnets.
R1# show ip route
172.30.0.0/24 is subnetted, 2 subnets
C 172.30.2.0 is directly connected, Loopback0
C 172.30.1.0 is directly connected, FastEthernet0/0209.165.200.0/30 is subnetted, 2 subnets
R 209.165.200.232 [120/1] via 209.165.200.229, 00:00:16,Serial0/0/0
C 209.165.200.228 is directly connected, Serial0/0/0
R 10.0.0.0/8 [120/1] via 209.165.200.229, 00:00:16, Serial0/0/0
R1#
What do you expect to see?
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 23/61
Determining the mask and network address
Receiving an Update: Determining subnet mask for routing table
What is the major classful network address of the receiving interface?
What is the major classful network address of the network in the routingupdate?
Are they the same major classful network address?
Yes: Apply subnet mask of the receiving interface for this network
address in the routing table.
No: Apply classful subnet mask for this network address in the
routing table.
Sending an Update: Determining whether or not to summarize route sent
What is the major classful network address of the sending interface?
What is the major classful network address of the network in the routing
update?
Are they the same major classful network address?
Yes: Send subnet network address
No: Send summary address – the classful network address
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 24/61
How Classful Routing
Protocols Determine
Subnet Masks
172.30.0.0 172.30.0.0
Apply classful default
mask of /16
Apply classful default
mask of /16
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 25/61
How Classful Routing
Protocols Determine
Subnet Masks
10.0.0.0
Apply classful
default mask
of /8
Apply classful
default mask of
/8
10.0.0.0
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 26/61
How Classful Routing
Protocols Determine
Subnet Masks
172.30.2.0
172.30.110.0
172.30.1.0
172.30.100.0172.30.200.16
172.30.200.32
VLSM issues: will discuss next
172.30.0.0
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 27/61
RIPv1: No VLSM Support
When RIPv1 on R3 send s its 172.30.0.0 sub nets o ut its exit interface
FastEthernet 0/0, it wil l on ly in clu de tho se 172.30.0.0 sub nets w ith the
same su bnet mask as th e exit inter face.
Added R4 for purposes of this discussion
172.30.100.1/24
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 28/61
RIPv1: No CIDR Support
We see the static route, let’s see if it is be sent in RIPv1 updateswith the other RIPv1 routes…
R2(config)# ip route 192.168.0.0 255.255.0.0 null0
R2(config)# router rip
R2(config-router)# redistribute static
R2(config-router)# network 10.0.0.0
R2(config-router)# network 209.165.200.0
R2(config-router)# end
R2# show ip route
R 172.30.0.0/16 [120/1] via 209.165.200.230, 00:00:09, Serial0/0/0
[120/1] via 209.165.200.234, 00:00:11, Serial0/0/1
209.165.200.0/30 is subnetted, 2 subnets
C 209.165.200.232 is directly connected, Serial0/0/1
C 209.165.200.228 is directly connected, Serial0/0/0
10.0.0.0/16 is subnetted, 1 subnets
C 10.1.0.0 is directly connected, FastEthernet0/0
S 192.168.0.0/16 is directly connected, Null0
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 29/61
R1 Routing Table
Notice that R1 is not receiving this 192.168.0.0/16 route in its RIP
updates from R2
R1# show ip route
172.30.0.0/24 is subnetted, 2 subnetsC 172.30.2.0 is directly connected, FastEthernet0/1
C 172.30.1.0 is directly connected, FastEthernet0/0
209.165.200.0/30 is subnetted, 2 subnets
R 209.165.200.232 [120/1] via 209.165.200.229, 00:00:16,Serial0/0/0
C 209.165.200.228 is directly connected, Serial0/0/0
R 10.0.0.0/8 [120/1] via 209.165.200.229, 00:00:16, Serial0/0/0
What do you expect to see?
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 30/61
debug ip rip
R2 is not including the 192.168.0.0/16 route in its RIPv1 updates toeither R1 or R3.
R2# debug ip rip
RIP: received v1 update from 209.165.200.230 on Serial0/0/0
172.30.0.0 in 1 hops
RIP: received v1 update from 209.165.200.234 on Serial0/0/1
172.30.0.0 in 1 hops
RIP: sending v1 update to 255.255.255.255 via Serial0/0/0 (209.165.200.229)
RIP: build update entries
network 10.0.0.0 metric 1
subnet 209.165.200.232 metric 1
RIP: sending v1 update to 255.255.255.255 via Serial0/0/1 (209.165.200.233)
RIP: build update entries
network 10.0.0.0 metric 1subnet 209.165.200.228 metric 1
What do you expect to see?
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 31/61
RIPv1: No CIDR Support
The static route 192.168.0.0 has a /16 mask.
This is fewer b its than th e classful Class C mask of /24.
RIPv1 and o ther classfu l rout ing protoc ols c annot su ppo rt CIDR routes that are
summarized rou tes with a smal ler sub net mask than the classfu l mask of theroute.
RIPv1 ignores these supernets in the routing table and does not include them in
updates to other routers.
This is because the receiv ing router would only be able to apply the larger /24
classfu l m ask to the u pdate and not the s horter /16 mask.
Note: If the 192.168.0.0 static route were configured with a /24 mask or greater, this
route would be included in the RIP updates.
The receiving routers would apply the classful /24 mask to this update.
R2(config)# ip route 192.168.0.0 255.255.0.0 null0
R2(config)# router rip
R2(config-router)# redistribute static
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 32/61
Configuring RIPv2
Enabling and Verifying RIPv2 Auto-Summary and RIPv2
Disabling Auto-Summary in RIPv2
Verifying RIPv2 Updates
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 33/61
33
RIPv2 allows both CIDR and VLSM to be used in the network.
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 34/61
Enabling and Verifying RIPv2
Default RIPv1: When configuring RIP
Router only sends RIPv1 messages, it can process both RIPv1 and
RIPv2 messages. Ignore the RIPv2 fields in the route entry.
RIPv2 will ignore RIPv1 updates.
R2# show ip protocols
<output omitted>
Default version control: send version 1, receive any version
Interface Send Recv Triggered RIP Key-chain
Serial0/0/0 1 1 2
Serial0/0/1 1 1 2
Automatic network summarization is in effect<output omitted >
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 35/61
Enabling and Verifying RIPv2
version 2 command is used to modify RIP to use Version 2.
This command should be configured on all routers in the routing
domain.
R1(config)# router rip
R1(config-router)# version 2
R2(config)# router rip
R2(config-router)# version 2
R3(config)# router rip
R3(config-router)# version 2
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 36/61
Enabling and Verifying RIPv2
R2# show ip protocols
Routing Protocol is “rip”
Sending updates every 30 seconds, next due in 1 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Outgoing update filter list for all interfaces is
Incoming update filter list for all interfaces is
Redistributing: static, rip
Default version control: send version 2, receive version 2
Interface Send Recv Triggered RIP Key-chain
Serial0/0/0 2 2
Serial0/0/1 2 2
Automatic network summarization is in effect
<output omitted for brevity>
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 37/61
Auto-Summary and RIPv2
You still see the summarized 172.30.0.0/16 route with the same
two equal-cost paths.
R2# show ip route
R 172.30.0.0/16 [120/1] via 209.165.200.230, 00:00:28, Serial0/0/0
[120/1] via 209.165.200.234, 00:00:18, Serial0/0/1
209.165.200.0/30 is subnetted, 2 subnets
C 209.165.200.232 is directly connected, Serial0/0/1
C 209.165.200.228 is directly connected, Serial0/0/0
10.0.0.0/16 is subnetted, 1 subnetsC 10.1.0.0 is directly connected, FastEthernet0/0
S 192.168.0.0/16 is directly connected, Null0
What do you expect to see?
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 38/61
Auto-Summary and RIPv2
Routers R1 and R3 still do not include the 172.30.0.0 subnets of the other router.
The only difference so far between RIPv1 and RIPV2 is that R1 and R3 each have a route to192.168.0.0/16.
(CIDR) static route configured on R2 and redistributed by RIP.
R1# show ip route
172.30.0.0/24 is subnetted, 2 subnets
C 172.30.2.0 is directly connected, Loopback0
C 172.30.1.0 is directly connected, FastEthernet0/0209.165.200.0/30 is subnetted, 2 subnets
R 209.165.200.232 [120/1] via 209.165.200.229, 00:00:04,Serial0/0/0
C 209.165.200.228 is directly connected, Serial0/0/0
R 10.0.0.0/8 [120/1] via 209.165.200.229, 00:00:04, Serial0/0/0
R 192.168.0.0/16 [120/1] via 209.165.200.229, 00:00:04, Serial0/0/0
What do you expect to see?
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 39/61
Auto-Summary and RIPv2
Notice that RIPv2 is sending both the network address and subnet mask.
Notice that the route sent is the summarized classful network address, 172.30.0.0/16
Not the individual 172.30.1.0/24 and 172.30.2.0/24 subnets.
R1# debug ip rip
RIP: sending v2 update to 224.0.0.9 via Serial0/0/0
(209.165.200.230)
RIP: build update entries
172.30.0.0/16 via 0.0.0.0, metric 1, tag 0<output omitted for brevity>
RIP: received v2 update from 209.165.200.229 on Serial0/0/0
10.0.0.0/8 via 0.0.0.0 in 1 hops
192.168.0.0/16 via 0.0.0.0 in 1 hops
209.165.200.232/30 via 0.0.0.0 in 1 hops
What do you expect to see?
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 40/61
Auto-Summary and RIPv2
By d efaul t , RIPv2 automatical ly summarizes networks at major network
bou ndaries, jus t l ike RIPv1.
Both R1 and R3 routers are still summarizing their 172.30.0.0 subnets
R1# show ip protocols
Routing Protocol is “rip”
<output omitted>Default version control: send version 2, receive version 2
Interface Send Recv Triggered RIP Key-chain
FastEthernet0/0 2 2
FastEthernet0/1 2 2
Serial0/1/0 2 2
Automatic network summarization is in effect
Disabling Auto summary in RIPv2
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 41/61
Disabling Auto-summary in RIPv2
To modify the default RIPv2 behavior of automatic summarization,
use the no auto-summary command
R2(config)# router rip
R2(config-router)# no auto-summary
R3(config)# router rip
R3(config-router)# no auto-summary
R1(config)# router rip
R1(config-router)# no auto-summary
R1# show ip protocols
<output omitted>
Automatic network summarization is not in effect
<output omitted>
V if i RIP 2 U d t
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 42/61
Verifying RIPv2 Updates
The routing table for R2 now contains the individual subnets for 172.30.0.0/16. Notice that a single summary route with two equal-cost paths no longer exists.
Each subnet and mask has its own specific entry, along with the exit interface andnext-hop address to reach that subnet.
R2# show ip route
172.30.0.0/16 is variably subnetted, 6 subnets, 2 masks
R 172.30.200.32/28 [120/1] via 209.165.200.234, 00:00:09, Serial0/0/1
R 172.30.200.16/28 [120/1] via 209.165.200.234, 00:00:09, Serial0/0/1
R 172.30.2.0/24 [120/1] via 209.165.200.230, 00:00:03, Serial0/0/0
R 172.30.1.0/24 [120/1] via 209.165.200.230, 00:00:03, Serial0/0/0
R 172.30.100.0/24 [120/1] via 209.165.200.234, 00:00:09, Serial0/0/1
R 172.30.110.0/24 [120/1] via 209.165.200.234, 00:00:09, Serial0/0/1
209.165.200.0/30 is subnetted, 2 subnetsC 209.165.200.232 is directly connected, Serial0/0/1
C 209.165.200.228 is directly connected, Serial0/0/0
10.0.0.0/16 is subnetted, 1 subnets
C 10.1.0.0 is directly connected, FastEthernet0/0
S 192.168.0.0/16 is directly connected, Null0
What do you expect to see?
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 43/61
Verifying RIPv2 Updates
Fully converged routing tables.
R1# show ip route
172.30.0.0/16 is variably subnetted, 6 subnets, 2 masks
R 172.30.200.32/28 [120/2] via 209.165.200.229, 00:00:01, Serial0/0/0
R 172.30.200.16/28 [120/2] via 209.165.200.229, 00:00:01, Serial0/0/0
C 172.30.2.0/24 is directly connected, Loopback0
C 172.30.1.0/24 is directly connected, FastEthernet0/0R 172.30.100.0/24 [120/2] via 209.165.200.229, 00:00:01, Serial0/0/0
R 172.30.110.0/24 [120/2] via 209.165.200.229, 00:00:01, Serial0/0/0
209.165.200.0/30 is subnetted, 2 subnets
R 209.165.200.232 [120/1] via 209.165.200.229, 00:00:02, Serial0/0/0
C 209.165.200.228 is directly connected, Serial0/0/0
10.0.0.0/16 is subnetted, 1 subnets
R 10.1.0.0 [120/1] via 209.165.200.229, 00:00:02, Serial0/0/0
R 192.168.0.0/16 [120/1] via 209.165.200.229, 00:00:02, Serial0/0/0
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 44/61
Verifying RIPv2 Updates
Fully converged routing tables.
R3# show ip route
172.30.0.0/16 is variably subnetted, 6 subnets, 2 masks
C 172.30.200.32/28 is directly connected, Loopback2
C 172.30.200.16/28 is directly connected, Loopback1
R 172.30.2.0/24 [120/2] via 209.165.200.233, 00:00:01, Serial0/0/1
R 172.30.1.0/24 [120/2] via 209.165.200.233, 00:00:01, Serial0/0/1
C 172.30.100.0/24 is directly connected, FastEthernet0/0
C 172.30.110.0/24 is directly connected, Loopback0
209.165.200.0/30 is subnetted, 2 subnets
C 209.165.200.232 is directly connected, Serial0/0/1
R 209.165.200.228 [120/1] via 209.165.200.233, 00:00:02, Serial0/0/1
10.0.0.0/16 is subnetted, 1 subnets
R 10.1.0.0 [120/1] via 209.165.200.233, 00:00:02, Serial0/0/1
R 192.168.0.0/16 [120/1] via 209.165.200.233, 00:00:02, Serial0/0/1
f
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 45/61
Verifying RIPv2 Updates
R2# debug ip rip
RIP: received v2 update from 209.165.200.234 on Serial0/0/1
172.30.100.0/24 via 0.0.0.0 in 1 hops
172.30.110.0/24 via 0.0.0.0 in 1 hops
172.30.200.16/28 via 0.0.0.0 in 1 hops
172.30.200.32/28 via 0.0.0.0 in 1 hops
RIP: sending v2 update to 224.0.0.9 via Serial0/0/0 (209.165.200.229)
RIP: build update entries
10.1.0.0/16 via 0.0.0.0, metric 1, tag 0
172.30.100.0/24 via 0.0.0.0, metric 2, tag 0
172.30.110.0/24 via 0.0.0.0, metric 2, tag 0
172.30.200.16/28 via 0.0.0.0, metric 2, tag 0
172.30.200.32/28 via 0.0.0.0, metric 2, tag 0
192.168.0.0/16 via 0.0.0.0, metric 1, tag 0209.165.200.232/30 via 0.0.0.0, metric 1, tag 0
Sending and receiving routing updates, which are individual routes with their
subnet mask instead of a single summary route with the classful mask.
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 46/61
Verifying RIPv2 Updates
Notice also that the updates are sent using the multicast address
224.0.0.9.
RIPv1 sends updates as a broadcast 255.255.255.255. In general multicast updates:
Take up less bandwidth on the network.
Require less processing by devices that are not RIP enabled.
R2# debug ip rip
RIP: sending v2 update to 224.0.0.9 via Serial0/0/0(209.165.200.229)
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 47/61
VLSM and CIDR
RIPv2 and VLSM RIPv2 and CIDR
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 48/61
RIPv2 and VLSM
R3 nows include all the 172.30.0.0 subnets in its routing updates to R4
Because RIPv2 includes the subnet mask with the network address.
Added R4 for purposes of this discussion
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 49/61
RIPv2 and VLSM
R3# debug ip rip
RIP: sending v2 update to 224.0.0.9 via FastEthernet0/0 (172.30.100.1)
RIP: build update entries
10.1.0.0/16 via 0.0.0.0, metric 2, tag 0
172.30.1.0/24 via 0.0.0.0, metric 3, tag 0
172.30.2.0/24 via 0.0.0.0, metric 3, tag 0
172.30.110.0/24 via 0.0.0.0, metric 1, tag 0
172.30.200.16/28 via 0.0.0.0, metric 1, tag 0
172.30.200.32/28 via 0.0.0.0, metric 1, tag 0
192.168.0.0/16 via 0.0.0.0, metric 2, tag 0
209.165.200.228/30 via 0.0.0.0, metric 2, tag 0
209.165.200.232/30 via 0.0.0.0, metric 1, tag 0
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 50/61
RIPv2 and CIDR
Supernets have masks that are smal ler than the classful mask
(/16 here, instead of the classful /24).
For the supernet to be included in a routing update, the routing
protocol must have the capability of carrying that mask.
In other words, it must be a classless routing protocol, like RIPv2.
R2(config)# ip route 192.168.0.0 255.255.0.0 Null0
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 51/61
RIPv2 and CIDR
CIDR supernet is included in the routing update sent by R2.
Automatic summarization does not have to be disabled on RIPv2 or any
classless routing protocol for supernets to be included in the updates.
R2# debug ip rip
RIP: sending v2 update to 224.0.0.9 via Serial0/0/0 (209.165.200.229)
RIP: build update entries
10.1.0.0/16 via 0.0.0.0, metric 1, tag 0
172.30.100.0/24 via 0.0.0.0, metric 2, tag 0
172.30.110.0/24 via 0.0.0.0, metric 2, tag 0
172.30.200.16/28 via 0.0.0.0, metric 2, tag 0
172.30.200.32/28 via 0.0.0.0, metric 2, tag 0
192.168.0.0/16 via 0.0.0.0, metric 1, tag 0
209.165.200.232/30 via 0.0.0.0, metric 1, tag 0
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 52/61
RIPv2 and CIDR
R1# show ip route
172.30.0.0/16 is variably subnetted, 6 subnets, 2 masks
R 172.30.200.32/28 [120/2] via 209.165.200.229, 00:00:01, Serial0/0/0
R 172.30.200.16/28 [120/2] via 209.165.200.229, 00:00:01, Serial0/0/0
C 172.30.2.0/24 is directly connected, Loopback0
C 172.30.1.0/24 is directly connected, FastEthernet0/0
R 172.30.100.0/24 [120/2] via 209.165.200.229, 00:00:01, Serial0/0/0
R 172.30.110.0/24 [120/2] via 209.165.200.229, 00:00:01, Serial0/0/0
209.165.200.0/30 is subnetted, 2 subnetsR 209.165.200.232 [120/1] via 209.165.200.229, 00:00:02, Serial0/0/0
C 209.165.200.228 is directly connected, Serial0/0/0
10.0.0.0/16 is subnetted, 1 subnets
R 10.1.0.0 [120/1] via 209.165.200.229, 00:00:02, Serial0/0/0
R 192.168.0.0/16 [120/1] via 209.165.200.229, 00:00:02, Serial0/0/0
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 53/61
Verifying and Troubleshooting RIPv2
Verification and Troubleshooting Commands
Common RIPv2 Issues
Authentication
show ip route Command
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 54/61
First command to use to check for network convergence.
Important to look for the routes that you expect to be in the
rout in g table as wel l as for those that shou ld no t be in the
rout ing table .
R1# show ip route
172.30.0.0/16 is variably subnetted, 6 subnets, 2 masks
R 172.30.200.32/28 [120/2] via 209.165.200.229, 00:00:01, Serial0/0/0
R 172.30.200.16/28 [120/2] via 209.165.200.229, 00:00:01, Serial0/0/0
C 172.30.2.0/24 is directly connected, Loopback0
C 172.30.1.0/24 is directly connected, FastEthernet0/0
R 172.30.100.0/24 [120/2] via 209.165.200.229, 00:00:01, Serial0/0/0
R 172.30.110.0/24 [120/2] via 209.165.200.229, 00:00:01, Serial0/0/0
209.165.200.0/30 is subnetted, 2 subnets
R 209.165.200.232 [120/1] via 209.165.200.229, 00:00:02, Serial0/0/0
C 209.165.200.228 is directly connected, Serial0/0/0
10.0.0.0/16 is subnetted, 1 subnets
R 10.1.0.0 [120/1] via 209.165.200.229, 00:00:02, Serial0/0/0
R 192.168.0.0/16 [120/1] via 209.165.200.229, 00:00:02, Serial0/0/0
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 55/61
show ip interface brief Command
If a network is missing from the routing table, it is often because
an interface is down or incorrectly configured.
The show ip interface brief command quickly verifies the
status of all interfaces.
R1# show ip interface brief
Interface IP-Address OK? Method Status Protocol
FastEthernet0/0 172.30.1.1 YES NVRAM up up
FastEthernet0/1 172.30.2.1 YES NVRAM up up
Serial0/0/0 209.165.200.230 YES NVRAM up up
Serial0/0/1 unassigned YES NVRAM down down
show ip protocols Command
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 56/61
56
Is RIP is enabled, the version of RIP, the status of automaticsummarization, and the networks that were included in the network
statements.
R1# show ip protocols
Routing Protocol is “rip”
Sending updates every 30 seconds, next due in 29 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not setRedistributing: rip
Default version control: send version 2, receive version 2
Interface Send Recv Triggered RIP Key-chain
FastEthernet0/0 2 2
FastEthernet0/1 2 2
Serial0/0/0 2 2
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
172.30.0.0
209.165.200.0
Routing Information Sources:
Gateway Distance Last Update
209.165.200.229 120 00:00:18
Distance: (default is 120)
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 57/61
debug ip rip CommandR2# debug ip rip
RIP: received v2 update from 209.165.200.234 on Serial0/0/1
172.30.100.0/24 via 0.0.0.0 in 1 hops
172.30.110.0/24 via 0.0.0.0 in 1 hops
172.30.200.16/28 via 0.0.0.0 in 1 hops
172.30.200.32/28 via 0.0.0.0 in 1 hops
RIP: sending v2 update to 224.0.0.9 via Serial0/0/0 (209.165.200.229)
RIP: build update entries
10.1.0.0/16 via 0.0.0.0, metric 1, tag 0
172.30.100.0/24 via 0.0.0.0, metric 2, tag 0
172.30.110.0/24 via 0.0.0.0, metric 2, tag 0
172.30.200.16/28 via 0.0.0.0, metric 2, tag 0
172.30.200.32/28 via 0.0.0.0, metric 2, tag 0
192.168.0.0/16 via 0.0.0.0, metric 1, tag 0
209.165.200.232/30 via 0.0.0.0, metric 1, tag 0
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 58/61
58
ping Command
R2# ping 172.30.2.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.30.2.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 28/28/28 ms
R2# ping 172.30.100.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.30.100.1, timeout is 2 seconds:!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 28/28/28 ms
show running-config Command
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 59/61
59
R1# show running-config
!
hostname R1
!
interface FastEthernet0/0ip address 172.30.1.1 255.255.255.0
!
interface FastEthernet0/1
ip address 172.30.2.1 255.255.255.0
!
interface Serial0/0/0
ip address 209.165.200.230 255.255.255.252
clock rate 64000
!
router rip
version 2
network 172.30.0.0
network 209.165.200.0
no auto-summary
!
<some output omitted for brevity>
Common RIPv2 Issues
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 60/61
Version:
Although RIPv1 and RIPv2 can be made compatible with additional commands
beyond the scope of this course, RIPv1 does not support discontiguous subnets,
VLSM, or CIDR supernet routes.
network statements:
Another source of problems might be incorrectly configured or missingnetwork statements configured with the network command.
Remember, the network command does two things:
1. It enables the routing protocol to send and receive updates on any local
interfaces that belong to that network.
2. It includes the configured network in its routing updates to its neighboring
routers.
A missing or incorrect network statement will result in missed routing updates
and routing updates not being sent or received on an interface.
Automatic summarization:
If there is a need or expectation for sending specific subnets and not justsummarized routes, make sure that automatic summarization has been disabledwith the no auto-summary command.
7/17/2019 14 CCNA 200-120 RIPV2
http://slidepdf.com/reader/full/14-ccna-200-120-ripv2 61/61
Cisco certification training
Instructor:- ASHOK TAMBE
Contactus:-9930157345ashoktambe
https://www.facebook.com/ashok.tambe.733
https://www.facebook.com/groups/networkingwanschool/