Question 730
At a campus network built with Juniper EX switches, a Junos specialist investigates this scenario: Two customers using overlapping inner VLAN IDs communicate unexpectedly after a service-provider bridging change. The intended segmentation and loop prevention must remain intact. What protocol behavior accounts for this failure?
Explanation
Correct Answer
For a campus network built with Juniper EX switches, the governing mechanism is: A provider S-VLAN or equivalent encapsulation boundary is needed to keep identical customer C-VLAN numbers separate. It explains the reported symptom: Two customers using overlapping inner VLAN IDs communicate unexpectedly after a service-provider bridging change. The intended response is: Assign distinct outer service VLAN identities to the independent customer services. Verification: Captures show identical inner tags transported only within their intended outer service VLANs.
Incorrect Answers
Layer 2 protocol tunneling can transport specified customer control frames across a separate provider bridging domain. This alternative mechanism does not match the current fault.
Filter-based VLANs can classify ingress frames and assign eligible traffic to a selected VLAN. Fixing that different mechanism would not address the current root cause: a provider S-VLAN or equivalent encapsulation boundary is needed to keep identical customer C-VLAN numbers separate.
IEEE 802.1ad Q-in-Q encapsulates customer-tagged frames with an outer service VLAN tag. Its verification is distinct from the reported condition: Two customers using overlapping inner VLAN IDs communicate unexpectedly after a service-provider bridging change. The intended segmentation and loop prevention must remain intact.