Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document.
Note: Even the most advanced machine translation cannot match the quality of professional translators.
Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Licensing Requirements and Limitations for VLANs
Involved Network Elements
Other network elements are not required.
Licensing Requirements
VLAN technology is a basic feature of a switch and is not under license control.
Version Requirements
Table 4-6 Products and versions supporting VLAN technology
Series |
Products |
Software Version |
|---|---|---|
S12700 |
S12708, S12712 |
V200R005C00, V200R006C00, V200R007C00, V200R007C20, V200R008C00, V200R009C00, V200R010C00, V200R011C10 |
S12710 |
V200R010C00, V200R011C10 |
|
S12704 |
V200R008C00, V200R009C00, V200R010C00, V200R011C10 |
Feature Limitations
- Table 4-7 describes the specifications of VLAN technology.
- If LNP is used to dynamically negotiate the link type (LNP is enabled by default), it is recommended that each interface should be added to a maximum of 1000 VLANs and a maximum of 200 interfaces should be configured on a switch. If 4094 VLANs are configured globally, it is recommended that a maximum of 50 interfaces should be enabled with LNP. Otherwise, the alarm about a high CPU usage is generated for a short time.
- You are advised to plan service and management VLANs so that any broadcast storms in service VLANs do not affect switch management.
- In practice, specify VLANs from which packets need to be transparently transmitted by a trunk interface. Do not use the port trunk allow-pass vlan all command if possible.
- All interfaces join VLAN 1 by default. When unknown unicast, multicast,
or broadcast packets of VLAN 1 exist on the network, broadcast storms
may occur. When VLAN 1 is used, pay attention to the following points:
- You are not advised to use VLAN 1 as the management VLAN or service VLAN.
- Remove the interfaces that do not need to join VLAN 1 from VLAN 1 to prevent loops. A trunk interface often permits packets from VLAN 1 to pass through. If a trunk interface rejects packets from VLAN 1, some protocol packets transmitted in VLAN 1 may be incorrectly discarded. To prevent such faults, take measures to prevent potential risks when packets of VLAN 1 are allowed to pass through.
- If a spanning tree protocol is used and a trunk interface on the switch rejects packets from VLAN 1, run the stp bpdu vlan command to enable the switch to encapsulate the specified VLAN ID in outgoing STP BPDUs so that the spanning tree protocol runs properly.
- You are advised to remove interfaces from VLAN 1 in Eth-Trunk or ring networking.
- When the switch connects to an access device, to prevent broadcast storms in VLAN 1, do not configure the uplink interface of the access device to transparently transmit packets from VLAN 1.
- When an interface is bound to a VLANIF interface for Layer 3 forwarding, remove the interface from VLAN 1 to prevent Layer 2 loops in VLAN 1.