No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Configuration Guide - IP Unicast Routing

CloudEngine 12800 and 12800E V200R002C50

This document describes the configurations of IP Unicast Routing, including IP Routing, Static Route, RIP, RIPng, OSPF, OSPFv3, IPv4 IS-IS, IPv6 IS-IS, BGP, Routing Policy, and PBR.

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring RIP Timers

Configuring RIP Timers


RIP uses 4 timers: Update, Age, Suppress, and Garbage-collect. Changing the timer values affects the convergence speed of RIP routes.


  1. Run system-view

    The system view is displayed.

  2. Run rip [ process-id ]

    The RIP view is displayed.

  3. Run timers rip update age suppress garbage-collect

    RIP timers are configured.

    • RIP timers take effect immediately after being changed.

    • Route flapping occurs if the values of the four timers are set improperly. The relationship between the values is as follows: update must be smaller than age and suppress must be smaller than garbage-collect. For example, if the update time is longer than the aging time, and a RIP route changes within the update time, the switch cannot inform its neighbors of the change on time.

    • You must configure RIP timers based on the network performance and uniformly on all the devices running RIP. This avoids unnecessary network traffic or route flapping.

    By default, the Update timer is 30s; the Age timer is 180s; the Suppress timer is 0s; the Garbage-collect timer is four times the Update timer, namely, 120s.

    In practice, the Garbage-collect timer is not fixed. If the Update timer is set to 30s, the Garbage-collect timer may range from 90s to 120s.

    Before permanently deleting an unreachable route from the routing table, RIP advertises this route (with the metric being set to 16) by periodically sending Update packets four times. Subsequently, all the neighbors know that this route is unreachable. Because a route may not always become unreachable at the beginning of an Update period, the Garbage-collect timer is actually three or four times the Update timer.

  4. Run commit

    The configuration is committed.

Updated: 2019-03-21

Document ID: EDOC1000166601

Views: 272311

Downloads: 161

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next