DarkFiber

http://www.sadikhov.com/forum/ Page 1/5

RIPv2 Summary
The characteristics of RIPv2 follow :

Distance-vector protocol. Use UDP port 520. Makes Automatic summarization on network Class boundary. Classless protocol (supports VLSMs). Have the power to shut the Auto-summarization And make a configured manual Summarization. Supports VLSMs. Metric is router hop count. Maximum hop count is 15; infinite (unreachable) routes have a metric of 16. Periodic route updates sent every 30 seconds to multicast address 224.0.0.9. 25 routes per RIP message (24 if authentication is used). Invalid route marked after 180 sec. Flush timer is 280 sec. Hold-down timer 180 sec. Supports authentication. Implements split horizon with poison reverse. Implements triggered updates. Subnet mask included in route entry. Administrative distance for RIPv2 is 120. Used in small, flat networks or at the edge of larger networks.

DarkFiber

http://www.sadikhov.com/forum/ Page 2/5

RIP Request Message Types

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 route table. In the former case, the Request message will have a single route entry in which the address family identifier is set to zero, the address is all zeros (0.0.0.0), and the metric is 16. A device receiving such a request responds by unicasting its full route table to the requesting address, honoring such rules as split horizon and boundary summarization Some diagnostic processes might need to know information about a specific route or routes. In this case, a Request message might be sent with entries specifying the addresses in question. A device receiving this request will process the entries one by one, building a Response message from the Request message. If the device has an entry in its route table corresponding to an address in the request, it will enter the metric of its own route entry into the metric field. If not, the metric field will be set to 16. The response will tell exactly what the router "knows," with no consideration given to split horizon or boundary summarization.

RIPv2 Convergence
The steps for RIPv1 convergence are as follows: 1- When the local router sees a connected route disappear, it sends a Flash update and removes the route entry from its table. This is Called a triggered update with poison reverse. 2- The receiving routers send a Flash update and put the affected route in holddown. 3- The originating router queries (request message) its neighbor (DC) for alternative routes. If the neighbor has an alternative route, it is sent (respond); otherwise, the Poisoned route is sent. 4- The originating router installs the best alternative route that it hears because it has purged the original routes, and Send the new updates in its periodic routing update timer (30 sec). 5- Routers that are in holddown ignore only the alternative route, Unless its metric is much lower than the invalid route, it will accept it immediately and won't obey the holdown timer rule. 6- When the other routers emerge from holddown, they will accept the alternative route. 7- Convergence takes the time for detection, plus holddown, plus the number of routing updates (equal to the hop-count diameter of the network). This could take a long time.

DarkFiber

http://www.sadikhov.com/forum/ Page 3/5

RIP v2 Configuration config)# router rip conf-router)# version 2 (classfull) conf-router)# network < Net ID> conf-router)#passive-interface <interface> conf-router)#maximum paths <N> (Up to 6 Links for load sharing on a R.B basis,
Over equal metric paths default =is 4 paths)

conf-router)#traffic-share min (How to compute traffic share over alternate paths) conf-if)# no ip split-horizon (Disables it from a specific interface) conf-router)#distance <N> (Define an administrative distance, default =120) conf-router)# timers basic < update - invalid holdown flush sleep > conf-router)# neighbor < ip add>
(Because RIP is a broadcast protocol you may configure RIP to exchange routing information in a Point-Point non-broadcast network such as Frame Relay. In this type of network, RIP must be informed of neighbor RIP routers, Also When it is used in combination with the passiveinterface cmd, routing information can be Only exchanged between the router and this nei Ex. Unix server on a LAN )
(Adjust timers in sec , Sleeptime is a timer used to specify a period, in milliseconds, to delay a regular routing update after receiving a triggered update.)

conf-router)#validate-update-source
(This command is applicable only to RIP and IGRP. The software ensures that the source IP address of incoming routing updates is on the same IP network as one of the addresses defined for the receiving interface. Disabling split horizon on the incoming interface will also cause the system to perform this validation check. For unnumbered IP interfaces (interfaces configured as IP unnumbered), no checking is performed. )

conf-router)# no auto-summary conf-if )# ip summary-address rip < Net ID + mask> Show Commands # sh ip route # sh ip route rip # sh ip route < Net ID > # sh ip rip database # sh ip protocols #debug ip rip #debug ip rip events # no debug all

DarkFiber

http://www.sadikhov.com/forum/ Page 4/5

Sending & Receiving Routing Updates Options

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 cmd. The network administrator can configure the router to only receive and send Version 1 OR version 2 packets.

Here is the cmds : conf-router)# version <1 / 2> config-if)# ip rip send version 1 (Send only ver 1 updates) config-if)# ip rip send version 2 (Send only ver 2 updates) config-if)# ip rip send version 1 2 (Send Both ver 1 and 2 updates) config-if)# ip rip receive version 1 ( Accept only ver 1 updates) config-if)# ip rip receive version 2 ( Accept only ver 2 updates) config-if)# ip rip receive version 1 2 ( Accept both ver 1 and 2 updates) Note : Use this command to override the default behavior of RIP as specified by the version command.

DarkFiber

http://www.sadikhov.com/forum/ Page 5/5

RIP Authentication
The Cisco implementation of RIPv2 message authentication includes the choice of simple password or MD5 authentication, and the option of defining multiple keys with there associated passwords, on the same "key chain." The router may be configured to use more than one "key chain." & also different keys at different times (key management). Auth must be done in a fixed order rather than this you may have problems, The steps for setting up RIPv2 authentication follow: 1-Define a key chain with a name. 2- Define the authentication key or keys on the key chain 3- Define the password of the key or keys. 4- Specify whether the interface will use clear text or MD5 authentication. 5- Apply authentication on an interface and specify the key chain to be used. 6- Optionally configure key management.

Here is the cmds : config)# key chain <name> config-keychain)# key <#> config-keychain-key)# key-string < password>
(start time) (End time)

config-keychain-key)#accept-lifetime<h:m:s mm dd yy>duration< mm- infinite > config-keychain-key)#send-lifetime <h:m:s mm dd yy> duration < mm- infinite > config)# interface <int> config-if)# ip rip authentication mode < text - md5 > config-if)# ip rip authentication key-chain <name>

( default is clear txt)