McAfee-Secured Website

Exam Bundle

Exam Code: 350-501

Exam Name Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR)

Certification Provider: Cisco

Corresponding Certifications: CCIE Service Provider , CCNP Service Provider

Cisco 350-501 Bundle $28.79

100% Cisco 350-501 Guaranteed Success With Testking Training Materials

Get Real 350-501 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    350-501 Questions & Answers

    528 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual 350-501 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • 350-501 Video Course

    350-501 Video Course

    253 Video Lectures

    350-501 Video Course is developed by Cisco Professionals to help you pass the 350-501 exam.

    Description

    This course will improve your knowledge and skills required to pass Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR) exam.
  • Study Guide

    350-501 Study Guide

    1160 PDF Pages

    Developed by industry experts, this 1160-page guide spells out in painstaking detail all of the information you need to ace 350-501 exam.

Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR) (350-501) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $189.97
Bundle Price: $161.18

Purchase Individually

  • Questions & Answers

    Questions & Answers

    528 Questions

    $124.99
  • 350-501 Video Course

    Video Course

    253 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    1160 PDF Pages

    $24.99

Cisco 350-501 Practice Test 73

Question 720

To prevent recurrence of this provider network issue: A provider applies MPLS LSP ping only to the global transport loopback while a customer L3VPN remains broken, then claims VPN reachability is fully proven. Which control should be retained?

  1. Measure end-to-end label-stack MTU at every new pseudowire deployment.
  2. Monitor protected-session status and route-to-transport-loopback reachability.
  3. Include transport and service-layer OAM in VPN fault playbooks.
  4. Record reoptimization stability and path-change rate in monitoring.

Explanation

Correct Answer

C:

Include transport and service-layer OAM in VPN fault playbooks. This helps prevent recurrence of the issue: A provider applies MPLS LSP ping only to the global transport loopback while a customer L3VPN remains broken, then claims VPN reachability is fully proven. Acceptance evidence should be: The test isolates a healthy transport LSP from a missing inner VPN route or label binding.

Incorrect Answers

A:

Measure end-to-end label-stack MTU at every new pseudowire deployment. That is a sensible control for ANOTHER scenario: An MPLS pseudowire intermittently drops large customer frames after VLAN tagging increases payload size beyond a transit link's supported frame budget. It is less targeted to this issue than: Include transport and service-layer OAM in VPN fault playbooks.

B:

Monitor protected-session status and route-to-transport-loopback reachability. That is a sensible control for ANOTHER scenario: An LDP transport session disappears whenever the direct router-to-router interface flaps, despite an alternate routed path existing between stable loopbacks. It is less targeted to this issue than: Include transport and service-layer OAM in VPN fault playbooks.

D:

Record reoptimization stability and path-change rate in monitoring. That is a sensible control for ANOTHER scenario: A tunnel between regional PEs oscillates because an optimizer recomputes explicit paths on every small telemetry fluctuation. It is less targeted to this issue than: Include transport and service-layer OAM in VPN fault playbooks.

Question 721

At a converged broadband aggregation team, an engineering review finds: A backbone planner expects constrained TE to calculate alternate paths while the IGP advertises only basic reachability and no extended TE link attributes. Which change most directly corrects the service problem?

  1. Enable supported IS-IS or OSPF TE extensions and validate link attribute advertisement before computing constrained paths.
  2. Install the intended route or autoroute steering policy into the established TE tunnel without affecting unrelated prefixes.
  3. Inspect RSVP reservation state and remove stale or excess allocations through supported teardown and reconciliation.
  4. Enable the agreed algorithm definition and participation on all required forwarding nodes or avoid steering through unsupported paths.

Explanation

Correct Answer

A:

Enable supported IS-IS or OSPF TE extensions and validate link attribute advertisement before computing constrained paths. This directly addresses the fictional service-provider network case: A backbone planner expects constrained TE to calculate alternate paths while the IGP advertises only basic reachability and no extended TE link attributes. The technical mechanism is: Link-state TE extensions carry topology attributes beyond ordinary SPF metrics for path computation. Verify success by: The TE database contains capacity and administrative-group information for all selected links and the constraint solver returns a valid route.

Incorrect Answers

B:

Install the intended route or autoroute steering policy into the established TE tunnel without affecting unrelated prefixes. This would respond to a DIFFERENT fictional service-provider network issue: The route processor shows an RSVP-TE tunnel Up, but a live traffic test still traverses native IGP forwarding because the tunnel is not selected for the destination. It does not directly address the current situation: A backbone planner expects constrained TE to calculate alternate paths while the IGP advertises only basic reachability and no extended TE link attributes.

C:

Inspect RSVP reservation state and remove stale or excess allocations through supported teardown and reconciliation. This would respond to a DIFFERENT fictional service-provider network issue: One router reports TE bandwidth exhausted even though link counters show the circuit nearly idle, and operators increase interface speed without investigating reservations. It does not directly address the current situation: A backbone planner expects constrained TE to calculate alternate paths while the IGP advertises only basic reachability and no extended TE link attributes.

D:

Enable the agreed algorithm definition and participation on all required forwarding nodes or avoid steering through unsupported paths. This would respond to a DIFFERENT fictional service-provider network issue: A Flexible Algorithm is activated only on a subset of routers and a service prefix uses a Flex-Algo SID that transit nodes cannot resolve. It does not directly address the current situation: A backbone planner expects constrained TE to calculate alternate paths while the IGP advertises only basic reachability and no extended TE link attributes.

Question 722

For a converged broadband aggregation team, operators addressed: A backbone planner expects constrained TE to calculate alternate paths while the IGP advertises only basic reachability and no extended TE link attributes. What is the strongest acceptance evidence?

  1. Available TE reservable bandwidth rises in line with released legitimate reservations without changing the physical capacity.
  2. The TE database contains capacity and administrative-group information for all selected links and the constraint solver returns a valid route.
  3. Simulated loss of one shared optical component leaves the backup LSP on a truly independent facility.
  4. A maximal permitted label-stack test forwards across the planned platform while an unsupported stack is rejected during provisioning.

Explanation

Correct Answer

B:

The TE database contains capacity and administrative-group information for all selected links and the constraint solver returns a valid route. This confirms the approved response: Enable supported IS-IS or OSPF TE extensions and validate link attribute advertisement before computing constrained paths. It is relevant because: Link-state TE extensions carry topology attributes beyond ordinary SPF metrics for path computation.

Incorrect Answers

A:

Available TE reservable bandwidth rises in line with released legitimate reservations without changing the physical capacity. This would validate ANOTHER scenario: One router reports TE bandwidth exhausted even though link counters show the circuit nearly idle, and operators increase interface speed without investigating reservations. The specific correction here is: Enable supported IS-IS or OSPF TE extensions and validate link attribute advertisement before computing constrained paths.

C:

Simulated loss of one shared optical component leaves the backup LSP on a truly independent facility. This would validate ANOTHER scenario: A traffic engineering policy considers only link bandwidth when selecting primary and backup paths, but both use one optical shared-risk group. The specific correction here is: Enable supported IS-IS or OSPF TE extensions and validate link attribute advertisement before computing constrained paths.

D:

A maximal permitted label-stack test forwards across the planned platform while an unsupported stack is rejected during provisioning. This would validate ANOTHER scenario: A core node imposes two service labels on an access interface with a hardware label-stack depth limit below the engineered VPN service, causing selective drops. The specific correction here is: Enable supported IS-IS or OSPF TE extensions and validate link attribute advertisement before computing constrained paths.

Question 723

Which network protocol or forwarding behavior explains the following issue: A backbone planner expects constrained TE to calculate alternate paths while the IGP advertises only basic reachability and no extended TE link attributes.

  1. Make-before-break can retain service continuity while TE paths are re-signaled, provided temporary bandwidth and state exist.
  2. Constrained Shortest Path First relies on advertised TE attributes and can make incorrect admission decisions if topology data is stale.
  3. Link-state TE extensions carry topology attributes beyond ordinary SPF metrics for path computation.
  4. MPLS stacks separate outer transport forwarding from inner VPN service identification, and PHP must not erase the service label.

Explanation

Correct Answer

C:

Link-state TE extensions carry topology attributes beyond ordinary SPF metrics for path computation. This explains the investigated issue: A backbone planner expects constrained TE to calculate alternate paths while the IGP advertises only basic reachability and no extended TE link attributes. The approved corrective response is: Enable supported IS-IS or OSPF TE extensions and validate link attribute advertisement before computing constrained paths.

Incorrect Answers

A:

Make-before-break can retain service continuity while TE paths are re-signaled, provided temporary bandwidth and state exist. That explains a DIFFERENT scenario: A provisioning system attempts to reoptimize an RSVP LSP using a new path but drops the existing path before the replacement is established, causing service interruption. The mechanism to prioritize for this question is: Link-state TE extensions carry topology attributes beyond ordinary SPF metrics for path computation.

B:

Constrained Shortest Path First relies on advertised TE attributes and can make incorrect admission decisions if topology data is stale. That explains a DIFFERENT scenario: An MPLS traffic-engineering tunnel reserves 500 Mbps but physically traverses a 100 Mbps access link because the advertised TE bandwidth attributes are stale. The mechanism to prioritize for this question is: Link-state TE extensions carry topology attributes beyond ordinary SPF metrics for path computation.

D:

MPLS stacks separate outer transport forwarding from inner VPN service identification, and PHP must not erase the service label. That explains a DIFFERENT scenario: A transit router keeps unexpectedly popping a provider's VPN label one hop before the target PE, sending customer traffic toward the global routing table. The mechanism to prioritize for this question is: Link-state TE extensions carry topology attributes beyond ordinary SPF metrics for path computation.

Question 724

A core network change board wants to avoid: A backbone planner expects constrained TE to calculate alternate paths while the IGP advertises only basic reachability and no extended TE link attributes. Which ongoing safeguard fits best?

  1. Audit RSVP reservation lifetimes and headend ownership regularly.
  2. Maintain optical SRLG metadata with core IGP-TE inventory.
  3. Monitor protected-session status and route-to-transport-loopback reachability.
  4. Include TE database completeness checks during IGP maintenance.

Explanation

Correct Answer

D:

Include TE database completeness checks during IGP maintenance. This helps prevent recurrence of the issue: A backbone planner expects constrained TE to calculate alternate paths while the IGP advertises only basic reachability and no extended TE link attributes. Acceptance evidence should be: The TE database contains capacity and administrative-group information for all selected links and the constraint solver returns a valid route.

Incorrect Answers

A:

Audit RSVP reservation lifetimes and headend ownership regularly. That is a sensible control for ANOTHER scenario: One router reports TE bandwidth exhausted even though link counters show the circuit nearly idle, and operators increase interface speed without investigating reservations. It is less targeted to this issue than: Include TE database completeness checks during IGP maintenance.

B:

Maintain optical SRLG metadata with core IGP-TE inventory. That is a sensible control for ANOTHER scenario: A traffic engineering policy considers only link bandwidth when selecting primary and backup paths, but both use one optical shared-risk group. It is less targeted to this issue than: Include TE database completeness checks during IGP maintenance.

C:

Monitor protected-session status and route-to-transport-loopback reachability. That is a sensible control for ANOTHER scenario: An LDP transport session disappears whenever the direct router-to-router interface flaps, despite an alternate routed path existing between stable loopbacks. It is less targeted to this issue than: Include TE database completeness checks during IGP maintenance.

Question 725

A carrier service activation check discovers: An ingress PE applies SRv6 encapsulation but an interworking gateway only supports MPLS label forwarding, so remote L3VPN traffic cannot cross the domain boundary. Which action best restores the intended behavior?

  1. Align micro-segment block, locator and local function behavior on every participating SRv6 node.
  2. Implement the supported SRv6-to-MPLS service interworking behavior or keep the service within compatible transport domains.
  3. Bind the service SID's decapsulation and table lookup behavior to the intended customer VRF.
  4. Set explicit TE priority and bandwidth allocation policies for the intended service classes.

Explanation

Correct Answer

B:

Implement the supported SRv6-to-MPLS service interworking behavior or keep the service within compatible transport domains. This directly addresses the fictional service-provider network case: An ingress PE applies SRv6 encapsulation but an interworking gateway only supports MPLS label forwarding, so remote L3VPN traffic cannot cross the domain boundary. The technical mechanism is: SRv6 SIDs and MPLS labels represent different forwarding architectures requiring explicit conversion at an interworking point. Verify success by: An isolated service-prefix test traverses the gateway with the expected service context preserved.

Incorrect Answers

A:

Align micro-segment block, locator and local function behavior on every participating SRv6 node. This would respond to a DIFFERENT fictional service-provider network issue: A provider compresses SRv6 micro-segments into a uSID container but configures an incompatible locator block structure on one endpoint, breaking the final function lookup. It does not directly address the current situation: An ingress PE applies SRv6 encapsulation but an interworking gateway only supports MPLS label forwarding, so remote L3VPN traffic cannot cross the domain boundary.

C:

Bind the service SID's decapsulation and table lookup behavior to the intended customer VRF. This would respond to a DIFFERENT fictional service-provider network issue: An SRv6 egress router discards traffic because a local End.DT4 service SID is placed in the wrong VRF context, even though the locator is reachable. It does not directly address the current situation: An ingress PE applies SRv6 encapsulation but an interworking gateway only supports MPLS label forwarding, so remote L3VPN traffic cannot cross the domain boundary.

D:

Set explicit TE priority and bandwidth allocation policies for the intended service classes. This would respond to a DIFFERENT fictional service-provider network issue: A provider enables RSVP bandwidth reservation but leaves all tunnels with one identical setup and holding priority, making critical voice LSP preemption unpredictable. It does not directly address the current situation: An ingress PE applies SRv6 encapsulation but an interworking gateway only supports MPLS label forwarding, so remote L3VPN traffic cannot cross the domain boundary.

Question 726

Following a supported configuration correction, the original issue was: An ingress PE applies SRv6 encapsulation but an interworking gateway only supports MPLS label forwarding, so remote L3VPN traffic cannot cross the domain boundary. Which observation verifies success?

  1. Flex-Algo route and SID tables show a consistent constraint topology across the intended service path.
  2. A test packet advances through the micro-segment sequence and exits at the intended service SID.
  3. An isolated service-prefix test traverses the gateway with the expected service context preserved.
  4. A stress test admits or rejects reservations according to the per-class budget without starving the protected class.

Explanation

Correct Answer

C:

An isolated service-prefix test traverses the gateway with the expected service context preserved. This confirms the approved response: Implement the supported SRv6-to-MPLS service interworking behavior or keep the service within compatible transport domains. It is relevant because: SRv6 SIDs and MPLS labels represent different forwarding architectures requiring explicit conversion at an interworking point.

Incorrect Answers

A:

Flex-Algo route and SID tables show a consistent constraint topology across the intended service path. This would validate ANOTHER scenario: A Flexible Algorithm is activated only on a subset of routers and a service prefix uses a Flex-Algo SID that transit nodes cannot resolve. The specific correction here is: Implement the supported SRv6-to-MPLS service interworking behavior or keep the service within compatible transport domains.

B:

A test packet advances through the micro-segment sequence and exits at the intended service SID. This would validate ANOTHER scenario: A provider compresses SRv6 micro-segments into a uSID container but configures an incompatible locator block structure on one endpoint, breaking the final function lookup. The specific correction here is: Implement the supported SRv6-to-MPLS service interworking behavior or keep the service within compatible transport domains.

D:

A stress test admits or rejects reservations according to the per-class budget without starving the protected class. This would validate ANOTHER scenario: Two DS-TE class types share one link, but one tunnel consumes the other class's reserved budget due to a misconfigured bandwidth constraint allocation. The specific correction here is: Implement the supported SRv6-to-MPLS service interworking behavior or keep the service within compatible transport domains.

Question 727

At an inter-AS service aggregation carrier, an engineer examines: An ingress PE applies SRv6 encapsulation but an interworking gateway only supports MPLS label forwarding, so remote L3VPN traffic cannot cross the domain boundary. Which technical principle is most applicable?

  1. SR Flexible Algorithm computes paths using a shared algorithm definition and participant capability set, not ordinary best-effort SPF alone.
  2. SRv6 End.DT4 behavior couples decapsulation to an IPv4 table lookup and must be associated with the right service routing context.
  3. MPLS transport routers do not normally maintain customer VRFs or service labels for all VPN destinations.
  4. SRv6 SIDs and MPLS labels represent different forwarding architectures requiring explicit conversion at an interworking point.

Explanation

Correct Answer

D:

SRv6 SIDs and MPLS labels represent different forwarding architectures requiring explicit conversion at an interworking point. This explains the investigated issue: An ingress PE applies SRv6 encapsulation but an interworking gateway only supports MPLS label forwarding, so remote L3VPN traffic cannot cross the domain boundary. The approved corrective response is: Implement the supported SRv6-to-MPLS service interworking behavior or keep the service within compatible transport domains.

Incorrect Answers

A:

SR Flexible Algorithm computes paths using a shared algorithm definition and participant capability set, not ordinary best-effort SPF alone. That explains a DIFFERENT scenario: A Flexible Algorithm is activated only on a subset of routers and a service prefix uses a Flex-Algo SID that transit nodes cannot resolve. The mechanism to prioritize for this question is: SRv6 SIDs and MPLS labels represent different forwarding architectures requiring explicit conversion at an interworking point.

B:

SRv6 End.DT4 behavior couples decapsulation to an IPv4 table lookup and must be associated with the right service routing context. That explains a DIFFERENT scenario: An SRv6 egress router discards traffic because a local End.DT4 service SID is placed in the wrong VRF context, even though the locator is reachable. The mechanism to prioritize for this question is: SRv6 SIDs and MPLS labels represent different forwarding architectures requiring explicit conversion at an interworking point.

C:

MPLS transport routers do not normally maintain customer VRFs or service labels for all VPN destinations. That explains a DIFFERENT scenario: A P router allocates labels for customer routes that should only exist at the VRF-aware PE, and the core sees unexpected VPN forwarding context. The mechanism to prioritize for this question is: SRv6 SIDs and MPLS labels represent different forwarding architectures requiring explicit conversion at an interworking point.

Question 728

For an inter-AS service aggregation carrier, the change record describes: An ingress PE applies SRv6 encapsulation but an interworking gateway only supports MPLS label forwarding, so remote L3VPN traffic cannot cross the domain boundary. What preventive validation should be standard?

  1. Verify control-plane service route labels and locator reachability across interdomain handoffs.
  2. Distinguish SR policy state from RSVP-TE tunnel state in operational runbooks.
  3. Verify local SID behaviors and VRF bindings during VPN service provisioning.
  4. Track per-platform maximum label-stack depth in service design inventory.

Explanation

Correct Answer

A:

Verify control-plane service route labels and locator reachability across interdomain handoffs. This helps prevent recurrence of the issue: An ingress PE applies SRv6 encapsulation but an interworking gateway only supports MPLS label forwarding, so remote L3VPN traffic cannot cross the domain boundary. Acceptance evidence should be: An isolated service-prefix test traverses the gateway with the expected service context preserved.

Incorrect Answers

B:

Distinguish SR policy state from RSVP-TE tunnel state in operational runbooks. That is a sensible control for ANOTHER scenario: A provider enables SR-MPLS forwarding but assumes each SR-TE path requires RSVP-TE state on every transit router, blocking deployment when RSVP is disabled. It is less targeted to this issue than: Verify control-plane service route labels and locator reachability across interdomain handoffs.

C:

Verify local SID behaviors and VRF bindings during VPN service provisioning. That is a sensible control for ANOTHER scenario: An SRv6 egress router discards traffic because a local End.DT4 service SID is placed in the wrong VRF context, even though the locator is reachable. It is less targeted to this issue than: Verify control-plane service route labels and locator reachability across interdomain handoffs.

D:

Track per-platform maximum label-stack depth in service design inventory. That is a sensible control for ANOTHER scenario: A core node imposes two service labels on an access interface with a hardware label-stack depth limit below the engineered VPN service, causing selective drops. It is less targeted to this issue than: Verify control-plane service route labels and locator reachability across interdomain handoffs.

Question 729

For a regional service-provider operations center, the failure is: An inter-AS EVPN service advertises Ethernet MAC routes across the border without the expected next-hop and encapsulation capabilities, leaving routes visible but unusable. Which authorized correction best addresses it?

  1. Keep tenant multicast routing contexts and mVPN signaling separate across the provider transport.
  2. Validate EVPN MAC mobility extended communities and accept the newer sequence state under supported mobility procedures.
  3. Align border-gateway EVPN route exchange, next-hop reachability and tunnel encapsulation compatibility.
  4. Inspect and configure MLD listener state for IPv6 independently from IPv4 IGMP.

Explanation

Correct Answer

C:

Align border-gateway EVPN route exchange, next-hop reachability and tunnel encapsulation compatibility. This directly addresses the fictional service-provider network case: An inter-AS EVPN service advertises Ethernet MAC routes across the border without the expected next-hop and encapsulation capabilities, leaving routes visible but unusable. The technical mechanism is: EVPN route reachability depends on both MP-BGP control-plane exchange and usable data-plane tunnel endpoints. Verify success by: A remote MAC route resolves to the correct border and service encapsulation and transmits a unicast frame.

Incorrect Answers

A:

Keep tenant multicast routing contexts and mVPN signaling separate across the provider transport. This would respond to a DIFFERENT fictional service-provider network issue: A multicast VPN customer uses overlapping group addresses with another tenant, and the service provider combines the flows into one global multicast state. It does not directly address the current situation: An inter-AS EVPN service advertises Ethernet MAC routes across the border without the expected next-hop and encapsulation capabilities, leaving routes visible but unusable.

B:

Validate EVPN MAC mobility extended communities and accept the newer sequence state under supported mobility procedures. This would respond to a DIFFERENT fictional service-provider network issue: Two PEs establish BGP EVPN but remote MAC mobility updates are ignored because a device keeps an older sequence number as authoritative. It does not directly address the current situation: An inter-AS EVPN service advertises Ethernet MAC routes across the border without the expected next-hop and encapsulation capabilities, leaving routes visible but unusable.

D:

Inspect and configure MLD listener state for IPv6 independently from IPv4 IGMP. This would respond to a DIFFERENT fictional service-provider network issue: An IPv6 multicast receiver joins an MLDv2 group, but the adjacent router polls only IGMP state and reports no listeners. It does not directly address the current situation: An inter-AS EVPN service advertises Ethernet MAC routes across the border without the expected next-hop and encapsulation capabilities, leaving routes visible but unusable.

Question 730

After fixing the following network problem, what should the team verify: An inter-AS EVPN service advertises Ethernet MAC routes across the border without the expected next-hop and encapsulation capabilities, leaving routes visible but unusable.

  1. A remote customer VRF imports the approved prefix and delivers labeled packets across both provider ASes.
  2. A lab MAC route from tenant A does not enter tenant B's MAC-VRF while shared authorized services remain reachable.
  3. A lab traffic test passes with consistent pseudowire labels and expected Ethernet frame format.
  4. A remote MAC route resolves to the correct border and service encapsulation and transmits a unicast frame.

Explanation

Correct Answer

D:

A remote MAC route resolves to the correct border and service encapsulation and transmits a unicast frame. This confirms the approved response: Align border-gateway EVPN route exchange, next-hop reachability and tunnel encapsulation compatibility. It is relevant because: EVPN route reachability depends on both MP-BGP control-plane exchange and usable data-plane tunnel endpoints.

Incorrect Answers

A:

A remote customer VRF imports the approved prefix and delivers labeled packets across both provider ASes. This would validate ANOTHER scenario: An inter-AS L3VPN reaches the first provider but customer prefixes vanish at the AS boundary because VPNv4 routes and label context are not exchanged under the chosen inter-AS model. The specific correction here is: Align border-gateway EVPN route exchange, next-hop reachability and tunnel encapsulation compatibility.

B:

A lab MAC route from tenant A does not enter tenant B's MAC-VRF while shared authorized services remain reachable. This would validate ANOTHER scenario: A provider imports all EVPN routes from every retail tenant into one MAC-VRF, and identical MAC addresses cause cross-customer service confusion. The specific correction here is: Align border-gateway EVPN route exchange, next-hop reachability and tunnel encapsulation compatibility.

C:

A lab traffic test passes with consistent pseudowire labels and expected Ethernet frame format. This would validate ANOTHER scenario: A layer-2 pseudowire on two PEs is signaled Up but customer frames are dropped because local and remote pseudowire encapsulation modes differ. The specific correction here is: Align border-gateway EVPN route exchange, next-hop reachability and tunnel encapsulation compatibility.