Licensing Requirements and Limitations for MUX VLANs

Involved Network Elements

Other network elements are not required.

Licensing Requirements

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

Feature Support in V200R019C10

All models of S2720, S5700, and S6700 series switches support MUX VLAN.

For details about software mappings, visit Hardware Query Tool and search for the desired product model.

Feature Limitations

• Table 1 describes the specifications of the MUX VLAN.

  Table 1 Specifications of the MUX VLAN

  Item	Specification
  Maximum number of principal VLANs on the entire device	128
  Maximum number of separate VLANs in each principal VLAN	1
  Maximum number of group VLANs in each principal VLAN	128 NOTE: Each principal VLAN supports a total of 128 separate and group VLANs. That is, if one separate VLAN is configured, a maximum of 127 group VLANs can be configured.

• The VLAN ID assigned to a principal VLAN cannot be used to configure the super-VLAN or sub-VLAN. Additionally, it is not recommended that this VLAN ID be used to configure VLAN mapping and VLAN stacking.
• The VLAN ID assigned to a group or separate VLAN cannot be used to configure a VLANIF interface, super-VLAN, or sub-VLAN. Additionally, it is not recommended that this VLAN ID be used to configure VLAN mapping and VLAN stacking.
• The VLAN ID assigned to a Layer 2 static multicast group and the MUX VLAN IDs (including the principal VLAN ID and subordinate VLAN IDs) cannot be the same.
• Disabling MAC address learning or limiting the number of learned MAC addresses on an interface will compromise the performance of the MUX VLAN function.
• The VLAN specified in the static MAC address entry cannot be the MUX VLAN.
• MUX VLAN and port security cannot be configured on the same interface.
• MUX VLAN and MAC address authentication cannot be configured on the same interface.
• MUX VLAN and 802.1x authentication cannot be configured on the same interface.

• When both DHCP snooping and MUX VLAN are configured, if DHCP snooping is configured in the subordinate VLAN and DHCP clients are configured in the principal VLAN, the DHCP clients may fail to obtain IP addresses. In this case, configure the DHCP server in the principal VLAN.

• After the MUX VLAN function is enabled on an interface, VLAN mapping or VLAN stacking cannot be configured on the interface.
• You cannot create a VLANIF interface for a subordinate group VLAN or separate VLAN. However, you can create a VLANIF interface for a principal VLAN on the device excluding the S2750-EI, S5700-LI, S5700S-28P-LI-AC, S5700S-28P-PWR-LI-AC, and S5700S-52P-LI-AC.
• When the interface is enabled with MUX VLAN and configured with the PVID using the port trunk pvid vlan command, do not configure the PVID as the ID of the principal VLAN or subordinate VLAN of the MUX VLAN. For example, VLAN 10 is the principal VLAN, VLAN 11 is a subordinate group VLAN, and VLAN 12 is a subordinate separate VLAN. After the port mux-vlan enable vlan 10 command is used on the interface to enable MUX VLAN, do not run the port trunk pvid vlan command to set the PVID to VLAN 11 or VLAN 12.
• In versions earlier than V200R012C00, the MUX VLAN cannot forward Layer 2 multicast traffic. Starting from V200R012C00, after the multicast-snooping mux-vlan enable command is run in the system view, the MUX VLAN can forward Layer 2 multicast traffic.