Licensing Requirements and Limitations for VLAN Mapping

Involved Network Elements

Other network elements are not required.

Licensing Requirements

VLAN mapping is a basic feature of a switch and is not under license control.

Version Requirements of VLAN Mapping

To know details about software mappings, see Hardware Query Tool.

Feature Limitations

• do not support 2:1 and 2:2 VLAN mapping.
• VLAN mapping can be configured only on a trunk or hybrid interface, and the hybrid interface must be added to the translated VLAN.

• When N:1 VLAN mapping is configured, the interface needs to join the original VLAN in tagged mode.

• For SA series cards, when VLAN mapping is configured, do not configure map-vlan for the VLAN corresponding to the VLANIF interface. For other cards, when VLAN mapping is configured, it is not recommended that map-vlan be configured for the VLAN corresponding to the VLANIF interface.

• N:1 VLAN mapping takes effect only when the packets with original VLANs are sent first. In this case, if packets are sent from the S-VLAN first, the C-VLAN to be mapped cannot be determined because no ACL entry is generated. As a result, the packets are discarded.
• N:1 VLAN mapping does not take effect for reverse BUM traffic.

• A VLAN bound to a BD cannot be specified as the value of map-vlan (the outer VLAN ID in the mapped tag) in VLAN mapping commands. Similarly, a VLAN specified as the value of map-vlan in VLAN mapping commands cannot be bound to a BD.

• SA boards of S series, and X series cards do not support N:1 VLAN mapping.

• N:1 VLAN mapping is not supported on an Eth-Trunk.

• If a large number of VLAN mappings are configured in a version earlier than V100R006 and the version is upgraded to V100R006 or a later version, a message indicating insufficient resources or hash conflicts may be displayed during VLAN mapping configuration, affecting services.