VLAN C
ONFIGURATION
13-28
8. If the egress port is an untagged member of the SPVLAN, the outer
tag will be stripped. If it is a tagged member, the outgoing packet will
have two tags.
Configuration Limitations for QinQ
• The native VLAN of uplink ports should not be used as the SPVL AN.
If the SPVLAN is the uplink port's native VLAN, the uplink port must
be an untagged member of the SPVLAN. Then the outer SPVLAN tag
will be stripped when the packets are sent out. Another reason is that it
causes none-customer packets to be forwarded to SPVLAN.
• Static trunk port groups are compatible with QinQ tunnel ports as long
as the QinQ configuration is consistent within a trunk port gr oup.
• QinQ and VLAN Swap mode cannot be supp orted at the same time.
• The native VLAN (VLAN 1) is not normally added to transmitted
frames. Avoid using VLAN 1 as an SPVLAN tag for customer traffic to
reduce the risk of misconfiguration. Instead, VLAN 1 can be used as a
management VLAN instead of a data VLAN in the service provider
network.
• There are some inherent incompatibilities between Layer 2 and Layer 3
features when using 802.1Q tunneling:
- Tunnel ports do not support IP Access Control Lists .
- Layer 3 Quality of Service (QoS) and other QoS f eatures containing
Layer 3 information are not supported on tunnel ports.
- Spanning tree bridge protocol data unit (BPDU) filtering is
automatically disabled on a tunnel port.
General Configuration Guidelines for QinQ
1. Configure the switch to QinQ mode (see “Selecting the VLAN
Operation Mode” on page 13-1).
2. Create a Service Provider VLAN, also referred to as an SPVLAN (see
“Creating VLANs” on page 13-10).
3. Configure the QinQ tunnel port to dot1Q tunnel port mode (see
“Adding an Interface to a QinQ Tunnel” on page 13-30).