Juniper JN0-664 Practice Test 43
Question 420
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. A provider mistakenly imports an MVPN customer group's traffic into another VRF and must restore per-tenant multicast isolation while keeping authorized streams active. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.
- Treat an RD as an access-control filter and set identical RDs for every unrelated VPN while leaving permissive RT import policy unrestricted.
- Assume every MAC learned on an EVPN remote PE must be discovered exclusively by data-plane flood without any BGP MAC/IP advertisement.
- Enable MP-BGP VPN unicast for a tenant and promise its source multicast group will automatically traverse provider PEs with no MVPN or multicast setup.
- Assume an established VPNv4 BGP session automatically advertises the IPv6 prefix 2001:db8:50::/48 into every remote instance.inet6.0.
Explanation
Correct Answer
C:That conflicts with the edge-to-cloud principle: MVPN carries customer multicast across provider networks using supported control-plane membership and provider transport mechanisms; unicast VRF reachability alone does not prove multicast distribution.
Incorrect Answers
A:This alternative proposes: Treat an RD as an access-control filter and set identical RDs for every unrelated VPN while leaving permissive RT import policy unrestricted. It concerns a different Junos engineering issue Layer 3 VPN route distinguishers versus route targets, not the directly tested provider-network issue Multicast VPN provider and customer traffic separation.
B:This alternative proposes: Assume every MAC learned on an EVPN remote PE must be discovered exclusively by data-plane flood without any BGP MAC/IP advertisement. It concerns a different Junos engineering issue EVPN MAC IP route type two control plane and learning, not the directly tested provider-network issue Multicast VPN provider and customer traffic separation.
D:This alternative proposes: Assume an established VPNv4 BGP session automatically advertises the IPv6 prefix 2001:db8:50::/48 into every remote instance.inet6.0. It concerns a different Junos engineering issue IPv6 Layer 3 VPN VPNv6 route families and forwarding, not the directly tested provider-network issue Multicast VPN provider and customer traffic separation.
Question 421
A Junos service-provider routing engineer investigates the following routing and service incident: A customer E-Line service fails after one PE changes its virtual circuit ID from 501 to 502 while the far PE still uses 501. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Confirm the eligibility requirements for BGP multipath and distinguish multiple accepted routes from actual installed forwarding next hops.
- Trace an LDP Layer 2 circuit end to end using neighbor signaling, pseudowire identifiers and operational connection state before changing customer VLANs.
- Validate BGP Layer 2 VPN service discovery through negotiated signaling families, route distinguishers/targets and customer connection mappings.
- Verify service MTU and any supported pseudowire encapsulation/control-word expectations when a pseudowire is signaled Up but customer frames fail.
Explanation
Correct Answer
B:The case-specific routing and services action is: Trace an LDP Layer 2 circuit end to end using neighbor signaling, pseudowire identifiers and operational connection state before changing customer VLANs. The governing Junos routing/service principle is: An LDP-signaled pseudowire uses locally and remotely agreed circuit identifiers, transport paths and VC labels; mismatched endpoints or identifiers can prevent service Up state.
Incorrect Answers
A:This alternative proposes: Confirm the eligibility requirements for BGP multipath and distinguish multiple accepted routes from actual installed forwarding next hops. It concerns a different Junos engineering issue BGP multipath equal cost and per-flow forwarding, not the directly tested provider-network issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers.
C:This alternative proposes: Validate BGP Layer 2 VPN service discovery through negotiated signaling families, route distinguishers/targets and customer connection mappings. It concerns a different Junos engineering issue BGP-signaled Layer 2 VPN NLRI and route target import, not the directly tested provider-network issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers.
D:This alternative proposes: Verify service MTU and any supported pseudowire encapsulation/control-word expectations when a pseudowire is signaled Up but customer frames fail. It concerns a different Junos engineering issue Layer 2 pseudowire MTU and control-word interworking, not the directly tested provider-network issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers.
Question 422
A provider routing design review considers this situation. A customer E-Line service fails after one PE changes its virtual circuit ID from 501 to 502 while the far PE still uses 501. A colleague proposes: Trace an LDP Layer 2 circuit end to end using neighbor signaling, pseudowire identifiers and operational connection state before changing customer VLANs. Which technical principle BEST supports that action? Select ONE best answer.
- MVPN carries customer multicast across provider networks using supported control-plane membership and provider transport mechanisms; unicast VRF reachability alone does not prove multicast distribution.
- Pseudowire transport can impose encapsulation overhead and require compatible payload/MTU or control-word behavior; signaling Up does not guarantee all customer frame sizes are successfully delivered.
- An LDP-signaled pseudowire uses locally and remotely agreed circuit identifiers, transport paths and VC labels; mismatched endpoints or identifiers can prevent service Up state.
- A BGP-signaled Layer 2 VPN advertises service-related NLRI and label reachability; route-target and instance-policy behavior determine which remote service participates.
Explanation
Correct Answer
C:The relevant Junos service-provider networking principle is: An LDP-signaled pseudowire uses locally and remotely agreed circuit identifiers, transport paths and VC labels; mismatched endpoints or identifiers can prevent service Up state. In the described provider-network case (A customer E-Line service fails after one PE changes its virtual circuit ID from 501 to 502 while the far PE still uses 501.), it supports the planned action: Trace an LDP Layer 2 circuit end to end using neighbor signaling, pseudowire identifiers and operational connection state before changing customer VLANs.
Incorrect Answers
A:This alternative proposes: MVPN carries customer multicast across provider networks using supported control-plane membership and provider transport mechanisms; unicast VRF reachability alone does not prove multicast distribution. It concerns a different Junos engineering issue Multicast VPN provider and customer traffic separation, not the directly tested provider-network issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers.
B:This alternative proposes: Pseudowire transport can impose encapsulation overhead and require compatible payload/MTU or control-word behavior; signaling Up does not guarantee all customer frame sizes are successfully delivered. It concerns a different Junos engineering issue Layer 2 pseudowire MTU and control-word interworking, not the directly tested provider-network issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers.
D:This alternative proposes: A BGP-signaled Layer 2 VPN advertises service-related NLRI and label reachability; route-target and instance-policy behavior determine which remote service participates. It concerns a different Junos engineering issue BGP-signaled Layer 2 VPN NLRI and route target import, not the directly tested provider-network issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers.
Question 423
A Juniper service-provider engineer needs decisive verification evidence for this situation. A customer E-Line service fails after one PE changes its virtual circuit ID from 501 to 502 while the far PE still uses 501. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Inspect BGP family negotiation, received Layer 2 VPN routes, RD/RT communities, service site identifiers, label mapping and per-instance state.
- Inspect show l2circuit connections, LDP session state, neighbor addresses, VC IDs, service-facing interfaces and transport LSP reachability.
- Check service-site IDs, multihoming preference, attachment circuits, signaling reachability, MAC moves and measured forwarding during failover.
- Compare selected BGP attributes, multipath configuration, show route next-hop entries, route preferences and forwarding table resolution.
Explanation
Correct Answer
B:The direct discriminating observation is: Inspect show l2circuit connections, LDP session state, neighbor addresses, VC IDs, service-facing interfaces and transport LSP reachability. In the stated situation (A customer E-Line service fails after one PE changes its virtual circuit ID from 501 to 502 while the far PE still uses 501.), the intended acceptance outcome is: The two attachment circuits join only their authorized sites and the pseudowire status and customer traffic counters remain stable.
Incorrect Answers
A:This alternative proposes: Inspect BGP family negotiation, received Layer 2 VPN routes, RD/RT communities, service site identifiers, label mapping and per-instance state. It concerns a different Junos engineering issue BGP-signaled Layer 2 VPN NLRI and route target import, not the directly tested provider-network issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers.
C:This alternative proposes: Check service-site IDs, multihoming preference, attachment circuits, signaling reachability, MAC moves and measured forwarding during failover. It concerns a different Junos engineering issue VPLS site identifiers multihoming and service convergence, not the directly tested provider-network issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers.
D:This alternative proposes: Compare selected BGP attributes, multipath configuration, show route next-hop entries, route preferences and forwarding table resolution. It concerns a different Junos engineering issue BGP multipath equal cost and per-flow forwarding, not the directly tested provider-network issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers.
Question 424
A service-provider acceptance team reviews the result of a provider-service change. A customer E-Line service fails after one PE changes its virtual circuit ID from 501 to 502 while the far PE still uses 501. The intended verification is: Inspect show l2circuit connections, LDP session state, neighbor addresses, VC IDs, service-facing interfaces and transport LSP reachability. Which outcome BEST demonstrates success? Select ONE best answer.
- The two attachment circuits join only their authorized sites and the pseudowire status and customer traffic counters remain stable.
- Neighbor databases converge on consistent current LSPs and the intended network prefixes resolve through matching shortest-path computations.
- Participating customer sites exchange permitted Ethernet frames through a correctly signaled multipoint service without bridging unrelated tenants.
- Customer traffic follows learned remote PE paths and floods only where required without generating a provider-wide bridging loop.
Explanation
Correct Answer
A:The verified success outcome is: The two attachment circuits join only their authorized sites and the pseudowire status and customer traffic counters remain stable. Confirm this by: Inspect show l2circuit connections, LDP session state, neighbor addresses, VC IDs, service-facing interfaces and transport LSP reachability.
Incorrect Answers
B:That option concerns IS-IS link-state packet flooding and database consistency. The related controlled intervention is: Trace an LDP Layer 2 circuit end to end using neighbor signaling, pseudowire identifiers and operational connection state before changing customer VLANs.
C:That option concerns VPLS service control plane LDP versus BGP distribution. The related controlled intervention is: Trace an LDP Layer 2 circuit end to end using neighbor signaling, pseudowire identifiers and operational connection state before changing customer VLANs.
D:This alternative proposes: Customer traffic follows learned remote PE paths and floods only where required without generating a provider-wide bridging loop. It concerns a different Junos engineering issue VPLS MAC learning flooding and split-horizon safeguards, not the directly tested provider-network issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers.
Question 425
A provider change-review board examines this Junos service case. A customer E-Line service fails after one PE changes its virtual circuit ID from 501 to 502 while the far PE still uses 501. Which THREE statements together give an appropriate corrective action, supporting diagnostic check and success outcome? Select THREE answers.
- The two attachment circuits join only their authorized sites and the pseudowire status and customer traffic counters remain stable.
- Trace an LDP Layer 2 circuit end to end using neighbor signaling, pseudowire identifiers and operational connection state before changing customer VLANs.
- Validate multicast VPN control and data-plane dependencies before claiming a customer group's IP multicast stream should traverse an MPLS provider backbone.
- Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used.
- Inspect MAC tables per VPLS instance, flood counters, PE attachment circuits, pseudowire membership, MAC aging and loop-protection state.
- Inspect show l2circuit connections, LDP session state, neighbor addresses, VC IDs, service-facing interfaces and transport LSP reachability.
Explanation
Correct Answers
A:Confirm this by: Inspect show l2circuit connections, LDP session state, neighbor addresses, VC IDs, service-facing interfaces and transport LSP reachability.
B:The case-specific routing and services action is: Trace an LDP Layer 2 circuit end to end using neighbor signaling, pseudowire identifiers and operational connection state before changing customer VLANs. The governing Junos routing/service principle is: An LDP-signaled pseudowire uses locally and remotely agreed circuit identifiers, transport paths and VC labels; mismatched endpoints or identifiers can prevent service Up state. Verify the decision through: Inspect show l2circuit connections, LDP session state, neighbor addresses, VC IDs, service-facing interfaces and transport LSP reachability.
F:The direct discriminating observation is: Inspect show l2circuit connections, LDP session state, neighbor addresses, VC IDs, service-facing interfaces and transport LSP reachability.
Incorrect Answers
C:That option concerns Multicast VPN provider and customer traffic separation. Confirm this by: Inspect show l2circuit connections, LDP session state, neighbor addresses, VC IDs, service-facing interfaces and transport LSP reachability.
D:That option concerns BGP external multihop and loopback peer reachability. Confirm this by: Inspect show l2circuit connections, LDP session state, neighbor addresses, VC IDs, service-facing interfaces and transport LSP reachability.
E:That option concerns VPLS MAC learning flooding and split-horizon safeguards. Confirm this by: Inspect show l2circuit connections, LDP session state, neighbor addresses, VC IDs, service-facing interfaces and transport LSP reachability.
Question 426
A Junos service-provider routing engineer investigates the following routing and service incident: Two provider nodes have reachable loopbacks yet their Layer 2 circuit remains Down due to missing LDP signaling and the operator attempts to modify BGP unicast policy instead. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Diagnose unknown unicast flooding and Layer 2 loops by distinguishing learned customer MAC paths, BUM handling and VPLS split-horizon behavior.
- Select the supported inter-AS or carrier-of-carriers VPN interconnection model according to trust, labels, MP-BGP signaling and administrative boundary requirements.
- Verify service MTU and any supported pseudowire encapsulation/control-word expectations when a pseudowire is signaled Up but customer frames fail.
- Trace an LDP Layer 2 circuit end to end using neighbor signaling, pseudowire identifiers and operational connection state before changing customer VLANs.
Explanation
Correct Answer
D:The case-specific routing and services action is: Trace an LDP Layer 2 circuit end to end using neighbor signaling, pseudowire identifiers and operational connection state before changing customer VLANs.
Incorrect Answers
A:This alternative proposes: Diagnose unknown unicast flooding and Layer 2 loops by distinguishing learned customer MAC paths, BUM handling and VPLS split-horizon behavior. It concerns a different Junos engineering issue VPLS MAC learning flooding and split-horizon safeguards, not the directly tested provider-network issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers.
B:This alternative proposes: Select the supported inter-AS or carrier-of-carriers VPN interconnection model according to trust, labels, MP-BGP signaling and administrative boundary requirements. It concerns a different Junos engineering issue Interprovider Layer 3 VPN options and carrier of carriers, not the directly tested provider-network issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers.
C:This alternative proposes: Verify service MTU and any supported pseudowire encapsulation/control-word expectations when a pseudowire is signaled Up but customer frames fail. It concerns a different Junos engineering issue Layer 2 pseudowire MTU and control-word interworking, not the directly tested provider-network issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers.
Question 427
A provider routing design review considers this situation. Two provider nodes have reachable loopbacks yet their Layer 2 circuit remains Down due to missing LDP signaling and the operator attempts to modify BGP unicast policy instead. A colleague proposes: Trace an LDP Layer 2 circuit end to end using neighbor signaling, pseudowire identifiers and operational connection state before changing customer VLANs. Which technical principle BEST supports that action? Select ONE best answer.
- VPLS site identification and multihoming mechanisms help coordinate PE access, but customer-facing redundant paths need a supported convergence and loop-control design.
- A BGP-signaled Layer 2 VPN advertises service-related NLRI and label reachability; route-target and instance-policy behavior determine which remote service participates.
- IS-IS elects a DIS on a broadcast segment to originate pseudonode information; it has no OSPF-style separately elected backup designated router, and election behavior differs.
- An LDP-signaled pseudowire uses locally and remotely agreed circuit identifiers, transport paths and VC labels; mismatched endpoints or identifiers can prevent service Up state.
Explanation
Correct Answer
D:The relevant Junos service-provider networking principle is: An LDP-signaled pseudowire uses locally and remotely agreed circuit identifiers, transport paths and VC labels; mismatched endpoints or identifiers can prevent service Up state. In the described provider-network case (Two provider nodes have reachable loopbacks yet their Layer 2 circuit remains Down due to missing LDP signaling and the operator attempts to modify BGP unicast policy instead.), it supports the planned action: Trace an LDP Layer 2 circuit end to end using neighbor signaling, pseudowire identifiers and operational connection state before changing customer VLANs.
Incorrect Answers
A:This alternative proposes: VPLS site identification and multihoming mechanisms help coordinate PE access, but customer-facing redundant paths need a supported convergence and loop-control design. It concerns a different Junos engineering issue VPLS site identifiers multihoming and service convergence, not the directly tested provider-network issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers.
B:This alternative proposes: A BGP-signaled Layer 2 VPN advertises service-related NLRI and label reachability; route-target and instance-policy behavior determine which remote service participates. It concerns a different Junos engineering issue BGP-signaled Layer 2 VPN NLRI and route target import, not the directly tested provider-network issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers.
C:This alternative proposes: IS-IS elects a DIS on a broadcast segment to originate pseudonode information; it has no OSPF-style separately elected backup designated router, and election behavior differs. It concerns a different Junos engineering issue IS-IS DIS pseudonode and broadcast circuit election, not the directly tested provider-network issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers.
Question 428
A Juniper service-provider engineer needs decisive verification evidence for this situation. Two provider nodes have reachable loopbacks yet their Layer 2 circuit remains Down due to missing LDP signaling and the operator attempts to modify BGP unicast policy instead. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Compare CE frame sizes, attachment-circuit encapsulation, pseudowire MTU, control-word configuration, interface drops and forwarding test results at both PEs.
- Inspect show l2circuit connections, LDP session state, neighbor addresses, VC IDs, service-facing interfaces and transport LSP reachability.
- Inspect BGP family negotiation, received Layer 2 VPN routes, RD/RT communities, service site identifiers, label mapping and per-instance state.
- Examine scheduler-map bindings, allocated rates, interface queue statistics, high-priority activity and low-priority drain rate under load.
Explanation
Correct Answer
B:The direct discriminating observation is: Inspect show l2circuit connections, LDP session state, neighbor addresses, VC IDs, service-facing interfaces and transport LSP reachability. In the stated situation (Two provider nodes have reachable loopbacks yet their Layer 2 circuit remains Down due to missing LDP signaling and the operator attempts to modify BGP unicast policy instead.), the intended acceptance outcome is: The two attachment circuits join only their authorized sites and the pseudowire status and customer traffic counters remain stable.
Incorrect Answers
A:This alternative proposes: Compare CE frame sizes, attachment-circuit encapsulation, pseudowire MTU, control-word configuration, interface drops and forwarding test results at both PEs. It concerns a different Junos engineering issue Layer 2 pseudowire MTU and control-word interworking, not the directly tested provider-network issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers.
C:This alternative proposes: Inspect BGP family negotiation, received Layer 2 VPN routes, RD/RT communities, service site identifiers, label mapping and per-instance state. It concerns a different Junos engineering issue BGP-signaled Layer 2 VPN NLRI and route target import, not the directly tested provider-network issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers.
D:This alternative proposes: Examine scheduler-map bindings, allocated rates, interface queue statistics, high-priority activity and low-priority drain rate under load. It concerns a different Junos engineering issue CoS schedulers scheduler-maps and bandwidth sharing, not the directly tested provider-network issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers.
Question 429
A service-provider acceptance team reviews the result of a provider-service change. Two provider nodes have reachable loopbacks yet their Layer 2 circuit remains Down due to missing LDP signaling and the operator attempts to modify BGP unicast policy instead. The intended verification is: Inspect show l2circuit connections, LDP session state, neighbor addresses, VC IDs, service-facing interfaces and transport LSP reachability. Which outcome BEST demonstrates success? Select ONE best answer.
- Customer dual-homing provides the intended redundancy without duplicate broadcast delivery or loss of reachability when either PE fails.
- Customer traffic follows learned remote PE paths and floods only where required without generating a provider-wide bridging loop.
- The two attachment circuits join only their authorized sites and the pseudowire status and customer traffic counters remain stable.
- The intended external subnet is reachable under the area policy without exposing all provider external LSAs to remote access routers.
Explanation
Correct Answer
C:The verified success outcome is: The two attachment circuits join only their authorized sites and the pseudowire status and customer traffic counters remain stable. Confirm this by: Inspect show l2circuit connections, LDP session state, neighbor addresses, VC IDs, service-facing interfaces and transport LSP reachability. The related controlled intervention is: Trace an LDP Layer 2 circuit end to end using neighbor signaling, pseudowire identifiers and operational connection state before changing customer VLANs.
Incorrect Answers
A:That option concerns EVPN Ethernet segment multihoming and designated forwarder. The related controlled intervention is: Trace an LDP Layer 2 circuit end to end using neighbor signaling, pseudowire identifiers and operational connection state before changing customer VLANs.
B:This alternative proposes: Customer traffic follows learned remote PE paths and floods only where required without generating a provider-wide bridging loop. It concerns a different Junos engineering issue VPLS MAC learning flooding and split-horizon safeguards, not the directly tested provider-network issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers.
D:That option concerns OSPF stub NSSA and external LSA handling. The related controlled intervention is: Trace an LDP Layer 2 circuit end to end using neighbor signaling, pseudowire identifiers and operational connection state before changing customer VLANs.
Question 430
A Junos service-provider routing engineer investigates this service-provider network scenario. Two provider nodes have reachable loopbacks yet their Layer 2 circuit remains Down due to missing LDP signaling and the operator attempts to modify BGP unicast policy instead. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.
- Select the supported inter-AS or carrier-of-carriers VPN interconnection model according to trust, labels, MP-BGP signaling and administrative boundary requirements.
- Trace an LDP Layer 2 circuit end to end using neighbor signaling, pseudowire identifiers and operational connection state before changing customer VLANs.
- Use reverse-path forwarding checks to determine why an arriving multicast packet is accepted on one interface but discarded on another.
- Inspect show l2circuit connections, LDP session state, neighbor addresses, VC IDs, service-facing interfaces and transport LSP reachability.
- Compare CE frame sizes, attachment-circuit encapsulation, pseudowire MTU, control-word configuration, interface drops and forwarding test results at both PEs.
Explanation
Correct Answers
B:The case-specific routing and services action is: Trace an LDP Layer 2 circuit end to end using neighbor signaling, pseudowire identifiers and operational connection state before changing customer VLANs. Verify the decision through: Inspect show l2circuit connections, LDP session state, neighbor addresses, VC IDs, service-facing interfaces and transport LSP reachability.
D:The direct discriminating observation is: Inspect show l2circuit connections, LDP session state, neighbor addresses, VC IDs, service-facing interfaces and transport LSP reachability.
Incorrect Answers
A:This alternative proposes: Select the supported inter-AS or carrier-of-carriers VPN interconnection model according to trust, labels, MP-BGP signaling and administrative boundary requirements. It concerns a different Junos engineering issue Interprovider Layer 3 VPN options and carrier of carriers, not the directly tested provider-network issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers in the stated situation (Two provider nodes have reachable loopbacks yet their Layer 2 circuit remains Down due to missing LDP signaling and the operator attempts to modify BGP unicast policy instead.). A better case-specific check is: Inspect show l2circuit connections, LDP session state, neighbor addresses, VC IDs, service-facing interfaces and transport LSP reachability. The more targeted action is: Trace an LDP Layer 2 circuit end to end using neighbor signaling, pseudowire identifiers and operational connection state before changing customer VLANs.
C:This alternative proposes: Use reverse-path forwarding checks to determine why an arriving multicast packet is accepted on one interface but discarded on another. It concerns a different Junos engineering issue Multicast RPF validation and source reachability, not the directly tested provider-network issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers.
E:This alternative proposes: Compare CE frame sizes, attachment-circuit encapsulation, pseudowire MTU, control-word configuration, interface drops and forwarding test results at both PEs. It concerns a different Junos engineering issue Layer 2 pseudowire MTU and control-word interworking, not the directly tested provider-network issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers in the stated situation (Two provider nodes have reachable loopbacks yet their Layer 2 circuit remains Down due to missing LDP signaling and the operator attempts to modify BGP unicast policy instead.). A better case-specific check is: Inspect show l2circuit connections, LDP session state, neighbor addresses, VC IDs, service-facing interfaces and transport LSP reachability. The more targeted action is: Trace an LDP Layer 2 circuit end to end using neighbor signaling, pseudowire identifiers and operational connection state before changing customer VLANs.