Question 950
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: A customer has accidentally assigned the same MAC to hosts in two sites and BGP EVPN repeatedly alternates the remote MAC owner. Which operational control would best prevent a recurrence of this exact failure mode?
- Maintain a per-VPN site-ID allocation register.
- Alert on oscillating MAC addresses that exceed planned mobility behavior.
- Track MAC churn and unknown-unicast levels separately from ordinary broadcast traffic.
- Alert on rapid MAC moves and validate redundant CPE topology.
Explanation
Correct Answer
B:Alert on oscillating MAC addresses that exceed planned mobility behavior. The control limits repetition of the described root condition: Repeated conflicting MAC advertisements can indicate duplicate endpoint identity rather than valid sequential migration. During audits, confirm: The duplicate source is corrected and MAC ownership stabilizes on one authorized site.
Incorrect Answers
A:Maintain a per-VPN site-ID allocation register. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically BGP L2VPN site ID collision. BGP L2VPN site identifiers help map distinct site attachments into the signaled service topology. In this scenario, however, the distinguishing issue is EVPN duplicate MAC protection and the confirming observation is: The duplicate source is corrected and MAC ownership stabilizes on one authorized site.
C:Track MAC churn and unknown-unicast levels separately from ordinary broadcast traffic. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically VPLS flooding unknown unicast. VPLS provides multipoint Ethernet bridging, so traffic to unknown MAC addresses can be flooded within the VPN forwarding domain. In this scenario, however, the distinguishing issue is EVPN duplicate MAC protection and the confirming observation is: The duplicate source is corrected and MAC ownership stabilizes on one authorized site.
D:Alert on rapid MAC moves and validate redundant CPE topology. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically VPLS MAC move instability. Multipoint Layer 2 forwarding can become unstable when the same source MAC appears alternately from multiple ports or pseudowires. In this scenario, however, the distinguishing issue is EVPN duplicate MAC protection and the confirming observation is: The duplicate source is corrected and MAC ownership stabilizes on one authorized site.
Question 951
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: A PE attached to a shared Ethernet segment fails and remote sites continue forwarding traffic toward the lost PE for too long. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare ESI values advertised by both PEs and the physical multihoming design.
- Inspect local and remote site IDs and the BGP L2VPN route connection mapping.
- Inspect Ethernet segment reachability advertisements and fast convergence or mass-withdraw behavior.
- Inspect newer EVPN MAC/IP route sequence and withdrawal of stale reachability.
Explanation
Correct Answer
C:Inspect Ethernet segment reachability advertisements and fast convergence or mass-withdraw behavior. This check examines the decisive condition for EVPN multihoming mass withdrawal before any unrelated changes are made. The underlying mechanism is: EVPN multihoming can signal a PE or segment failure so remote PEs quickly invalidate affected MAC reachability. The confirming observation is: Remote forwarding moves away from the failed PE after the segment withdrawal or protection event.
Incorrect Answers
A:Compare ESI values advertised by both PEs and the physical multihoming design. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically EVPN Ethernet segment identifier mismatch. EVPN multihoming relies on consistent Ethernet segment identification among PEs attached to the same segment. In this scenario, however, the distinguishing issue is EVPN multihoming mass withdrawal and the confirming observation is: Remote forwarding moves away from the failed PE after the segment withdrawal or protection event.
B:Inspect local and remote site IDs and the BGP L2VPN route connection mapping. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically BGP L2VPN site ID collision. BGP L2VPN site identifiers help map distinct site attachments into the signaled service topology. In this scenario, however, the distinguishing issue is EVPN multihoming mass withdrawal and the confirming observation is: Remote forwarding moves away from the failed PE after the segment withdrawal or protection event.
D:Inspect newer EVPN MAC/IP route sequence and withdrawal of stale reachability. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically EVPN MAC mobility sequence. EVPN MAC mobility procedures identify the newer location of a moving MAC and help remote PEs replace old forwarding state. In this scenario, however, the distinguishing issue is EVPN multihoming mass withdrawal and the confirming observation is: Remote forwarding moves away from the failed PE after the segment withdrawal or protection event.
Question 952
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A PE attached to a shared Ethernet segment fails and remote sites continue forwarding traffic toward the lost PE for too long. Which routing or service mechanism best explains the reported behavior?
- EVPN multihoming relies on consistent Ethernet segment identification among PEs attached to the same segment.
- EVPN MAC mobility procedures identify the newer location of a moving MAC and help remote PEs replace old forwarding state.
- BGP L2VPN site identifiers help map distinct site attachments into the signaled service topology.
- EVPN multihoming can signal a PE or segment failure so remote PEs quickly invalidate affected MAC reachability.
Explanation
Correct Answer
D:EVPN multihoming can signal a PE or segment failure so remote PEs quickly invalidate affected MAC reachability. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Remote forwarding moves away from the failed PE after the segment withdrawal or protection event. The targeted correction is: Restore the supported Ethernet segment failure signaling and backup forwarding path.
Incorrect Answers
A:EVPN multihoming relies on consistent Ethernet segment identification among PEs attached to the same segment. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically EVPN Ethernet segment identifier mismatch. EVPN multihoming relies on consistent Ethernet segment identification among PEs attached to the same segment. In this scenario, however, the distinguishing issue is EVPN multihoming mass withdrawal and the confirming observation is: Remote forwarding moves away from the failed PE after the segment withdrawal or protection event.
B:EVPN MAC mobility procedures identify the newer location of a moving MAC and help remote PEs replace old forwarding state. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically EVPN MAC mobility sequence. EVPN MAC mobility procedures identify the newer location of a moving MAC and help remote PEs replace old forwarding state. In this scenario, however, the distinguishing issue is EVPN multihoming mass withdrawal and the confirming observation is: Remote forwarding moves away from the failed PE after the segment withdrawal or protection event.
C:BGP L2VPN site identifiers help map distinct site attachments into the signaled service topology. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically BGP L2VPN site ID collision. BGP L2VPN site identifiers help map distinct site attachments into the signaled service topology. In this scenario, however, the distinguishing issue is EVPN multihoming mass withdrawal and the confirming observation is: Remote forwarding moves away from the failed PE after the segment withdrawal or protection event.
Question 953
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: A PE attached to a shared Ethernet segment fails and remote sites continue forwarding traffic toward the lost PE for too long. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Remote forwarding moves away from the failed PE after the segment withdrawal or protection event.
- Both peers advertise a matching ESI and remote control-plane state recognizes the multi-attached segment.
- Remote PEs resolve the mobile MAC to the current PE after processing the new route.
- Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
Explanation
Correct Answer
A:Remote forwarding moves away from the failed PE after the segment withdrawal or protection event. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: EVPN multihoming can signal a PE or segment failure so remote PEs quickly invalidate affected MAC reachability.
Incorrect Answers
B:Both peers advertise a matching ESI and remote control-plane state recognizes the multi-attached segment. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically EVPN Ethernet segment identifier mismatch. EVPN multihoming relies on consistent Ethernet segment identification among PEs attached to the same segment. In this scenario, however, the distinguishing issue is EVPN multihoming mass withdrawal and the confirming observation is: Remote forwarding moves away from the failed PE after the segment withdrawal or protection event.
C:Remote PEs resolve the mobile MAC to the current PE after processing the new route. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically EVPN MAC mobility sequence. EVPN MAC mobility procedures identify the newer location of a moving MAC and help remote PEs replace old forwarding state. In this scenario, however, the distinguishing issue is EVPN multihoming mass withdrawal and the confirming observation is: Remote forwarding moves away from the failed PE after the segment withdrawal or protection event.
D:Each site advertises its planned unique identity and the remote connection mapping is unambiguous. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically BGP L2VPN site ID collision. BGP L2VPN site identifiers help map distinct site attachments into the signaled service topology. In this scenario, however, the distinguishing issue is EVPN multihoming mass withdrawal and the confirming observation is: Remote forwarding moves away from the failed PE after the segment withdrawal or protection event.
Question 954
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A PE attached to a shared Ethernet segment fails and remote sites continue forwarding traffic toward the lost PE for too long. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Configure the intended matching ESI with compatible redundancy parameters.
- Restore the supported Ethernet segment failure signaling and backup forwarding path.
- Restore correct MAC mobility signaling and clear only proven stale entries if necessary.
- Assign unique service site IDs and align site ranges according to the intended topology.
Explanation
Correct Answer
B:Restore the supported Ethernet segment failure signaling and backup forwarding path. The change addresses the root behavior described here: EVPN multihoming can signal a PE or segment failure so remote PEs quickly invalidate affected MAC reachability. Verify success with: Remote forwarding moves away from the failed PE after the segment withdrawal or protection event.
Incorrect Answers
A:Configure the intended matching ESI with compatible redundancy parameters. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically EVPN Ethernet segment identifier mismatch. EVPN multihoming relies on consistent Ethernet segment identification among PEs attached to the same segment. In this scenario, however, the distinguishing issue is EVPN multihoming mass withdrawal and the confirming observation is: Remote forwarding moves away from the failed PE after the segment withdrawal or protection event.
C:Restore correct MAC mobility signaling and clear only proven stale entries if necessary. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically EVPN MAC mobility sequence. EVPN MAC mobility procedures identify the newer location of a moving MAC and help remote PEs replace old forwarding state. In this scenario, however, the distinguishing issue is EVPN multihoming mass withdrawal and the confirming observation is: Remote forwarding moves away from the failed PE after the segment withdrawal or protection event.
D:Assign unique service site IDs and align site ranges according to the intended topology. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically BGP L2VPN site ID collision. BGP L2VPN site identifiers help map distinct site attachments into the signaled service topology. In this scenario, however, the distinguishing issue is EVPN multihoming mass withdrawal and the confirming observation is: Remote forwarding moves away from the failed PE after the segment withdrawal or protection event.
Question 955
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: A PE attached to a shared Ethernet segment fails and remote sites continue forwarding traffic toward the lost PE for too long. Which operational control would best prevent a recurrence of this exact failure mode?
- Validate ESI consistency before enabling dual-homed production traffic.
- Exercise host mobility while watching route age and forwarding convergence.
- Test PE failure recovery with live MAC entries, not only a ping to the surviving PE.
- Maintain a per-VPN site-ID allocation register.
Explanation
Correct Answer
C:Test PE failure recovery with live MAC entries, not only a ping to the surviving PE. The control limits repetition of the described root condition: EVPN multihoming can signal a PE or segment failure so remote PEs quickly invalidate affected MAC reachability. During audits, confirm: Remote forwarding moves away from the failed PE after the segment withdrawal or protection event.
Incorrect Answers
A:Validate ESI consistency before enabling dual-homed production traffic. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically EVPN Ethernet segment identifier mismatch. EVPN multihoming relies on consistent Ethernet segment identification among PEs attached to the same segment. In this scenario, however, the distinguishing issue is EVPN multihoming mass withdrawal and the confirming observation is: Remote forwarding moves away from the failed PE after the segment withdrawal or protection event.
B:Exercise host mobility while watching route age and forwarding convergence. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically EVPN MAC mobility sequence. EVPN MAC mobility procedures identify the newer location of a moving MAC and help remote PEs replace old forwarding state. In this scenario, however, the distinguishing issue is EVPN multihoming mass withdrawal and the confirming observation is: Remote forwarding moves away from the failed PE after the segment withdrawal or protection event.
D:Maintain a per-VPN site-ID allocation register. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically BGP L2VPN site ID collision. BGP L2VPN site identifiers help map distinct site attachments into the signaled service topology. In this scenario, however, the distinguishing issue is EVPN multihoming mass withdrawal and the confirming observation is: Remote forwarding moves away from the failed PE after the segment withdrawal or protection event.
Question 956
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: A new PE receives EVPN advertisements from its reflector but the intended EVI does not contain any remote MAC entries. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect BGP L2VPN route distinguishers and the relevant service NLRI.
- Compare ESI values advertised by both PEs and the physical multihoming design.
- Inspect newer EVPN MAC/IP route sequence and withdrawal of stale reachability.
- Inspect EVPN RT values and the receiving EVI's route-import policy.
Explanation
Correct Answer
D:Inspect EVPN RT values and the receiving EVI's route-import policy. This check examines the decisive condition for EVPN BGP route target not imported before any unrelated changes are made. The underlying mechanism is: BGP EVPN route receipt and local service membership are separate; route targets control eligible imports. The confirming observation is: The EVI imports only its authorized remote MAC reachability when RT settings match.
Incorrect Answers
A:Inspect BGP L2VPN route distinguishers and the relevant service NLRI. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically BGP Layer 2 VPN route distinguisher. BGP-signaled L2VPN routes need distinguishable VPN identifiers so unrelated overlapping customer service advertisements do not collide. In this scenario, however, the distinguishing issue is EVPN BGP route target not imported and the confirming observation is: The EVI imports only its authorized remote MAC reachability when RT settings match.
B:Compare ESI values advertised by both PEs and the physical multihoming design. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically EVPN Ethernet segment identifier mismatch. EVPN multihoming relies on consistent Ethernet segment identification among PEs attached to the same segment. In this scenario, however, the distinguishing issue is EVPN BGP route target not imported and the confirming observation is: The EVI imports only its authorized remote MAC reachability when RT settings match.
C:Inspect newer EVPN MAC/IP route sequence and withdrawal of stale reachability. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically EVPN MAC mobility sequence. EVPN MAC mobility procedures identify the newer location of a moving MAC and help remote PEs replace old forwarding state. In this scenario, however, the distinguishing issue is EVPN BGP route target not imported and the confirming observation is: The EVI imports only its authorized remote MAC reachability when RT settings match.
Question 957
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: A new PE receives EVPN advertisements from its reflector but the intended EVI does not contain any remote MAC entries. Which routing or service mechanism best explains the reported behavior?
- BGP EVPN route receipt and local service membership are separate; route targets control eligible imports.
- BGP-signaled L2VPN routes need distinguishable VPN identifiers so unrelated overlapping customer service advertisements do not collide.
- EVPN multihoming uses designated forwarder selection to prevent duplicate BUM forwarding to a shared Ethernet segment.
- A pseudowire control word adds context or sequence fields in supported encapsulations, so endpoints must interpret a compatible format.
Explanation
Correct Answer
A:BGP EVPN route receipt and local service membership are separate; route targets control eligible imports. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The EVI imports only its authorized remote MAC reachability when RT settings match. The targeted correction is: Align the EVI's RT import/export conventions without opening other tenants.
Incorrect Answers
B:BGP-signaled L2VPN routes need distinguishable VPN identifiers so unrelated overlapping customer service advertisements do not collide. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically BGP Layer 2 VPN route distinguisher. BGP-signaled L2VPN routes need distinguishable VPN identifiers so unrelated overlapping customer service advertisements do not collide. In this scenario, however, the distinguishing issue is EVPN BGP route target not imported and the confirming observation is: The EVI imports only its authorized remote MAC reachability when RT settings match.
C:EVPN multihoming uses designated forwarder selection to prevent duplicate BUM forwarding to a shared Ethernet segment. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically EVPN designated forwarder election. EVPN multihoming uses designated forwarder selection to prevent duplicate BUM forwarding to a shared Ethernet segment. In this scenario, however, the distinguishing issue is EVPN BGP route target not imported and the confirming observation is: The EVI imports only its authorized remote MAC reachability when RT settings match.
D:A pseudowire control word adds context or sequence fields in supported encapsulations, so endpoints must interpret a compatible format. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically Pseudowire control-word handling. A pseudowire control word adds context or sequence fields in supported encapsulations, so endpoints must interpret a compatible format. In this scenario, however, the distinguishing issue is EVPN BGP route target not imported and the confirming observation is: The EVI imports only its authorized remote MAC reachability when RT settings match.
Question 958
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: A new PE receives EVPN advertisements from its reflector but the intended EVI does not contain any remote MAC entries. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Distinct RDs preserve separate advertisements and only correct tenant membership is imported.
- The EVI imports only its authorized remote MAC reachability when RT settings match.
- Remote PEs import the appropriate Ethernet AD signaling and react correctly when one PE withdraws its segment reachability.
- Only the elected eligible DF forwards the relevant BUM traffic toward the dual-homed site.
Explanation
Correct Answer
B:The EVI imports only its authorized remote MAC reachability when RT settings match. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: BGP EVPN route receipt and local service membership are separate; route targets control eligible imports.
Incorrect Answers
A:Distinct RDs preserve separate advertisements and only correct tenant membership is imported. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically BGP Layer 2 VPN route distinguisher. BGP-signaled L2VPN routes need distinguishable VPN identifiers so unrelated overlapping customer service advertisements do not collide. In this scenario, however, the distinguishing issue is EVPN BGP route target not imported and the confirming observation is: The EVI imports only its authorized remote MAC reachability when RT settings match.
C:Remote PEs import the appropriate Ethernet AD signaling and react correctly when one PE withdraws its segment reachability. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically EVPN Ethernet AD signaling. Ethernet AD routes help distribute EVPN segment reachability and can support multihoming convergence mechanisms. In this scenario, however, the distinguishing issue is EVPN BGP route target not imported and the confirming observation is: The EVI imports only its authorized remote MAC reachability when RT settings match.
D:Only the elected eligible DF forwards the relevant BUM traffic toward the dual-homed site. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically EVPN designated forwarder election. EVPN multihoming uses designated forwarder selection to prevent duplicate BUM forwarding to a shared Ethernet segment. In this scenario, however, the distinguishing issue is EVPN BGP route target not imported and the confirming observation is: The EVI imports only its authorized remote MAC reachability when RT settings match.
Question 959
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: A new PE receives EVPN advertisements from its reflector but the intended EVI does not contain any remote MAC entries. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Assign unique appropriate service RDs and verify per-tenant RT imports.
- Evaluate EVPN where supported against the operator's explicit scale and redundancy goals.
- Align the EVI's RT import/export conventions without opening other tenants.
- Restore correct type 3 advertisement and service membership signaling.
Explanation
Correct Answer
C:Align the EVI's RT import/export conventions without opening other tenants. The change addresses the root behavior described here: BGP EVPN route receipt and local service membership are separate; route targets control eligible imports. Verify success with: The EVI imports only its authorized remote MAC reachability when RT settings match.
Incorrect Answers
A:Assign unique appropriate service RDs and verify per-tenant RT imports. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically BGP Layer 2 VPN route distinguisher. BGP-signaled L2VPN routes need distinguishable VPN identifiers so unrelated overlapping customer service advertisements do not collide. In this scenario, however, the distinguishing issue is EVPN BGP route target not imported and the confirming observation is: The EVI imports only its authorized remote MAC reachability when RT settings match.
B:Evaluate EVPN where supported against the operator's explicit scale and redundancy goals. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically EVPN versus traditional VPLS scaling. EVPN offers a BGP control-plane model for MAC reachability that can reduce some flood-and-learn limitations and improve multihoming control. In this scenario, however, the distinguishing issue is EVPN BGP route target not imported and the confirming observation is: The EVI imports only its authorized remote MAC reachability when RT settings match.
D:Restore correct type 3 advertisement and service membership signaling. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically EVPN inclusive multicast route. EVPN type 3 advertisements can establish participants in broadcast, unknown-unicast and multicast replication for an EVI. In this scenario, however, the distinguishing issue is EVPN BGP route target not imported and the confirming observation is: The EVI imports only its authorized remote MAC reachability when RT settings match.
Question 960
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: A new PE receives EVPN advertisements from its reflector but the intended EVI does not contain any remote MAC entries. Which operational control would best prevent a recurrence of this exact failure mode?
- Audit VPN identifiers before consolidating L2VPN routes on shared reflectors.
- Test failover with previously learned MACs rather than only unknown destination frames.
- Track control-plane MAC routes alongside local bridge-table entries.
- Run per-EVI negative and positive import checks during onboarding.
Explanation
Correct Answer
D:Run per-EVI negative and positive import checks during onboarding. The control limits repetition of the described root condition: BGP EVPN route receipt and local service membership are separate; route targets control eligible imports. During audits, confirm: The EVI imports only its authorized remote MAC reachability when RT settings match.
Incorrect Answers
A:Audit VPN identifiers before consolidating L2VPN routes on shared reflectors. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically BGP Layer 2 VPN route distinguisher. BGP-signaled L2VPN routes need distinguishable VPN identifiers so unrelated overlapping customer service advertisements do not collide. In this scenario, however, the distinguishing issue is EVPN BGP route target not imported and the confirming observation is: The EVI imports only its authorized remote MAC reachability when RT settings match.
B:Test failover with previously learned MACs rather than only unknown destination frames. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically VPLS MAC withdrawal timing. VPLS forwarding uses learned MAC entries; stale bindings may persist until aging or explicit flush removes them. In this scenario, however, the distinguishing issue is EVPN BGP route target not imported and the confirming observation is: The EVI imports only its authorized remote MAC reachability when RT settings match.
C:Track control-plane MAC routes alongside local bridge-table entries. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically EVPN MAC reachability signaling. EVPN can distribute learned customer MAC reachability through BGP control-plane type 2 routes instead of relying only on data-plane flooding. In this scenario, however, the distinguishing issue is EVPN BGP route target not imported and the confirming observation is: The EVI imports only its authorized remote MAC reachability when RT settings match.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests