300-510 · Question #81
After an engineer configures BGP in R1, it starts receiving this message Which action makes the peering come back up again?
The correct answer is D. Set up a hold-down timer higher. The BGP error message in the exhibit is a NOTIFICATION indicating the Hold Timer has expired. BGP peers exchange KEEPALIVE messages at regular intervals; if a router does not receive a KEEPALIVE or UPDATE within the negotiated Hold Time, it sends a NOTIFICATION with error code…
Question
After an engineer configures BGP in R1, it starts receiving this message Which action makes the peering come back up again?
Options
- AMake a soft reset to the peer.
- BSet up a minimum hold-down timer higher.
- CSet up a hello timer higher.
- DSet up a hold-down timer higher.
How the community answered
(19 responses)- A5% (1)
- C11% (2)
- D84% (16)
Explanation
The BGP error message in the exhibit is a NOTIFICATION indicating the Hold Timer has expired. BGP peers exchange KEEPALIVE messages at regular intervals; if a router does not receive a KEEPALIVE or UPDATE within the negotiated Hold Time, it sends a NOTIFICATION with error code 'Hold Timer Expired' and tears down the session. Setting a higher hold-down (hold) timer gives more tolerance for delayed KEEPALIVEs before the session is declared dead, resolving transient keepalive delivery issues. Option A (soft reset) clears the RIB without fixing the timer mismatch. Option B/C (hello timer) - BGP does not use a 'hello' timer in the same sense as OSPF; the relevant timers are keepalive and hold. Option C sets hello higher which is not applicable to BGP.
Topics
Community Discussion
No community discussion yet for this question.