Question 860
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: An Ethernet pseudowire transitions into an error or down state after one customer link changes its service MTU. Which operational control would best prevent a recurrence of this exact failure mode?
- Qualify every attachment encapsulation before approving mixed-media L2 VPN provisioning.
- Require a loop-free attachment design before adding redundant customer trunks.
- Benchmark control-plane route count, BUM replication and convergence before migration.
- Document L2 service frame-size requirements and test near-MTU frames.
Explanation
Correct Answer
D:Document L2 service frame-size requirements and test near-MTU frames. The control limits repetition of the described root condition: Pseudowire endpoint parameter mismatches can prevent a usable circuit or lead to frame loss even with valid transport. During audits, confirm: Both PEs agree on service MTU and the maximum allowed customer frame crosses successfully.
Incorrect Answers
A:Qualify every attachment encapsulation before approving mixed-media L2 VPN provisioning. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically Layer 2 interworking mismatch. Different Layer 2 attachment encapsulations may require explicit compatible interworking, not an assumption that raw frames are identical. In this scenario, however, the distinguishing issue is Pseudowire MTU mismatch and the confirming observation is: Both PEs agree on service MTU and the maximum allowed customer frame crosses successfully.
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 Pseudowire MTU mismatch and the confirming observation is: Both PEs agree on service MTU and the maximum allowed customer frame crosses successfully.
C:Benchmark control-plane route count, BUM replication and convergence before migration. This is a plausible preventive practice 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 Pseudowire MTU mismatch and the confirming observation is: Both PEs agree on service MTU and the maximum allowed customer frame crosses successfully.
Question 861
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: A provider attempts to connect a frame-relay-style legacy service to an Ethernet attachment over a pseudowire without any compatible interworking treatment. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect attachment circuit type and the pseudowire's configured interworking mode.
- Compare advertised and local pseudowire MTU and encapsulation parameters.
- Compare VPLS MAC control behavior with EVPN BGP MAC signaling and multihoming capabilities.
- Compare remote label mapping and withdraw state against the targeted LDP session.
Explanation
Correct Answer
A:Inspect attachment circuit type and the pseudowire's configured interworking mode. This check examines the decisive condition for Layer 2 interworking mismatch before any unrelated changes are made. The underlying mechanism is: Different Layer 2 attachment encapsulations may require explicit compatible interworking, not an assumption that raw frames are identical. The confirming observation is: The CE-facing frames are correctly interpreted at the remote attachment after supported interworking.
Incorrect Answers
B:Compare advertised and local pseudowire MTU and encapsulation parameters. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically Pseudowire MTU mismatch. Pseudowire endpoint parameter mismatches can prevent a usable circuit or lead to frame loss even with valid transport. In this scenario, however, the distinguishing issue is Layer 2 interworking mismatch and the confirming observation is: The CE-facing frames are correctly interpreted at the remote attachment after supported interworking.
C:Compare VPLS MAC control behavior with EVPN BGP MAC signaling and multihoming capabilities. This is a plausible diagnostic check 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 Layer 2 interworking mismatch and the confirming observation is: The CE-facing frames are correctly interpreted at the remote attachment after supported interworking.
D:Compare remote label mapping and withdraw state against the targeted LDP session. This is a plausible diagnostic check 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 Layer 2 interworking mismatch and the confirming observation is: The CE-facing frames are correctly interpreted at the remote attachment after supported interworking.
Question 862
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A provider attempts to connect a frame-relay-style legacy service to an Ethernet attachment over a pseudowire without any compatible interworking treatment. Which routing or service mechanism best explains the reported behavior?
- Pseudowire endpoint parameter mismatches can prevent a usable circuit or lead to frame loss even with valid transport.
- Different Layer 2 attachment encapsulations may require explicit compatible interworking, not an assumption that raw frames are identical.
- EVPN offers a BGP control-plane model for MAC reachability that can reduce some flood-and-learn limitations and improve multihoming control.
- An LDP pseudowire requires valid label bindings for its service, separate from availability of the transport LSP.
Explanation
Correct Answer
B:Different Layer 2 attachment encapsulations may require explicit compatible interworking, not an assumption that raw frames are identical. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The CE-facing frames are correctly interpreted at the remote attachment after supported interworking. The targeted correction is: Use a supported pseudowire interworking configuration or adapt the service at the boundary.
Incorrect Answers
A:Pseudowire endpoint parameter mismatches can prevent a usable circuit or lead to frame loss even with valid transport. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically Pseudowire MTU mismatch. Pseudowire endpoint parameter mismatches can prevent a usable circuit or lead to frame loss even with valid transport. In this scenario, however, the distinguishing issue is Layer 2 interworking mismatch and the confirming observation is: The CE-facing frames are correctly interpreted at the remote attachment after supported interworking.
C:EVPN offers a BGP control-plane model for MAC reachability that can reduce some flood-and-learn limitations and improve multihoming control. This is a plausible protocol explanation 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 Layer 2 interworking mismatch and the confirming observation is: The CE-facing frames are correctly interpreted at the remote attachment after supported interworking.
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 Layer 2 interworking mismatch and the confirming observation is: The CE-facing frames are correctly interpreted at the remote attachment after supported interworking.
Question 863
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: A provider attempts to connect a frame-relay-style legacy service to an Ethernet attachment over a pseudowire without any compatible interworking treatment. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Both PEs agree on service MTU and the maximum allowed customer frame crosses successfully.
- A pilot shows remote host reachability learned by EVPN route advertisement with bounded BUM flooding.
- The CE-facing frames are correctly interpreted at the remote attachment after supported interworking.
- A fresh valid service label mapping is present before forwarding is restored.
Explanation
Correct Answer
C:The CE-facing frames are correctly interpreted at the remote attachment after supported interworking. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Different Layer 2 attachment encapsulations may require explicit compatible interworking, not an assumption that raw frames are identical.
Incorrect Answers
A:Both PEs agree on service MTU and the maximum allowed customer frame crosses successfully. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically Pseudowire MTU mismatch. Pseudowire endpoint parameter mismatches can prevent a usable circuit or lead to frame loss even with valid transport. In this scenario, however, the distinguishing issue is Layer 2 interworking mismatch and the confirming observation is: The CE-facing frames are correctly interpreted at the remote attachment after supported interworking.
B:A pilot shows remote host reachability learned by EVPN route advertisement with bounded BUM flooding. This is a plausible observed evidence 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 Layer 2 interworking mismatch and the confirming observation is: The CE-facing frames are correctly interpreted at the remote attachment after supported interworking.
D:A fresh valid service label mapping is present before forwarding is restored. This is a plausible observed evidence 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 Layer 2 interworking mismatch and the confirming observation is: The CE-facing frames are correctly interpreted at the remote attachment after supported interworking.
Question 864
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: A provider attempts to connect a frame-relay-style legacy service to an Ethernet attachment over a pseudowire without any compatible interworking treatment. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Align the end-to-end service MTU with core overhead and CE requirements.
- Evaluate EVPN where supported against the operator's explicit scale and redundancy goals.
- Repair the remote service signaling and reestablish the expected VC label state.
- Use a supported pseudowire interworking configuration or adapt the service at the boundary.
Explanation
Correct Answer
D:Use a supported pseudowire interworking configuration or adapt the service at the boundary. The change addresses the root behavior described here: Different Layer 2 attachment encapsulations may require explicit compatible interworking, not an assumption that raw frames are identical. Verify success with: The CE-facing frames are correctly interpreted at the remote attachment after supported interworking.
Incorrect Answers
A:Align the end-to-end service MTU with core overhead and CE requirements. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically Pseudowire MTU mismatch. Pseudowire endpoint parameter mismatches can prevent a usable circuit or lead to frame loss even with valid transport. In this scenario, however, the distinguishing issue is Layer 2 interworking mismatch and the confirming observation is: The CE-facing frames are correctly interpreted at the remote attachment after supported interworking.
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 Layer 2 interworking mismatch and the confirming observation is: The CE-facing frames are correctly interpreted at the remote attachment after supported interworking.
C:Repair the remote service signaling and reestablish the expected VC label state. This is a plausible configuration or operational fix 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 Layer 2 interworking mismatch and the confirming observation is: The CE-facing frames are correctly interpreted at the remote attachment after supported interworking.
Question 865
During a core-routing migration rehearsal, an HPE Juniper Networking engineer investigates this situation: A provider attempts to connect a frame-relay-style legacy service to an Ethernet attachment over a pseudowire without any compatible interworking treatment. Which operational control would best prevent a recurrence of this exact failure mode?
- Qualify every attachment encapsulation before approving mixed-media L2 VPN provisioning.
- Document L2 service frame-size requirements and test near-MTU frames.
- Benchmark control-plane route count, BUM replication and convergence before migration.
- Monitor service-label mapping events apart from core transport failures.
Explanation
Correct Answer
A:Qualify every attachment encapsulation before approving mixed-media L2 VPN provisioning. The control limits repetition of the described root condition: Different Layer 2 attachment encapsulations may require explicit compatible interworking, not an assumption that raw frames are identical. During audits, confirm: The CE-facing frames are correctly interpreted at the remote attachment after supported interworking.
Incorrect Answers
B:Document L2 service frame-size requirements and test near-MTU frames. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically Pseudowire MTU mismatch. Pseudowire endpoint parameter mismatches can prevent a usable circuit or lead to frame loss even with valid transport. In this scenario, however, the distinguishing issue is Layer 2 interworking mismatch and the confirming observation is: The CE-facing frames are correctly interpreted at the remote attachment after supported interworking.
C:Benchmark control-plane route count, BUM replication and convergence before migration. This is a plausible preventive practice 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 Layer 2 interworking mismatch and the confirming observation is: The CE-facing frames are correctly interpreted at the remote attachment after supported interworking.
D:Monitor service-label mapping events apart from core transport failures. This is a plausible preventive practice 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 Layer 2 interworking mismatch and the confirming observation is: The CE-facing frames are correctly interpreted at the remote attachment after supported interworking.
Question 866
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: An MPLS Layer 2 service has intermittent packet ordering or parsing issues because its endpoints disagree about use of the pseudowire control word. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect BGP L2VPN route distinguishers and the relevant service NLRI.
- Inspect control-word negotiation and egress frame parsing for the specific pseudowire type.
- Inspect attachment circuit type and the pseudowire's configured interworking mode.
- Inspect targeted LDP hello and TCP session status between the pseudowire endpoints.
Explanation
Correct Answer
B:Inspect control-word negotiation and egress frame parsing for the specific pseudowire type. This check examines the decisive condition for Pseudowire control-word handling before any unrelated changes are made. The underlying mechanism is: A pseudowire control word adds context or sequence fields in supported encapsulations, so endpoints must interpret a compatible format. The confirming observation is: The endpoints agree on control-word use and CE traffic is decoded correctly after label removal.
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 Pseudowire control-word handling and the confirming observation is: The endpoints agree on control-word use and CE traffic is decoded correctly after label removal.
C:Inspect attachment circuit type and the pseudowire's configured interworking mode. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically Layer 2 interworking mismatch. Different Layer 2 attachment encapsulations may require explicit compatible interworking, not an assumption that raw frames are identical. In this scenario, however, the distinguishing issue is Pseudowire control-word handling and the confirming observation is: The endpoints agree on control-word use and CE traffic is decoded correctly after label removal.
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 Pseudowire control-word handling and the confirming observation is: The endpoints agree on control-word use and CE traffic is decoded correctly after label removal.
Question 867
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: An MPLS Layer 2 service has intermittent packet ordering or parsing issues because its endpoints disagree about use of the pseudowire control word. Which routing or service mechanism best explains the reported behavior?
- BGP-signaled L2VPN routes need distinguishable VPN identifiers so unrelated overlapping customer service advertisements do not collide.
- Different Layer 2 attachment encapsulations may require explicit compatible interworking, not an assumption that raw frames are identical.
- A pseudowire control word adds context or sequence fields in supported encapsulations, so endpoints must interpret a compatible format.
- VPLS needs loop-prevention controls such as split-horizon behavior when forwarding between remote pseudowires.
Explanation
Correct Answer
C:A pseudowire control word adds context or sequence fields in supported encapsulations, so endpoints must interpret a compatible format. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The endpoints agree on control-word use and CE traffic is decoded correctly after label removal. The targeted correction is: Align supported control-word settings at both pseudowire ends.
Incorrect Answers
A: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 Pseudowire control-word handling and the confirming observation is: The endpoints agree on control-word use and CE traffic is decoded correctly after label removal.
B:Different Layer 2 attachment encapsulations may require explicit compatible interworking, not an assumption that raw frames are identical. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically Layer 2 interworking mismatch. Different Layer 2 attachment encapsulations may require explicit compatible interworking, not an assumption that raw frames are identical. In this scenario, however, the distinguishing issue is Pseudowire control-word handling and the confirming observation is: The endpoints agree on control-word use and CE traffic is decoded correctly after label removal.
D: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 Pseudowire control-word handling and the confirming observation is: The endpoints agree on control-word use and CE traffic is decoded correctly after label removal.
Question 868
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: An MPLS Layer 2 service has intermittent packet ordering or parsing issues because its endpoints disagree about use of the pseudowire control word. 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 CE-facing frames are correctly interpreted at the remote attachment after supported interworking.
- Test frames cross the intended CE attachments once without repeated amplification.
- The endpoints agree on control-word use and CE traffic is decoded correctly after label removal.
Explanation
Correct Answer
D:The endpoints agree on control-word use and CE traffic is decoded correctly after label removal. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: A pseudowire control word adds context or sequence fields in supported encapsulations, so endpoints must interpret a compatible format.
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 Pseudowire control-word handling and the confirming observation is: The endpoints agree on control-word use and CE traffic is decoded correctly after label removal.
B:The CE-facing frames are correctly interpreted at the remote attachment after supported interworking. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically Layer 2 interworking mismatch. Different Layer 2 attachment encapsulations may require explicit compatible interworking, not an assumption that raw frames are identical. In this scenario, however, the distinguishing issue is Pseudowire control-word handling and the confirming observation is: The endpoints agree on control-word use and CE traffic is decoded correctly after label removal.
C: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 Pseudowire control-word handling and the confirming observation is: The endpoints agree on control-word use and CE traffic is decoded correctly after label removal.
Question 869
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: An MPLS Layer 2 service has intermittent packet ordering or parsing issues because its endpoints disagree about use of the pseudowire control word. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Align supported control-word settings at both pseudowire ends.
- Assign unique appropriate service RDs and verify per-tenant RT imports.
- Restore the supported VPLS split-horizon or equivalent loop-free topology behavior.
- Restore bidirectional loopback reachability and supported targeted LDP configuration.
Explanation
Correct Answer
A:Align supported control-word settings at both pseudowire ends. The change addresses the root behavior described here: A pseudowire control word adds context or sequence fields in supported encapsulations, so endpoints must interpret a compatible format. Verify success with: The endpoints agree on control-word use and CE traffic is decoded correctly after label removal.
Incorrect Answers
B: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 Pseudowire control-word handling and the confirming observation is: The endpoints agree on control-word use and CE traffic is decoded correctly after label removal.
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 Pseudowire control-word handling and the confirming observation is: The endpoints agree on control-word use and CE traffic is decoded correctly after label removal.
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 Pseudowire control-word handling and the confirming observation is: The endpoints agree on control-word use and CE traffic is decoded correctly after label removal.
Question 870
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: An MPLS Layer 2 service has intermittent packet ordering or parsing issues because its endpoints disagree about use of the pseudowire control word. Which operational control would best prevent a recurrence of this exact failure mode?
- Audit VPN identifiers before consolidating L2VPN routes on shared reflectors.
- Include control-word agreement and payload parsing in L2VPN acceptance tests.
- Qualify every attachment encapsulation before approving mixed-media L2 VPN provisioning.
- Test broadcast storm containment before admitting additional VPLS PEs.
Explanation
Correct Answer
B:Include control-word agreement and payload parsing in L2VPN acceptance tests. The control limits repetition of the described root condition: A pseudowire control word adds context or sequence fields in supported encapsulations, so endpoints must interpret a compatible format. During audits, confirm: The endpoints agree on control-word use and CE traffic is decoded correctly after label removal.
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 Pseudowire control-word handling and the confirming observation is: The endpoints agree on control-word use and CE traffic is decoded correctly after label removal.
C:Qualify every attachment encapsulation before approving mixed-media L2 VPN provisioning. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically Layer 2 interworking mismatch. Different Layer 2 attachment encapsulations may require explicit compatible interworking, not an assumption that raw frames are identical. In this scenario, however, the distinguishing issue is Pseudowire control-word handling and the confirming observation is: The endpoints agree on control-word use and CE traffic is decoded correctly after label removal.
D: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 Pseudowire control-word handling and the confirming observation is: The endpoints agree on control-word use and CE traffic is decoded correctly after label removal.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests