Assignment IGRP

CHAPTER 7
Routing Information Protocol Version 2
• Operation of RIPv2
• Configuring RIPv2
• Troubleshooting RIPv2
www.Taleem.greatnow.com
1
RIPV2
• It is RIPv1 with some extensions to bring it more up-to-date
with modern routing environments. These extensions are:
1. Subnet masks carried with each route entry
2. Authentication of routing updates
3. Next-hop addresses carried with each route entry
4. External route tags
5. Multicast route updates
• The most important of these extensions is the addition of a
Subnet Mask field to the routing update entries, enabling
the use of variable-length subnet masks and qualifying
RIPv2 as a classless routing protocol.
2
Operation of RIPv2
• All of the operational procedures, timers, and stability
functions of RIPv1 remain the same in version 2, with the
exception of the broadcast updates. RIPv2 multicasts
updates to other RIPv2-speaking routers, using the reserved
class D address 224.0.0.9.
• When a router performs classless route lookups, it does not
pay attention to the class of the destination address. Instead,
it performs a bit-by-bit best match between the destination
address and all its known routes.
• The true defining characteristic of classless routing
protocols is the capability to carry subnet masks in their
route advertisements. Classless routing protocols enable the
use of variable-length subnet masking.
3
Compatibility With RIP1
Newer editions of the protocol, like RIPv2, can be backward compatible

with RIPv1.
“Compatibility switch” with four settings, which allows versions 1 and 2
to interoperate:
1. RIP1, in which only RIPv1 messages are transmitted
2. RIP1 Compatibility, which causes RIPv2 to broadcast its message
instead of multicast them so that RIPv1 may receive them
3. RIP2, in which RIPv2 messages are multicast to destination
address 224.0.0.9
4. None, in which no updates are sent.
4
Compatibility With RIP1
• Classless routing protocols carry subnet masks in their

routing updates.
• One benefit of having a mask associated with each route
is that the all-zeros and all-ones subnets are now available
for use. Classful routing protocols cannot distinguish
between an all-zeros subnet (172.16.0.0, for example) and
the major network number (172.16.0.0). Likewise, they
cannot distinguish between a broadcast on the all-ones
subnet (172.16.255.255) and an all-subnets broadcast
(172.16.255.255).
5
Variable-Length Subnet Masking
If a subnet mask can be individually associated with each destination

address advertised throughout an Internetwork, there is no reason why all
the masks must be of equal length. That fact is the basis for VLSM.
Using VLSM, the class C address shown can be subnetted to accommodate
this internetwork and the hosts on each of its data links.
6
• With VLSM the widely varying host address requirements of the
internetwork of Figure 7.4 can be met using a class C network address.
Table 7.1 shows the subnets and the address ranges available within each.
• VLSM can be thoughts of as sub-subnetting.
7
•VLSM allows each of these PVCs to be configured as a
separate subnet without wasting host addresses.
8
This class B address has been submitted with a 24-bit mask.

172.17.11.0 has been subsubnetted with a 30-bit mask; the resulting
64 subnets can be assigned to point-to-point links.
9
A Basic RIPv2 Configuration
• By default, a RIP process configured on a Cisco router sends only RIPv1
messages but listens to both RIPv1 and RIPv2. This default is changed with
the version command, as in the following example:
router rip
version 2
network 172.25.0.0
network 192.168.50.0
• In this mode, the router sends and receives only RIPv2 messages.
• The router can be configured to send and receive only RIPv1 messages:
router rip
version 1
network 172.25.0.0
network 192.168.50.0
10
Case Study: Compatibility with RIPv1
e0 e1
e2
11
Case Study: Compatibility with RIPv1
• interface Ethernet0
• 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 255.255.255.240
• !
• router rip
• version 2
• network 172.25.0.0
• network 192.168.50.0
12
Case Study: Using VLSM
• Referring again to (Previous Slide), the subnet 172.25.150.0/24 has been
assigned to the internet shown. That subnet has been further subnetted to fit
the various data links by expanding the mask to 28 bits; the available sub-
subnets, in binary and dotted decimal, are shown below. Each of the subnets
will have, according to the 2n – 2 formula, 14 host addresses. Out of these,
172.25.150.32, 172.25.150.192, and 172.25.150.224 have been used.
13
VLSM can be used to adapt addresses to the requirements of

individual data links.
14
A 30-bit mask is applied to subnet 172.25.150.240.
15
Case Study: Discontiguous Subnets
& Classless Routing
Cochiti, Isleta, Jemez, and Tesuque are each attached to two

Ethernets. One Ethernet at each router is a member of subnet
172.25.150.0/24, and the other is a member of network 92.168.50.0/24.
16
& Classless Routing
The default behavior of RIPv2, however, is to summarize at network boundaries
the same as RIPv1. To turn off summarization and allow subnets to be
advertised across network boundaries, use the command no auto-summary
with the RIP process. The configuration for Cochiti is:
interface Ethernet0
ip address 192.168.50.1 255.255.255.224
!
interface Ethernet1
ip address 172.25.150.1 255.255.255.240
!
interface Serial0
ip address 172.25.150.242 255.255.255.252
17
& Classless Routing
!
router rip
version 2
network 172.25.0.0
network 192.168.50.0
no auto-summary
Isleta, Jemez, and Tesuque will have similar configurations. Summarization
must also be turned off at Taos and at Acoma. Recall from Figure (case study
Compatibility with RIPv1) that Laguna was running RIPv1. For this
configuration to work, it must be changed to version 2.
18
Case Study: Authentication
Cisco's implementation of RIPv2 message authentication includes the choice of
simple password or MD5 authentication, and the option of defining multiple
keys, or passwords, on a "key chain." The router may then be configured to use
different keys at different times
In the following example, a key chain named Tewa is configured at Taos. Key 1,
the only key on the chain, has a password of Kachina; interface E0 then uses the
key, with MD5 authentication, to validate updates from Laguna.
The steps for setting up RIPv2 authentication follow.
1. Define a key chain with a name.
2. Define the key or keys on the key chain.
3. Enable authentication on an interface and specify the key chain to be used.
4. Specify whether the interface will use clear text or MD5 authentication.
5. Optionally configure key management..
19
Taos(config)#key chain Tewa
Taos(config-keychain)#key 1
Taos(config-keychain-key)#key-string Kachina
Taos(config-keychain-key)#interface ethernet 0
Taos(config-if)#ip rip authentication key-chain Tewa
Taos(config-if)#ip rip authentication mode md5
Key management is used to migrate from one authentication key to another. In
the following example, Laguna is configured to begin using the first key at 4:30
p.m. on November 28, 1997, for 12 hours (43200 seconds). The second key
becomes valid at 4:00 a.m. on November 29, 1997, and will be used until 1:00
p.m. on April 15, 1998. The third key becomes valid at 12:30 p.m. on April 15,
1998, and will remain valid permanently after that.
20
key chain Keres
key 1
key-string Kachina
accept-lifetime 16:30:00 Nov 28 1997 duration 43200
send-lifetime 16:30:00 Nov 28 1997 duration 43200
key 2
key-string Kiva
accept-lifetime 04:00:00 Nov 29 1997 13:00:00 Apr 15
1998
send-lifetime 04:00:00 Nov 29 1997 13:00:00 Apr 15
1998
key 3
key-string Koshare www.Taleem.greatnow.com
21
accept-lifetime 12:30:00 Apr 15 1998 infinite
send-lifetime 12:30:00 Apr 15 1998 infinite
!
interface Ethernet0
ip address 198.168.50.130 255.255.255.192
ip rip authentication key-chain Keres
ip rip authentication mode md5
22
Troubleshooting RIPv2
• Two configuration problems common to RIPv2 are mismatched
versions and misconfigured authentication. Both difficulties are easy
to discover with debugging
23
Case Study: Misconfigured VLSM
• Host C in Figure (next slide) cannot communicate across the
internetwork, and it cannot even ping the other hosts or routers on the
local data link. Hosts A and B have no communications problems with
each other or with any other host across the internetwork, but they
cannot communicate with C. All hosts are configured to use
172.19.35.1 as the default gateway address.
• When host B pings host C, the first ping is successful and
subsequent pings fail.
24
Hosts A and B can communicate across the internetwork, but

host C cannot.
25
• Host C's ARP cache shows the correct MAC address
associated with all addresses.
26
• Host B's ARP cache shows that C's IP address is mapped
to the MAC address of San_Felipe's interface 172.19.35.2.
27
• The ping results begin to make sense. B broadcasts an ARP Request
for 172.19.35.72. C sends an ARP Reply, and B sends its first ping
correctly. In the meantime, San_Felipe has received the ARP Request
• and apparently believes that it has a route to 172.19.35.72. It responds
with a proxy ARP (later than C because it has to perform a route
lookup first), which causes B to overwrite C's MAC address.
• Subsequent Echo Request packets are sent to San_Felipe, where they
are routed off the local data link and lost. A protocol analyzer attached
to the Ethernet proves the point (Figure 7.24).
28
• A protocol analyzer, filtering for ARP packets, shows B's
ARP request to C and replies from both host C
(00a0.24a8.a1a5) and router San_Felipe (0000.0c0a.2aa9).
• When analyzing any addressing scheme, and especially a

VLSM design, the subnets for every data link should be
determined so that conflicts and overlaps may be discovered.
29
• C's IP addresses with subnet bits of the last octet highlighted.
• A comparison shows that the first three bits of 172.19.35.72/25 match

subnet 172.19.35.64/27. San Felipe has routes to both 172.19.35.0/25 and
to 172.19.35.64/27. Fig (next slide)
• The solution to this trouble is to re-address either host C or subnet
172.19.35.64. This step sounds easy on paper. In real life, it may
involve some difficult decisions, as it did for the client on whose
internetwork this case study is based.
30
• san_fellipe has routes to both 172.19.35.0/25 and to
172.19.35.64/27;the second route is a better match of host
c's address than is the first route.
31
A 27-bit subnet mask is applied to subnet 172.19.35.0.
The difficult decision is in deciding whether to re-address the backbone,

giving up some address space there, or to re-address the two remote subnets
and give up address space on each of them. The second option was chosen,
using a 28-bit mask to divide 172.19.35.224/27 into two subnets for the
remote sites.
32

Assignment IGRP

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Assignment IGRP

Uploaded by

Copyright:

Available Formats

CHAPTER 7

Routing Information Protocol Version 2

Newer editions of the protocol, like RIPv2, can be backward compatible

• Classless routing protocols carry subnet masks in their

If a subnet mask can be individually associated with each destination

This class B address has been submitted with a 24-bit mask.

VLSM can be used to adapt addresses to the requirements of

A 30-bit mask is applied to subnet 172.25.150.240.

Cochiti, Isleta, Jemez, and Tesuque are each attached to two

Hosts A and B can communicate across the internetwork, but

• When analyzing any addressing scheme, and especially a

• A comparison shows that the first three bits of 172.19.35.72/25 match

The difficult decision is in deciding whether to re-address the backbone,

You might also like