Question 840
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A provider advertises one tenant's large aggregate to all regional PEs, but the aggregate contains prefixes not actually assigned to that customer. Which operational control would best prevent a recurrence of this exact failure mode?
- Review route-target interest and scale during multi-tenant growth.
- Include interface-to-tenant mapping validation in turn-up checklists.
- Validate security inspection and symmetric routing for each tenant.
- Check aggregate coverage and negative reachability at the tenant boundary.
Explanation
Correct Answer
D:Check aggregate coverage and negative reachability at the tenant boundary. The control limits repetition of the described root condition: VPN export summaries must respect each tenant's address scope; a broad aggregate can attract unrelated traffic even if RTs are correct. During audits, confirm: The aggregate advertises only assigned and reachable tenant prefixes and does not black-hole neighboring addresses.
Incorrect Answers
A:Review route-target interest and scale during multi-tenant growth. This is a plausible preventive practice for a different Layer 3 VPNs condition, specifically Route-target constraint scale. Route-target-based distribution can limit which VPN routes are propagated toward routers that have corresponding VPN interests. In this scenario, however, the distinguishing issue is VRF export summary overscoped and the confirming observation is: The aggregate advertises only assigned and reachable tenant prefixes and does not black-hole neighboring addresses.
B:Include interface-to-tenant mapping validation in turn-up checklists. This is a plausible preventive practice for a different Layer 3 VPNs condition, specifically Customer CE interface mapped wrong VRF. L3VPN separation starts at the correct PE customer interface association with the VRF. In this scenario, however, the distinguishing issue is VRF export summary overscoped and the confirming observation is: The aggregate advertises only assigned and reachable tenant prefixes and does not black-hole neighboring addresses.
C:Validate security inspection and symmetric routing for each tenant. This is a plausible preventive practice for a different Layer 3 VPNs condition, specifically L3VPN Internet breakout design. Internet access for L3VPN customers depends on explicit routing, route leaking or central breakout topology. In this scenario, however, the distinguishing issue is VRF export summary overscoped and the confirming observation is: The aggregate advertises only assigned and reachable tenant prefixes and does not black-hole neighboring addresses.
Question 841
During a core-routing migration rehearsal, an HPE Juniper Networking engineer investigates this situation: Two customer edge ports are attached to a provisioned LDP pseudowire but the Layer 2 circuit never becomes operational although PE loopbacks are reachable. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare the virtual circuit identifier and encapsulation expected on both pseudowire endpoints.
- Inspect targeted LDP hello and TCP session status between the pseudowire endpoints.
- Compare ingress VLAN unit counters and the specific L2VPN instance's attachment configuration.
- Inspect BGP L2VPN route distinguishers and the relevant service NLRI.
Explanation
Correct Answer
A:Compare the virtual circuit identifier and encapsulation expected on both pseudowire endpoints. This check examines the decisive condition for LDP pseudowire VC ID mismatch before any unrelated changes are made. The underlying mechanism is: An LDP-signaled point-to-point Layer 2 circuit needs compatible pseudowire identity and service parameters on both PEs. The confirming observation is: Both endpoints show the expected circuit ID and an up data plane after matching configuration.
Incorrect Answers
B: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 LDP pseudowire VC ID mismatch and the confirming observation is: Both endpoints show the expected circuit ID and an up data plane after matching configuration.
C:Compare ingress VLAN unit counters and the specific L2VPN instance's attachment configuration. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically L2VPN attachment interface wrong unit. A signaled pseudowire only carries CE frames that enter its actual local attachment circuit. In this scenario, however, the distinguishing issue is LDP pseudowire VC ID mismatch and the confirming observation is: Both endpoints show the expected circuit ID and an up data plane after matching configuration.
D: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 LDP pseudowire VC ID mismatch and the confirming observation is: Both endpoints show the expected circuit ID and an up data plane after matching configuration.
Question 842
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: Two customer edge ports are attached to a provisioned LDP pseudowire but the Layer 2 circuit never becomes operational although PE loopbacks are reachable. Which routing or service mechanism best explains the reported behavior?
- Remote LDP-signaled pseudowires require an appropriate targeted control session in addition to core label transport.
- An LDP-signaled point-to-point Layer 2 circuit needs compatible pseudowire identity and service parameters on both PEs.
- 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.
Explanation
Correct Answer
B:An LDP-signaled point-to-point Layer 2 circuit needs compatible pseudowire identity and service parameters on both PEs. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Both endpoints show the expected circuit ID and an up data plane after matching configuration. The targeted correction is: Align the intended pseudowire VC ID on both ends without changing unrelated circuits.
Incorrect Answers
A: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 LDP pseudowire VC ID mismatch and the confirming observation is: Both endpoints show the expected circuit ID and an up data plane after matching configuration.
C: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 LDP pseudowire VC ID mismatch and the confirming observation is: Both endpoints show the expected circuit ID and an up data plane after matching configuration.
D: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 LDP pseudowire VC ID mismatch and the confirming observation is: Both endpoints show the expected circuit ID and an up data plane after matching configuration.
Question 843
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: Two customer edge ports are attached to a provisioned LDP pseudowire but the Layer 2 circuit never becomes operational although PE loopbacks are reachable. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The remote PE LDP session is established and exchanges the service label for the circuit.
- 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.
- Distinct RDs preserve separate advertisements and only correct tenant membership is imported.
Explanation
Correct Answer
C:Both endpoints show the expected circuit ID and an up data plane after matching configuration. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: An LDP-signaled point-to-point Layer 2 circuit needs compatible pseudowire identity and service parameters on both PEs.
Incorrect Answers
A: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 LDP pseudowire VC ID mismatch and the confirming observation is: Both endpoints show the expected circuit ID and an up data plane after matching configuration.
B:Packet counters on the intended unit and pseudowire both increase for a test frame. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically L2VPN attachment interface wrong unit. A signaled pseudowire only carries CE frames that enter its actual local attachment circuit. In this scenario, however, the distinguishing issue is LDP pseudowire VC ID mismatch and the confirming observation is: Both endpoints show the expected circuit ID and an up data plane after matching configuration.
D: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 LDP pseudowire VC ID mismatch and the confirming observation is: Both endpoints show the expected circuit ID and an up data plane after matching configuration.
Question 844
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: Two customer edge ports are attached to a provisioned LDP pseudowire but the Layer 2 circuit never becomes operational although PE loopbacks are reachable. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Restore bidirectional loopback reachability and supported targeted LDP configuration.
- Bind the correct VLAN logical unit or service interface to the L2VPN instance.
- Assign unique appropriate service RDs and verify per-tenant RT imports.
- Align the intended pseudowire VC ID on both ends without changing unrelated circuits.
Explanation
Correct Answer
D:Align the intended pseudowire VC ID on both ends without changing unrelated circuits. The change addresses the root behavior described here: An LDP-signaled point-to-point Layer 2 circuit needs compatible pseudowire identity and service parameters on both PEs. Verify success with: Both endpoints show the expected circuit ID and an up data plane after matching configuration.
Incorrect Answers
A: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 LDP pseudowire VC ID mismatch and the confirming observation is: Both endpoints show the expected circuit ID and an up data plane after matching configuration.
B:Bind the correct VLAN logical unit or service interface to the L2VPN instance. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically L2VPN attachment interface wrong unit. A signaled pseudowire only carries CE frames that enter its actual local attachment circuit. In this scenario, however, the distinguishing issue is LDP pseudowire VC ID mismatch and the confirming observation is: Both endpoints show the expected circuit ID and an up data plane after matching configuration.
C: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 LDP pseudowire VC ID mismatch and the confirming observation is: Both endpoints show the expected circuit ID and an up data plane after matching configuration.
Question 845
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: Two customer edge ports are attached to a provisioned LDP pseudowire but the Layer 2 circuit never becomes operational although PE loopbacks are reachable. 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.
- Cross-check physical port, VLAN tag and logical unit against customer acceptance drawings.
- Audit VPN identifiers before consolidating L2VPN routes on shared reflectors.
Explanation
Correct Answer
A:Use a two-ended pseudowire service record for every provisioned VC. The control limits repetition of the described root condition: An LDP-signaled point-to-point Layer 2 circuit needs compatible pseudowire identity and service parameters on both PEs. During audits, confirm: Both endpoints show the expected circuit ID and an up data plane after matching configuration.
Incorrect Answers
B: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 LDP pseudowire VC ID mismatch and the confirming observation is: Both endpoints show the expected circuit ID and an up data plane after matching configuration.
C:Cross-check physical port, VLAN tag and logical unit against customer acceptance drawings. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically L2VPN attachment interface wrong unit. A signaled pseudowire only carries CE frames that enter its actual local attachment circuit. In this scenario, however, the distinguishing issue is LDP pseudowire VC ID mismatch and the confirming observation is: Both endpoints show the expected circuit ID and an up data plane after matching configuration.
D: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 LDP pseudowire VC ID mismatch and the confirming observation is: Both endpoints show the expected circuit ID and an up data plane after matching configuration.
Question 846
During a multisite network cutover, 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 targeted check most directly distinguishes the likely cause before a configuration change?
- Compare the virtual circuit identifier and encapsulation expected on both pseudowire endpoints.
- Inspect targeted LDP hello and TCP session status between the pseudowire endpoints.
- Inspect EVPN BGP next-hop resolution and the MPLS transport or VXLAN encapsulation path in use.
- Inspect outer transport label reachability and remote PE next-hop resolution independent of the VC label.
Explanation
Correct Answer
B:Inspect targeted LDP hello and TCP session status between the pseudowire endpoints. This check examines the decisive condition for Targeted LDP session absent before any unrelated changes are made. The underlying mechanism is: Remote LDP-signaled pseudowires require an appropriate targeted control session in addition to core label transport. The confirming observation is: The remote PE LDP session is established and exchanges the service label for the circuit.
Incorrect Answers
A: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 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:Inspect EVPN BGP next-hop resolution and the MPLS transport or VXLAN encapsulation path in use. This is a plausible diagnostic check 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:Inspect outer transport label reachability and remote PE next-hop resolution independent of the VC label. This is a plausible diagnostic check 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 847
During a metro aggregation incident, 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 routing or service mechanism best explains the reported behavior?
- An LDP-signaled point-to-point Layer 2 circuit needs compatible pseudowire identity and service parameters on both PEs.
- EVPN control-plane MAC information needs an independently working transport data plane to deliver frames.
- Remote LDP-signaled pseudowires require an appropriate targeted control session in addition to core label transport.
- Pseudowire service labels identify the circuit, while a separate MPLS transport path carries the traffic to the remote PE.
Explanation
Correct Answer
C:Remote LDP-signaled pseudowires require an appropriate targeted control session in addition to core label transport. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The remote PE LDP session is established and exchanges the service label for the circuit. The targeted correction is: Restore bidirectional loopback reachability and supported targeted LDP configuration.
Incorrect Answers
A:An LDP-signaled point-to-point Layer 2 circuit needs compatible pseudowire identity and service parameters on both PEs. This is a plausible protocol explanation 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.
B: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 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:Pseudowire service labels identify the circuit, while a separate MPLS transport path carries the traffic to the remote PE. This is a plausible protocol explanation 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 848
During a managed service audit, 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. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Both endpoints show the expected circuit ID and an up data plane after matching configuration.
- The remote PE next hop and encapsulation path are valid and frames reach the advertised MAC.
- The endpoints agree on control-word use and CE traffic is decoded correctly after label removal.
- The remote PE LDP session is established and exchanges the service label for the circuit.
Explanation
Correct Answer
D:The remote PE LDP session is established and exchanges the service label for the circuit. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Remote LDP-signaled pseudowires require an appropriate targeted control session in addition to core label transport.
Incorrect Answers
A: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 Targeted LDP session absent and the confirming observation is: The remote PE LDP session is established and exchanges the service label for the circuit.
B: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 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:The endpoints agree on control-word use and CE traffic is decoded correctly after label removal. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically Pseudowire control-word handling. A pseudowire control word adds context or sequence fields in supported encapsulations, so endpoints must interpret a compatible format. In this scenario, however, the distinguishing issue is 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 849
During a network architecture troubleshooting workshop, 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 response or focused corrective action best addresses this situation without changing unrelated components?
- Restore bidirectional loopback reachability and supported targeted LDP configuration.
- Align the intended pseudowire VC ID on both ends without changing unrelated circuits.
- Restore the underlying MPLS transport without resetting a healthy service-label agreement.
- Align supported control-word settings at both pseudowire ends.
Explanation
Correct Answer
A:Restore bidirectional loopback reachability and supported targeted LDP configuration. The change addresses the root behavior described here: Remote LDP-signaled pseudowires require an appropriate targeted control session in addition to core label transport. Verify success with: The remote PE LDP session is established and exchanges the service label for the circuit.
Incorrect Answers
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 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:Restore the underlying MPLS transport without resetting a healthy service-label agreement. This is a plausible configuration or operational fix 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.
D:Align supported control-word settings at both pseudowire ends. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically Pseudowire control-word handling. A pseudowire control word adds context or sequence fields in supported encapsulations, so endpoints must interpret a compatible format. In this scenario, however, the distinguishing issue is 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 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.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests