La configuration RIP de base à été en suite ajouté :

conf t
  router rip 
     no auto-summary 
     version 2 
     network 10.0.0.0
end

Vérifications:

R6#show ip route rip
     10.0.0.0/24 is subnetted, 11 subnets
R       10.1.14.0 [120/1] via 10.1.46.4, 00:00:00, Serial0/0.64
R       10.1.13.0 [120/2] via 10.1.46.4, 00:00:00, Serial0/0.64
R       10.1.12.0 [120/2] via 10.1.46.4, 00:00:00, Serial0/0.64
R       10.1.24.0 [120/1] via 10.1.46.4, 00:00:00, Serial0/0.64
R       10.1.45.0 [120/1] via 10.1.56.5, 00:00:03, FastEthernet0/0
                  [120/1] via 10.1.46.4, 00:00:00, Serial0/0.64
R       10.1.111.0 [120/2] via 10.1.46.4, 00:00:00, Serial0/0.64
R       10.1.100.0 [120/2] via 10.1.46.4, 00:00:00, Serial0/0.64
R       10.1.113.0 [120/3] via 10.1.46.4, 00:00:00, Serial0/0.64
R       10.1.112.0 [120/2] via 10.1.46.4, 00:00:00, Serial0/0.64

Timers

La commande « show ip protocols » permet afficher la valeur des timers RIP

R1#show ip protocols
Routing Protocol is "rip"
Sending updates every 30 seconds, next due in 20 seconds 
Invalid after 180 seconds, hold down 180, flushed after 240 
 Outgoing update filter list for all interfaces is not set
  Incoming update filter list for all interfaces is not set
  Redistributing: rip
  Default version control: send version 2, receive version 2
    Interface             Send  Recv  Triggered RIP  Key-chain
    FastEthernet0/0       2     2
    Serial0/0.12          2     2
    Serial0/0.13          2     2
    Serial0/0.14          2     2
    Serial0/1             2     2
  Automatic network summarization is not in effect
  Maximum path: 4
  Routing for Networks:
    10.0.0.0
  Routing Information Sources:
    Gateway         Distance      Last Update
    10.1.14.4            120      00:00:06
    10.1.12.2            120      00:00:05
    10.1.13.3            120      00:00:27
    10.1.100.3           120      00:00:13
  Distance: (default is 120)

Ces valeurs peuvent être ajustés avec la commandes « timers » :

R1#conf t
R1(config)#router rip
R1(config-router)#timers ?
  basic  Basic routing protocol update timers

R1(config-router)#timers basic ?
    <0-4294967295>  Interval between updates

R1(config-router)#timers basic 1 ?
    <1-4294967295>  Invalid

R1(config-router)#timers basic 1 5 ?
    <0-4294967295>  Holddown

R1(config-router)#timers basic 1 5 5 ?
    <1-4294967295>  Flush

R1(config-router)#timers basic 1 5 5 5 ?
    <1-4294967295>  Sleep time, in milliseconds

R1(config-router)#timers basic 1 5 5 5 100 ?

flash-update-threshold

Supprime les mises à jour de la flash si les mise à jour arrivent à périodes régulières

R1(config)#router rip
R1(config-router)#flash-update-threshold ?
    <0-30>   threshold in seconds

R1(config-router)#flash-update-threshold 10

R1#show ip protocols
Routing Protocol is "rip"
  Sending updates every 60 seconds, next due in 42 seconds
  Flash update is suppressed when next update due within 10 seconds
  Invalid after 360 seconds, hold down 360, flushed after 500

Authentification

Rip authentification « clear test » ou « md5 »

no validate-update-source

Contrairement à d’autres protocoles de routage, RIP (et IGRP) n’accepte que des routes de ces voisins comportant un next-hop valide en vérifiant que l’IP utilisée lors de l’update est bien directement connectée
Ce comportement par défaut peut-être modifié :

R1(config)#router rip
R1(config-router)#no validate-update-source 

distribute-list

Il possible de filtrer les réseaux appris (in) ou diffusés (ou) selon la longueur du préfixe

R1#show ip route rip | inc 10.1.111.111
R       101.0.0.0/8 [120/1] via 10.1.111.111, 00:00:08, FastEthernet0/0
R       102.0.0.0/9 [120/1] via 10.1.111.111, 00:00:08, FastEthernet0/0
R       103.0.0.0/10 [120/1] via 10.1.111.111, 00:00:08, FastEthernet0/0
R       104.0.0.0/11 [120/1] via 10.1.111.111, 00:00:08, FastEthernet0/0
R       105.0.0.0/14 [120/1] via 10.1.111.111, 00:00:08, FastEthernet0/0
R       106.1.1.32/27 [120/1] via 10.1.111.111, 00:00:08, FastEthernet0/0
R       107.1.1.0/25 [120/1] via 10.1.111.111, 00:00:08, FastEthernet0/0
R       108.1.1.64/26 [120/1] via 10.1.111.111, 00:00:08, FastEthernet0/0
R       109.1.4.0/22 [120/1] via 10.1.111.111, 00:00:08, FastEthernet0/0
R       110.1.1.16/28 [120/1] via 10.1.111.111, 00:00:08, FastEthernet0/0

R1#conf t
R1(config)#ip prefix-list NET-OK seq 10 permit 0.0.0.0/0 ge 10 le 26
R1(config)#ip prefix-list BB1 seq 10 permit 10.1.111.111/32
R1(config)#
R1(config)#router rip
R1(config-router)#distribute-list prefix NET-OK gateway BB1 in fa0/0 

R1#show ip route rip | inc 10.1.111.111
R       103.0.0.0 [120/1] via 10.1.111.111, 00:00:32, FastEthernet0/0
R       104.0.0.0 [120/1] via 10.1.111.111, 00:00:32, FastEthernet0/0
R       105.0.0.0 [120/1] via 10.1.111.111, 00:00:32, FastEthernet0/0
R       107.1.1.0 [120/1] via 10.1.111.111, 00:00:32, FastEthernet0/0
R       108.1.1.64 [120/1] via 10.1.111.111, 00:00:32, FastEthernet0/0
R       109.1.4.0 [120/1] via 10.1.111.111, 00:00:32, FastEthernet0/0

offset-list

« offset-list » permet de modifier le metric des routes annoncées ou reçues, et ainsi d’influencer le routage.
l’interface (in ou out) peut être spécifiée?

Par exemple,
R1 annonce le réseau 101.0.0.0/8 à R2 en incrémentant le metric de 9
R1 annonce le réseau 101.0.0.0/8 à R4 en incrémentant le metric de 10

R1#conf t
R1(config)#access-list 1 permit 101.0.0.0 0.255.255.255
R1(config)#access-list 1 permit 102.0.0.0 0.127.255.255

R1(config)#router rip
R1(config-router)#offset-list 1 out 9 serial 0/0.12
R1(config-router)#offset-list 1 out 10 serial 0/0.14

Vérifications:

R2#show ip route 101.0.0.0
Routing entry for 101.0.0.0/8
  Known via "rip", distance 120, metric 11
  Redistributing via rip
  Last update from 10.1.12.1 on Serial0/0.21, 00:00:14 ago
  Routing Descriptor Blocks:
  * 10.1.12.1, from 10.1.12.1, 00:00:14 ago, via Serial0/0.21
      Route metric is 11, traffic share count is 1

Puisque R2 ré-annonce le réseau 101.0.0.0/8 à R4 en incrémentant de façon naturel le metric de 1,
R4 obtient 2 routes possibles à metric égale pour atteindre 101.0.00

R4#show ip route 101.0.0.0
Routing entry for 101.0.0.0/8
  Known via "rip", distance 120, metric 12
  Redistributing via rip
  Last update from 10.1.14.1 on Serial0/0.41, 00:00:18 ago
  Routing Descriptor Blocks:
  * 10.1.24.2, from 10.1.24.2, 00:00:24 ago, via FastEthernet0/0
      Route metric is 12, traffic share count is 1
    10.1.14.1, from 10.1.14.1, 00:00:18 ago, via Serial0/0.41
      Route metric is 12, traffic share count is 1

ip rip triggered

« ip rip triggered » permet de réduire le trafic RIP sur les liens WAN point à point ou multipoint , seul les changements de topologie seront transmis.

R1#conf t
R1(config-subif)#int s0/0.14
R1(config-subif)#ip rip triggered

passive-interface

R2#conf t
R2(config)#router rip
R2(config-router)#default passive-interface default

R2#conf t
R2(config)#router rip
R2(config-router)#passive-interface fa0/0.24

neighbor

« neighbor » permet de configurer une relation de voisinage RIP exclusivement en Unicast

R2#conf t
R2(config)#router rip
R2(config-router)#passive-interface fa0/0.24
R2(config-router)#neighbor 10.1.24.4

R4#conf t
R4(config)#router rip
R4(config-router)#passive-interface fa0/0
R4(config-router)#neighbor 10.1.24.2

ip rip v2-broadcast

R6#conf t
R6(config)#int fa0/0
R6(config-if)#ip rip v2-broadcast

Vérifications

R6#debug ip rip
RIP protocol debugging is on

R6#
*Mar  4 18:54:50.819: RIP: sending v2 update to 255.255.255.255 via FastEthernet0/0 (10.1.56.5)

ip summary-address rip

Vérifications avant modification :

BB3#show ip route 112.0.0.0
R       112.2.2.0 [120/5] via 10.1.113.3, 00:00:13, Ethernet0
R       112.1.1.0 [120/5] via 10.1.113.3, 00:00:13, Ethernet0

Le router BB2 annonce un /8 au lieu de ces 2 /24

BB2#conf t
BB2(config)#int e0
BB2(config-if)#ip summary-address rip 112.1.0.0 255.0.0.0

Vérifications :

BB3#show ip route 112.0.0.0
Routing entry for 112.0.0.0/8, 1 known subnets
  Redistributing via rip

R       112.0.0.0 [120/4] via 10.1.113.3, 00:00:02, Ethernet0

output-delay & input-queue

« output-delay » permet d’introduire un délai entre chaque paquet RIP, afin d’éviter d’engorger le routeur voisin

R1(config)#router rip
R1(config-router)#output-delay ?
    <8-50>  Delay in milliseconds

« input-queue » permet d’introduire un délai entre chaque paquet RIP à la réception :

R1(config)#router rip
R1(config-router)#input-queue ?
    <0-1024>  queue depth

Les 9 routeurs sont mis à contribution :

hostname BB1
!
!
interface Loopback1
 ip address 101.0.0.111 255.0.0.0
!
interface Loopback2
 ip address 102.0.0.111 255.128.0.0
!
interface Loopback3
 ip address 103.0.0.111 255.192.0.0
!
interface Loopback4
 ip address 104.0.0.111 255.224.0.0
!
interface Loopback5
 ip address 105.0.0.111 255.252.0.0
!
interface Loopback6
 ip address 106.1.1.33 255.255.255.224
!
interface Loopback7
 ip address 107.1.1.111 255.255.255.128
!
interface Loopback8
 ip address 108.1.1.65 255.255.255.192
!
interface Loopback9
 ip address 109.1.4.111 255.255.252.0
!
interface Loopback10
 ip address 110.1.1.17 255.255.255.240
!
interface Ethernet0
 ip address 10.1.111.111 255.255.255.0
!
interface Serial0
 no ip address
 shutdown
 no fair-queue
!
interface Serial1
 no ip address
 shutdown
!

hostname BB2
!
!
interface Loopback0
 ip address 112.1.1.1 255.255.255.0
!
interface Loopback1
 ip address 112.2.2.2 255.255.255.0
!
interface Ethernet0
 ip address 10.1.112.112 255.255.255.0
!
interface Serial0
 no ip address
 shutdown
!
interface Serial1
 no ip address
 shutdown
!

 
hostname BB3
!
!
interface Ethernet0
 ip address 10.1.113.1 255.255.255.0
!
interface Serial0
 no ip address
 shutdown
!
interface Serial1
 no ip address
 shutdown
!

hostname R1
!
!
interface FastEthernet0/0
 ip address 10.1.111.1 255.255.255.0
 duplex auto
 speed auto
!
interface Serial0/0
 no ip address
 encapsulation frame-relay
!
interface Serial0/0.12 point-to-point
 ip address 10.1.12.1 255.255.255.0
 frame-relay interface-dlci 102
!
interface Serial0/0.13 point-to-point
 ip address 10.1.14.1 255.255.255.0
 frame-relay interface-dlci 104
!
interface Serial0/0.14 point-to-point
 ip address 10.1.13.1 255.255.255.0
 frame-relay interface-dlci 103
!
interface Serial0/1
 ip address 10.1.100.1 255.255.255.0
!

hostname R2
!
!
interface FastEthernet0/0
 no ip address
 duplex auto
 speed auto
!
interface FastEthernet0/0.24
 encapsulation dot1Q 24
 ip address 10.1.24.2 255.255.255.0
 no snmp trap link-status
!
interface FastEthernet0/0.112
 encapsulation dot1Q 112
 ip address 10.1.112.2 255.255.255.0
 no snmp trap link-status
!
interface Serial0/0
 no ip address
 encapsulation frame-relay
!
interface Serial0/0.21 point-to-point
 ip address 10.1.12.2 255.255.255.0
 frame-relay interface-dlci 201
!
interface Serial0/1
 no ip address
 shutdown
!

hostname R3
!
!
interface FastEthernet0/0
 ip address 10.1.113.3 255.255.255.0
 duplex auto
 speed auto
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial1/0
 no ip address
 encapsulation frame-relay
!
interface Serial1/0.31 point-to-point
 ip address 10.1.13.3 255.255.255.0
 frame-relay interface-dlci 301
!
interface Serial1/1
 no ip address
 shutdown
!
interface Serial1/2
 ip address 10.1.100.3 255.255.255.0
 clock rate 64000
!
interface Serial1/3
 no ip address
 shutdown
!

hostname R4
!
interface FastEthernet0/0
 ip address 10.1.24.4 255.255.255.0
 duplex auto
 speed auto
!
interface Serial0/0
 no ip address
 encapsulation frame-relay
!
interface Serial0/0.41 point-to-point
 ip address 10.1.14.4 255.255.255.0
 frame-relay interface-dlci 401
!
interface Serial0/0.45 point-to-point
 ip address 10.1.45.4 255.255.255.0
 frame-relay interface-dlci 405
!
interface Serial0/0.46 point-to-point
 ip address 10.1.46.4 255.255.255.0
 frame-relay interface-dlci 406
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/1
 no ip address
 encapsulation frame-relay
 shutdown
!

hostname R5
!
!
interface FastEthernet0/0
 ip address 10.1.56.5 255.255.255.0
 duplex auto
 speed auto
!
interface Serial0/0
 no ip address
 encapsulation frame-relay
 no fair-queue
!
interface Serial0/0.54 point-to-point
 ip address 10.1.45.5 255.255.255.0
 frame-relay interface-dlci 504
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/1
 no ip address
 shutdown
!

hostname R6
!
!
interface FastEthernet0/0
 ip address 10.1.56.6 255.255.255.0
 duplex auto
 speed auto
!
interface Serial0/0
 no ip address
 encapsulation frame-relay
 no fair-queue
!
interface Serial0/0.64 point-to-point
 ip address 10.1.46.6 255.255.255.0
 frame-relay interface-dlci 604
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!

R1#conf t
R1(config)#router rip
R1(config-router)#version 2
R1(config-router)#no auto-summary
R1(config-router)#network 10.0.0.0
R1(config-router)#network 1.0.0.0

 R2#conf t
R2(config)#router rip
R2(config-router)#version 2
R2(config-router)#no auto-summary
R2(config-router)#network 10.0.0.0
R2(config-router)#network 2.0.0.0

 R3#conf t
R3(config)#router rip
R3(config-router)#version 2
R3(config-router)#no auto-summary
R3(config-router)#network 10.0.0.0
R3(config-router)#network 3.0.0.0

vérifications:

 R1#show ip route rip
R    2.0.0.0/8 [120/2] via 10.1.1.3, 00:00:13, FastEthernet0/0
R    3.0.0.0/8 [120/1] via 10.1.1.3, 00:00:16, FastEthernet0/0
     10.0.0.0/24 is subnetted, 2 subnets
R       10.2.2.0 [120/1] via 10.1.1.3, 00:00:16, FastEthernet0/0

 R2#show ip route rip
R    1.0.0.0/8 [120/2] via 10.2.2.3, 00:00:11, FastEthernet0/0
R    3.0.0.0/8 [120/1] via 10.2.2.3, 00:00:11, FastEthernet0/0
     10.0.0.0/24 is subnetted, 2 subnets
R       10.1.1.0 [120/1] via 10.2.2.3, 00:00:11, FastEthernet0/0

 R3#show ip route rip
R    1.0.0.0/8 [120/1] via 10.1.1.1, 00:00:27, FastEthernet0/0
R    2.0.0.0/8 [120/1] via 10.2.2.2, 00:00:09, FastEthernet0/1

Configuration de l’authentification RIPv2 « clear text » entre R1 et R3

 R1#conf t
R1(config)#key chain TEST12345
R1(config-keychain)#key 1
R1(config-keychain-key)#key-string CISCO12345

R1(config)#interface fa0/0
R1(config-if)#ip rip authentication key-chain TEST12345

 R3#conf t
R3(config)#key chain TEST12345
R3(config-keychain)#key 1
R3(config-keychain-key)#key-string CISCO12345

R3(config)#int fa0/0
R3(config-if)#ip rip authentication key-chain TEST12345

Configuration de l’authentification RIPv2 « MD5 » entre R3 et R2

 R3#conf t
R3(config)#key chain TEST123
R3(config-keychain)#key 1
R3(config-keychain-key)#key-string cisco123

R3(config)#interface fa0/1
R3(config-if)#ip rip authentication key-chain TEST123
R3(config-if)#ip rip authentication mode md5

 R2#conf t
R2(config)#key chain TEST123
R2(config-keychain)#key 1
R2(config-keychain-key)#key-string cisco123

R2(config)#int fa0/0
R2(config-if)#ip rip authentication key-chain TEST123
R2(config-if)#ip rip authentication mode md5

Vérifications :

  
R2#debug ip rip
RIP protocol debugging is on

*Mar 11 03:50:30.331: RIP: received packet with MD5 authentication
*Mar 11 03:50:30.331: RIP: received v2 update from 10.2.2.3 on FastEthernet0/0
*Mar 11 03:50:30.331:      1.0.0.0/8 via 0.0.0.0 in 2 hops
*Mar 11 03:50:30.335:      3.0.0.0/8 via 0.0.0.0 in 1 hops
*Mar 11 03:50:30.335:      10.1.1.0/24 via 0.0.0.0 in 1 hops

  
R2#show ip route rip
R    1.0.0.0/8 [120/2] via 10.2.2.3, 00:00:25, FastEthernet0/0
R    3.0.0.0/8 [120/1] via 10.2.2.3, 00:00:25, FastEthernet0/0
     10.0.0.0/24 is subnetted, 2 subnets
R       10.1.1.0 [120/1] via 10.2.2.3, 00:00:25, FastEthernet0/0

Dans cette exemple une liaison de type point à point FrameRelay est configuré entre R2<->R1, et R3<->R1 , de la façon suivante

R1
interface Serial0/0.100 multipoint
 ip address 10.1.1.1 255.255.255.0
 frame-relay map ip 10.1.1.2 102 broadcast
 frame-relay map ip 10.1.1.3 103 broadcas

R2
interface Serial0/0
 ip address 10.1.1.2 255.255.255.0
 encapsulation frame-relay
 frame-relay map ip 10.1.1.1 201
 frame-relay map ip 10.1.1.3 201
 no frame-relay inverse-arp

R3
interface Serial1/0
 ip address 10.1.1.3 255.255.255.0
 encapsulation frame-relay
 frame-relay map ip 10.1.1.1 301
 frame-relay map ip 10.1.1.2 301
 no frame-relay inverse-arp

Une interface loopback est configurée sur chaque routeur

Configuration de RIP v2

Configuration classique, et très simple, sur chaque routeur

R1#conf t
R1(config)#router rip
R1(config-router)#version 2
R1(config-router)#no auto-summary
R1(config-router)#network 10.0.0.0
R1(config-router)#network 1.0.0.0

R2#conf t
R2(config)#router rip
R2(config-router)#version 2
R2(config-router)#no auto-summary
R2(config-router)#network 10.0.0.0
R2(config-router)#network 2.0.0.0

R3#conf t
R3(config)#router rip
R3(config-router)#version 2
R3(config-router)#no auto-summary
R3(config-router)#network 10.0.0.0
R3(config-router)#network 3.0.0.0

Vérifications :

R1#sho ip route rip
R    2.0.0.0/8 [120/1] via 10.1.1.2, 00:00:21, Serial0/0.100
R    3.0.0.0/8 [120/1] via 10.1.1.3, 00:00:09, Serial0/0.100

R2#show ip route rip
R    1.0.0.0/8 [120/1] via 10.1.1.1, 00:00:19, Serial0/0

R3#show ip route rip
R    1.0.0.0/8 [120/1] via 10.1.1.1, 00:00:08, Serial1/0

De part la nature de cette topologie « point à point », les routeurs R2 et R2 ne reçoivent pas correctement les informations de routage propagés par RIP

Raison du dysfonctionnement : SPLIT HORIZON est activé sur le routeur R1

R1#show ip interface s0/0.100
Serial0/0.100 is up, line protocol is up
  Internet address is 10.1.1.1/24
  Broadcast address is 255.255.255.255
  Address determined by non-volatile memory
  MTU is 1500 bytes
  Helper address is not set
  Directed broadcast forwarding is disabled
  Multicast reserved groups joined: 224.0.0.9
  Outgoing access list is not set
  Inbound  access list is not set
  Proxy ARP is enabled
  Local Proxy ARP is disabled
  Security level is default
  Split horizon is enabled
  ICMP redirects are always sent
  ICMP unreachables are always sent
  ICMP mask replies are never sent
  IP fast switching is enabled
  IP fast switching on the same interface is enabled
  IP Flow switching is disabled
  IP CEF switching is enabled
  IP CEF Fast switching turbo vector
  IP multicast fast switching is enabled
  IP multicast distributed fast switching is disabled
  IP route-cache flags are Fast, CEF
  Router Discovery is disabled
  IP output packet accounting is disabled
  IP access violation accounting is disabled
  TCP/IP header compression is disabled
  RTP/IP header compression is disabled
  Policy routing is disabled
  Network address translation is disabled
  BGP Policy Mapping is disabled

Correction : désactivation de « split horizon » sur R1

R1(config)#int s0/0.100
R1(config-subif)#no ip split-horizon 

Vérifications :

R1#show ip interface s0/0.100 | inc Spli
  Split horizon is disabled

R2#show ip route rip
R    1.0.0.0/8 [120/1] via 10.1.1.1, 00:00:09, Serial0/0
R    3.0.0.0/8 [120/2] via 10.1.1.3, 00:00:09, Serial0/0

Attention : R1 et R2 doivent pouvoir s’atteindre mutuellement (via R1) ,
il est donc nécessaire de faire évoluer la configuration :

R2#conf t
R2(config)#int s0/0
R2(config-if)#frame-relay map ip 10.1.1.3 201 

R3#conf t
R3(config)#int s1/0
R3(config-if)#frame-relay map ip 10.1.1.2 301