Routing Information Protocol next generation (RIPng) allows routers to exchange information for computing routes through an IPv6–based network. You should implement RIPng only on routers. IPv6 provides neighbor router information required by RIPng protocol to function as intended. A RIPng router is assumed to have interfaces in several networks and the protocol relies primarily on the metric of each network to compute routes using the distance vector algorithm.
RIP identifies network reachability based on cost, and cost is defined as hop count. One hop is the distance from one router to the next. This cost, or hop count, is the metric.
RIPng-enabled routers use UDP port 521 (the RIPng port) to exchange routing information. RIPng responds to a request by sending a message to the port from which the request originates. Specific queries can be sent from ports other than the RIPng port, but they must be directed to the RIPng port on the target machine.
Note
These time interval values are default values which are configurable by the user.
The IPv6 prefix of the destination.
A metric that represents the total cost of getting a datagram from the router to that destination. The metric is the sum of the costs of traversing the networks to arrive at the destination.
The IPv6 address of the next router in the path to the destination (the next hop). The next-hop IPv6 address is a linklocal address.
The VLAN or brouter port on which the RIPng routes were learned.
The age of the RIPng route.
RIPng protocol implementation is specified in IETF document RFC 2080.
RIPng-enabled routers use UDP port 521 (the RIPng port) to send and receive datagrams.
command: Specifies the purpose of the message.
version: The version of RIPng.
Generally you use a default route when it is not convenient to list every possible network in RIPng updates, and one or more routers in the system are able to handle traffic to networks that RIPng does not explicitly list.
RIPng is enabled with the default route only option. When you enable default route only on an interface, it suppresses all other routes in the update sent for the interface, and advertises only the default route.
Update timer: The RIPng process sends a complete routing table to each neighboring router every 30 seconds. To prevent collisions on broadcast networks, the process adds an offset value to the timer.
Timeout time interval: This is a 180 second time interval associated with every route. If the time interval expires, the metric for this route updates to the value of infinity (16) and the route is no longer valid. However, the routing table retains the value for another 120 seconds.
Garbage collection time interval: After the timeout time interval expires and the route becomes invalid, it remains in the routing table until the garbage collection time interval expires. The garbage collection time interval is 120 seconds. Until the garbage collection time interval expires all updates sent by this router include the invalid route. When the garbage collection timer expires, the process removes the route from the routing table.
Triggered update time interval: The triggered update time interval is set to a random value between 1 and 5 seconds after a triggered update is sent. A single update is sent even if multiple triggered updates occur before the timer expires.
Configuration of timers or time intervals is supported only at the CLI/SNMP/EDM level. Configuration of timers or time intervals is not supported at the interface/port level.