CISCO CCNP ROUTE 640-902,300-101

WELCOME TO CISCO CCNP

ROUTE
(640-902, 300-101)
 Routing Information Protocol (RIP)

• The RIP process operates from UDP port 520; all RIP messages are
encapsulated in a UDP segment with both the Source and
Destination Port fields set to that value.
• RIP defines two message types: Request messages and Response
messages.
• A Request message is used to ask neighboring routers to send an
update. A Response message carries the update.
• The metric used by RIP is hop count, with 1 signifying a directly
connected network of the advertising router and 16 signifying an
unreachable network.
• On startup, RIP broadcasts a packet carrying a Request message
out each RIP-enabled interface.
• The RIP process then enters a loop, listening for RIP Request or
Response messages from other routers. Neighbors receiving the
Request send a Response containing their routing table.
 Routing Information Protocol (RIP)

• When the requesting router receives the Response messages, it

processes the enclosed information.
• If a particular route entry included in the update is new, it is
entered into the routing table along with the address of the
advertising router, which is read from the source address field of
the update packet.
• If the route is for a network that is already in the table, the existing
entry will be replaced only if the new route has a lower hop count.
• If the advertised hop count is higher than the recorded hop count
and the update was originated by the recorded next-hop router, the
route will be marked as unreachable for a specified holddown
period.
• If at the end of that time the same neighbor is still advertising the
higher hop count, the new metric will be accepted
 About the Instructor
• STEPHEN ANAAFI
• BSC and MSC Information Technology
• CCIE(WRITTEN), CCNP, CCNA, CCNAS,
• CPT,CHFI,CEH,CISA,CISSP
• MCSE: Server Infrastructure 2012
• MCSE:Exchange 2013,
• MCSE:Server 2008
• 14 years experience
 Routing Information Protocol (RIP)

• When the requesting router receives the Response messages, it

processes the enclosed information.
• If a particular route entry included in the update is new, it is
entered into the routing table along with the address of the
advertising router, which is read from the source address field of
the update packet.
• If the route is for a network that is already in the table, the existing
entry will be replaced only if the new route has a lower hop count.
• If the advertised hop count is higher than the recorded hop count
and the update was originated by the recorded next-hop router, the
route will be marked as unreachable for a specified holddown
period.
• If at the end of that time the same neighbor is still advertising the
higher hop count, the new metric will be accepted
 Routing Information Protocol (RIPV1)

• RIP Timers and Stability Features

• After startup, the router sends a Response message out every RIP-
enabled interface every 30 seconds, on average.
• The Response message, or update, contains the router's full routing
table with the exception of entries suppressed by the split horizon
rule.
• The update timer initiating this periodic update includes a random
variable to prevent table synchronization.
• The RIP updates from Cisco routers vary from 25.5 to 30 seconds
• The destination address of the update is the all-hosts broadcast
255.255.255.255
• the invalidation timer, which distance vector protocols use to
limit the amount of time a route can stay in a routing table without
being updated.
 Routing Information Protocol (RIPV1)
• RIP Timers and Stability Features
• The expiration timer is initialized to 180 seconds whenever a new
route is established and is reset to the initial value whenever an
update is heard for that route.
• If an update for a route is not heard within that 180 seconds (six
update periods), the hop count for the route is changed to 16,
marking the route as unreachable.
• garbage collection or flush timer: is set to 240 seconds–60
seconds longer than the expiration time. The route will be
advertised with the unreachable metric until the garbage collection
timer expires, at which time the route is removed from the routing
table.
• holddown timer: A per-route timer (default 180 seconds) that
begins after a route has been declared invalid (that is, after the
Invalid aftertimer expire. Command manipulated is:
• timers basic update invalid holddown flush
 Routing Information Protocol (RIPV1)
• RIP Timers and Stability Features
• These four timers can be manipulated with the command:

timers basic update invalid holddown flush

• This command applies to the entire RIP process. If the timing of one
router is changed, the timing of all the routers in the RIP domain
must be changed.
• RIP has an administrative distance of 120, and the metric for RIP is
hop count
• If a device has two paths to the destination network, the path
with fewer hops will be chosen as the path to forward traffic
• If more than one route exists to the same destination with equal
hop counts, equal-cost load balancing will be performed
 Routing Information Protocol (RIPV1)
• Classful Routing
• When a packet enters a RIP-speaking router and a route table
lookup is performed, the various choices in the table are pruned
until a single path remains.
• First, the network portion of the destination address is read and the
routing table is consulted for a match.
• It is this first step of reading the major class A, B, or C network
number that defines a classful routing table lookup.
• If there is no match for the major network, the packet is dropped
and an ICMP Destination Unreachable message is sent to the
packet's source.
• If there is a match for the network portion, the subnets listed for
that network are examined.
• If a match can be found, the packet is routed. If a match cannot be
made, the packet is dropped and a Destination Unreachable
message is sent
 Routing Information Protocol (RIPV1)
• Classful Routing Summarization at Boundary Routers
• there is no provision for RIP to advertise a subnet mask along with
each route entry. And accordingly, no masks are associated with the
individual subnets in the routing table
• Boundary routers perform route summarization, also known as
subnet hiding
• Figure shows a router that is attached at the boundary of two
major networks, the class A network 10.0.0.0 and the class C
network 192.168.115.0.
• This boundary router does not send details of the subnets of one
major network into the other major network.
• As the illustration shows, it automatically performs summarization,
or subnet hiding.
• It advertises only the address 10.0.0.0 into network 192.168.115.0
and advertises only the address 192.168.115.0 into network
10.0.0.0.
•
 Routing Information Protocol (RIPV1)
• Classful Routing Summarization at Boundary Routers
• Figure 5.6. This router, at the boundary of two major networks,
does not advertise the subnets of one network to routers within the
other network.
 Routing Information Protocol (RIPV1)
• Classful Routing Summarization at Boundary Routers
• the routing tables for routers within network 192.168.115.0 have
only a single entry that directs packets for 10.0.0.0 toward the
boundary router.
• The boundary router has an interface directly on network 10.0.0.0
and therefore has a subnet mask with which to derive the subnet
for routing a packet within that network's "cloud.“
• classful routing does not advertise an address mask along with the
advertised destination address. Therefore, a classful routing
protocol must first match the major class A, B, or C network portion
of a destination address.
 Routing Information Protocol (RIPV1)
• Classful Routing Summarization at Boundary Routers
• through the router:
• If the destination address is a member of a directly connected major
network, the subnet mask configured on the interface attached to
that network will be used to determine the subnet of the destination
address. Therefore, the same subnet mask must be used
consistently throughout that major network.
• If the destination address is not a member of a directly connected
major network, the router will try to match only the major class A,
B, or C portion of the destination address
• RIP is capable of load balancing traffic over equal-cost paths. The
default is four equal-cost paths.
• If the maximum number of paths is set to one, load
balancing is disabled
 Routing Information Protocol (RIP)
• RIPv2 Convergence and Loop Prevention
• split horizon. Split horizon prevents routing information from
being sent out the same interface from which it was received
• Split horizon with poison reverse: this principle states that a
network should always be explicitly advertised as unreachable over
the interface that is used to reach that network. sends update with
a metric of 16, which is considered unreachable by RIP. The idea is
that it is better to explicitly tell a neighbor that a route is
inaccessible than not tell the neighbor at all.
• Route poisoning (setting the metric to 16) is also used by a router
to inform a neighbor when it no longer has a route to a specific
network. is a mechanism used to rapidly flush a route that has
become unreachable by advertising this route with the metric set to
infinity.
• A router that receives an update about a network from its next hop
with an infinite metric will immediately remove the route to the
network through that particular next hop from its routing table
 Routing Information Protocol (RIP)
• RIPv2 Convergence and Loop Prevention
• NB: Poisoned Reverse is an extension to the Split Horizon
principle that advertises a route as unreachable back to its next hop
to prevent it from creating a routing loop, while
• Route Poisoning advertises a truly unreachable route to quickly
flush it from routing tables and to allow a backup path to take over
• Triggered updates are sent in the moment of detecting a change
in reachability of a network, rather than waiting for the full Update
interval to expire.
• Connecting or learning about a new network, disconnecting it or
learning about its unreachability, or a change to its metric will
cause a router to immediately send an advertisement with the
updated information.
• This update commonly carries only the changed network, without
listing all other known networks
 Routing Information Protocol (RIP)
• RIPv2 Convergence and Loop Prevention
• Invalid after timer: A per-route timer (default 180 seconds) that
is reset and begins after an update about a route has been received
from its next hop. If the updates about the route from its next hop
cease to be received and the Invalid after timer reaches its limit,
the route is declared invalid and the Holddown timer starts for this
route
• Hold down: A per-route timer (default 180 seconds) that begins
after a route has been declared invalid (that is, after the Invalid
after timer expires). The router starts advertising that route as
unreachable, does not accept any updated information, and does
not modify the routing table entry for that route until the Hold down
timer for that route expires.
• Its main purpose is to delay processing updates about a network
whose reachability has become questionable, as the received
updates might not yet contain up-to-date information
 Routing Information Protocol (RIP)
• RIP Convergence and Loop Prevention
• Flushed after time: A per-route timer (default 240 seconds) that
is reset and begins after an update about a route has been received
from its next hop. If the updates about the route from its next hop
cease to be received and the Flushed after timer reaches its limit,
the router removes the route from the routing table entirely

Configuring RIP
• Two steps are necessary to configure RIP:
• Enable RIP with the command router rip.
• Specify each major network on which to run RIP with the network
command
 Routing Information Protocol (RIP)
Configuring RIP
• Figure shows a four-router internetwork, with four major network
numbers. Router Goober is attached to two subnets of network
172.17.0.0.
 Routing Information Protocol (RIP)
Configuring RIP
• Both Andy and Barney are border routers between class-level
networks
• The commands necessary to enable RIP are:
• Goober(config)#router rip
• Goober(config-router)#network 172.17.0.0

• Opie(config)#router rip
• Opie(config-router)#network 172.17.0.0
• Barney(config)#router rip
Barney(config-router)#network 10.0.0.0
Barney(config-router)#network 192.168.83.0
•
Andy(config)#router rip
Andy(config-router)#network 172.17.0.0
Andy(config-router)#network 192.168.12.0
Andy(config-router)#network 192.168.83.0
 Routing Information Protocol (RIP)
Configuring RIP (Passive Interfaces)
• The router Floyd has been added to the internetwork. It is desired
that no RIP advertisements be exchanged between Floyd and Andy.
 Routing Information Protocol (RIP)
Configuring RIP (Passive Interfaces)
• By not including a network statement for 192.168.12.0, Floyd will
not advertise on interface 192.168.12.66. Andy, however, has two
interfaces attached to 172.17.0.0; the network must be included
under RIP.
• To block RIP broadcasts on an interface connected to a subnet of a
RIP-enabled network, add the passive-interface command to the
RIP process. Andy's RIP configuration is:
Andy(config)#router rip
Andy(config)#passive-interface Ethernet0
Andy(config)# network 172.17.0.0
Andy(config)# network 192.168.12.0
Andy(config)# network 192.168.83.0

Floyd(config)#router rip
Floyd(config-router)#network 192.168.100.0
Floyd(config-router)#network 192.168.12.0
 Routing Information Protocol (RIP)
Configuring RIP (Unicast Updates)
• Next, router Bea is added to the Ethernet link that Andy and Floyd
share. The no-RIP policy between Andy and Floyd remains in place,
but now Bea and Andy, as well as Bea and Floyd, must exchange
RIP advertisements
 Routing Information Protocol (RIP)
Configuring RIP (Unicast Updates)
• Next, router Bea is added to the Ethernet link that Andy and Floyd
share. The no-RIP policy between Andy and Floyd remains in place,
but now Bea and Andy, as well as Bea and Floyd, must exchange
RIP advertisements

Bea(config)#router rip
bea(config)# network 192.168.12.0
bea(config)# network 192.168.200.0

Andy(config)#router rip
Andy(config)#passive-interface Ethernet0
Andy(config)# network 172.17.0.0
Andy(config)# network 192.168.12.0
Andy(config)# network 192.168.83.0
Andy(config)# neighbor192.168.12.67
 Routing Information Protocol (RIP)
Configuring RIP (Unicast Updates)
• The addition of a neighbor command under the RIP processes of
Andy enables RIP to send a unicast advertisement to Bea's interface
while the passive-interface command continues to prevent
broadcast updates on the link

Floyd(config)#router rip
Floyd(config)#passive-interface Ethernet 0
Floyd(config-router)#network 192.168.100.0
Floyd(config-router)#network 192.168.12.0
Floyd(config-router)#neighbor192.168.12.67

Because Floyd must now send advertisements to Bea, a network

command for 192.168.12.0 must be added. Passive-interface is also
added to prevent broadcast updates, and a neighbor command is
added to enable unicast updates to Bea:
 Routing Information Protocol (RIP)
Configuring RIP (Discontiguous Subnets)
• In another router has been added to the internetwork with a subnet
10.33.32.0/20 on its E1 interface. The problem is that the other
subnet of network 10.0.0.0, 10.33.0.0/20, is connected to Barney,
and the only route between the subnets is via 192.168.83.0 and
192.168.12.0—two entirely different networks. As a result, network
10.0.0.0 is discontiguous.
• Classful protocols such as RIP and IGRP cannot route a topology in
which the subnets of network 10.0.0.0 are separated by different
networks
• Barney will consider itself a border router between network 10.0.0.0
and network 192.168.83.0; likewise, Ernest_T will consider itself a
border router between 10.0.0.0 and 192.168.12.0.
• Both will advertise a summary route of 10.0.0.0, and as a result
Andy will be fooled into thinking that it has two equal-cost paths to
the same network.
 Routing Information Protocol (RIP)
Configuring RIP (Discontiguous Subnets)
• Andy will load share on the links to Barney and Ernest_T, and there
is now only a 50-50 chance that packets to network 10.0.0.0 will
reach the correct subnet
 Routing Information Protocol (RIP)
Configuring RIP (Discontiguous Subnets)
• The solution is to configure subnets of network 10.0.0.0 on the
same links on which 192.168.83.0/24 and 192.168.12.192/27
reside. This is accomplished with secondary IP addresses, as
follows:
• Barney(config)#interface e0
• Barney(config-if)#ip address 10.33.55.1 255.255.240.0 secondary

• Andy(config)#interface e1
• Andy(config-if)#ip address 10.33.55.2 255.255.240.0 secondary
Andy(config-if)#interface e2
• Andy(config-if)#ip address 10.33.75.1 255.255.240.0 secondary
• Andy(config-if)#router rip Andy(config-router)#network 10.0.0.0

• Ernest_T(config)#interface e0
• Ernest_T(config-if)#ip address 10.33.75.2 255.255.240.0 secondary
 Routing Information Protocol (RIP)
Configuring RIP (Discontiguous Subnets)
Because Andy did not previously have an interface on network
10.0.0.0, a network statement is added to the RIP process. The
result of the configuration can be seen in FIG. The existing logical
network structure remains in place, and a contiguous network
10.0.0.0 is "overlaid" onto it. The use of secondary addresses can
contribute to congestion on the network
 Routing Information Protocol (RIP)
Configuring RIP (Manipulating RIP Metrics)
• A serial link, to be used as a backup, has been added between
Ernest_T and Barney. This link should be used only if the route via
Andy fails. The problem is that the path between Barney's 10.33.0.0
subnet and Ernest_T's 10.33.32.0 subnet is 1 hop via the serial link
and 2 hops via the preferred Ethernet links. Under normal
circumstances, RIP will choose the serial link.
• The route metrics can be manipulated with the offset-list command.
The command specifies a number to add to the metric of a route
entry and references an access list to determine which route entries
to modify. The syntax of the command is:
• offset-list {access-list-number | name} {in| out} offset [type
number]
 Routing Information Protocol (RIP)
Configuring RIP (Manipulating RIP Metrics)

• RIP metrics must be manipulated so that the 2-hop Ethernet route

between Barney and Ernest_T will be preferred over the 1-hop serial
route
 Routing Information Protocol (RIP)
Configuring RIP (Manipulating RIP Metrics)
• Ernest_T(config)#access-list 1 permit 10.33.0.0 0.0.0.0
Ernest_T(config)#router rip
Ernest_T(config-router)#network 192.168.12.0
Ernest_T(config-router)#network 10.0.0.0
Ernest_T(config-router)#offset-list 1 in 2 Serial0

• An access list is written that identifies the route to subnet

10.33.0.0. The syntax of the offset list says, "Examine RIP
advertisements incoming from interface S0. For route entries
matching the addresses specified in access list 1, add 2 hops to the
metric."
• After Barney is configured, it will have the following entries in its
configuration file
 Routing Information Protocol (RIP)
Configuring RIP (Manipulating RIP Metrics)
• Barney(config)#access-list 5 permit 10.33.32.0 0.0.0.0

• Barney(config)# router rip

• Barney(config)# offset-list 5 in 2 Serial0
• Barney(config)# network 10.0.0.0
• Barney(config)# network 192.168.83.0
•
 Routing Information Protocol (RIP v2)
• RIPv2 multicasts updates to other RIPv2-speaking routers, using
the reserved class D address 224.0.0.9
• RIPv2 operates from UDP port 520 and has a maximum datagram
size (with an eight-byte UDP header) of 512 octets.
• Subnet Mask is 32-bit mask that identifies the network and subnet
portion of the IP address
• Metric is a hop count between 1 and 16

Compatibility with RIPv1

• compatibility settings for RIPv1 and RIPv2

RFC 1723 defines a "compatibility switch" with four settings, which

allows versions 1 and 2 to interoperate:
• RIP-1, in which only RIPv1 messages are transmitted
 Routing Information Protocol (RIP v2)
• Compatibility with RIPv1
• RIP-1 Compatibility, which causes RIPv2 to broadcast its messages
instead of multicast them so that RIPv1 may receive them
• RIP-2, in which RIPv2 messages are multicast to destination
address 224.0.0.9
• None, in which no updates are sent
• The RFC recommends that these switches be configurable on a per
interface basis.
• Additionally, RFC 1723 defines a "receive control switch" to regulate
the reception of updates. The four recommended settings of this
switch are:
• RIP-1 Only; RIP-2 Only
• Both
• None
 Routing Information Protocol (RIP v2)
• Classless Route Lookups
• Classless routing protocols carry subnet masks in their routing
updates
• 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 default behavior for classful routing protocols such as RIPv1
and IGRP can be changed, by entering the global command ip
classless
• Supports vlsm
• Supports authentication
 Routing Information Protocol (RIP v2)
• Configuring RIPv2 (Compatibility with RIPv1)
• The internetwork in Figure contains routers speaking both RIPv1
and RIPv2. Additionally, Pojoaque is a Linux host running routed,
which understands only RIPv1.
 Routing Information Protocol (RIP v2)
• Configuring RIPv2 (Compatibility with RIPv1)
• Taos is running RIPv2 but must also speak version 1 to some
devices.
• The configuration of Taos is:
• interface Ethernet0 
 ip address 192.168.50.129 255.255.255.192 
 ip rip send version 1 
 ip rip receive version 1 
! 
interface Ethernet1 
 ip address 172.25.150.193 255.255.255.240 
 ip rip send version 1 2 
! 
interface Ethernet2 
 ip address 172.25.150.225 255.255.255.240 
! 
 Routing Information Protocol (RIP v2)
• Configuring RIPv2 (Compatibility with RIPv1)
• The configuration of Taos is:

!
router rip 
 version 2 
 network 172.25.0.0 
 network 192.168.50.0

• Because router Laguna is a RIPv1 speaker, E0 of Taos is configured

to send and receive RIPv1 updates.
• E1 is configured to send both version 1 and 2 updates, to
accommodate the RIPv1 at Pojoaque and the RIPv2 at Sandia. E2
has no special configuration; it sends and receives version 2 by
default
 Routing Information Protocol (RIP v2)
• Configuring RIPv2 (Compatibility with RIPv1)
• So, Pojoaque does not know about subnet 172.25.150.32. Two
remedies are available: First, Sandia could be configured to send
both RIP versions. Second, split horizon can be turned off at Taos's
E1 interface with the following c onfiguration:
• interface Ethernet1 
 ip address 172.25.150.193 255.255.255.240 
 ip rip send version 1 2 
 no ip split-horizon 
 Routing Information Protocol (RIP v2)
• Configuring RIPv2 (Discontiguous Subnets and Classless
Routing )
• shows that two Ethernets are connected to each of the four new
routers. At each site, one Ethernet is a member of subnet
172.25.150.0/24 and will have no more than 12 hosts.. Four unused
subnets are chosen from Figure and assigned
 Routing Information Protocol (RIP v2)
• Configuring RIPv2 (Discontiguous Subnets and 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 
! 
 Routing Information Protocol (RIP v2)
• Configuring RIPv2 (Discontiguous Subnets and 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
 Routing Information Protocol (RIP v2)
• Configuring RIPv2 (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
• The steps for setting up RIPv2 authentication follow.
• Define a key chain with a name.
• Define the key or keys on the key chain.
• Enable authentication on an interface and specify the key chain to
be used.
• Specify whether the interface will use clear text or MD5
authentication.
• Optionally configure key management.
 Routing Information Protocol (RIP v2)
• Configuring RIPv2 (Authentication )
• 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
• 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

• If the command ip rip authentication mode md5 is not added, the

interface will use the default clear text authentication.
• Key management is used to migrate from one authentication key to
another.
 Routing Information Protocol (RIP v2)
• Configuring RIPv2 (Authentication )
• 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.
• key chain CCNP 
 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 
  accept-lifetime 12:30:00 Apr 15 1998 infinite 
  send-lifetime 12:30:00 Apr 15 1998 infinite 
 Routing Information Protocol (RIP v2)
• Configuring RIPv2 (Authentication )

!
interface Ethernet0 
 ip address 198.168.50.130 255.255.255.192 
 ip rip authentication key-chain CCNP
 ip rip authentication mode md5 
• Both the accept-lifetime and the send-lifetime commands must have
a specified start time and may have either a specified duration or
end time or the keyword infinite
• The key numbers are examined from the lowest to the highest, and
the first valid key is used.
• Although this configuration uses a 30-minute overlap to compensate
for differences in system times, it is highly recommended that a
time synchronization protocol such as Network Time Protocol (NTP)
be used with key management
 Routing Information Protocol (RIP v2)
• Configuring RIPv2 (Authentication )

!
interface Ethernet0 
 ip address 198.168.50.130 255.255.255.192 
 ip rip authentication key-chain CCNP
 ip rip authentication mode md5 
• Both the accept-lifetime and the send-lifetime commands must have
a specified start time and may have either a specified duration or
end time or the keyword infinite
• The key numbers are examined from the lowest to the highest, and
the first valid key is used.
• Although this configuration uses a 30-minute overlap to compensate
for differences in system times, it is highly recommended that a
time synchronization protocol such as Network Time Protocol (NTP)
be used with key management
Routing Information Protocol (RIPNG)

•RIPNG
 Routing Information Protocol (RIPNG)
• Comparing RIPv2 to RIPng
• Some small differences in the Update message format exist as well,
with the most obvious difference being that the Updates list IPv6
prefixes and prefix lengths.
• IPv6 supports authentication using the IPsec Authentication Header
(AH), RIPng does not natively support authentication, instead
relying on IPsec.
• RIPng remains a plain distance-vector protocol utilizing UDP port
521 instead of 520
• The destination IPv6 address for multicasted RIPng messages is
FF02::9. Metric is again based on hop count, with 15 being the
maximum usable metric and 16 representing infinity.
 Routing Information Protocol (RIPNG)
• Comparing RIPv2 to RIPng
 Routing Information Protocol (RIPNG)
• Configuring RIPng
• The following list shows the basic configuration steps for RIPng,
including steps to enable IPv6 routing and enabling IPv6 on the
interfaces:
• Step 1. Enable IPv6 routing with the ipv6 unicast-routing global
command.
• Step 2. Enable RIPng using the ipv6 router rip name global
configuration command. The name must be unique on a router but
does not need to match on neighboring routers.
• Step 3. Enable IPv6 on the interface, typically with one of these two
methods:
 Configure an IPv6 unicast address on each interface using the ipv6
address address/prefix-length [eui-64] interface command.
 Configure the ipv6 enable command, which enables IPv6 and causes the
router to derive its link-local address.
 Routing Information Protocol (RIPNG)
• Configuring RIPng
• Step 4. Enable RIP on the interface with the ipv6 rip name enable
interface subcommand (where the name matches the ipv6 router rip
name global configuration command).
• As with RIPv1 and RIPv2, for any interface on which RIPng has been
enabled, the RIP process does three main actions:
• 1. It starts sending RIP updates on that interface.
• 2. It also starts processing any RIP updates received on that
interface.
• 3. Finally, it advertises the connected routes on that interface. In
particular, because IPv6 allows the configuration of multiple IPv6
unicast addresses on an interface, RIP advertises most IPv6 unicast
prefixes associated with the interface.
• The notable exceptions are that RIP does not advertise any link-
local addresses, nor does RIP advertise the local host routes—routes
 Routing Information Protocol (RIPNG)
• Configuring RIPng
 Routing Information Protocol (RIPNG)
• Configuring RIPng
• R1# show running-config

ipv6 unicast-routing
ipv6 router rip fred
interface FastEthernet0/0.1
ipv6 address 2012::1/64  
ipv6 rip fred enable 
!
! interface FastEthernet0/0.2
  ipv6 address 2017::1/64  
ipv6 rip fred enable 
 Routing Information Protocol (RIPNG)
• Configuring RIPng
• R1# show running-config
! interface FastEthernet0/1.18
  ipv6 address 2018::1/64   
ipv6 rip fred enable  
!
interface Serial0/0/0.3  
ipv6 address 2013::1/64  
ipv6 rip fred enable 
!
interface Serial0/0/0.4
  ipv6 address 2014::1/64
ipv6 rip fred enable
! 

interface Serial0/0/0.5  
ipv6 address 2015::1/64  
ipv6 rip fred enable
 Routing Information Protocol (RIPNG)
• Configuring RIPng

• RIPng is already preconfigured on R1. On R1, there is a static

default route that is already configured, which routes all the
unknown traffic toward the Internet. Later in this section, R1
will be configured to share this default route with R2 using RIPng
 Routing Information Protocol (RIPNG)
• Configuring RIPng
• R2(config)# ipv6 unicast-routing
• R2(config)# ipv6 router rip CCNP_RIP
• R2(config)# interface ethernet 0/1
• R2(config-if)# ipv6 rip CCNP_RIP enable
• R2(config-if)# interface loopback 0
• R2(config-if)# ipv6 rip CCNP_RIP enable
 Routing Information Protocol (RIPNG)
• Configuring RIPng
 Routing Information Protocol (RIPNG)
• Configuring RIPng
• Note :
• There is a significant difference in how RIPv2 and RIPng calculate
the number of hops for a remote network. In RIPng, the routers
adds one hop to the metric when it receives the RIPng update and
then includes that metric in its IPv6 routing table for that network.
• In RIPv1 and RIPv2, the router receives the RIP update, uses that
metric for its IPv4 routing table and then increments the metric by
one before sending the update to other routers. The effect of all of
this is that RIPng will show a metric, a hop count of one more
than RIPv1 or RIPv2.
• The concept of classful networks doesn’t exist in IPv6, so there isn’t
any automatic route summarization in RIPng
• To configure RIPng to advertise summarized IPv6 addresses on
an interface, manual summarization, use the ipv6 rip
summary-address command in interface configuration mod
 Routing Information Protocol (RIPNG)
• Configuring RIPng (SUMMARIZATION)

• In Example 1-10, the two loopback interfaces on R1 are

summarized out the Ethernet 0/3 interface for the RIPng process
CCNP_RIP
• The same process for summarizing IPv4 networks is used for
summarizing IPv6 prefixes. The 2001:DB8:A01:100::/64 and
2001:DB8:A01:A00::/64 prefixes have the first 52 bits in
common, represented as 2001:DB8:A01::/52
 Routing Information Protocol (RIPNG)
• Configuring RIPng (Propagating a Default Route)
• In Figure R1 has a configured static default route that that sends
all the unknown traffic toward the Internet
 Routing Information Protocol (RIPNG)
• Configuring RIPng (Propagating a Default Route)
• If you want R1 to share this default route with R2, use the following
command:
• R1(config-if)# ipv6 rip name default-information originate | only
• R1(config)# interface Ethernet 0/3
• R1(config-if)# ipv6 rip CCNP_RIP default-information originate
• On R2, verify that R1 has shared its default IPv6 route. Use the
show ipv6 route rip command
 Routing Information Protocol (RIPNG)
• Configuring RIPng (Propagating a Default Route)
• On R1’s Ethernet 0/3 interface, enter the ipv6 rip name default-
information only command, as shown. With this configuration, R1
shares only its defaultroute with R2 through the RIPng routing
process
• R1(config)# interface Ethernet 0/3
• R1(config-if)# ipv6 rip CCNP_RIP default-information only
 Routing Information Protocol (RIPNG)
• Veriying RIPnG (Investigating the RIPng Database)
• The show ipv6 rip command shows you information about all
RIPng routing processes on the router. In the bottom of the output,
interfaces that are enabled for RIPng are shown
 Routing Information Protocol (RIPNG)
• Veriying RIPnG (Investigating the RIPng Database)