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

Reminder

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

upgrade

CLI-based Configuration Guide - IP Unicast Routing

AR100, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R009

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 RIPng Timers

Configuring RIPng Timers

Context

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

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ripng [ process-id ] [ vpn-instance vpn-instance-name ]

    The RIPng process is enabled and the RIPng view is displayed.

  3. Run timers ripng update age garbage-collect

    RIPng timers are configured.

    NOTE:
    • RIPng timers take effect immediately after being changed.

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

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

    By default, the Update timer is 30s; the Age timer is 180s; 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, RIPng 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.

Translation
Download
Updated: 2019-05-17

Document ID: EDOC1000174069

Views: 130637

Downloads: 274

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next