Question 760
At a managed network team troubleshooting an internet edge, a Junos specialist investigates this scenario: An external BGP peering repeatedly fails negotiation because the configured peer AS differs from the neighbor's actual AS. The diagnosis must distinguish a healthy BGP session from eligible received routes. What is the most appropriate correction to implement?
Explanation
Correct Answer
For a managed network team troubleshooting an internet edge, the direct corrective action is: Correct the peer-as setting for the specific external BGP neighbor and recheck the session. This addresses the mechanism: BGP OPEN messages carry AS information and external peers must agree on their intended local and remote AS relationship. Confirm by checking: show BGP neighbor reports Established with the expected external peer AS. During rollout, verify provider documentation and do not broaden peer trust to arbitrary autonomous systems.
Incorrect Answers
In Junos BGP best-path selection an eligible shorter AS path is generally preferred after higher-priority criteria tie. The appropriate correction for the reported case is: Correct the peer-as setting for the specific external BGP neighbor and recheck the session.
BGP depends on a reachable TCP transport path, normally using destination port 179. Fixing that different mechanism would not address the current root cause: BGP OPEN messages carry AS information and external peers must agree on their intended local and remote AS relationship.
IBGP requires compatible local and remote AS settings, TCP reachability and correct neighbor addresses. Its verification is distinct from the reported condition: An external BGP peering repeatedly fails negotiation because the configured peer AS differs from the neighbor's actual AS. The diagnosis must distinguish a healthy BGP session from eligible received routes.