Question 960
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: A new PE receives EVPN advertisements from its reflector but the intended EVI does not contain any remote MAC entries. Which operational control would best prevent a recurrence of this exact failure mode?
- Audit VPN identifiers before consolidating L2VPN routes on shared reflectors.
- Test failover with previously learned MACs rather than only unknown destination frames.
- Track control-plane MAC routes alongside local bridge-table entries.
- Run per-EVI negative and positive import checks during onboarding.
Explanation
Correct Answer
D:Run per-EVI negative and positive import checks during onboarding. The control limits repetition of the described root condition: BGP EVPN route receipt and local service membership are separate; route targets control eligible imports. During audits, confirm: The EVI imports only its authorized remote MAC reachability when RT settings match.
Incorrect Answers
A:Audit VPN identifiers before consolidating L2VPN routes on shared reflectors. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically BGP Layer 2 VPN route distinguisher. BGP-signaled L2VPN routes need distinguishable VPN identifiers so unrelated overlapping customer service advertisements do not collide. In this scenario, however, the distinguishing issue is EVPN BGP route target not imported and the confirming observation is: The EVI imports only its authorized remote MAC reachability when RT settings match.
B:Test failover with previously learned MACs rather than only unknown destination frames. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically VPLS MAC withdrawal timing. VPLS forwarding uses learned MAC entries; stale bindings may persist until aging or explicit flush removes them. In this scenario, however, the distinguishing issue is EVPN BGP route target not imported and the confirming observation is: The EVI imports only its authorized remote MAC reachability when RT settings match.
C:Track control-plane MAC routes alongside local bridge-table entries. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically EVPN MAC reachability signaling. EVPN can distribute learned customer MAC reachability through BGP control-plane type 2 routes instead of relying only on data-plane flooding. In this scenario, however, the distinguishing issue is EVPN BGP route target not imported and the confirming observation is: The EVI imports only its authorized remote MAC reachability when RT settings match.
Question 961
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: An EVPN type 2 route is accepted but data traffic still fails because the advertising PE's transport next hop cannot be reached. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect EVPN BGP next-hop resolution and the MPLS transport or VXLAN encapsulation path in use.
- Compare remote label mapping and withdraw state against the targeted LDP session.
- Inspect targeted LDP hello and TCP session status between the pseudowire endpoints.
- Inspect Ethernet segment reachability advertisements and fast convergence or mass-withdraw behavior.
Explanation
Correct Answer
A:Inspect EVPN BGP next-hop resolution and the MPLS transport or VXLAN encapsulation path in use. This check examines the decisive condition for EVPN core route resolution before any unrelated changes are made. The underlying mechanism is: EVPN control-plane MAC information needs an independently working transport data plane to deliver frames. The confirming observation is: The remote PE next hop and encapsulation path are valid and frames reach the advertised MAC.
Incorrect Answers
B:Compare remote label mapping and withdraw state against the targeted LDP session. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically LDP pseudowire label withdrawal. An LDP pseudowire requires valid label bindings for its service, separate from availability of the transport LSP. In this scenario, however, the distinguishing issue is EVPN core route resolution and the confirming observation is: The remote PE next hop and encapsulation path are valid and frames reach the advertised MAC.
C: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 EVPN core route resolution and the confirming observation is: The remote PE next hop and encapsulation path are valid and frames reach the advertised MAC.
D:Inspect Ethernet segment reachability advertisements and fast convergence or mass-withdraw behavior. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically EVPN multihoming mass withdrawal. EVPN multihoming can signal a PE or segment failure so remote PEs quickly invalidate affected MAC reachability. In this scenario, however, the distinguishing issue is EVPN core route resolution and the confirming observation is: The remote PE next hop and encapsulation path are valid and frames reach the advertised MAC.
Question 962
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: An EVPN type 2 route is accepted but data traffic still fails because the advertising PE's transport next hop cannot be reached. Which routing or service mechanism best explains the reported behavior?
- An LDP pseudowire requires valid label bindings for its service, separate from availability of the transport LSP.
- 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
B:EVPN control-plane MAC information needs an independently working transport data plane to deliver frames. 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 next hop and encapsulation path are valid and frames reach the advertised MAC. The targeted correction is: Restore the relevant PE underlay or transport reachability before editing correct MAC advertisements.
Incorrect Answers
A:An LDP pseudowire requires valid label bindings for its service, separate from availability of the transport LSP. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically LDP pseudowire label withdrawal. An LDP pseudowire requires valid label bindings for its service, separate from availability of the transport LSP. In this scenario, however, the distinguishing issue is EVPN core route resolution and the confirming observation is: The remote PE next hop and encapsulation path are valid and frames reach the advertised MAC.
C: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 EVPN core route resolution and the confirming observation is: The remote PE next hop and encapsulation path are valid and frames reach the advertised MAC.
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 EVPN core route resolution and the confirming observation is: The remote PE next hop and encapsulation path are valid and frames reach the advertised MAC.
Question 963
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: An EVPN type 2 route is accepted but data traffic still fails because the advertising PE's transport next hop cannot be reached. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- A fresh valid service label mapping is present before forwarding is restored.
- The remote PE LDP session is established and exchanges the service label for the circuit.
- The remote PE next hop and encapsulation path are valid and frames reach the advertised MAC.
- Label switching to the far PE is operational and the service frames are delivered over the signaled circuit.
Explanation
Correct Answer
C:The remote PE next hop and encapsulation path are valid and frames reach the advertised MAC. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: EVPN control-plane MAC information needs an independently working transport data plane to deliver frames.
Incorrect Answers
A:A fresh valid service label mapping is present before forwarding is restored. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically LDP pseudowire label withdrawal. An LDP pseudowire requires valid label bindings for its service, separate from availability of the transport LSP. In this scenario, however, the distinguishing issue is EVPN core route resolution and the confirming observation is: The remote PE next hop and encapsulation path are valid and frames reach the advertised MAC.
B: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 EVPN core route resolution and the confirming observation is: The remote PE next hop and encapsulation path are valid and frames reach the advertised MAC.
D:Label switching to the far PE is operational and the service frames are delivered over the signaled circuit. This is a plausible observed evidence 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 EVPN core route resolution and the confirming observation is: The remote PE next hop and encapsulation path are valid and frames reach the advertised MAC.
Question 964
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: An EVPN type 2 route is accepted but data traffic still fails because the advertising PE's transport next hop cannot be reached. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Repair the remote service signaling and reestablish the expected VC label state.
- Restore the supported Ethernet segment failure signaling and backup forwarding path.
- Assign unique service site IDs and align site ranges according to the intended topology.
- Restore the relevant PE underlay or transport reachability before editing correct MAC advertisements.
Explanation
Correct Answer
D:Restore the relevant PE underlay or transport reachability before editing correct MAC advertisements. The change addresses the root behavior described here: EVPN control-plane MAC information needs an independently working transport data plane to deliver frames. Verify success with: The remote PE next hop and encapsulation path are valid and frames reach the advertised MAC.
Incorrect Answers
A:Repair the remote service signaling and reestablish the expected VC label state. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically LDP pseudowire label withdrawal. An LDP pseudowire requires valid label bindings for its service, separate from availability of the transport LSP. In this scenario, however, the distinguishing issue is EVPN core route resolution and the confirming observation is: The remote PE next hop and encapsulation path are valid and frames reach the advertised MAC.
B:Restore the supported Ethernet segment failure signaling and backup forwarding path. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically EVPN multihoming mass withdrawal. EVPN multihoming can signal a PE or segment failure so remote PEs quickly invalidate affected MAC reachability. In this scenario, however, the distinguishing issue is EVPN core route resolution and the confirming observation is: The remote PE next hop and encapsulation path are valid and frames reach the advertised MAC.
C:Assign unique service site IDs and align site ranges according to the intended topology. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically BGP L2VPN site ID collision. BGP L2VPN site identifiers help map distinct site attachments into the signaled service topology. In this scenario, however, the distinguishing issue is EVPN core route resolution and the confirming observation is: The remote PE next hop and encapsulation path are valid and frames reach the advertised MAC.
Question 965
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: An EVPN type 2 route is accepted but data traffic still fails because the advertising PE's transport next hop cannot be reached. Which operational control would best prevent a recurrence of this exact failure mode?
- Verify BGP EVPN routes and actual encapsulated packet forwarding independently.
- Track transport LSP reachability separately from targeted pseudowire signaling.
- Require both service label and transport label checks before declaring a pseudowire active.
- Monitor service-label mapping events apart from core transport failures.
Explanation
Correct Answer
A:Verify BGP EVPN routes and actual encapsulated packet forwarding independently. The control limits repetition of the described root condition: EVPN control-plane MAC information needs an independently working transport data plane to deliver frames. During audits, confirm: The remote PE next hop and encapsulation path are valid and frames reach the advertised MAC.
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 EVPN core route resolution and the confirming observation is: The remote PE next hop and encapsulation path are valid and frames reach the advertised MAC.
C: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 EVPN core route resolution and the confirming observation is: The remote PE next hop and encapsulation path are valid and frames reach the advertised MAC.
D:Monitor service-label mapping events apart from core transport failures. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically LDP pseudowire label withdrawal. An LDP pseudowire requires valid label bindings for its service, separate from availability of the transport LSP. In this scenario, however, the distinguishing issue is EVPN core route resolution and the confirming observation is: The remote PE next hop and encapsulation path are valid and frames reach the advertised MAC.
Question 966
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: Two EVPN participating sites use different local VLAN IDs for the same customer service and frames are unexpectedly dropped or leaked. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect VPLS MAC learning tables, aging and broadcast/unknown-unicast flood counters.
- Inspect EVI service type and ingress/egress VLAN normalization or translation settings.
- Inspect Ethernet segment identifier, DF election result and per-VLAN forwarder eligibility.
- Inspect duplicate MAC detection and mobility events before assuming a legitimate workload move.
Explanation
Correct Answer
B:Inspect EVI service type and ingress/egress VLAN normalization or translation settings. This check examines the decisive condition for VLAN normalization mismatch before any unrelated changes are made. The underlying mechanism is: EVPN can separate local VLAN identifiers from a shared service identity when correct translation and normalization are configured. The confirming observation is: Test frames from each local VLAN appear only on the intended counterpart service at the remote site.
Incorrect Answers
A:Inspect VPLS MAC learning tables, aging and broadcast/unknown-unicast flood counters. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically VPLS flooding unknown unicast. VPLS provides multipoint Ethernet bridging, so traffic to unknown MAC addresses can be flooded within the VPN forwarding domain. In this scenario, however, the distinguishing issue is VLAN normalization mismatch and the confirming observation is: Test frames from each local VLAN appear only on the intended counterpart service at the remote site.
C:Inspect Ethernet segment identifier, DF election result and per-VLAN forwarder eligibility. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically EVPN designated forwarder election. EVPN multihoming uses designated forwarder selection to prevent duplicate BUM forwarding to a shared Ethernet segment. In this scenario, however, the distinguishing issue is VLAN normalization mismatch and the confirming observation is: Test frames from each local VLAN appear only on the intended counterpart service at the remote site.
D:Inspect duplicate MAC detection and mobility events before assuming a legitimate workload move. This is a plausible diagnostic check for a different Layer 2 VPNs condition, specifically EVPN duplicate MAC protection. Repeated conflicting MAC advertisements can indicate duplicate endpoint identity rather than valid sequential migration. In this scenario, however, the distinguishing issue is VLAN normalization mismatch and the confirming observation is: Test frames from each local VLAN appear only on the intended counterpart service at the remote site.
Question 967
During a core-routing migration rehearsal, an HPE Juniper Networking engineer investigates this situation: Two EVPN participating sites use different local VLAN IDs for the same customer service and frames are unexpectedly dropped or leaked. Which routing or service mechanism best explains the reported behavior?
- VPLS provides multipoint Ethernet bridging, so traffic to unknown MAC addresses can be flooded within the VPN forwarding domain.
- EVPN multihoming uses designated forwarder selection to prevent duplicate BUM forwarding to a shared Ethernet segment.
- EVPN can separate local VLAN identifiers from a shared service identity when correct translation and normalization are configured.
- Repeated conflicting MAC advertisements can indicate duplicate endpoint identity rather than valid sequential migration.
Explanation
Correct Answer
C:EVPN can separate local VLAN identifiers from a shared service identity when correct translation and normalization are configured. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Test frames from each local VLAN appear only on the intended counterpart service at the remote site. The targeted correction is: Apply supported VLAN translation or consistent VLAN-based service mapping across sites.
Incorrect Answers
A:VPLS provides multipoint Ethernet bridging, so traffic to unknown MAC addresses can be flooded within the VPN forwarding domain. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically VPLS flooding unknown unicast. VPLS provides multipoint Ethernet bridging, so traffic to unknown MAC addresses can be flooded within the VPN forwarding domain. In this scenario, however, the distinguishing issue is VLAN normalization mismatch and the confirming observation is: Test frames from each local VLAN appear only on the intended counterpart service at the remote site.
B:EVPN multihoming uses designated forwarder selection to prevent duplicate BUM forwarding to a shared Ethernet segment. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically EVPN designated forwarder election. EVPN multihoming uses designated forwarder selection to prevent duplicate BUM forwarding to a shared Ethernet segment. In this scenario, however, the distinguishing issue is VLAN normalization mismatch and the confirming observation is: Test frames from each local VLAN appear only on the intended counterpart service at the remote site.
D:Repeated conflicting MAC advertisements can indicate duplicate endpoint identity rather than valid sequential migration. This is a plausible protocol explanation for a different Layer 2 VPNs condition, specifically EVPN duplicate MAC protection. Repeated conflicting MAC advertisements can indicate duplicate endpoint identity rather than valid sequential migration. In this scenario, however, the distinguishing issue is VLAN normalization mismatch and the confirming observation is: Test frames from each local VLAN appear only on the intended counterpart service at the remote site.
Question 968
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: Two EVPN participating sites use different local VLAN IDs for the same customer service and frames are unexpectedly dropped or leaked. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site.
- Only the elected eligible DF forwards the relevant BUM traffic toward the dual-homed site.
- The duplicate source is corrected and MAC ownership stabilizes on one authorized site.
- Test frames from each local VLAN appear only on the intended counterpart service at the remote site.
Explanation
Correct Answer
D:Test frames from each local VLAN appear only on the intended counterpart service at the remote site. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: EVPN can separate local VLAN identifiers from a shared service identity when correct translation and normalization are configured.
Incorrect Answers
A:MAC learning stabilizes and flooding reduces while known unicast frames target the correct remote site. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically VPLS flooding unknown unicast. VPLS provides multipoint Ethernet bridging, so traffic to unknown MAC addresses can be flooded within the VPN forwarding domain. In this scenario, however, the distinguishing issue is VLAN normalization mismatch and the confirming observation is: Test frames from each local VLAN appear only on the intended counterpart service at the remote site.
B:Only the elected eligible DF forwards the relevant BUM traffic toward the dual-homed site. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically EVPN designated forwarder election. EVPN multihoming uses designated forwarder selection to prevent duplicate BUM forwarding to a shared Ethernet segment. In this scenario, however, the distinguishing issue is VLAN normalization mismatch and the confirming observation is: Test frames from each local VLAN appear only on the intended counterpart service at the remote site.
C:The duplicate source is corrected and MAC ownership stabilizes on one authorized site. This is a plausible observed evidence for a different Layer 2 VPNs condition, specifically EVPN duplicate MAC protection. Repeated conflicting MAC advertisements can indicate duplicate endpoint identity rather than valid sequential migration. In this scenario, however, the distinguishing issue is VLAN normalization mismatch and the confirming observation is: Test frames from each local VLAN appear only on the intended counterpart service at the remote site.
Question 969
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: Two EVPN participating sites use different local VLAN IDs for the same customer service and frames are unexpectedly dropped or leaked. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Apply supported VLAN translation or consistent VLAN-based service mapping across sites.
- Fix MAC learning or excessive churn rather than disabling legitimate service discovery broadly.
- Align multihoming and DF-election configuration for the shared Ethernet segment.
- Resolve the duplicate MAC condition and use supported detection or suppression controls.
Explanation
Correct Answer
A:Apply supported VLAN translation or consistent VLAN-based service mapping across sites. The change addresses the root behavior described here: EVPN can separate local VLAN identifiers from a shared service identity when correct translation and normalization are configured. Verify success with: Test frames from each local VLAN appear only on the intended counterpart service at the remote site.
Incorrect Answers
B:Fix MAC learning or excessive churn rather than disabling legitimate service discovery broadly. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically VPLS flooding unknown unicast. VPLS provides multipoint Ethernet bridging, so traffic to unknown MAC addresses can be flooded within the VPN forwarding domain. In this scenario, however, the distinguishing issue is VLAN normalization mismatch and the confirming observation is: Test frames from each local VLAN appear only on the intended counterpart service at the remote site.
C:Align multihoming and DF-election configuration for the shared Ethernet segment. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically EVPN designated forwarder election. EVPN multihoming uses designated forwarder selection to prevent duplicate BUM forwarding to a shared Ethernet segment. In this scenario, however, the distinguishing issue is VLAN normalization mismatch and the confirming observation is: Test frames from each local VLAN appear only on the intended counterpart service at the remote site.
D:Resolve the duplicate MAC condition and use supported detection or suppression controls. This is a plausible configuration or operational fix for a different Layer 2 VPNs condition, specifically EVPN duplicate MAC protection. Repeated conflicting MAC advertisements can indicate duplicate endpoint identity rather than valid sequential migration. In this scenario, however, the distinguishing issue is VLAN normalization mismatch and the confirming observation is: Test frames from each local VLAN appear only on the intended counterpart service at the remote site.
Question 970
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: Two EVPN participating sites use different local VLAN IDs for the same customer service and frames are unexpectedly dropped or leaked. Which operational control would best prevent a recurrence of this exact failure mode?
- Track MAC churn and unknown-unicast levels separately from ordinary broadcast traffic.
- Maintain a site-VLAN-to-EVI mapping table and test isolation after adding services.
- Fail over the DF during testing and check for duplicate frames or blackholes.
- Alert on oscillating MAC addresses that exceed planned mobility behavior.
Explanation
Correct Answer
B:Maintain a site-VLAN-to-EVI mapping table and test isolation after adding services. The control limits repetition of the described root condition: EVPN can separate local VLAN identifiers from a shared service identity when correct translation and normalization are configured. During audits, confirm: Test frames from each local VLAN appear only on the intended counterpart service at the remote site.
Incorrect Answers
A:Track MAC churn and unknown-unicast levels separately from ordinary broadcast traffic. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically VPLS flooding unknown unicast. VPLS provides multipoint Ethernet bridging, so traffic to unknown MAC addresses can be flooded within the VPN forwarding domain. In this scenario, however, the distinguishing issue is VLAN normalization mismatch and the confirming observation is: Test frames from each local VLAN appear only on the intended counterpart service at the remote site.
C:Fail over the DF during testing and check for duplicate frames or blackholes. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically EVPN designated forwarder election. EVPN multihoming uses designated forwarder selection to prevent duplicate BUM forwarding to a shared Ethernet segment. In this scenario, however, the distinguishing issue is VLAN normalization mismatch and the confirming observation is: Test frames from each local VLAN appear only on the intended counterpart service at the remote site.
D:Alert on oscillating MAC addresses that exceed planned mobility behavior. This is a plausible preventive practice for a different Layer 2 VPNs condition, specifically EVPN duplicate MAC protection. Repeated conflicting MAC advertisements can indicate duplicate endpoint identity rather than valid sequential migration. In this scenario, however, the distinguishing issue is VLAN normalization mismatch and the confirming observation is: Test frames from each local VLAN appear only on the intended counterpart service at the remote site.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests