Question 260
At fictional Oakridge Energy, a network engineer supporting field substations is reviewing BGP routing, path attributes and EVPN exchange during a baseline compliance test (HCIP-H12-821-BGP-065). The observed network issue is: An eBGP peer accepts a route with its own AS already in AS_PATH and an engineer proposes disabling loop avoidance broadly. Which next engineering action best addresses the reported problem?
Explanation
Correct Answer
The directly responsive action is: Investigate the accidental AS path and repair policy instead of weakening protection. The specific reported fault is: An eBGP peer accepts a route with its own AS already in AS_PATH and an engineer proposes disabling loop avoidance broadly. Confirmation should show: Normal loop-containing paths are rejected and intended routes pass the clean AS path. The supporting technical principle is: BGP AS_PATH includes information used for inter-AS loop prevention.
Incorrect Answers
“Match BGP remote-as values with the intended eBGP or iBGP relationship and check session logs” responds to another technical or business failure: Two routers establish TCP connectivity but BGP stays in Active because the configured peer AS differs from the neighbor's actual AS. That source case depends on: BGP peering requires agreement about autonomous-system identity and session roles. The present issue is: An eBGP peer accepts a route with its own AS already in AS_PATH and an engineer proposes disabling loop avoidance broadly. The more direct action is “Investigate the accidental AS path and repair policy instead of weakening protection” because BGP AS_PATH includes information used for inter-AS loop prevention.
“Verify RR cluster design and use appropriate cluster IDs for intentional reflection domains” responds to another technical or business failure: Two route reflectors use an accidental identical cluster identifier across a design where distinct clusters are required. That source case depends on: BGP route reflectors use cluster-list attributes to detect reflection loops. The present issue is: An eBGP peer accepts a route with its own AS already in AS_PATH and an engineer proposes disabling loop avoidance broadly. The more direct action is “Investigate the accidental AS path and repair policy instead of weakening protection” because BGP AS_PATH includes information used for inter-AS loop prevention.
“Verify EVPN Type 2 MAC/IP route origination and import RTs between the VTEPs” responds to another technical or business failure: A VXLAN VTEP fails to learn a remote host's MAC and IP even though underlay IP reachability is working. That source case depends on: EVPN Type 2 routes distribute endpoint MAC reachability and related IP bindings. The present issue is: An eBGP peer accepts a route with its own AS already in AS_PATH and an engineer proposes disabling loop avoidance broadly. The more direct action is “Investigate the accidental AS path and repair policy instead of weakening protection” because BGP AS_PATH includes information used for inter-AS loop prevention.