Question 850
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: Two PEs have normal hop-by-hop LDP in the transport network but cannot negotiate a remote Layer 2 circuit because no targeted LDP session forms between their loopbacks. Which operational control would best prevent a recurrence of this exact failure mode?
- Use a two-ended pseudowire service record for every provisioned VC.
- Track transport LSP reachability separately from targeted pseudowire signaling.
- Verify BGP EVPN routes and actual encapsulated packet forwarding independently.
- Require both service label and transport label checks before declaring a pseudowire active.
Explanation
Correct Answer
B:Track transport LSP reachability separately from targeted pseudowire signaling. The control limits repetition of the described root condition: Remote LDP-signaled pseudowires require an appropriate targeted control session in addition to core label transport. During audits, confirm: The remote PE LDP session is established and exchanges the service label for the circuit.
Incorrect Answers
A: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 Targeted LDP session absent and the confirming observation is: The remote PE LDP session is established and exchanges the service label for the circuit.
C:Verify BGP EVPN routes and actual encapsulated packet forwarding independently. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically EVPN core route resolution. EVPN control-plane MAC information needs an independently working transport data plane to deliver frames. In this scenario, however, the distinguishing issue is Targeted LDP session absent and the confirming observation is: The remote PE LDP session is established and exchanges the service label for the circuit.
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 Targeted LDP session absent and the confirming observation is: The remote PE LDP session is established and exchanges the service label for the circuit.
Question 851
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: An LDP circuit has exchanged service labels successfully but customer frames are discarded because the provider core has no valid MPLS path to the far PE. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect VPLS MAC learning tables, aging and broadcast/unknown-unicast flood counters.
- Inspect split-horizon forwarding treatment for traffic received from VPLS pseudowires.
- Inspect outer transport label reachability and remote PE next-hop resolution independent of the VC label.
- Inspect targeted LDP hello and TCP session status between the pseudowire endpoints.
Explanation
Correct Answer
C:Inspect outer transport label reachability and remote PE next-hop resolution independent of the VC label. This check examines the decisive condition for Pseudowire transport unreachable before any unrelated changes are made. The underlying mechanism is: Pseudowire service labels identify the circuit, while a separate MPLS transport path carries the traffic to the remote PE. The confirming observation is: Label switching to the far PE is operational and the service frames are delivered over the signaled circuit.
Incorrect Answers
A:Inspect VPLS MAC learning tables, aging and broadcast/unknown-unicast flood counters. This is a plausible diagnostic check 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 Pseudowire transport unreachable and the confirming observation is: Label switching to the far PE is operational and the service frames are delivered over the signaled circuit.
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 Pseudowire transport unreachable and the confirming observation is: Label switching to the far PE is operational and the service frames are delivered over the signaled circuit.
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 transport unreachable and the confirming observation is: Label switching to the far PE is operational and the service frames are delivered over the signaled circuit.
Question 852
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: An LDP circuit has exchanged service labels successfully but customer frames are discarded because the provider core has no valid MPLS path to the far PE. Which routing or service mechanism best explains the reported behavior?
- VPLS provides multipoint Ethernet bridging, so traffic to unknown MAC addresses can be flooded within the VPN forwarding domain.
- VPLS needs loop-prevention controls such as split-horizon behavior when forwarding between remote pseudowires.
- EVPN control-plane MAC information needs an independently working transport data plane to deliver frames.
- Pseudowire service labels identify the circuit, while a separate MPLS transport path carries the traffic to the remote PE.
Explanation
Correct Answer
D:Pseudowire service labels identify the circuit, while a separate MPLS transport path carries the traffic to the remote PE. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Label switching to the far PE is operational and the service frames are delivered over the signaled circuit. The targeted correction is: Restore the underlying MPLS transport without resetting a healthy service-label agreement.
Incorrect Answers
A:VPLS provides multipoint Ethernet bridging, so traffic to unknown MAC addresses can be flooded within the VPN forwarding domain. This is a plausible protocol explanation 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 Pseudowire transport unreachable and the confirming observation is: Label switching to the far PE is operational and the service frames are delivered over the signaled circuit.
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 Pseudowire transport unreachable and the confirming observation is: Label switching to the far PE is operational and the service frames are delivered over the signaled circuit.
C:EVPN control-plane MAC information needs an independently working transport data plane to deliver frames. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically EVPN core route resolution. EVPN control-plane MAC information needs an independently working transport data plane to deliver frames. In this scenario, however, the distinguishing issue is Pseudowire transport unreachable and the confirming observation is: Label switching to the far PE is operational and the service frames are delivered over the signaled circuit.
Question 853
During a core-routing migration rehearsal, an HPE Juniper Networking engineer investigates this situation: An LDP circuit has exchanged service labels successfully but customer frames are discarded because the provider core has no valid MPLS path to the far PE. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Label switching to the far PE is operational and the service frames are delivered over the signaled circuit.
- MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site.
- Test frames cross the intended CE attachments once without repeated amplification.
- The remote PE next hop and encapsulation path are valid and frames reach the advertised MAC.
Explanation
Correct Answer
A:Label switching to the far PE is operational and the service frames are delivered over the signaled circuit. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Pseudowire service labels identify the circuit, while a separate MPLS transport path carries the traffic to the remote PE.
Incorrect Answers
B:MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site. This is a plausible observed evidence 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 Pseudowire transport unreachable and the confirming observation is: Label switching to the far PE is operational and the service frames are delivered over the signaled circuit.
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 transport unreachable and the confirming observation is: Label switching to the far PE is operational and the service frames are delivered over the signaled circuit.
D:The remote PE next hop and encapsulation path are valid and frames reach the advertised MAC. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically EVPN core route resolution. EVPN control-plane MAC information needs an independently working transport data plane to deliver frames. In this scenario, however, the distinguishing issue is Pseudowire transport unreachable and the confirming observation is: Label switching to the far PE is operational and the service frames are delivered over the signaled circuit.
Question 854
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: An LDP circuit has exchanged service labels successfully but customer frames are discarded because the provider core has no valid MPLS path to the far PE. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Fix MAC learning or excessive churn rather than disabling legitimate service discovery broadly.
- Restore the underlying MPLS transport without resetting a healthy service-label agreement.
- 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:Restore the underlying MPLS transport without resetting a healthy service-label agreement. The change addresses the root behavior described here: Pseudowire service labels identify the circuit, while a separate MPLS transport path carries the traffic to the remote PE. Verify success with: Label switching to the far PE is operational and the service frames are delivered over the signaled circuit.
Incorrect Answers
A:Fix MAC learning or excessive churn rather than disabling legitimate service discovery broadly. This is a plausible configuration or operational fix 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 Pseudowire transport unreachable and the confirming observation is: Label switching to the far PE is operational and the service frames are delivered over the signaled circuit.
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 transport unreachable and the confirming observation is: Label switching to the far PE is operational and the service frames are delivered over the signaled circuit.
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 transport unreachable and the confirming observation is: Label switching to the far PE is operational and the service frames are delivered over the signaled circuit.
Question 855
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: An LDP circuit has exchanged service labels successfully but customer frames are discarded because the provider core has no valid MPLS path to the far PE. 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.
- Test broadcast storm containment before admitting additional VPLS PEs.
- Require both service label and transport label checks before declaring a pseudowire active.
- Verify BGP EVPN routes and actual encapsulated packet forwarding independently.
Explanation
Correct Answer
C:Require both service label and transport label checks before declaring a pseudowire active. The control limits repetition of the described root condition: Pseudowire service labels identify the circuit, while a separate MPLS transport path carries the traffic to the remote PE. During audits, confirm: Label switching to the far PE is operational and the service frames are delivered over the signaled circuit.
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 Pseudowire transport unreachable and the confirming observation is: Label switching to the far PE is operational and the service frames are delivered over the signaled circuit.
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 Pseudowire transport unreachable and the confirming observation is: Label switching to the far PE is operational and the service frames are delivered over the signaled circuit.
D:Verify BGP EVPN routes and actual encapsulated packet forwarding independently. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically EVPN core route resolution. EVPN control-plane MAC information needs an independently working transport data plane to deliver frames. In this scenario, however, the distinguishing issue is Pseudowire transport unreachable and the confirming observation is: Label switching to the far PE is operational and the service frames are delivered over the signaled circuit.
Question 856
During a high-availability validation, 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 targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect attachment circuit type and the pseudowire's configured interworking mode.
- Compare VPLS MAC control behavior with EVPN BGP MAC signaling and multihoming capabilities.
- Inspect EVPN Ethernet auto-discovery type 1 advertisements associated with the shared segment.
- Compare advertised and local pseudowire MTU and encapsulation parameters.
Explanation
Correct Answer
D:Compare advertised and local pseudowire MTU and encapsulation parameters. This check examines the decisive condition for Pseudowire MTU mismatch before any unrelated changes are made. The underlying mechanism is: Pseudowire endpoint parameter mismatches can prevent a usable circuit or lead to frame loss even with valid transport. The confirming observation is: Both PEs agree on service MTU and the maximum allowed customer frame crosses successfully.
Incorrect Answers
A: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 MTU mismatch and the confirming observation is: Both PEs agree on service MTU and the maximum allowed customer frame crosses successfully.
B: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 Pseudowire MTU mismatch and the confirming observation is: Both PEs agree on service MTU and the maximum allowed customer frame crosses successfully.
C:Inspect EVPN Ethernet auto-discovery type 1 advertisements associated with the shared segment. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically EVPN Ethernet AD signaling. Ethernet AD routes help distribute EVPN segment reachability and can support multihoming convergence mechanisms. In this scenario, however, the distinguishing issue is Pseudowire MTU mismatch and the confirming observation is: Both PEs agree on service MTU and the maximum allowed customer frame crosses successfully.
Question 857
During a Junos routing maintenance review, 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 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.
- Ethernet AD routes help distribute EVPN segment reachability and can support multihoming convergence mechanisms.
Explanation
Correct Answer
A:Pseudowire endpoint parameter mismatches can prevent a usable circuit or lead to frame loss even with valid transport. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Both PEs agree on service MTU and the maximum allowed customer frame crosses successfully. The targeted correction is: Align the end-to-end service MTU with core overhead and CE requirements.
Incorrect Answers
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 MTU mismatch and the confirming observation is: Both PEs agree on service MTU and the maximum allowed customer frame crosses successfully.
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 Pseudowire MTU mismatch and the confirming observation is: Both PEs agree on service MTU and the maximum allowed customer frame crosses successfully.
D:Ethernet AD routes help distribute EVPN segment reachability and can support multihoming convergence mechanisms. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically EVPN Ethernet AD signaling. Ethernet AD routes help distribute EVPN segment reachability and can support multihoming convergence mechanisms. In this scenario, however, the distinguishing issue is Pseudowire MTU mismatch and the confirming observation is: Both PEs agree on service MTU and the maximum allowed customer frame crosses successfully.
Question 858
During a multisite network cutover, 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. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The CE-facing frames are correctly interpreted at the remote attachment after supported interworking.
- Both PEs agree on service MTU and the maximum allowed customer frame crosses successfully.
- Broadcast replication returns to normal after the customer loop is isolated or protected.
- A pilot shows remote host reachability learned by EVPN route advertisement with bounded BUM flooding.
Explanation
Correct Answer
B:Both PEs agree on service MTU and the maximum allowed customer frame crosses successfully. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Pseudowire endpoint parameter mismatches can prevent a usable circuit or lead to frame loss even with valid transport.
Incorrect Answers
A: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 MTU mismatch and the confirming observation is: Both PEs agree on service MTU and the maximum allowed customer frame crosses successfully.
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 Pseudowire MTU mismatch and the confirming observation is: Both PEs agree on service MTU and the maximum allowed customer frame crosses successfully.
D: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 Pseudowire MTU mismatch and the confirming observation is: Both PEs agree on service MTU and the maximum allowed customer frame crosses successfully.
Question 859
During a metro aggregation incident, 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 response or focused corrective action best addresses this situation without changing unrelated components?
- Use a supported pseudowire interworking configuration or adapt the service at the boundary.
- Enforce customer loop controls and supported storm-control limits at the PE edge.
- 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.
Explanation
Correct Answer
C:Align the end-to-end service MTU with core overhead and CE requirements. The change addresses the root behavior described here: Pseudowire endpoint parameter mismatches can prevent a usable circuit or lead to frame loss even with valid transport. Verify success with: Both PEs agree on service MTU and the maximum allowed customer frame crosses successfully.
Incorrect Answers
A:Use a supported pseudowire interworking configuration or adapt the service at the boundary. This is a plausible configuration or operational fix 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: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 Pseudowire MTU mismatch and the confirming observation is: Both PEs agree on service MTU and the maximum allowed customer frame crosses successfully.
D: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 Pseudowire MTU mismatch and the confirming observation is: Both PEs agree on service MTU and the maximum allowed customer frame crosses successfully.
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.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests