RIP NEXT GENERATION (RIPng)
RIP next generation is very similar to the RIP-2 version in IPv4 however there is no such concept of auto-summarization in RIPng by default in IPv6.
We can adopt following procedure to enable RIPng on Global and then on interface level.
It tells router that IPv6 routing is enabled on this router.
ipv6 router rip name
It defines the RIP process and (name) should be unique on that particular router atleast.
Interface level commands
IPv6 address xxxx.xxxx.xxxx.xxxx.xxxx.xxxx.xxxx.xxxx.xxxx
IPv6 address xxxx.xxxx.xxxx.xxxx::/64 eui-64
either use simple IPv6 unicast addressing as in the above line or assign it through eui-64 process..
ipv6 rip name enable
Name should be same as defined earlier when defined the RIP process globally.
To the simplest level you can verify RIPng configuration through the following commands.
which will show the RIPng process and if already enabled on interface.
PING IPv6 address
Will verify if IPv6 routing is being responsive.
no ip address (this line shows if the IPv4 address is also configured)
ipv6 address 3002::3/64
show ipv6 int brief
FE80::C000:D5FF:FED8:0 (its the link local address )
3002::3 (this is the IPv6 address)
show ipv6 int f0/0
FastEthernet0/0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::C000:D5FF:FED8:0
No Virtual link-local address(es):
Global unicast address(es):
3002::3, subnet is 3002::/64
Joined group address(es):
MTU is 1500 bytes
Now from another connected router where the RIPng protocol is also enabled
ping ipv6 3002::3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 3002::3, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/4/8 ms
Successful reply from another router will ensure the IPv6 routing and the RIPng processes between two between two routers are functional.