Question 510
A remote BGP neighbor uses a different AS number than configured and the session fails during OPEN negotiation. What is the most defensible network engineering correction?
Explanation
Correct Answer
This option addresses the stated case rather than another networking issue. Principle: BGP OPEN negotiation includes AS identity that must match peering intent. Remedy: Confirm the configured local and peer AS values with the authoritative design. Proof: The session reaches Established only with the documented correct peer AS.
Incorrect Answers
Review EBGP multihop transport reachability and session parameters is a relevant step for the separate scenario in which a multihop EBGP session is configured like a directly connected neighbor and never establishes across the transit hop. It does not directly fix this case. Instead confirm the configured local and peer AS values with the authoritative design; verify: The session reaches Established only with the documented correct peer AS.
This answer would be more suitable when a BGP peer is stuck in Active after a maintenance window even though the remote address is configured, where the corrective action is to verify IP reachability, routing instance context, TCP transport and session authentication. The failure here is different: BGP OPEN negotiation includes AS identity that must match peering intent. Required validation: The session reaches Established only with the documented correct peer AS.
This option overlooks the decisive condition. Its supporting principle is oSPF neighbor-state interpretation depends on multiaccess election roles, while this scenario depends on bGP OPEN negotiation includes AS identity that must match peering intent. Verify the correction with: The session reaches Established only with the documented correct peer AS.