Setting the BGP4+ ConnectRetry Interval

You can speed up or slow down the establishment of BGP4+ peer relationships to adapt the network changes by changing the BGP4+ ConnectRetry interval.

Context

When BGP4+ initiates a TCP connection, the ConnectRetry timer is stopped if the TCP connection is established successfully. If the first attempt to establish a TCP connection fails, BGP4+ tries again to establish the TCP connection after the ConnectRetry timer expires. The ConnectRetry interval can be adjusted as needed.

The ConnectRetry interval can be reduced in order to lessen the time BGP4+ waits to retry establishing a TCP connection after the first attempt fails.
To suppress route flapping caused by constant peer flapping, the ConnectRetry interval can be increased to speed up route convergence.

Procedure

Configure a BGP ConnectRetry timer for all peers or peer groups.
1. Access the system view.
  system-view
2. Access the BGP view.
  bgp { as-number-plain | as-number-dot }
3. Set the BGP ConnectRetry timer for all peers or peer groups.
  timer connect-retry connect-retry-time
  
  By default, the ConnectRetry timer value is 32s.
Configure a ConnectRetry timer for a specific peer or peer group.
1. Access the system view.
  system-view
2. Access the BGP view.
  bgp { as-number-plain | as-number-dot }
3. Set the ConnectRetry timer for a specific peer or peer group.
  peer { group-name | ipv6-address } timer connect-retry connect-retry-time
  
  By default, the ConnectRetry timer value is 32s.
  
  The ConnectRetry timer configured for a peer or peer group takes precedence over that configured for all peers or peer groups.