Controlling the Valid Time of the Routing Policy

Configuring the delay for applying the routing policy can promote network stability.

Context

In actual applications, when the configurations of multiple cooperative routing policies change, the Routing Management Module (RM) immediately notifies related protocols to apply a new routing policy, after the configuration of the routing policy is complete. An incomplete routing policy causes route flapping, instability of the network, and a waste of time during packet processing.

The system provides the following rules for processing changes of a routing policy:

By default, the RM immediately notifies the protocol of applying the new policy when the routing policy changes.
If the valid time of the routing policy is configured, when the commands used to configure the routing policy change, the RM does not notify various protocols of immediately processing the changes. Instead, the RM waits for a certain period, and then notifies various protocols of applying the changed routing policy.
If the routing policy changes again during the waiting time, the RM resets the timer.

Procedure

Access the system view.
system-view
Set the delay for applying the routing policy.
route-policy-change notify-delay delay-time

The delay ranges from 1 to 180, in seconds.

By default, the RM immediately notifies the protocol of applying the new policy when the routing policy changes.

USG6000E: The delay ranges from 1 to 180, in seconds.

By default, the RM immediately notifies the protocol of applying the new policy when the routing policy changes.
(Optional) Configure BGP to apply the new routing policy.
refresh bgp all { export | import }

After the command is used, the effect of the policy filtering can be found immediately. You can run the command to configure BGP to immediately apply new policies.

The policies affected by the timer are ACLs, IP prefix lists, AS_Path filters, community filters, extended community filters, RD filters, and Route-Policies.