Question 890
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: Two sites in the same BGP-signaled L2VPN were provisioned with identical site identifiers and the service fails to map remote connections predictably. Which operational control would best prevent a recurrence of this exact failure mode?
- Alert on oscillating MAC addresses that exceed planned mobility behavior.
- Maintain a per-VPN site-ID allocation register.
- Use positive and negative RT import tests for each new Layer 2 VPN tenant.
- Test PE failure recovery with live MAC entries, not only a ping to the surviving PE.
Explanation
Correct Answer
B:Maintain a per-VPN site-ID allocation register. The control limits repetition of the described root condition: BGP L2VPN site identifiers help map distinct site attachments into the signaled service topology. During audits, confirm: Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
Incorrect Answers
A:Alert on oscillating MAC addresses that exceed planned mobility behavior. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically EVPN duplicate MAC protection. Repeated conflicting MAC advertisements can indicate duplicate endpoint identity rather than valid sequential migration. In this scenario, however, the distinguishing issue is BGP L2VPN site ID collision and the confirming observation is: Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
C:Use positive and negative RT import tests for each new Layer 2 VPN tenant. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically BGP L2VPN route target mismatch. Route targets control membership and distribution of BGP-based L2VPN service advertisements. In this scenario, however, the distinguishing issue is BGP L2VPN site ID collision and the confirming observation is: Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
D:Test PE failure recovery with live MAC entries, not only a ping to the surviving PE. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically EVPN multihoming mass withdrawal. EVPN multihoming can signal a PE or segment failure so remote PEs quickly invalidate affected MAC reachability. In this scenario, however, the distinguishing issue is BGP L2VPN site ID collision and the confirming observation is: Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
Question 891
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: A VPLS tenant reports high core bandwidth after many destination MACs age out and frames are repeatedly flooded to all participating sites. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect EVI service type and ingress/egress VLAN normalization or translation settings.
- Inspect EVPN type 3 inclusive multicast route exchange and associated flooding membership.
- Inspect VPLS MAC learning tables, aging and broadcast/unknown-unicast flood counters.
- Inspect customer attachment loops, MAC-flap counters and VPLS flood replication rates.
Explanation
Correct Answer
C:Inspect VPLS MAC learning tables, aging and broadcast/unknown-unicast flood counters. This check examines the decisive condition for VPLS flooding unknown unicast before any unrelated changes are made. The underlying mechanism is: VPLS provides multipoint Ethernet bridging, so traffic to unknown MAC addresses can be flooded within the VPN forwarding domain. The confirming observation is: MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site.
Incorrect Answers
A:Inspect EVI service type and ingress/egress VLAN normalization or translation settings. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically VLAN normalization mismatch. EVPN can separate local VLAN identifiers from a shared service identity when correct translation and normalization are configured. In this scenario, however, the distinguishing issue is VPLS flooding unknown unicast and the confirming observation is: MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site.
B:Inspect EVPN type 3 inclusive multicast route exchange and associated flooding membership. This is a plausible diagnostic check 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 VPLS flooding unknown unicast and the confirming observation is: MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site.
D:Inspect customer attachment loops, MAC-flap counters and VPLS flood replication rates. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically VPLS root cause of broadcast storm. An uncontrolled customer Layer 2 loop can amplify flooding throughout a multipoint virtual bridge. In this scenario, however, the distinguishing issue is VPLS flooding unknown unicast and the confirming observation is: MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site.
Question 892
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: A VPLS tenant reports high core bandwidth after many destination MACs age out and frames are repeatedly flooded to all participating sites. Which routing or service mechanism best explains the reported behavior?
- EVPN can separate local VLAN identifiers from a shared service identity when correct translation and normalization are configured.
- EVPN type 3 advertisements can establish participants in broadcast, unknown-unicast and multicast replication for an EVI.
- An uncontrolled customer Layer 2 loop can amplify flooding throughout a multipoint virtual bridge.
- VPLS provides multipoint Ethernet bridging, so traffic to unknown MAC addresses can be flooded within the VPN forwarding domain.
Explanation
Correct Answer
D:VPLS provides multipoint Ethernet bridging, so traffic to unknown MAC addresses can be flooded within the VPN forwarding domain. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site. The targeted correction is: Fix MAC learning or excessive churn rather than disabling legitimate service discovery broadly.
Incorrect Answers
A:EVPN can separate local VLAN identifiers from a shared service identity when correct translation and normalization are configured. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically VLAN normalization mismatch. EVPN can separate local VLAN identifiers from a shared service identity when correct translation and normalization are configured. In this scenario, however, the distinguishing issue is VPLS flooding unknown unicast and the confirming observation is: MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site.
B:EVPN type 3 advertisements can establish participants in broadcast, unknown-unicast and multicast replication for an EVI. This is a plausible protocol explanation 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 VPLS flooding unknown unicast and the confirming observation is: MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site.
C:An uncontrolled customer Layer 2 loop can amplify flooding throughout a multipoint virtual bridge. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically VPLS root cause of broadcast storm. An uncontrolled customer Layer 2 loop can amplify flooding throughout a multipoint virtual bridge. In this scenario, however, the distinguishing issue is VPLS flooding unknown unicast and the confirming observation is: MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site.
Question 893
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: A VPLS tenant reports high core bandwidth after many destination MACs age out and frames are repeatedly flooded to all participating sites. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site.
- Test frames from each local VLAN appear only on the intended counterpart service at the remote site.
- Broadcast replication returns to normal after the customer loop is isolated or protected.
- Each authorized PE appears in the replication set and controlled BUM test traffic reaches the intended sites.
Explanation
Correct Answer
A:MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: VPLS provides multipoint Ethernet bridging, so traffic to unknown MAC addresses can be flooded within the VPN forwarding domain.
Incorrect Answers
B:Test frames from each local VLAN appear only on the intended counterpart service at the remote site. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically VLAN normalization mismatch. EVPN can separate local VLAN identifiers from a shared service identity when correct translation and normalization are configured. In this scenario, however, the distinguishing issue is VPLS flooding unknown unicast and the confirming observation is: MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site.
C:Broadcast replication returns to normal after the customer loop is isolated or protected. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically VPLS root cause of broadcast storm. An uncontrolled customer Layer 2 loop can amplify flooding throughout a multipoint virtual bridge. In this scenario, however, the distinguishing issue is VPLS flooding unknown unicast and the confirming observation is: MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site.
D:Each authorized PE appears in the replication set and controlled BUM test traffic reaches the intended sites. This is a plausible observed evidence 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 VPLS flooding unknown unicast and the confirming observation is: MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site.
Question 894
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: A VPLS tenant reports high core bandwidth after many destination MACs age out and frames are repeatedly flooded to all participating sites. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Apply supported VLAN translation or consistent VLAN-based service mapping across sites.
- Fix MAC learning or excessive churn rather than disabling legitimate service discovery broadly.
- Enforce customer loop controls and supported storm-control limits at the PE edge.
- Restore correct type 3 advertisement and service membership signaling.
Explanation
Correct Answer
B:Fix MAC learning or excessive churn rather than disabling legitimate service discovery broadly. The change addresses the root behavior described here: VPLS provides multipoint Ethernet bridging, so traffic to unknown MAC addresses can be flooded within the VPN forwarding domain. Verify success with: MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site.
Incorrect Answers
A:Apply supported VLAN translation or consistent VLAN-based service mapping across sites. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically VLAN normalization mismatch. EVPN can separate local VLAN identifiers from a shared service identity when correct translation and normalization are configured. In this scenario, however, the distinguishing issue is VPLS flooding unknown unicast and the confirming observation is: MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site.
C:Enforce customer loop controls and supported storm-control limits at the PE edge. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically VPLS root cause of broadcast storm. An uncontrolled customer Layer 2 loop can amplify flooding throughout a multipoint virtual bridge. In this scenario, however, the distinguishing issue is VPLS flooding unknown unicast and the confirming observation is: MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site.
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 VPLS flooding unknown unicast and the confirming observation is: MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site.
Question 895
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: A VPLS tenant reports high core bandwidth after many destination MACs age out and frames are repeatedly flooded to all participating sites. Which operational control would best prevent a recurrence of this exact failure mode?
- Maintain a site-VLAN-to-EVI mapping table and test isolation after adding services.
- Require a loop-free attachment design before adding redundant customer trunks.
- Track MAC churn and unknown-unicast levels separately from ordinary broadcast traffic.
- Require both service label and transport label checks before declaring a pseudowire active.
Explanation
Correct Answer
C:Track MAC churn and unknown-unicast levels separately from ordinary broadcast traffic. The control limits repetition of the described root condition: VPLS provides multipoint Ethernet bridging, so traffic to unknown MAC addresses can be flooded within the VPN forwarding domain. During audits, confirm: MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site.
Incorrect Answers
A:Maintain a site-VLAN-to-EVI mapping table and test isolation after adding services. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically VLAN normalization mismatch. EVPN can separate local VLAN identifiers from a shared service identity when correct translation and normalization are configured. In this scenario, however, the distinguishing issue is VPLS flooding unknown unicast and the confirming observation is: MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site.
B:Require a loop-free attachment design before adding redundant customer trunks. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically VPLS root cause of broadcast storm. An uncontrolled customer Layer 2 loop can amplify flooding throughout a multipoint virtual bridge. In this scenario, however, the distinguishing issue is VPLS flooding unknown unicast and the confirming observation is: MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site.
D:Require both service label and transport label checks before declaring a pseudowire active. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically Pseudowire transport unreachable. Pseudowire service labels identify the circuit, while a separate MPLS transport path carries the traffic to the remote PE. In this scenario, however, the distinguishing issue is VPLS flooding unknown unicast and the confirming observation is: MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site.
Question 896
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A customer bridges two sites through parallel VPLS paths and the same MAC address oscillates rapidly between remote attachments. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect duplicate MAC detection and mobility events before assuming a legitimate workload move.
- Inspect local and remote site IDs and the BGP L2VPN route connection mapping.
- Inspect newer EVPN MAC/IP route sequence and withdrawal of stale reachability.
- Inspect VPLS MAC move history and physical loop or dual-attachment behavior.
Explanation
Correct Answer
D:Inspect VPLS MAC move history and physical loop or dual-attachment behavior. This check examines the decisive condition for VPLS MAC move instability before any unrelated changes are made. The underlying mechanism is: Multipoint Layer 2 forwarding can become unstable when the same source MAC appears alternately from multiple ports or pseudowires. The confirming observation is: The customer MAC learns on the expected attachment without repeated moves after loop removal.
Incorrect Answers
A:Inspect duplicate MAC detection and mobility events before assuming a legitimate workload move. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically EVPN duplicate MAC protection. Repeated conflicting MAC advertisements can indicate duplicate endpoint identity rather than valid sequential migration. In this scenario, however, the distinguishing issue is VPLS MAC move instability and the confirming observation is: The customer MAC learns on the expected attachment without repeated moves after loop removal.
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 VPLS MAC move instability and the confirming observation is: The customer MAC learns on the expected attachment without repeated moves after loop removal.
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 VPLS MAC move instability and the confirming observation is: The customer MAC learns on the expected attachment without repeated moves after loop removal.
Question 897
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: A customer bridges two sites through parallel VPLS paths and the same MAC address oscillates rapidly between remote attachments. Which routing or service mechanism best explains the reported behavior?
- Multipoint Layer 2 forwarding can become unstable when the same source MAC appears alternately from multiple ports or pseudowires.
- Repeated conflicting MAC advertisements can indicate duplicate endpoint identity rather than valid sequential migration.
- BGP L2VPN site identifiers help map distinct site attachments into the signaled service topology.
- EVPN MAC mobility procedures identify the newer location of a moving MAC and help remote PEs replace old forwarding state.
Explanation
Correct Answer
A:Multipoint Layer 2 forwarding can become unstable when the same source MAC appears alternately from multiple ports or pseudowires. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The customer MAC learns on the expected attachment without repeated moves after loop removal. The targeted correction is: Correct customer bridging topology or supported dual-homing protections before resetting MAC tables.
Incorrect Answers
B:Repeated conflicting MAC advertisements can indicate duplicate endpoint identity rather than valid sequential migration. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically EVPN duplicate MAC protection. Repeated conflicting MAC advertisements can indicate duplicate endpoint identity rather than valid sequential migration. In this scenario, however, the distinguishing issue is VPLS MAC move instability and the confirming observation is: The customer MAC learns on the expected attachment without repeated moves after loop removal.
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 VPLS MAC move instability and the confirming observation is: The customer MAC learns on the expected attachment without repeated moves after loop removal.
D: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 VPLS MAC move instability and the confirming observation is: The customer MAC learns on the expected attachment without repeated moves after loop removal.
Question 898
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: A customer bridges two sites through parallel VPLS paths and the same MAC address oscillates rapidly between remote attachments. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The duplicate source is corrected and MAC ownership stabilizes on one authorized site.
- The customer MAC learns on the expected attachment without repeated moves after loop removal.
- Each site advertises its planned unique identity and the remote connection mapping is unambiguous.
- Frames retain the correct VLAN bridge-domain scope across remote sites and no cross-VLAN leakage occurs.
Explanation
Correct Answer
B:The customer MAC learns on the expected attachment without repeated moves after loop removal. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Multipoint Layer 2 forwarding can become unstable when the same source MAC appears alternately from multiple ports or pseudowires.
Incorrect Answers
A:The duplicate source is corrected and MAC ownership stabilizes on one authorized site. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically EVPN duplicate MAC protection. Repeated conflicting MAC advertisements can indicate duplicate endpoint identity rather than valid sequential migration. In this scenario, however, the distinguishing issue is VPLS MAC move instability and the confirming observation is: The customer MAC learns on the expected attachment without repeated moves after loop removal.
C: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 VPLS MAC move instability and the confirming observation is: The customer MAC learns on the expected attachment without repeated moves after loop removal.
D:Frames retain the correct VLAN bridge-domain scope across remote sites and no cross-VLAN leakage occurs. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically EVPN VLAN-aware bundle isolation. A VLAN-aware EVPN design retains separation of customer broadcast domains even when sharing an EVI framework. In this scenario, however, the distinguishing issue is VPLS MAC move instability and the confirming observation is: The customer MAC learns on the expected attachment without repeated moves after loop removal.
Question 899
During a core-routing migration rehearsal, an HPE Juniper Networking engineer investigates this situation: A customer bridges two sites through parallel VPLS paths and the same MAC address oscillates rapidly between remote attachments. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Resolve the duplicate MAC condition and use supported detection or suppression controls.
- Assign unique service site IDs and align site ranges according to the intended topology.
- Correct customer bridging topology or supported dual-homing protections before resetting MAC tables.
- Correct VLAN-aware bundle mapping and bridge-domain membership.
Explanation
Correct Answer
C:Correct customer bridging topology or supported dual-homing protections before resetting MAC tables. The change addresses the root behavior described here: Multipoint Layer 2 forwarding can become unstable when the same source MAC appears alternately from multiple ports or pseudowires. Verify success with: The customer MAC learns on the expected attachment without repeated moves after loop removal.
Incorrect Answers
A:Resolve the duplicate MAC condition and use supported detection or suppression controls. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically EVPN duplicate MAC protection. Repeated conflicting MAC advertisements can indicate duplicate endpoint identity rather than valid sequential migration. In this scenario, however, the distinguishing issue is VPLS MAC move instability and the confirming observation is: The customer MAC learns on the expected attachment without repeated moves after loop removal.
B: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 VPLS MAC move instability and the confirming observation is: The customer MAC learns on the expected attachment without repeated moves after loop removal.
D:Correct VLAN-aware bundle mapping and bridge-domain membership. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically EVPN VLAN-aware bundle isolation. A VLAN-aware EVPN design retains separation of customer broadcast domains even when sharing an EVI framework. In this scenario, however, the distinguishing issue is VPLS MAC move instability and the confirming observation is: The customer MAC learns on the expected attachment without repeated moves after loop removal.
Question 900
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: A customer bridges two sites through parallel VPLS paths and the same MAC address oscillates rapidly between remote attachments. Which operational control would best prevent a recurrence of this exact failure mode?
- Alert on oscillating MAC addresses that exceed planned mobility behavior.
- Maintain a per-VPN site-ID allocation register.
- Maintain a site-VLAN-to-EVI mapping table and test isolation after adding services.
- Alert on rapid MAC moves and validate redundant CPE topology.
Explanation
Correct Answer
D:Alert on rapid MAC moves and validate redundant CPE topology. The control limits repetition of the described root condition: Multipoint Layer 2 forwarding can become unstable when the same source MAC appears alternately from multiple ports or pseudowires. During audits, confirm: The customer MAC learns on the expected attachment without repeated moves after loop removal.
Incorrect Answers
A:Alert on oscillating MAC addresses that exceed planned mobility behavior. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically EVPN duplicate MAC protection. Repeated conflicting MAC advertisements can indicate duplicate endpoint identity rather than valid sequential migration. In this scenario, however, the distinguishing issue is VPLS MAC move instability and the confirming observation is: The customer MAC learns on the expected attachment without repeated moves after loop removal.
B: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 VPLS MAC move instability and the confirming observation is: The customer MAC learns on the expected attachment without repeated moves after loop removal.
C:Maintain a site-VLAN-to-EVI mapping table and test isolation after adding services. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically VLAN normalization mismatch. EVPN can separate local VLAN identifiers from a shared service identity when correct translation and normalization are configured. In this scenario, however, the distinguishing issue is VPLS MAC move instability and the confirming observation is: The customer MAC learns on the expected attachment without repeated moves after loop removal.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests