8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
1/66
Chapter 7: RIPv2
CCNA Ex loration version 4.0
1
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
2/66
Overview
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 2
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
3/66
RIPv1 Limitations
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 3
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
4/66
Lab Topology
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 4
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
5/66
VLSM
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 5
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
6/66
Lab Topology: Private Address
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 6
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
7/66
Lab Topology: Loopback interface
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 7
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
8/66
RIPv1 Topology Limitations
Static Routes and Null Interfaces
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 8
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
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.
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 9
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.
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
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
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 10
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.
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
11/66
Extra: Using discard routes
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 11
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
12/66
RIPv1 Topology Limitations
Verifying and Testing Connectivity
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 12
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
13/66
RIPv1 Topology Limitations
Verifying and Testing Connectivity
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 13
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
14/66
Lab 7.1.2.3: RIPv1 Topology Limitations
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 14
Use the Packet Tracer Activity to practice your router configuration skills,including RIPv1 configurations.
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
15/66
RIPv1: Discontiguous Networks
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 15
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.
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
16/66
RIPv1: Discontiguous Networks
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 16
Because the subnet mask is not included in the update, RIPv1and other classful routing protocols must summarize networks atmajor network boundaries.
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
17/66
RIPv1: Discontiguous Networks
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 17
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
18/66
RIPv1: Discontiguous Networks
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 18
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
19/66
RIPv1: Discontiguous Networks
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 19
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
20/66
RIPv1: No VLSM Support
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 20
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
21/66
RIPv1: No CIDR support
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 21
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
22/66
RIPv1: No CIDR support
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 22
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
23/66
Lab 7.1.5.2: RIPv1-No CIDR support
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 23
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.
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
24/66
Configuring RIPv2
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 24
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
25/66
Enabling and Verifying RIPv2
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 25
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
26/66
Extra: Next Hop
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 26
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
27/66
Enabling and Verifying RIPv2
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 27
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
28/66
Enabling and Verifying RIPv2
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 28
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
29/66
Enabling and Verifying RIPv2
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 29
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
30/66
Auto-summary and RIPv2
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 30
By default, RIPv2 automatically summarizes networks at majornetwork boundaries, just like RIPv1.
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
31/66
Auto-summary and RIPv2
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 31
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
32/66
Auto-summary and RIPv2
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 32
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
33/66
Auto-summary and RIPv2
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 33
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
34/66
Disabling Auto-summay in RIPv2
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 34
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
35/66
Verifying RIPv2 Updates
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 35
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
36/66
Verifying RIPv2 Updates
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 36
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
37/66
Lab 7.2.4.2: Verifying RIPv2 Updates
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 37
Use the Packet Tracer Activity to configure RIPv2, disableautomatic summarization, and verify your configurations.
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
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
interface fastethernet0/1
RIPv2
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 38
ip address 172.25.150.193 255.255.255.240ip rip send version 1 2
interface fastethernet0/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.
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
39/66
interface fastethernet0/0
ip rip send version {1 | 2}
ip rip receive version {1 | 2}
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 39
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
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
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 40
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
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
41/66
router rip
redistribute static
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 41
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
42/66
VLSM and CIDR
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 42
RIP 2 d VLSM
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
43/66
RIPv2 and VLSM
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 43
RIP 2 d CIDR
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
44/66
RIPv2 and CIDR
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 44
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
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
45/66
RIPv2 and CIDR
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 45
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
46/66
Verifying and Troubleshooting RIPv2
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 46
Verification and Troubleshooting Commands
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
47/66
Verification and Troubleshooting Commands
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 47
Verification and Troubleshooting Commands
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
48/66
Verification and Troubleshooting Commands
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.
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 48
.
correct IP address and subnet maskon each interface.
4. Remove any unnecessary
configuration commands that are nolonger necessary or have beenreplaced by other commands.
Verification and Troubleshooting Commands
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
49/66
Verification and Troubleshooting Commands
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
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 49
. . . . . . , ,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)
Verification and Troubleshooting Commands
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
50/66
Verification and Troubleshooting Commands
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 50
Verification and Troubleshooting Commands
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
51/66
Verification and Troubleshooting Commands
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 51
Verification and Troubleshooting Commands
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
52/66
Verification and Troubleshooting Commands
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
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 52
. . .
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
Verification and Troubleshooting Commands
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
53/66
Verification and Troubleshooting Commands
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 53
Verification and Troubleshooting Commands
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
54/66
Verification and Troubleshooting Commands
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 54
Verification and Troubleshooting Commands
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
55/66
Verification and Troubleshooting Commands
Router# show ip rip database
172.19.0.0/16 auto-summary
172.19.64.0/24 directly connected, Ethernet0172.19.65.0/24
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 55
. . . , ,
[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
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
56/66
Common RIPv2 issues
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 56
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
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
57/66
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 57
Configuring authentication
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
58/66
g g
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 58
Configuring authentication
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
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
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 59
.
Router(config)#interface fastethernet 0/0Router(config-if)#ip rip authentication key-chain Romeo
(option) Router(config-if)#ip rip authentication mode md5
Configuring authentication
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
60/66
g g
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 60
Clear Text Authentication
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
61/66
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 61
MD5 Authentication
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
62/66
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 62
RIPv2 redistribution
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
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
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
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
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
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
8/3/2019 CA Ex S2M07 Ripv2.Ppt [Compatibility Mode]
66/66
Hc vin mng Cisco Bch Khoa - Website: www.ciscobachkhoa.com 66
Top Related