RIPng for IPv6
While the mechanisms of RIP remain unchanged, RIPng for IPv6 has been added to include support for IPv6
addressing and prefixes, different packet formats, packet lengths and no authentication on switches.
RIPng is for IPv6 only just as RIPv2 is for IPv4 only. RIPv2 and RIPng must be regarded as two independent
protocols with no interaction between them.
RIPng is specified by RFC 2080 and RFC 2081
NOTE:
RIPng and RIPv2 can be supported on the same interface/VLAN.
Supported features
• RIPng global enable/disableEnables/Disables RIPng protocol in the config context.
• Split horizonPrevents the formation of loops in routing. A router is not allowed the advertisement of routes back
to the interface where it was initially learned. Enabled by default. Split Horizon is a non-configurable feature.
• Poison-ReverseOptimizes the transmission of routing information and improves the time-to-reach network
convergence. Enabled by default and can be disabled per VLAN interface.
• Redistribute connected/static/ospfv3 routesRIPng protocol advertises routes learned from static, connected
and other routing protocols(example OSPFv3) to its peers.
• Metric configuration for imported routesUpdates the metric for imported routes based on the value configured.
◦ Router ripng default-metric — for routes imported from protocols other than RIPng
◦
vlan <id> ipv6 ripng
metric — for routes received from other RIPng peer
• Configuration of RIPng timers: update, timeout and garbage collect.
◦ Update timer defines interval between update messages.
◦ Timeout timer defines route aging time.
◦ The garbage-collect timer defines the time interval when the metric of a route is 16 to the time when it is
deleted from the routing table.
• Administrative distances: The default value can be modified and the value is applied to all routes learned
through RIPng.
• RIPng will listen only to RIPng packets sent to the multicast address FF02::9. All packets sent out will be
addressed to FF02::9 and the source IP will be the linklocal IP address of the VLAN.
• Route maps — Route maps are applied in the redistribution process to control route prefixes or to modify the
attributes of the routes. Route-maps can be used in RIPng redistribution to apply route policy configurations.
• RIPng notifications/traps — Traps are generated as the result of finding an unusual condition while parsing an
RIPng packet or a processing a timer event. Disabled by default.
Limitations
Chapter 10
RIPng
186
Aruba 3810 / 5400R Multicast and Routing Guide for ArubaOS-
Switch 16.08