Beruflich Dokumente
Kultur Dokumente
Overview
RIPv1 Limitations
Lab Topology
This topology is discontiguous and will not converge because 172.30.0.0/16 is divided by the 209.165.200.0/24. R2 router has a static summary route to the 192.168.0.0/16 network. For now, understand that this summary route will cause problems with RIPv1 because 192.168.0.0/16 is not a major classful address and includes all of the /24 versions of 192.168.0.0/16.
Hc vin mng Bach Khoa - Website: www.bkacad.com 4
You already know that RIPv1 is a classful routing protocol. As you can see in the RIPv1 message format, 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.
Because the subnet mask is not included in the update, RIPv1 and other classful routing protocols must summarize networks at major network boundaries.
Hc vin mng Bach Khoa - Website: www.bkacad.com
Configuring RIPv2
The Next Hop address is used to identify a better next-hop address - if one exists - 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 the best next-hop address.
Hc vin mng Bach Khoa - Website: www.bkacad.com 8
By default, RIPv2 automatically summarizes networks at major network boundaries, just like RIPv1.
Hc vin mng Bach Khoa - Website: www.bkacad.com 10
11
12
Remember, the 192.168.0.0/16 route could not be distributed with RIPv1 because the subnet mask was less than the classful mask. Because the mask is not included in RIPv1 updates, there was no way for the RIPv1 router to determine what that mask should be. Therefore, the update was never sent.
Hc vin mng Bach Khoa - Website: www.bkacad.com 13
14
15
16
RIPv2
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 ip address 172.25.150.193 255.255.255.240 ip 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
17
Interface FastEthernet0/0 is configured to send and receive RIP v1 updates. FastEthernet0/1 is configured to send both version 1 and 2 updates. FastEthernet0/2 has no special configuration and therefore sends and receives version 2 by default.
Two steps to propagate default route into RIPv2: Create default route in propagator. Implement default-information originate in router mode.
Internet
10.0.0.0/8
.1 .25 .1 e0 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 static network 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.2 etherenet0
ISP
s0 s1 .21
192.168.4.24/30
192.168.4.20/30 172.30.200.32/28
Lo2
.26
s0
s0
.22
Lo1 .1
172.30.200.16/28
172.30.2.0/24
Lo0 .1 SantaCruz1 .1 e0
SantaCruz2 Lo0
.1 e0
172.30.110.0/24
172.30.1.0/24
172.30.100.0/24
18
19
20
22
Authentication
Whatever the reason, it is good practice to authenticate routing information transmitted between routers. RIPv2, EIGRP, OSPF, IS-IS, and BGP can be configured to authenticate routing information. This practice ensures routers will only accept routing information from other routers that have been configured with the same password or authentication information. Note: Authentication does not encrypt the routing table.
Hc vin mng Bach Khoa - Website: www.bkacad.com 23
Configuring authentication
Router(config)#key chain Romeo Router(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 the default clear text authentication. Although clear text authentication may be necessary to communicate with some RIP v2 implementations, for security concerns use the more secure MD5 authentication whenever possible.
Hc vin mng Bach Khoa - Website: www.bkacad.com 24
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 migration process Select a method for injecting the required edge protocol routes into the core.
Hc vin mng Bach Khoa - Website: www.bkacad.com 25
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 ?
26
protocol process-id
match route-type
metric metric-value
(Optional) Parameter used to specify the RIP seed metric for the redistributed route. When you are redistributing into RIP, this value is not specified and no value is specified using the default-metric router configuration command, then the default metric is 0, which is interpreted as infinity, and routes will not be redistributed. The metric for RIP is the hop count.
(Optional) Identifier of a configured route map to be interrogated to filter the importation of routes from this source routing protocol to the current routing protocol.
27
route-map map-tag
28
There are several ways to verify and troubleshoot RIPv2. Many of the same commands used 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 each interface. 4. Remove any unnecessary configuration commands that are no longer necessary or have been replaced by other commands.
Hc vin mng Bach Khoa - Website: www.bkacad.com 29
Router#show ip route C C R R C C R C R R 172.30.0.0/16 is variably subnetted, 6 subnets, 2 masks 172.30.200.32/28 is directly connected, Loopback2 172.30.200.16/28 is directly connected, Loopback1 172.30.2.0/24 [120/2] via 192.168.4.21, 00:00:21, Serial0 172.30.1.0/24 [120/2] via 192.168.4.21, 00:00:21, Serial0 172.30.100.0/24 is directly connected, Ethernet0 172.30.110.0/24 is directly connected, Loopback0 192.168.4.0/30 is subnetted, 2 subnets 192.168.4.24 [120/1] via 192.168.4.21, 00:00:21, Serial0 192.168.4.20 is directly connected, Serial0 10.0.0.0/8 [120/1] via 192.168.4.21, 00:00:21, Serial0 207.0.0.0/8 [120/1] via 192.168.4.21, 00:00:21, Serial0
31
32
33
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 Includes mask 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 multicast 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 <text omitted>
Hc vin mng Bach Khoa - Website: www.bkacad.com 34
35
36
The show ip rip database command to check summary address entries in the RIP 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, the summary address is also removed from the routing table.
Hc vin mng Bach Khoa - Website: www.bkacad.com 37
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.
Hc vin mng Bach Khoa - Website: www.bkacad.com 38
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 CIDR supernets, VLSM and discontiguous networks.
39
40
41
42
43
44