Configuring an Update Message Timer

Context

BGP does not periodically update a routing table. When BGP routes change, BGP updates the changed BGP routes in the BGP routing table by sending Update messages.

If a short Update message interval is set, BGP can fast detect route changes. This speeds up BGP network convergence, but increases the number of Update messages on the network and loads of devices, and consumes more network bandwidth resources.
If a long Update message interval is set, the number of Update messages on the network is reduced, loads of devices are reduced, and less network bandwidth is consumed. This avoids network flapping. If the Update message interval is too long, BGP is unable to detect route changes in a timely manner. This hinders the implementation of rapid BGP network convergence and may cause significant packet loss.

Procedure

Run system-view
The system view is displayed.
Run bgp { as-number-plain | as-number-dot }
The BGP view is displayed.
Enter the corresponding address family view based on network type to configure BGP devices on networks.
- Run ipv4-family { unicast | multicast }
  
  The IPv4 address family view is displayed.
- Run ipv6-family [ unicast ]
  
  The IPv6 address family view is displayed.
Run peer { ipv4-address | group-name | ipv6-address } route-update-interval interval
An Update message timer is configured.

By default, the interval at which Update messages are sent to IBGP peers is 15s, and the interval at which Update messages are sent to EBGP peers is 30s.