Question 600
At an enterprise core exchanging BGP routes over redundant WAN paths, a Junos specialist investigates this scenario: A BGP neighbor is configured correctly but remains in Connect or Active state across a protected interconnect. The chosen route must have a valid data-plane next hop. Which underlying distinction should guide troubleshooting?
Explanation
Correct Answer
For an enterprise core exchanging BGP routes over redundant WAN paths, the governing mechanism is: BGP depends on a reachable TCP transport path, normally using destination port 179. It explains the reported symptom: A BGP neighbor is configured correctly but remains in Connect or Active state across a protected interconnect. The intended response is: Check source reachability and permit the specifically authorized BGP TCP flow across the interconnect. Verification: The neighbor establishes its TCP session and BGP state changes to Established.
Incorrect Answers
Junos BGP best-path logic generally prefers the external route when preceding comparisons tie. This alternative mechanism does not match the current fault.
A BGP import policy determines which incoming route advertisements are accepted into the routing table. Fixing that different mechanism would not address the current root cause: BGP depends on a reachable TCP transport path, normally using destination port 179.
Route-flap damping can suppress repeatedly changing paths according to configured penalties and reuse rules. Its verification is distinct from the reported condition: A BGP neighbor is configured correctly but remains in Connect or Active state across a protected interconnect. The chosen route must have a valid data-plane next hop.