...
When deploying BGP, there are several timers can be configured.
| Table of Contents |
|---|
Configuring BGP Keepalive and Hold Timers
...
- 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 fewer network bandwidth are 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 is unhelpful for implementing rapid BGP network convergence and may cause many packets to be lost.
When routes change, the switch sends routing updates to notify its peers. If a route changes frequently, the set protocols bgp [vrf <vrf-name>] {neighbor <ip>| peer-group <peer-group> | interface <interface>} advertisement-interval <advert-interval> command can be used to adjust the interval at which Update packets are sent for changes of this route. This frees the switch from sending Update packets for every route change.
The following example commands set the advertisement interval to 5 seconds:
| Code Block |
|---|
admin@XorPlus# set protocols bgp neighbor 1.1.1.1 advertisement-interval 5
admin@XorPlus# commit |
Configuring the Global BGP Timers
In addition to the timers configured for a specific neighbor or a peer goup described above, BGP also supports to configure global timers for all the BGP neighbors.
The following example commands set the keepalive interval to 10 seconds and the hold time to 30 seconds globally for all the BGP neighbors.
| Code Block |
|---|
admin@XorPlus# set protocols bgp timers keepalive 10
admin@XorPlus# set protocols bgp timers holdtime 30
admin@XorPlus# commit |