Hvlan And Translation Feature Interactions - Allied Telesis SwitchBlade x3100 Series Manual

HVLAN and Translation Feature Interactions

The XE4 supports TPID configuration for each port. Thus XE4 ports configured for TPID=x9100 for example
will send out single or double tagged packets with x9100 in the outermost tag. On ingress, packets whose single
or double tag is x9100 are considered to indeed be a tag and the TPID will be translated to x8100.
The TPID translation feature is available on the GE8 SM and the XE1 NM.
On the GE and XE cards, tagged packets are identified by the FPGA based on the TPID that the interface has
been configured with. Tagged packets that arrive with a TPID other than the configured TPID will be considered
to be untagged packets by the FPGA.
The interactions of TPID translation and other features are as follows:
VLAN translation and TPID translation can be configured on the same interface, so that a VLAN translation
•
AND a TPID translation can occur on the same packet.
VLANTUNNEL HVLAN(s) and TPID translation can be configured on the same interface. When a tunnel
•
tag is being added on egress, the TPID translation will occur on the outer tag only. The TPID of the inner tag
will remain unchanged.
4.10.4 HVLAN and Translation Feature Interactions
With the HVLAN and translation options, VLAN configurations interact with each other and other features as
follows:
The Port-based HVLAN and translation feature are not compatible on the same port. Once a port is config-
•
ured with the HVLAN option, it cannot use the translation feature, and vice-versa. This applies to the cards
that support both of these features (GE24POE, GE24SFP, XE4).
For traffic management, classifiers are used to filter traffic according to certain criteria, and this may be
•
affected with the double tagging of frames.
Link Aggregation (LAG) can still be enabled for a port that has an HVLAN as long as all member ports of the
•
LAG group belong to the same VLANs, both tagged and untagged.
IGMP Snooping and Port-based HVLAN are mutually exclusive features. If IGMP snooping is
•
enabled system wide and a port has IGMP snooping enabled, that port cannot participate in the HVLAN; if a
port is part of an HVLAN, IGMP snooping cannot be enabled on that port.
Spanning Tree Protocol can be enabled on an HVLAN port, as long as the following applies:
•
When customer traffic at multiple sites is tunneled over the network operator network, every customer
VLAN will need to build a spanning tree that includes the multiple sites across the VLAN. To enable this, the
Bridge Protocol Data Unit (BPDU) will need to be tunnelled across the network. (Note that the Network
Access product does not support tunneling BPDUs.)
The VLAN-based HVLAN and Translation features can be supported on one system, but in most
Note:
network engineering solutions, either one or the other is used.
Software Reference for SwitchBlade x3100 Series Switches (Layer Two Switching)
Introduction
4-207