Question 730
After fixing the following network problem, what should the team verify: An inter-AS EVPN service advertises Ethernet MAC routes across the border without the expected next-hop and encapsulation capabilities, leaving routes visible but unusable.
Explanation
Correct Answer
A remote MAC route resolves to the correct border and service encapsulation and transmits a unicast frame. This confirms the approved response: Align border-gateway EVPN route exchange, next-hop reachability and tunnel encapsulation compatibility. It is relevant because: EVPN route reachability depends on both MP-BGP control-plane exchange and usable data-plane tunnel endpoints.
Incorrect Answers
A remote customer VRF imports the approved prefix and delivers labeled packets across both provider ASes. This would validate ANOTHER scenario: An inter-AS L3VPN reaches the first provider but customer prefixes vanish at the AS boundary because VPNv4 routes and label context are not exchanged under the chosen inter-AS model. The specific correction here is: Align border-gateway EVPN route exchange, next-hop reachability and tunnel encapsulation compatibility.
A lab MAC route from tenant A does not enter tenant B's MAC-VRF while shared authorized services remain reachable. This would validate ANOTHER scenario: A provider imports all EVPN routes from every retail tenant into one MAC-VRF, and identical MAC addresses cause cross-customer service confusion. The specific correction here is: Align border-gateway EVPN route exchange, next-hop reachability and tunnel encapsulation compatibility.
A lab traffic test passes with consistent pseudowire labels and expected Ethernet frame format. This would validate ANOTHER scenario: A layer-2 pseudowire on two PEs is signaled Up but customer frames are dropped because local and remote pseudowire encapsulation modes differ. The specific correction here is: Align border-gateway EVPN route exchange, next-hop reachability and tunnel encapsulation compatibility.