What are the precautions for configuring N:1 VLAN mapping

10

The S2752 and S3700 do not support N:1 VLAN mapping.
N:1 VLAN mapping cannot be configured with port security or MAC address learning disabling.
The interface configured with N:1 VLAN mapping cannot process unknown unicast, broadcast, and multicast return traffic.

Other related questions:
What are precautions for configuring VLAN mapping on multiple interfaces of the switch
When configuring VLAN mapping on multiple user-side interfaces, do not map different C-VLAN IDs to the same S-VLAN ID. Otherwise, traffic sent from a user-side interface may be forwarded to another user-side interface that has the same S-VLAN ID configured.

What are the limitations for configuring VLAN mapping on the S2700
A maximum of 16 VLANs can be mapped on an interface. The C-VLAN ID must be different from the value obtained through the modulo operation against 128 on the VLAN allowed by the interface (VLAN ID mod 128); otherwise, a conflict occurs. For example, if the interface allows VLAN 130 to pass, the result of VLAN ID mod 128 is 2. In this case, the C-VLAN ID cannot be set to 2. The S2700SI does not support VLAN mapping.

What are the precautions for delivering dynamic VLANs
Dynamic VLANs are delivered in the following ways: 1. VLAN IDs 2. VLAN names To deliver dynamic VLANs based on VLAN names, configure the description that specifies the VLAN name in the VLAN view.

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.

What are precautions for configuring intra-VLAN proxy ARP and inter-VLAN proxy ARP
Compared with routed proxy ARP, intra-VLAN proxy ARP and inter-VLAN proxy ARP can determine whether VLAN information meets proxy requirement based on ARP entries matching source and destination IP addresses of packets. If no ARP entry matches the destination IP address of a packet, the switch broadcasts an ARP request in all sub-VLANs of the super-VLAN to learn the APR entry matching the destination IP addresses. When multiple switches on a network have proxy ARP enabled and a requested destination IP address does not exist, this ARP broadcast packet triggers the same proxy process on other switches. This cyclic proxy process will cause a broadcast storm.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top