Configuring RIP for IPv6 – RIPng

Just like RIP for IPv4 there is also RIP Next Generation which is used to build dynamic routed IPv6 networks. This lab will discuss and demonstrate the configuration and verification of RIP Next Generation

Real World Application & Core Knowledge

Now that you have a foundational understanding of IPv6 its time to move into the first of the three dynamic routing protocols discussed in the Free CCNA Workbook for IPv6. RIP Next Generation was created specifically for IPv6.

RIPng operates much like RIPv2, updates are sent every 30 seconds and the route expiration timer is 180 seconds. The default garbage collection interval is 120 seconds. RIP sends updates to the IPv6 multicast group FF02::9 using port 521 by default.

Configuring RIPng however is a tad bit easier then RIPv2. When configuring RIPng you do not use the network x.x.x.x command in router configuration mode to specific which interfaces participate in the RIP process anymore. As of RIPng you now configure RIP interface participation on a Per interface basis.

To configure an interface to participate in RIPng you use the ipv6 rip NAME enable command on a per interface basis. The name specified in the syntax is a locally significant name used to identify the RIPng process on that router as you can have multiple RIPng processes on a single router whereas RIP for IPv4 you can only have a single process.

To view the RIPng protocol timers and other related information you use the command show ipv6 rip NAME. To view the RIPng database you’ll use the show ipv6 rip NAME database command in user or privileged mode.

There is one new command for IPv6 that is not in RIP for IPv4 which is the show ipv6 rip NAME next-hops command. This command will display how many routes are are pointing towards each next-hop (neighboring router).

In this lab you will configure RIPng on the frame relay sub-interfaces between R1 & R2 and R2 to R3 to route IPv6 traffic between the simulated IPv6 networks located on the loopback0 interface of each router.

Familiarize yourself with the following new command(s);

Command	Description
show ipv6 rip NAME	This command when executed in interface configuration mode will configure that paticular interface to participate in the specified RIPng process name.
show ipv6 rip NAME	This command when executed in user or privileged mode will display current RIPng timers and statistics of the specified RIPng process name.
show ipv6 rip NAME database	This command when executed in user or privileged mode will display the RIPng data base of the specified RIPng process name.
show ipv6 rip NAME next-hops	This command when executed in user or privileged mode will display a summary of RIPng routes per RIPng process name based on their next-hop.
show ipv6 route	This command when executed in user or privileged mode will display the routing table on that particular device.

The following logical topology shown below is used in this lab;

Lab Prerequisites

If you are using GNS3 than load the Free CCNA Workbook GNS3 topology than start device(s); R1, R2 and R3
Establish a console session with device(s) R1, R2 and R3 than load the initial configurations provided below by copying the config from the textbox and pasting it into the respected routers console.

!################################################## !# Free CCNA Workbook Lab 12-4 R1 Initial Config # !################################################## ! enable configure terminal ! hostname R1 no ip domain-lookup ipv6 unicast-routing ! interface Loopback0 description ### IPv6 SIMULATED NETWORK ### ipv6 address 2001:ABAD:BEEF:1001::1/64 ! interface Serial0/0 description ### LINK TO FRAME RELAY SWITCH ### encapsulation frame-relay no frame-relay inverse-arp exit ! interface Serial0/0.122 point-to-point description ### LINK TO R2 ### ipv6 address 2001:ABAD:BEEF:1221::1/64 frame-relay interface-dlci 122 exit ! interface Serial0/0 no shutdown exit ! line con 0 logging sync no exec-timeout ! end !################################################## !# Free CCNA Workbook Lab 12-4 R2 Initial Config # !################################################## ! enable configure terminal ! hostname R2 no ip domain-lookup ipv6 unicast-routing ! interface Loopback0 description ### IPv6 SIMULATED NETWORK ### ipv6 address 2001:ABAD:BEEF:2002::1/64 ! interface Serial0/0 description ### LINK TO FRAME RELAY SWITCH ### no ip address encapsulation frame-relay no frame-relay inverse-arp exit ! interface Serial0/0.221 point-to-point description ### LINK TO R1 ### ipv6 address 2001:ABAD:BEEF:1221::2/64 frame-relay interface-dlci 221 exit ! interface Serial0/0.223 point-to-point description ### LINK TO R3 ### ipv6 address 2001:ABAD:BEEF:2332::2/64 frame-relay interface-dlci 223 exit ! interface Serial0/0 no shutdown exit ! line con 0 logging sync no exec-timeout ! end !################################################## !# Free CCNA Workbook Lab 12-4 R3 Initial Config # !################################################## ! enable configure terminal ! hostname R3 no ip domain-lookup ipv6 unicast-routing ! interface Loopback0 description ### IPv6 SIMULATED NETWORK ### ipv6 address 2001:ABAD:BEEF:3003::1/64 ! interface Serial0/0 description ### LINK TO FRAME RELAY SWITCH ### encapsulation frame-relay no frame-relay inverse-arp exit ! interface Serial0/0.322 point-to-point description ### LINK TO R2 ### ipv6 address 2001:ABAD:BEEF:2332::3/64 frame-relay interface-dlci 322 exit ! interface Serial0/0 no shutdown exit ! line con 0 logging sync no exec-timeout ! end

Lab Objectives

Enable RIPng on R1’s Loopback0 and Serial0/0.122 interfaces using the RIPng process name “FREE”.
Enable RIPng on R2’s Loopback0, Serial0/0.221 and Serial0/0.223 interfaces using the RIPng process name “CCNA”.
Enable RIPng on R3’s Loopback0 and Serial0/0.322 interfaces using the RIPng process name “WORKBOOK”.
Verify that IPv6 the route to R1’s Loopback0 network exists in the R3’s IPv6 routing table with a next-hop of R2’s Serial0/0.223 link-local IPv6 address.
Verify IPv6 communication by pinging R1’s Loopback0 interface from R3’s Loopback0 interface.

Lab Instruction

Objective 1. – Enable RIPng on R1’s Loopback0 and Serial0/0.122 interfaces using the RIPng process name “CCNA”.

R1>enable
R1#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
R1(config)#interface loopback0
R1(config-if)#ipv6 rip FREE enable
R1(config-if)#interface Serial0/0.122
R1(config-subif)#ipv6 rip FREE enable   
R1(config-subif)#end
R1#
%SYS-5-CONFIG_I: Configured from console by console
R1#

Objective 2. – Enable RIPng on R2’s Loopback0, Serial0/0.221 and Serial0/0.223 interfaces using the RIPng process name “CCNA”.

R2>enable
R2#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
R2(config)#interface loopback0
R2(config-if)#ipv6 rip CCNA enable
R2(config-if)#interface Serial0/0.221
R2(config-subif)#ipv6 rip CCNA enable
R2(config-if)#interface Serial0/0.223
R2(config-subif)#ipv6 rip CCNA enable  
R2(config-subif)#end
R2#
%SYS-5-CONFIG_I: Configured from console by console
R2#

Objective 3. – Enable RIPng on R3’s Loopback0 and Serial0/0.322 interfaces using the RIPng process name “WORKBOOK”.

R3>enable
R3#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
R3(config)#interface loopback0
R3(config-if)#ipv6 rip WORKBOOK enable
R3(config-if)#interface Serial0/0.322
R3(config-subif)#ipv6 rip WORKBOOK enable
R3(config-subif)#end
R3#
%SYS-5-CONFIG_I: Configured from console by console
R3#

Objective 4. – Verify that IPv6 the route to R1’s Loopback0 network exists in the R3’s IPv6 routing table with a next-hop of R2’s Serial0/0.223 link-local IPv6 address.

R3#show ipv6 route 2001:ABAD:BEEF:1001::/64
Routing entry for 2001:ABAD:BEEF:1001::/64
  Known via "rip WORKBOOK", distance 120, metric 3
  Route count is 1/1, share count 0
  Routing paths:
    FE80::C800:11FF:FE84:8, Serial0/0.322
      Last updated 00:01:22 ago

R3#

As shown above in R3’s routing table; the route to the 2001:ABAD:BEEF:1001::/64 network shows a next hop of FE80::C800:11FF:FE84:8 via Serial0/0.322. Immediately you should recognize that this address is a link-local address as it begins with “FF80”. You can further verify that this is R2’s Serial0/0.223 link-local address by using the show ipv6 interface Serial0/0.223 command on R2 as shown below. Notice that the underlined link-local addresses from R3’s routing table and R2’s Serial0/0.223 interface match.

R2#show ipv6 interface Serial0/0.223
Serial0/0.223 is up, line protocol is up
  IPv6 is enabled, link-local address is FE80::C800:11FF:FE84:8
  No Virtual link-local address(es):
  Description: ### LINK TO R3 ###
  Global unicast address(es):
    2001:ABAD:BEEF:2332::2, subnet is 2001:ABAD:BEEF:2332::/64 
  Joined group address(es):
    FF02::1
    FF02::2
    FF02::9
    FF02::1:FF00:2
    FF02::1:FF84:8
  MTU is 1500 bytes
  ICMP error messages limited to one every 100 milliseconds
  ICMP redirects are enabled
  ICMP unreachables are sent
  ND DAD is enabled, number of DAD attempts: 1
  ND reachable time is 30000 milliseconds (using 36654)
  Hosts use stateless autoconfig for addresses.
R2#

Objective 5. – Verify IPv6 communication by pinging R1’s Loopback0 interface from R3’s Loopback0 interface.

R3#ping 2001:ABAD:BEEF:1001::1 source loopback0

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:ABAD:BEEF:1001::1, timeout is 2 seconds:
Packet sent with a source address of 2001:ABAD:BEEF:3003::1
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/29/64 ms
R3#

◄ Previous Lab

Next Lab ►