.. _example_protocols_bgp_neighbor_timers:

######
Timers
######

Scenario to verify BGP neighbor timers configuration and functionality.
BGP uses three key timers to control session behavior:

- **holdtime**: Time to wait without receiving keepalives before declaring
  the neighbor down (default 180s).

- **keepalive**: Interval between sending keepalive messages (default
  holdtime/3, typically 60s).

- **connect**: Interval between connection retry attempts after a failure
  (default 120s).

Custom timers optimize convergence speed (lower values) or reduce overhead
(higher values). This test verifies that configured timer values are correctly
applied and visible in BGP neighbor information.

***********************************
Test iBGP - Neighbor holdtime timer
***********************************

Description
===========

Test BGP **neighbor holdtime timer** configuration. DUT0 configures
a custom holdtime value (30s) for the neighbor.
The holdtime specifies how long to wait without receiving keepalive before declaring the neighbor down.

Scenario
========

.. include:: timers/testibgp-neighborholdtimetimer

.. raw:: html

  <hr>

************************************
Test iBGP - Neighbor keepalive timer
************************************

Description
===========

Test BGP **neighbor keepalive timer** configuration. DUT0 configures
custom keepalive (10s) and holdtime (30s) values for the neighbor.
The keepalive timer specifies the interval at which keepalive messages are sent.

Scenario
========

.. include:: timers/testibgp-neighborkeepalivetimer

.. raw:: html

  <hr>

**********************************
Test iBGP - Neighbor connect timer
**********************************

Description
===========

Test BGP **neighbor connect timer** configuration. DUT0 configures
a custom connect timer value (15s) for the neighbor.
The connect timer specifies the interval between connection retry attempts.

Scenario
========

.. include:: timers/testibgp-neighborconnecttimer

.. raw:: html

  <hr>