Configuring RIP Timers

RIP has three timers: Update timer, Age timer and Garbage-collect timer. Changing the values of the three timers affects the RIP convergence speed.

Access the system view.
```
system-view
```
Configure a RIP process and access the RIP process view.
```
rip [ process-id ]
```
Configure RIP timers.
```
timers rip update age garbage-collect
```
- RIP timers take effect immediately after being changed.
- Route flapping occurs if the values of the times 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 RIP route changes within the update time, the FW cannot inform its neighbors of the change on time.
- You must configure RIP timers based on the network performance and uniformly on all the FW running RIP. 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, 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.