Proxim Wireless Corporation XB92WFR ユーザーズマニュアル

ページ / 336
Tsunami
®
 800 & 8000 Series - Software Management Guide 
309
E
QinQ
The Subscribers and End Point devices support QinQ VLAN feature that enables service providers to use a single VLAN ID to
support multiple customer VLANs by encapsulating the 802.1Q VLAN tag within another 802.1Q frame. The benefits with
QinQ are as follows:
Increases the VLAN space in a provider network or enterprise backbone
Reduce the number of VLANs that a provider needs to support within the provider network for the same number of 
customers
Enables customers to plan their own VLAN IDs, without running into conflicts with service provider VLAN IDs
Provides a simple Layer 2 VPN solution for small-sized MAN (Metropolitan Area Networks) or Intranet
Provides customer traffic isolation at Layer 2 within a service provider network
Consider a BSU and SU network, with QinQ (Double VLAN (Q in Q) Status) enabled on the SU.
Subscriber
– Based on the Ethernet VLAN configuration on the Subscriber, the data packets are tagged as follows:
Access Mode: SU double tags the packet with Access VLAN ID as inner tag and Service VLAN ID as outer tag. 
                      
: When Double VLAN is enabled on the device, the Access VLAN ID should not be set to -1.
Trunk Mode: SU expects a tagged packet (inner tag) and tags the packet with Service VLAN ID as outer tag.
                       
: When Double VLAN is enabled on the device, the Port VLAN ID should not be set to -1.
Transparent Mode: When QinQ is enabled, SU cannot be configured in the Transparent mode.
– In case of downlink traffic, SU always expects double tagged packet from the wireless side. If the outer VLAN tag 
matches with Service VLAN ID then SU will untag the packet and forward to Ethernet. Based on Ethernet VLAN 
configuration, the data packets are handled accordingly. When the outer VLAN tag does not match the Service 
VLAN ID, the packet is dropped.
– Different outer VLAN IDs can be configured for different SUs, but those VLAN IDs should also be configured on the 
BSU Ethernet. 
Base Station
– BSU always considers the first VLAN tag available in the packet; in case of double tagged packet it is the outer 
VLAN ID.
Trunk Mode: The outer tag of the packet arriving at the Ethernet side should match with the VLAN ID 
configured in the trunk table.
Transparent Mode: When configured in transparent mode, ensure the data packet is double tagged.
Device Management
– From the BSU Ethernet side, the BSU/SU can be managed with a single VLAN tagged packet that matches the 
Management VLAN ID.
– From the SU Ethernet side, only SU can be managed with a single VLAN tagged packet that matches the 
Management VLAN ID; BSU cannot be managed from the SU Ethernet side.