Question 970
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: Two EVPN participating sites use different local VLAN IDs for the same customer service and frames are unexpectedly dropped or leaked. Which operational control would best prevent a recurrence of this exact failure mode?
- Track MAC churn and unknown-unicast levels separately from ordinary broadcast traffic.
- Maintain a site-VLAN-to-EVI mapping table and test isolation after adding services.
- Fail over the DF during testing and check for duplicate frames or blackholes.
- Alert on oscillating MAC addresses that exceed planned mobility behavior.
Explanation
Correct Answer
B:Maintain a site-VLAN-to-EVI mapping table and test isolation after adding services. The control limits repetition of the described root condition: EVPN can separate local VLAN identifiers from a shared service identity when correct translation and normalization are configured. During audits, confirm: Test frames from each local VLAN appear only on the intended counterpart service at the remote site.
Incorrect Answers
A: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 VLAN normalization mismatch and the confirming observation is: Test frames from each local VLAN appear only on the intended counterpart service at the remote site.
C:Fail over the DF during testing and check for duplicate frames or blackholes. This is a plausible preventive practice 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 VLAN normalization mismatch and the confirming observation is: Test frames from each local VLAN appear only on the intended counterpart service at the remote site.
D: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 VLAN normalization mismatch and the confirming observation is: Test frames from each local VLAN appear only on the intended counterpart service at the remote site.
Question 971
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: An operator places several VLANs into one EVPN bundle and accidentally bridges traffic between VLANs that should remain separate. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect VPLS MAC move history and physical loop or dual-attachment behavior.
- Inspect split-horizon forwarding treatment for traffic received from VPLS pseudowires.
- Inspect EVPN VLAN-aware service configuration and per-VLAN bridge-domain identity.
- Inspect targeted LDP hello and TCP session status between the pseudowire endpoints.
Explanation
Correct Answer
C:Inspect EVPN VLAN-aware service configuration and per-VLAN bridge-domain identity. This check examines the decisive condition for EVPN VLAN-aware bundle isolation before any unrelated changes are made. The underlying mechanism is: A VLAN-aware EVPN design retains separation of customer broadcast domains even when sharing an EVI framework. The confirming observation is: Frames retain the correct VLAN bridge-domain scope across remote sites and no cross-VLAN leakage occurs.
Incorrect Answers
A:Inspect VPLS MAC move history and physical loop or dual-attachment behavior. This is a plausible diagnostic check 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 VLAN-aware bundle isolation and the confirming observation is: Frames retain the correct VLAN bridge-domain scope across remote sites and no cross-VLAN leakage occurs.
B:Inspect split-horizon forwarding treatment for traffic received from VPLS pseudowires. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically VPLS split-horizon protection. VPLS needs loop-prevention controls such as split-horizon behavior when forwarding between remote pseudowires. In this scenario, however, the distinguishing issue is EVPN VLAN-aware bundle isolation and the confirming observation is: Frames retain the correct VLAN bridge-domain scope across remote sites and no cross-VLAN leakage occurs.
D:Inspect targeted LDP hello and TCP session status between the pseudowire endpoints. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically Targeted LDP session absent. Remote LDP-signaled pseudowires require an appropriate targeted control session in addition to core label transport. In this scenario, however, the distinguishing issue is EVPN VLAN-aware bundle isolation and the confirming observation is: Frames retain the correct VLAN bridge-domain scope across remote sites and no cross-VLAN leakage occurs.
Question 972
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: An operator places several VLANs into one EVPN bundle and accidentally bridges traffic between VLANs that should remain separate. 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.
- VPLS needs loop-prevention controls such as split-horizon behavior when forwarding between remote pseudowires.
- Remote LDP-signaled pseudowires require an appropriate targeted control session in addition to core label transport.
- A VLAN-aware EVPN design retains separation of customer broadcast domains even when sharing an EVI framework.
Explanation
Correct Answer
D:A VLAN-aware EVPN design retains separation of customer broadcast domains even when sharing an EVI framework. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Frames retain the correct VLAN bridge-domain scope across remote sites and no cross-VLAN leakage occurs. The targeted correction is: Correct VLAN-aware bundle mapping and bridge-domain membership.
Incorrect Answers
A:Multipoint Layer 2 forwarding can become unstable when the same source MAC appears alternately from multiple ports or pseudowires. This is a plausible protocol explanation 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 VLAN-aware bundle isolation and the confirming observation is: Frames retain the correct VLAN bridge-domain scope across remote sites and no cross-VLAN leakage occurs.
B:VPLS needs loop-prevention controls such as split-horizon behavior when forwarding between remote pseudowires. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically VPLS split-horizon protection. VPLS needs loop-prevention controls such as split-horizon behavior when forwarding between remote pseudowires. In this scenario, however, the distinguishing issue is EVPN VLAN-aware bundle isolation and the confirming observation is: Frames retain the correct VLAN bridge-domain scope across remote sites and no cross-VLAN leakage occurs.
C:Remote LDP-signaled pseudowires require an appropriate targeted control session in addition to core label transport. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically Targeted LDP session absent. Remote LDP-signaled pseudowires require an appropriate targeted control session in addition to core label transport. In this scenario, however, the distinguishing issue is EVPN VLAN-aware bundle isolation and the confirming observation is: Frames retain the correct VLAN bridge-domain scope across remote sites and no cross-VLAN leakage occurs.
Question 973
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: An operator places several VLANs into one EVPN bundle and accidentally bridges traffic between VLANs that should remain separate. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Frames retain the correct VLAN bridge-domain scope across remote sites and no cross-VLAN leakage occurs.
- Test frames cross the intended CE attachments once without repeated amplification.
- The customer MAC learns on the expected attachment without repeated moves after loop removal.
- The remote PE LDP session is established and exchanges the service label for the circuit.
Explanation
Correct Answer
A:Frames retain the correct VLAN bridge-domain scope across remote sites and no cross-VLAN leakage occurs. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: A VLAN-aware EVPN design retains separation of customer broadcast domains even when sharing an EVI framework.
Incorrect Answers
B:Test frames cross the intended CE attachments once without repeated amplification. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically VPLS split-horizon protection. VPLS needs loop-prevention controls such as split-horizon behavior when forwarding between remote pseudowires. In this scenario, however, the distinguishing issue is EVPN VLAN-aware bundle isolation and the confirming observation is: Frames retain the correct VLAN bridge-domain scope across remote sites and no cross-VLAN leakage occurs.
C:The customer MAC learns on the expected attachment without repeated moves after loop removal. This is a plausible observed evidence 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 VLAN-aware bundle isolation and the confirming observation is: Frames retain the correct VLAN bridge-domain scope across remote sites and no cross-VLAN leakage occurs.
D:The remote PE LDP session is established and exchanges the service label for the circuit. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically Targeted LDP session absent. Remote LDP-signaled pseudowires require an appropriate targeted control session in addition to core label transport. In this scenario, however, the distinguishing issue is EVPN VLAN-aware bundle isolation and the confirming observation is: Frames retain the correct VLAN bridge-domain scope across remote sites and no cross-VLAN leakage occurs.
Question 974
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: An operator places several VLANs into one EVPN bundle and accidentally bridges traffic between VLANs that should remain separate. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Correct customer bridging topology or supported dual-homing protections before resetting MAC tables.
- Correct VLAN-aware bundle mapping and bridge-domain membership.
- Restore the supported VPLS split-horizon or equivalent loop-free topology behavior.
- Restore bidirectional loopback reachability and supported targeted LDP configuration.
Explanation
Correct Answer
B:Correct VLAN-aware bundle mapping and bridge-domain membership. The change addresses the root behavior described here: A VLAN-aware EVPN design retains separation of customer broadcast domains even when sharing an EVI framework. Verify success with: Frames retain the correct VLAN bridge-domain scope across remote sites and no cross-VLAN leakage occurs.
Incorrect Answers
A:Correct customer bridging topology or supported dual-homing protections before resetting MAC tables. This is a plausible configuration or operational fix 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 VLAN-aware bundle isolation and the confirming observation is: Frames retain the correct VLAN bridge-domain scope across remote sites and no cross-VLAN leakage occurs.
C:Restore the supported VPLS split-horizon or equivalent loop-free topology behavior. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically VPLS split-horizon protection. VPLS needs loop-prevention controls such as split-horizon behavior when forwarding between remote pseudowires. In this scenario, however, the distinguishing issue is EVPN VLAN-aware bundle isolation and the confirming observation is: Frames retain the correct VLAN bridge-domain scope across remote sites and no cross-VLAN leakage occurs.
D:Restore bidirectional loopback reachability and supported targeted LDP configuration. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically Targeted LDP session absent. Remote LDP-signaled pseudowires require an appropriate targeted control session in addition to core label transport. In this scenario, however, the distinguishing issue is EVPN VLAN-aware bundle isolation and the confirming observation is: Frames retain the correct VLAN bridge-domain scope across remote sites and no cross-VLAN leakage occurs.
Question 975
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: An operator places several VLANs into one EVPN bundle and accidentally bridges traffic between VLANs that should remain separate. Which operational control would best prevent a recurrence of this exact failure mode?
- Alert on rapid MAC moves and validate redundant CPE topology.
- Test broadcast storm containment before admitting additional VPLS PEs.
- Test negative connectivity across VLAN IDs after EVPN service changes.
- Track transport LSP reachability separately from targeted pseudowire signaling.
Explanation
Correct Answer
C:Test negative connectivity across VLAN IDs after EVPN service changes. The control limits repetition of the described root condition: A VLAN-aware EVPN design retains separation of customer broadcast domains even when sharing an EVI framework. During audits, confirm: Frames retain the correct VLAN bridge-domain scope across remote sites and no cross-VLAN leakage occurs.
Incorrect Answers
A: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 VLAN-aware bundle isolation and the confirming observation is: Frames retain the correct VLAN bridge-domain scope across remote sites and no cross-VLAN leakage occurs.
B:Test broadcast storm containment before admitting additional VPLS PEs. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically VPLS split-horizon protection. VPLS needs loop-prevention controls such as split-horizon behavior when forwarding between remote pseudowires. In this scenario, however, the distinguishing issue is EVPN VLAN-aware bundle isolation and the confirming observation is: Frames retain the correct VLAN bridge-domain scope across remote sites and no cross-VLAN leakage occurs.
D:Track transport LSP reachability separately from targeted pseudowire signaling. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically Targeted LDP session absent. Remote LDP-signaled pseudowires require an appropriate targeted control session in addition to core label transport. In this scenario, however, the distinguishing issue is EVPN VLAN-aware bundle isolation and the confirming observation is: Frames retain the correct VLAN bridge-domain scope across remote sites and no cross-VLAN leakage occurs.
Question 976
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A pseudowire itself is up, but local customer traffic never enters it because CE frames arrive on a logical unit not attached to the service instance. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect egress service label-to-circuit association independently of the outer transport label.
- Compare the virtual circuit identifier and encapsulation expected on both pseudowire endpoints.
- Inspect split-horizon forwarding treatment for traffic received from VPLS pseudowires.
- Compare ingress VLAN unit counters and the specific L2VPN instance's attachment configuration.
Explanation
Correct Answer
D:Compare ingress VLAN unit counters and the specific L2VPN instance's attachment configuration. This check examines the decisive condition for L2VPN attachment interface wrong unit before any unrelated changes are made. The underlying mechanism is: A signaled pseudowire only carries CE frames that enter its actual local attachment circuit. The confirming observation is: Packet counters on the intended unit and pseudowire both increase for a test frame.
Incorrect Answers
A:Inspect egress service label-to-circuit association independently of the outer transport label. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically L2VPN service-label swapped. The inner pseudowire service label identifies the Layer 2 circuit, while the outer MPLS label identifies transport. In this scenario, however, the distinguishing issue is L2VPN attachment interface wrong unit and the confirming observation is: Packet counters on the intended unit and pseudowire both increase for a test frame.
B:Compare the virtual circuit identifier and encapsulation expected on both pseudowire endpoints. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically LDP pseudowire VC ID mismatch. An LDP-signaled point-to-point Layer 2 circuit needs compatible pseudowire identity and service parameters on both PEs. In this scenario, however, the distinguishing issue is L2VPN attachment interface wrong unit and the confirming observation is: Packet counters on the intended unit and pseudowire both increase for a test frame.
C:Inspect split-horizon forwarding treatment for traffic received from VPLS pseudowires. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically VPLS split-horizon protection. VPLS needs loop-prevention controls such as split-horizon behavior when forwarding between remote pseudowires. In this scenario, however, the distinguishing issue is L2VPN attachment interface wrong unit and the confirming observation is: Packet counters on the intended unit and pseudowire both increase for a test frame.
Question 977
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: A pseudowire itself is up, but local customer traffic never enters it because CE frames arrive on a logical unit not attached to the service instance. Which routing or service mechanism best explains the reported behavior?
- A signaled pseudowire only carries CE frames that enter its actual local attachment circuit.
- The inner pseudowire service label identifies the Layer 2 circuit, while the outer MPLS label identifies transport.
- VPLS needs loop-prevention controls such as split-horizon behavior when forwarding between remote pseudowires.
- An LDP pseudowire requires valid label bindings for its service, separate from availability of the transport LSP.
Explanation
Correct Answer
A:A signaled pseudowire only carries CE frames that enter its actual local attachment circuit. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Packet counters on the intended unit and pseudowire both increase for a test frame. The targeted correction is: Bind the correct VLAN logical unit or service interface to the L2VPN instance.
Incorrect Answers
B:The inner pseudowire service label identifies the Layer 2 circuit, while the outer MPLS label identifies transport. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically L2VPN service-label swapped. The inner pseudowire service label identifies the Layer 2 circuit, while the outer MPLS label identifies transport. In this scenario, however, the distinguishing issue is L2VPN attachment interface wrong unit and the confirming observation is: Packet counters on the intended unit and pseudowire both increase for a test frame.
C:VPLS needs loop-prevention controls such as split-horizon behavior when forwarding between remote pseudowires. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically VPLS split-horizon protection. VPLS needs loop-prevention controls such as split-horizon behavior when forwarding between remote pseudowires. In this scenario, however, the distinguishing issue is L2VPN attachment interface wrong unit and the confirming observation is: Packet counters on the intended unit and pseudowire both increase for a test frame.
D:An LDP pseudowire requires valid label bindings for its service, separate from availability of the transport LSP. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically LDP pseudowire label withdrawal. An LDP pseudowire requires valid label bindings for its service, separate from availability of the transport LSP. In this scenario, however, the distinguishing issue is L2VPN attachment interface wrong unit and the confirming observation is: Packet counters on the intended unit and pseudowire both increase for a test frame.
Question 978
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: A pseudowire itself is up, but local customer traffic never enters it because CE frames arrive on a logical unit not attached to the service instance. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The destination PE maps the incoming service label to the intended customer attachment.
- Packet counters on the intended unit and pseudowire both increase for a test frame.
- Both endpoints show the expected circuit ID and an up data plane after matching configuration.
- Test frames cross the intended CE attachments once without repeated amplification.
Explanation
Correct Answer
B:Packet counters on the intended unit and pseudowire both increase for a test frame. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: A signaled pseudowire only carries CE frames that enter its actual local attachment circuit.
Incorrect Answers
A:The destination PE maps the incoming service label to the intended customer attachment. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically L2VPN service-label swapped. The inner pseudowire service label identifies the Layer 2 circuit, while the outer MPLS label identifies transport. In this scenario, however, the distinguishing issue is L2VPN attachment interface wrong unit and the confirming observation is: Packet counters on the intended unit and pseudowire both increase for a test frame.
C:Both endpoints show the expected circuit ID and an up data plane after matching configuration. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically LDP pseudowire VC ID mismatch. An LDP-signaled point-to-point Layer 2 circuit needs compatible pseudowire identity and service parameters on both PEs. In this scenario, however, the distinguishing issue is L2VPN attachment interface wrong unit and the confirming observation is: Packet counters on the intended unit and pseudowire both increase for a test frame.
D:Test frames cross the intended CE attachments once without repeated amplification. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically VPLS split-horizon protection. VPLS needs loop-prevention controls such as split-horizon behavior when forwarding between remote pseudowires. In this scenario, however, the distinguishing issue is L2VPN attachment interface wrong unit and the confirming observation is: Packet counters on the intended unit and pseudowire both increase for a test frame.
Question 979
During a core-routing migration rehearsal, an HPE Juniper Networking engineer investigates this situation: A pseudowire itself is up, but local customer traffic never enters it because CE frames arrive on a logical unit not attached to the service instance. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Repair the affected service label mapping and circuit signaling instead of changing healthy core IGP paths.
- Align the intended pseudowire VC ID on both ends without changing unrelated circuits.
- Bind the correct VLAN logical unit or service interface to the L2VPN instance.
- Restore the supported VPLS split-horizon or equivalent loop-free topology behavior.
Explanation
Correct Answer
C:Bind the correct VLAN logical unit or service interface to the L2VPN instance. The change addresses the root behavior described here: A signaled pseudowire only carries CE frames that enter its actual local attachment circuit. Verify success with: Packet counters on the intended unit and pseudowire both increase for a test frame.
Incorrect Answers
A:Repair the affected service label mapping and circuit signaling instead of changing healthy core IGP paths. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically L2VPN service-label swapped. The inner pseudowire service label identifies the Layer 2 circuit, while the outer MPLS label identifies transport. In this scenario, however, the distinguishing issue is L2VPN attachment interface wrong unit and the confirming observation is: Packet counters on the intended unit and pseudowire both increase for a test frame.
B:Align the intended pseudowire VC ID on both ends without changing unrelated circuits. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically LDP pseudowire VC ID mismatch. An LDP-signaled point-to-point Layer 2 circuit needs compatible pseudowire identity and service parameters on both PEs. In this scenario, however, the distinguishing issue is L2VPN attachment interface wrong unit and the confirming observation is: Packet counters on the intended unit and pseudowire both increase for a test frame.
D:Restore the supported VPLS split-horizon or equivalent loop-free topology behavior. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically VPLS split-horizon protection. VPLS needs loop-prevention controls such as split-horizon behavior when forwarding between remote pseudowires. In this scenario, however, the distinguishing issue is L2VPN attachment interface wrong unit and the confirming observation is: Packet counters on the intended unit and pseudowire both increase for a test frame.
Question 980
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: A pseudowire itself is up, but local customer traffic never enters it because CE frames arrive on a logical unit not attached to the service instance. Which operational control would best prevent a recurrence of this exact failure mode?
- Include service label disposition checks in multi-tenant label-table audits.
- Use a two-ended pseudowire service record for every provisioned VC.
- Test broadcast storm containment before admitting additional VPLS PEs.
- Cross-check physical port, VLAN tag and logical unit against customer acceptance drawings.
Explanation
Correct Answer
D:Cross-check physical port, VLAN tag and logical unit against customer acceptance drawings. The control limits repetition of the described root condition: A signaled pseudowire only carries CE frames that enter its actual local attachment circuit. During audits, confirm: Packet counters on the intended unit and pseudowire both increase for a test frame.
Incorrect Answers
A:Include service label disposition checks in multi-tenant label-table audits. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically L2VPN service-label swapped. The inner pseudowire service label identifies the Layer 2 circuit, while the outer MPLS label identifies transport. In this scenario, however, the distinguishing issue is L2VPN attachment interface wrong unit and the confirming observation is: Packet counters on the intended unit and pseudowire both increase for a test frame.
B:Use a two-ended pseudowire service record for every provisioned VC. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically LDP pseudowire VC ID mismatch. An LDP-signaled point-to-point Layer 2 circuit needs compatible pseudowire identity and service parameters on both PEs. In this scenario, however, the distinguishing issue is L2VPN attachment interface wrong unit and the confirming observation is: Packet counters on the intended unit and pseudowire both increase for a test frame.
C:Test broadcast storm containment before admitting additional VPLS PEs. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically VPLS split-horizon protection. VPLS needs loop-prevention controls such as split-horizon behavior when forwarding between remote pseudowires. In this scenario, however, the distinguishing issue is L2VPN attachment interface wrong unit and the confirming observation is: Packet counters on the intended unit and pseudowire both increase for a test frame.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests