← Back to Part 2 Modules
PART 2 · ADVANCED BGP THEORY · MODULE K

Module K – BGP Timers and Stability

Lesson content presented from the approved Part 2 master documentation.

Timers determine session liveness and retry behaviour. Graceful Restart and BFD affect failure detection and convergence.

Learning objectives

1. Core timers

TimerPurposeNotes
KeepalivePeriodic liveness messageCisco defaults may be 60 seconds; platform/configuration dependent.
Hold TimeMaximum interval without acceptable BGP messageLower non-zero proposal is used; if either proposes zero, negotiated Hold Time is zero.
ConnectRetryDelay before retrying TCP establishmentImplementation/configuration dependent.
Graceful Restart timersControl stale-route retention and restart/helper behaviourCapability and platform dependent.

2. Configuration

router bgp 65001
 timers bgp 30 90
 neighbor 11.1.1.2 timers 20 60

Verify syntax and precedence on the target release. Avoid changing timers without considering peer compatibility and operational impact.

3. Graceful Restart

Graceful Restart is not a guarantee of uninterrupted forwarding. Success depends on forwarding-plane continuity, capability negotiation, timers, topology and implementation.

4. BFD and BGP

Bidirectional Forwarding Detection provides fast failure detection. BGP can use BFD state to trigger neighbour failure handling faster than a long Hold Timer.

interface GigabitEthernet0/0
 bfd interval 300 min_rx 300 multiplier 3
!
router bgp 65001
 neighbor 11.1.1.2 fall-over bfd

Illustrative syntax only. Detection depends on negotiated intervals, multiplier, scheduling and platform implementation.

5. Convergence measurement

  1. Record baseline session, route count and forwarding path.
  2. Trigger a controlled link or peer failure.
  3. Measure detection and session-down time.
  4. Measure route withdrawal or alternate-path selection.
  5. Measure forwarding interruption and packet loss separately.
  6. Restore link and record session and route recovery.
  7. Repeat with timer/BFD/Graceful Restart settings.

Senior QA scenarios

IDTestExpected result
K-01Different Hold proposalsLower non-zero value; zero proposal yields zero.
K-02No acceptable BGP messageHold Timer expires at negotiated limit.
K-03Change KeepaliveMessages follow configured behaviour.
K-04Peer TCP unreachableRetry follows implementation.
K-05Graceful Restart peer restartEligible stale routes retained for applicable period.
K-06Route not refreshedStale route removed after timer.
K-07BFD failureBGP reacts to BFD down as supported.
K-08Vary BFD parametersDetection reflects negotiated values.
K-09Restore peerSession/routes recover.
K-10Control-plane restartData-plane impact recorded separately.

Interview questions

Student Knowledge Assessment – Module K (reconstructed)

Q1. What does the BGP Hold Timer measure?

A. Time since last acceptable BGP message

B. TCP retransmission count

C. Route age

D. IGP SPF interval

Correct answer: A. Time since last acceptable BGP message

Explanation: It expires if no acceptable BGP message is received within the negotiated interval.

Q2. How is a non-zero Hold Time generally negotiated?

A. Higher

B. Lower

C. Average

D. Random

Correct answer: B. Lower

Explanation: The lower non-zero proposed value is used.

Q3. What if either peer proposes Hold Time zero?

A. 180 seconds

B. 90 seconds

C. Negotiated Hold Time is zero

D. Session cannot establish

Correct answer: C. Negotiated Hold Time is zero

Explanation: A zero proposal results in a negotiated Hold Time of zero.

Q4. What is ConnectRetry used for?

A. Retrying TCP establishment

B. Refreshing ROAs

C. Selecting MED

D. Reflecting routes

Correct answer: A. Retrying TCP establishment

Explanation: It controls retry timing for TCP session establishment.

Q5. What is Graceful Restart intended to reduce?

A. Forwarding disruption during eligible control-plane restart

B. Prefix-list length

C. AS_PATH length

D. TCP port usage

Correct answer: A. Forwarding disruption during eligible control-plane restart

Explanation: It can preserve eligible stale routes temporarily during restart.

Q6. Does Graceful Restart guarantee no packet loss?

A. Yes

B. No

C. Only eBGP

D. Only with MED

Correct answer: B. No

Explanation: Forwarding continuity depends on platform and topology.

Q7. What does BFD provide?

A. Fast failure detection

B. Route aggregation

C. RPKI signing

D. AS translation

Correct answer: A. Fast failure detection

Explanation: BFD provides rapid detection of forwarding-path failure.

Q8. What influences BFD detection time?

A. Negotiated intervals/multiplier and scheduling

B. Hostname

C. Community name

D. Prefix length

Correct answer: A. Negotiated intervals/multiplier and scheduling

Explanation: Detection depends on negotiated parameters and implementation.

Q9. What should QA measure during failover?

A. Only BGP state

B. Only one ping

C. Detection, route convergence and forwarding impact separately

D. Only uptime

Correct answer: C. Detection, route convergence and forwarding impact separately

Explanation: Control-plane state and forwarding impact are distinct.

Q10. What happens if a stale route is not refreshed in the applicable GR period?

A. Retained forever

B. Removed

C. Becomes static

D. Changes origin

Correct answer: B. Removed

Explanation: Stale routes are removed when not refreshed within the applicable period.

Source and assessment note

Technical explanations, tables, examples, QA scenarios and assessments are presented from the approved Part 2 master documentation. Verify illustrative CLI syntax against the target router platform and software release before lab or production use.