Precautions for configuring MUX VLAN on S series switch

When configuring MUX VLAN on S series switches (except S1700), pay attention to the following points:
1. If a specified VLAN has been used as a principal VLAN, it cannot be configured for VLAN mapping, VLAN stacking, super-VLANs, or sub-VLANs.
2. If a specified VLAN has been used as a group VLAN or separate VLAN, it cannot be used to create VLANIF interfaces or configured for VLAN mapping, VLAN stacking, super-VLANs, or sub-VLANs.
3. Prohibiting MAC address learning on interfaces or limiting the number of MAC addresses learned on interfaces will affect the MUX VLAN function.
4. MUX VLAN and port security cannot be configured on the same interface.
5. MUX VLAN and MAC address authentication cannot be configured on the same interface.
6. MUX VLAN and 802.1x authentication cannot be configured on the same interface.
7. When both DHCP snooping and MUX VLAN are configured, a DHCP client cannot obtain an IP address if the DHCP server is at the subordinate VLAN side and the DHCP client is at the principal VLAN side. To avoid this problem, configure the DHCP server at the principal VLAN side.
8. After MUX VLAN is enabled on an interface, this interface cannot have VLAN mapping or VLAN stacking configured.
9. A VLANIF interface can be created for a principal VLAN but not for subordinate group VLANs or subordinate separate VLANs. If a VLANIF interface is created for the principal VLAN in a MUX VLAN, the port mux-vlan enable vlan vlan-id command cannot be configured on interfaces of SA cards on S series switches to enable any VLAN in the MUX VLAN, including principal and subordinate VLANs.

Other related questions:
Default MUX VLAN configuration on S series switch
If you have more questions, you can seek help from following ways:
To iKnow To Live Chat To Google
Scroll to top