Tuesday, 12 January 2016

RIPng


RIPng  https://tools.ietf.org/html/rfc2080
Routing information protocol (RIP) began life as one of the earliest efforts in the field of dynamic routing protocols back in the 1970. Later in the 1990 the RIP version 2 enhance RIP. with the original version becoming known as RIP version 1.
Also in the mid-1990, the process of defining IPv6 was drawing toward completion at least for the original IPv6 standards the RIPv3 or RIPng.





Feature  RIPv 2 RIPng
advertise routes for  IPv4 IPV6
Rip messages use these layer 3/4 protocol IPv4/UDP IPV6/UDP
UDP port  520 521
Distance vector  yes  yes 
default Administrative distance  120 120
Support VLSM  yes  yes 
can perform automatic summarization yes  no 
use split horizon  yes  yes 
use poison reverse yes  yes 
30 second periodic update yes  yes 
use trigger updates  yes  yes 
use hop count metric yes  yes 
metric  meaning infinity 16 16
support routes tags yes  yes 
multicast destination 224.0.0.9 FF02::9
authentication  RIP specific  IPV6 AH/ESP











































The overall operation of Ripng closely matches RIP-2. In both, routers send periodic full updates with all route, except for routes omitted due to split horizon rules.

Note: IPV6 support authentication using the IPsec Authentication header (AH), RIPng does not natively support authentication, instead relying on IPSEC. 


configuration of RIPng 

step 1 Enable Ipv6 with glabal command
ipv6 unicast-routing

step  2 enable ripng using global command
ipv6 router rip \name/ 

step 3 enable ipv6 on the interface, typically with oe of these two methods 
configure an ipv6 unicast address on each interface uing the ipv6 address adress/prefux-lenght  [eui-64]

configure the ipv6 enable command , which enable ipv6 and causes the router to derive is link local address

step 4 ipv6 rip name enable // in the subinterface , the name must match the previous one defined//

Example 
Requirements
  • Understanding of IPv6 Addressing Scheme
  • RIPv4 basics
Background
In this configuration example, routers R1 and R2 are connected via fast Ethernet interface.Loopback addresses are configured to generate networks. All the interface are configured with the IPv6 addresses.
Note: All configurations are tested in a lab environment on Cisco 3745 Router operating on Cisco IOS 12.4 version.
Topology Diagram

R1-serial2/0 -=========serial2/0 R2


Summary Steps
In Global Configuration Mode
  1. enable
  2. configure terminal
  3. ipv6 router rip word
  4. exit
In Interface Configuration Mode
  1. ipv6 rip word enable
  2. exit
Configuration
Router R1
Router R2
hostname R1
!
ip cef
!
ipv6 unicast-routing
-- enables forwarding of IPv6 packets
!


interface Loopback1
 no ip address
 ipv6 address 1111:1:1:1::1/128
 ipv6 rip RIPng enable
-- enables IPv6 RIP routing process (in our case RIPng1)

!
interface Loopback2

 no ip address
 ipv6 address 2222:2:2:2::1/128
 ipv6 rip RIPng enable

!
interface Serial2/0
 no ip address
 ipv6 address 1011:11:11:11::1/64
 ipv6 rip RIPng enable
 serial restart-delay 0

!
ipv6 router rip RIPng
-- Configures the IPv6 RIP routing process on the router
end
hostname R2
!
ip cef
!
ipv6 unicast-routing
!
interface Loopback0
interface Loopback0
 ip address 150.1.2.2 255.255.255.255
 ipv6 address 2001:150:2:2::2/128
 ipv6 address 2011::1/128
 ipv6 rip RIPng enable
!
interface Loopback1
no ip address
ipv6 address 2020::1/128
ipv6 rip RIPng enable
!
interface Serial2/0
 no ip address
 ipv6 address 1011:11:11:11::2/64
 ipv6 rip RIPng enable
 serial restart-delay 0
!
ipv6 router rip RIPng
!
end
Verify Commands
show ipv6 route rip
This command displays the contents of IPv6 routing table with all the IPv6 RIP routes.


R2#show ipv6 route rip
IPv6 Routing Table - default - 10 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
       B - BGP, HA - Home Agent, MR - Mobile Router, R - RIP
       H - NHRP, I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea
       IS - ISIS summary, D - EIGRP, EX - EIGRP external, NM - NEMO
       ND - ND Default, NDp - ND Prefix, DCE - Destination, NDr - Redirect
       O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
       ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2, ls - LISP site
       ld - LISP dyn-EID, a - Application
R   1111:1:1:1::1/128 [120/2]
     via FE80::A8BB:CCFF:FE00:100, Serial2/0
R   2222:2:2:2::1/128 [120/2]
     via FE80::A8BB:CCFF:FE00:100, Serial2/0
R2#

R1#show ipv6 rip
RIP process "RIPng", port 521, multicast-group FF02::9, pid 218
     Administrative distance is 120. Maximum paths is 16
     Updates every 30 seconds, expire after 180
     Holddown lasts 0 seconds, garbage collect after 120
     Split horizon is on; poison reverse is off
     Default routes are not generated
     Periodic updates 87, trigger updates 4
     Full Advertisement 1, Delayed Events 0
  Interfaces:
    Loopback2
    Loopback1
    Serial2/0
  Redistribution:
    None
R1#
show ipv6 rip [name][database]
This command displays the details of the entries in the specified RIP IPv6 routing table.

R1#show ipv6 rip RIPng database
RIP process "RIPng", local RIB
 1011:11:11:11::/64, metric 2
     Serial2/0/FE80::A8BB:CCFF:FE00:200, expires in 176 secs
 2001:150:2:2::2/128, metric 2, installed
     Serial2/0/FE80::A8BB:CCFF:FE00:200, expires in 176 secs
 2011::1/128, metric 2, installed
     Serial2/0/FE80::A8BB:CCFF:FE00:200, expires in 176 secs
 2020::1/128, metric 2, installed
     Serial2/0/FE80::A8BB:CCFF:FE00:200, expires in 176 secs
R1#
Note: To check RIPng timer related information and to check whether any route has route tag set, you can use this command.
show ipv6 rip [name][next-hops]
Using this command, you can check the details of the specified RIP IPv6 processes next hop addresses. If no RIP process name is specified, the next hop addresses for all RIP IPv6 processes will be displayed.

R1#show ipv6 rip RIPng next-hops
 RIP process "RIPng", Next Hops
  FE80::A8BB:CCFF:FE00:200/Serial2/0 [4 paths]
R1#
To display the debugging messages for IPv6 RIP routing transactions use this command debug ipv6 rip
R1#debug ipv6 rip
  RIP Routing Protocol debugging is on
R1#
R1#no debug ipv6 rip
RIPng: Packet waiting
RIPng: response received from FE80::A8BB:CCFF:FE00:200 on Serial2/0 for RIPng
       src=FE80::A8BB:CCFF:FE00:200 (Serial2/0)
       dst=FF02::9
       sport=521, dport=521, length=92
       command=2, version=1, mbz=0, #rte=4
       tag=0, metric=1, prefix=2001:150:2:2::2/128
       tag=0, metric=1, prefix=2011::1/128
       tag=0, metric=1, prefix=2020::1/128
       tag=0, metric=1, prefix=1011:11:11:11::/64
R1#no debug ipv6 rip
RIPng: Sending multicast update on Loopback2 for RIPng
       src=FE80::A8BB:CCFF:FE00:100
       dst=FF02::9 (Loopback2)
       sport=521, dport=521, length=132
       command=2, version=1, mbz=0, #rte=6
       tag=0, metric=1, prefix=2222:2:2:2::1/128
       tag=0, metric=1, prefix=1111:1:1:1::1/128
       tag=0, metric=1, prefix=1011:11:11:11::/64
       tag=0, metric=2, prefix=2001:150:2:2::2/128
       tag=0, metric=2, prefix=2011::1/128
       tag=0, metric=2, prefix=2020::1/128
RIPng: Sending multicast update on Loopback1 for RIPng
       src=FE80::A8BB:CCFF:FE00:100
       dst=FF02::9 (Loopback1)
       sport=521, dport=521, length=132
       command=2, version=1, mbz=0, #rte=6
       tag=0, metric=1, prefix=2222:2:2:2::1/128
       tag=0, metric=1, prefix=1111:1:1:1::1/128
       tag=0, metric=1, prefix=1011:11:11:11::/64
       tag=0, metric=2, prefix=2001:150:2:2::2/128
       tag=0, metric=2, prefix=2011::1/128
       tag=0, metric=2, prefix=2020::1/128
RIPng: Sending multicast update on Serial2/0 for RIPng
       src=FE80::A8BB:CCFF:FE00:100
       dst=FF02::9 (Serial2/0)
       sport=521, dport=521, length=72
       command=2, version=1, mbz=0, #rte=3
       tag=0, metric=1, prefix=2222:2:2:2::1/128
       tag=0, metric=1, prefix=1111:1:1:1::1/128
       tag=0, metric=1, prefix=1011:11:11:11::/64
R1#no debug ipv6 rip
RIPng: Packet waiting
RIPng: Process RIPng received own response on Loopback2
RIPng: Process RIPng received own response on Loopback1
R1#no debug ipv6 rip
  RIP Routing Protocol debugging is off
R1#
Ping
To verify the reachability between the routers R1 and R2, use the ping command and ping the loopback addresses of the router R1 from R2 and vice versa.

R1#ping 2011::1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2011::1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 7/10/12 ms
R1#
R2# ping 2222:2:2:2::1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2222:2:2:2::1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 10/12/22 ms
R2#



Posted by at
Subscribe to: Posts (Atom)