When two routers establish a pair of logical BGP peers through a multi-hop physical link, the peer connect-interface command must be used.

Question

Options

• ATRUE
• BFALSE
• C
• D

• A
  84% (51)
• B
  5% (3)
• C
  2% (1)
• D
  10% (6)

Explanation

A (TRUE) is correct because when BGP peers are not directly connected - meaning the TCP session must traverse multiple physical hops - the router cannot automatically determine which source interface to use for the connection. The peer connect-interface command explicitly binds the BGP session to a specific local interface, ensuring the TCP handshake originates from the correct IP address and that route reflectors or eBGP multi-hop peers can reliably reach each other.

B (FALSE) is wrong because omitting peer connect-interface in a multi-hop scenario typically causes session establishment to fail or use an unpredictable source address, breaking reachability - the command is not optional here.

C and D are empty distractors with no content to evaluate.

Memory tip: Think "multi-hop = must specify." Any time BGP peers aren't directly adjacent, you have to manually point the router to the right "door" to knock on - that's the peer connect-interface command. If they're directly connected, the router can figure it out on its own.

No community discussion yet for this question.