- The VLAN ID assigned to a principal VLAN cannot be used to configure VLAN mapping, VLAN stacking, super-VLAN, or sub-VLAN.
- The VLAN ID assigned to a group or separate VLAN cannot be used to configure a VLANIF interface, VLAN mapping, VLAN stacking, super-VLAN, or sub-VLAN.
- Disabling MAC address learning or limiting the number of learned MAC addresses on an interface will compromise the performance of the MUX VLAN function.
- 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 can create a VLANIF interface for a principal VLAN, but cannot create a VLANIF interface for a subordinate group VLAN or separate VLAN.
- 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 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.