Configuring RIP for IPv6

2017-11-03 09:05:07

Problem

You want to add a JUNOS router running RIP to your IPv6 network.

Solution

The configuration for the IPv6 version of RIP, called RIPng, is basically the same as for the IPv4 version of RIP. RIPng has a separate configuration hierarchy:

[edit protocols ripng] aviva@RouterH# set group v6-rip-group neighbor t1-4/0/0.0 aviva@RouterH# set group v6-rip-group neighbor fe-1/0/1.0

You also need to configure the interfaces to support IPv6 traffic:

[edit interfaces] aviva@RouterH# set t1-r/0/0 unit 0 family inet6 aviva@RouterH# set fe-1/0/1 unit 0 family inet6

To have the router advertise RIPng routes to its neighbors, configure a routing policy and apply it to the RIPng group:

[edit policy-options] aviva@RouterH# set policy-statement advertise-rip-routes term 1 from protocol direct aviva@RouterH# set policy-statement advertise-rip-routes term 1 from protocol rip aviva@RouterH# set policy-statement advertise-rip-routes term 1 then accept [edit protocols ripng] aviva@RouterH# set group v6-rip-group neighbor export advertise-rip-routes

Discussion

JUNOS RIPng configuration for IPv6 networks is almost identical to the IPv4 RIP configure configuration. You configure the protocol with set ripng commands instead of set rip commands and use show ripng commands instead of show rip commands to check the RIP status. Also, make sure to set the IPv6 address with the inet6 family on the interfaces running RIPng and on the loopback interface, lo0.

To have RIPng advertise its RIPng routes, you create a routing policy as you did with RIPv4. This recipe uses the same policy configured in Recipe 10.2.

To check that the RIPng configuration is working and the router knows about its neighbors, use the show ripng neighbor command:

aviva@RouterG> show ripng neighbor Source Dest In Neighbor State Address Address Send Recv Met -------- ----- ------- ------- ---- ---- --- fe-1/0/1.0 Up fe80::205:85ff:fec2:2ef5 ff02::9 yes yes 1 t1-4/0/0.0 Up fe80::205:85ff:fec2:2ed0 ff02::9 yes yes 1

This output shows the two configured RIPng interfaces. The first column shows the interface that connects to the neighbor, and the second column shows that the neighbor is operational, or Up, and is listening to RIPng traffic. The Send and Recv columns indicate that the router is both sending RIPng packets to and receiving packets from its neighbors. The last column shows the inbound metric, which is how many hops away the neighbor is. Here, each neighbor is directly connected and is one hop away, so the inbound metrics are 1. The metric value is included in the RIPng route to that neighbor that is placed in the routing table.

Check that the router has learned RIPng routes:

aviva@RouterG> show route table inet6 protocol ripng inet6.0: 7 destinations, 8 routes (7 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 1080::8:800:200c:2/128 *[RIPng/100] 00:13:36, metric 2, tag 0 > to fe80::205:85ff:fec4:72d0 via t1-4/0/0.0 1080::8:800:200c:3/128 *[RIPng/100] 00:12:43, metric 2, tag 0 > to fe80::205:85ff:fec1:d1f5 via fe-1/0/1.0 ff02::9/128 *[RIPng/100] 00:12:03, metric 1 MultiRecv

Finally, verify that RIPng is sending protocol updates to and receiving updates from its neighbors:

aviva@RouterG> show ripng statistics RIPng info: port 521; update interval 30s; holddown 180s; timeout 120s. rts learned rts held down rqsts dropped resps dropped 2 0 0 0 fe-1/0/1.0: 1 routes learned; 1 routes advertised Counter Total Last 5 min Last minute ------- ----------- ----------- ----------- Updates Sent 30 11 2 Triggered Updates Sent 0 0 0 Responses Sent 0 0 0 Bad Messages 0 0 0 Updates Received 32 11 2 Bad Route Entries 0 0 0 Updates Ignored 0 0 0 RIPng Requests Received 1 0 0 RIPng Requests Ignored 0 0 0 t1-4/0/0.0: 1 routes learned; 1 routes advertised Counter Total Last 5 min Last minute ------- ----------- ----------- ----------- Updates Sent 30 11 2 Triggered Updates Sent 0 0 0 Responses Sent 0 0 0 Bad Messages 0 0 0 Updates Received 34 11 2 Bad Route Entries 0 0 0 Updates Ignored 0 0 0 RIPng Requests Received 0 0 0 RIPng Requests Ignored 0 0 0

Категории