nerdexam
Cisco

352-001 · Question #466

Your company requires two diverse multihop eBGP peerings to a partner network. Which two methods should you use to improve lost peer detection? (Choose 2)

The correct answer is A. Use Fast Peering Session Deactivation for the peers. E. Use Selective Address Tracking and match the peers. For multihop eBGP, Fast Peering Session Deactivation and Selective Address Tracking provide rapid peer loss detection by reacting to interface events and routing table changes rather than waiting for hold-timer expiration. Sub-second timer tuning introduces CPU load and…

Layer 3 Control Plane

Question

Your company requires two diverse multihop eBGP peerings to a partner network. Which two methods should you use to improve lost peer detection? (Choose 2)

Options

  • AUse Fast Peering Session Deactivation for the peers.
  • BUse sub-second keepalives for the peers.
  • CUse sub-second hold timers for the peers.
  • DUse sub-second minimum route advertisement Interval timers for the peers.
  • EUse Selective Address Tracking and match the peers.

How the community answered

(27 responses)
  • A
    70% (19)
  • B
    7% (2)
  • C
    4% (1)
  • D
    19% (5)

Why each option

For multihop eBGP, Fast Peering Session Deactivation and Selective Address Tracking provide rapid peer loss detection by reacting to interface events and routing table changes rather than waiting for hold-timer expiration. Sub-second timer tuning introduces CPU load and instability risks, and MRAI affects update frequency, not peer detection.

AUse Fast Peering Session Deactivation for the peers.Correct

Fast Peering Session Deactivation immediately tears down a BGP session when the interface used to reach the peer goes down, bypassing the hold-timer countdown and providing near-instantaneous lost-peer detection for multihop sessions.

BUse sub-second keepalives for the peers.

Sub-second BGP keepalives are not recommended because they generate excessive CPU load on both peers and can cause session instability under congestion or packet loss, making them an unreliable detection mechanism.

CUse sub-second hold timers for the peers.

Sub-second hold timers risk excessive BGP session flapping from normal transient packet loss; BGP standards specify a minimum hold time of 3 seconds, and reducing this further creates operational instability.

DUse sub-second minimum route advertisement Interval timers for the peers.

The minimum route advertisement interval (MRAI) governs how frequently BGP sends UPDATE messages, which affects convergence speed but has no effect on how quickly a lost BGP peer session is detected.

EUse Selective Address Tracking and match the peers.Correct

Selective Address Tracking monitors the routing table for the reachability of the BGP peer's IP address; when the peer route is withdrawn or disappears, the BGP session is immediately deactivated, making it well-suited for multihop eBGP topologies where no direct interface link exists.

Concept tested: Multihop eBGP fast peer loss detection mechanisms

Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_bgp/configuration/xe-16/irg-xe-16-book/bgp-fast-peering-session-deactivation.html

Topics

#eBGP#fast peering session deactivation#selective address tracking#peer detection

Community Discussion

No community discussion yet for this question.

Full 352-001 Practice