Question 160
At a large enterprise updating redundant switch links, a Junos specialist investigates this scenario: Two customers using overlapping inner VLAN IDs communicate unexpectedly after a service-provider bridging change. The change must retain both link resilience and correct VLAN isolation. Which design objective is best served by this mechanism?
Explanation
Correct Answer
For a large enterprise updating redundant switch links, this mechanism fits the requirement: Use distinct Q-in-Q outer tags to isolate tenants with overlapping inner VLANs. The design is appropriate because: A provider S-VLAN or equivalent encapsulation boundary is needed to keep identical customer C-VLAN numbers separate. In this scenario, the observed issue is: Two customers using overlapping inner VLAN IDs communicate unexpectedly after a service-provider bridging change. The corresponding implementation is: Assign distinct outer service VLAN identities to the independent customer services.
Incorrect Answers
IEEE 802.1ad Q-in-Q encapsulates customer-tagged frames with an outer service VLAN tag. The appropriate correction for the reported case is: Assign distinct outer service VLAN identities to the independent customer services.
Private VLAN promiscuous ports can communicate with applicable secondary VLAN ports, providing a shared exit. 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.
Spanning tree prevents bridging loops by keeping appropriate redundant ports in nondesignated states. Its verification is distinct from the reported condition: Two customers using overlapping inner VLAN IDs communicate unexpectedly after a service-provider bridging change. The change must retain both link resilience and correct VLAN isolation.