Enabling the MUX VLAN Feature on a Port
Context
- Allow principal VLAN and subordinate VLAN to communicate with each other.
- Allow ports in a group VLAN to communicate with each other.
- Disallow ports in a separate VLAN to communicate with each other.
Pre-configuration Tasks
Before enabling the MUX VLAN function, ensure that the interface has been added to a principal or subordinate VLAN as an access, hybrid, or trunk interface.
Procedure
- Run system-view
The system view is displayed.
- Run interface interface-type interface-number
The interface view is displayed.
- Run port link-type { hybrid | access | trunk }
The link type of the port is set.
- Run port mux-vlan enable vlan { vlan-id1 [ to vlan-id2 ] } &<1-10>
The MUX VLAN feature is enabled on the port.
After the MUX VLAN feature is enabled on a port, VLAN mapping or VLAN stacking cannot be configured on the port.
You can create a VLANIF interface for a principal VLAN, but cannot create a VLANIF interface for a subordinate group VLAN or separate VLAN.
The port mux-vlan enable command is not supported on a negotiation-auto or negotiation-desirable port.
All principal ports, separate ports, and group ports need to be enabled with the MUX VLAN feature and bound to the corresponding VLANs.
Disabling MAC address learning or limiting the number of learned MAC addresses on a port will compromise the performance of the MUX VLAN feature.
MUX VLAN and port security cannot be configured on the same port.
MUX VLAN and MAC address authentication cannot be configured on the same port.
MUX VLAN and 802.1x authentication cannot be configured on the same port.
If a DHCP server is configured in the subordinate VLAN and DHCP clients are configured in the principal VLAN, the DHCP clients may fail to obtain IP addresses. Therefore, when the DHCP snooping function is configured, configure the DHCP server in the principal VLAN.