How to Configuring RIP for IPv6 - RIPng

While getting Cisco Training in Pakistan, now its time for you to move to third, dynamic routing protocol free CCNA Binder discusses the fundamental understanding of IPv6. Created specifically for the IPv6 RIP next generation.

Operation mode such as RIPv2, RIPng sending updates every 30 seconds and the route expiration timer time is 180 seconds. Default garbage collection interval is 120 seconds. RIP to send updates to the IPv6 multicast groups, and by default uses port 521 FF02::9.

Configuring RIPng only RIPv2, slightly easier. RIPng, you configured in router configuration mode to a specific interface not using network x.x.x.x command no longer participate in the RIP process. RIPng you participate now RIP interface is configured on a per-interface basis.

To configure an interface name RIPng you use IPv6 RIP command is enabled on a per-interface basis. IPv4 is the name specified in the syntax of local major name is used to identify the router RIPng processes on multiple processes on a single router RIPng, RIP can only have a single process.

RIPng Protocol timers, and other relevant information you want to see, use this command to display shows the name of the IPv6 RIP. To view the database will use the show IPv6 RIPng user names or privileged mode in the RIP database command.

There is a new order, not RIP to show IPv6 RIP command names the next-hop IPv4 to IPv6. This command displays the number of routes to each next-hop (a neighboring router).

In this lab you will R1&R2 and R3, R2 located on each router interface loopback0 IPv6 traffic between IPv6 network for the routing on a frame relay subinterface configuration between RIPng.

Familiarize yourself with the following new commands;

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.

Lab Objectives:

• Enable RIPng R1 ′ s and serial 0/0.122 interface Loopback0 used RIPng process name "none".
• Enable RIPng R2 ′ s Loopback0, serial 0/0.221 serial 0/0.223 interface using RIPng process name "CCNA".
• Enable RIPng R3 ′ s and serial 0/0.322 interface Loopback0 used RIPng process name "Binder".
• Validation R1 R2 ′ s ′ s Loopback0 network routing serial 0/0.223 link-local IPv6 address of the next hop of the R3 ′ s the IPv6 exists in the IPv6 routing table.
• Verified by pinging the R1 from R3 ′ s ′ s Loopback0 interface Loopback0 interface IPv6 traffic.

Step 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#

Step 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#

R3 as shown ′ s routing table; the route to the 2001:ABAD:BEEF:1001::/64 display FE80::C800:11FF:FE84:8 serial 0/0.322 the next-hop network. You should immediately recognize that the address is a link-local address, it begins with "FF80 ″. You can further verify this is through the use of R2, as shown in the following display interface R2 ′ s serial 0/0.223 serial 0/0.223 command IPv6 link-local addresses. Please pay attention to the bottom line of the link-local address from the R3 and R2 ′ s ′ s routing table matches the serial 0/0.223 interface.

Step 5: Verify that by pinging the R1 from R3 ′ s ′ s Loopback0 interface Loopback0 interface IPv6 traffic.