Question 430
In the fictional Orchard-3 east pod, a lab-to-production migration after a successful canary, the team reports that a leaf's routed BGP peering fails after peer-AS data was changed. A peer suggested: "Change the syslog severity to fix the session" That did not solve the constraint. What should be chosen instead?
Explanation
Correct Answer
BGP session establishment requires consistent neighbor transport and AS expectations. Check: the intended BGP neighbor is established with the correct peer identity.
Incorrect Answers
“Create a MAC-VRF rather than verifying the neighbor” targets a different operation from the reported requirement: “a leaf's routed BGP peering fails after peer-AS data was changed”. BGP session establishment requires consistent neighbor transport and AS expectations. The confirming result is: the intended BGP neighbor is established with the correct peer identity. For the staged migration, validate the affected path before expansion.
“Add a VXLAN VNI to establish the underlay BGP session” targets a different operation from the reported requirement: “a leaf's routed BGP peering fails after peer-AS data was changed”. BGP session establishment requires consistent neighbor transport and AS expectations. The confirming result is: the intended BGP neighbor is established with the correct peer identity. For the staged migration, validate the affected path before expansion.
“Change the syslog severity to fix the session” targets a different operation from the reported requirement: “a leaf's routed BGP peering fails after peer-AS data was changed”. BGP session establishment requires consistent neighbor transport and AS expectations. The confirming result is: the intended BGP neighbor is established with the correct peer identity. For the staged migration, validate the affected path before expansion.