The VLAN translation feature has the following limitations:
Requires more FDB entries than a standard VLAN.
VLAN tag duplication is not allowed.
VLAN name duplication is not allowed.
Each MAC address learned in the translation and member VLANs must be unique. A MAC address cannot exist in two or more VLANs that belong to the same VLAN translation domain.
MVR cannot be configured on translation and member VLANs.
A VMAN cannot be added to translation and member VLANs.
A PBB network (BVLAN) cannot be added to translation and member VLANs.
EAPS control VLANs cannot be either translation or member VLANs.
EAPS can only be configured on translation VLAN ports (and not on member VLAN ports). To support EAPS on the network VLAN, you must add all of the translation and member VLANs to the EAPS ring.
STP can only be configured on translation VLAN ports (and not on member VLAN ports). To support STP on the translation VLAN, you must add the translation VLAN and all of the member VLANs to STP.
ESRP can only be configured on translation VLAN ports (and not on member VLAN ports). To support ESRP on the network VLAN, you must add the translation VLAN and all of the member VLANs to ESRP.
There is no NetLogin support to add ports as translate to the translation VLAN, but the rest of NetLogin and the PVLAN feature do not conflict.
IGMP snooping is performed across the entire VLAN translation domain, spanning all the member VLANs. For VLANs that are not part of a VLAN translation domain, IGMP snooping operates as normal.
VLAN translation and VPLS are not supported on the same VLAN.
Member VLANs in a VLAN translation domain cannot exchange multicast data with VLANs outside the VLAN translation domain. However, the translation VLAN can exchange multicast data with VLANs outside the VLAN translation domain and with translation VLANs in other VLAN translation domains.