Configuring Route or Tunnel Iteration Suppression in Case of Flapping
Usage Scenario
In route or tunnel iteration scenarios, if a route or tunnel flaps frequently, services that depend on the route or tunnel are iterated frequently, causing frequent route updates. As a result, the CPU usage of the system keeps increasing. To solve the problem, enable route or tunnel iteration suppression in case of flapping. The suppression reduces the route update frequency and the CPU usage. To configure suppression periods for route or tunnel iteration, run the route recursive-lookup delay command.
Pre-configuration Tasks
Before configuring route or tunnel iteration suppression in case of flapping, complete the following tasks:
Configure link layer protocol parameters and IPv4 addresses for interfaces and ensure that the link layer protocol of the interfaces is Up.
Procedure
- Run system-view
The system view is displayed.
- Run undo route
recursive-lookup delay disable
Route or tunnel iteration suppression in case of flapping is enabled.
By default, route or tunnel iteration suppression in case of flapping is enabled.
To disable route or tunnel iteration suppression in case of flapping, run the route recursive-lookup delay disable command.
- (Optional) Run route recursive-lookup
delay start-time start-time increase-time increase-time max-time max-time
Suppression periods are configured for route or tunnel iteration, including the initial suppression period, incremental suppression period since the second suppression, and the maximum suppression period.
By default, the initial suppression period, incremental suppression period since the second suppression, and the maximum suppression period are 500 ms, 1000 ms, and 30000 ms, respectively.
- Run commit
The configuration is committed.