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 HPE 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


RIPng and RIPv2 can be supported on the same interface/VLAN.

Supported features

  • RIPng global enable/disable

    Enables/Disables RIPng protocol in the config context.

  • Split horizon

    Prevents 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 nonconfigurable feature.

  • Poison-Reverse

    Optimizes 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/staticroutes

    RIPng protocol advertises routes learned from static and connected networks. to its peers.

  • Metric configuration for imported routes

    Updates 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 link local IPv6 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.


Limits imposed on RIPng are as follows:

IPv6 loop back addresses cannot be redistributed into RIPng.

Number of interfaces/VLANs on which RIPng may be run:


Total number of routes supported:


Maximum number of IPv6 addresses per Vlan:


Maximum number of IPv6 Vlans:


Maximum number of IPv6 addresses:


NOTE: Starting from 16.01 onwards, the redistribution of OSPFv3 external routes (E1/E2/N1/N2) into RIPng is not supported.