D-Link xStack Reference Manual page 113

®
xStack DGS-3620 Series Layer 3 Managed Stackable Gigabit Switch Web UI Reference Guide
In this example, the Service Provider Access Network switch (Provider edge switch) is the device creating and
configuring Q-in-Q VLANs. Both CEVLANs (Customer VLANs), 10 and 11, are tagged with the SPVID 100 on the
Service Provider Access Network and therefore belong to one VLAN on the Service Provider's network, thus being
a member of two VLANs. In this way, the Customer can retain its normal VLAN and the Service Provider can
congregate multiple Customer VLANs within one SPVLAN, thus greatly regulating traffic and routing on the Service
Provider switch. This information is then routed to the Service Provider's main network and regarded there as one
VLAN, with one set of protocols and one routing behavior.
Regulations for Q-in-Q VLANs
•
Some rules and regulations apply with the implementation of the Q-in-Q VLAN procedure.
•
Ports can be configured as UNI ports or NNI ports.
•
Provider Edge switches must allow frames of at least 1522 bytes or more, due to the addition of the SPVID
tag.
•
UNI ports must be an un-tagged port of the service provider VLANs. NNI ports must be a tagged port of the
service provider VLANs.
•
The switch cannot have both double and normal VLANs co-existing. Once the change of VLAN is made, all
Access Control lists are cleared and must be reconfigured.
•
When Q-in-Q VLANs are enabled, GVRP can work with Q-in-Q VLANs.
•
The tags of all packets sent from the CPU to the UNI ports must be striped or replaced.
•
The following functions will not operate when the switch is in Q-in-Q VLAN mode:
Guest VLANs.
o
Web-based Access Control.
o
IP Multicast Routing.
o
All Regular 802.1Q VLAN functions.
o
Figure 5-32 QinQ example window
112