VLAN assignment should comply with the following principles:
- Assign VLANs based on service zones.
- Assign VLANs based on service types (web, app, or database) in a service zone.
- Allocate consecutive VLAN IDs to ensure proper use of VLAN resources.
- Reserve a specific number of VLANs for future use.
VLANs are classified into service, management, and interconnection VLANs. For details about the design suggestions, see
Table 3-1.
Table 3-1 VLAN design suggestionsCategory
|
Design Suggestion
|
|---|
Service VLAN
|
Assign VLANs by logical area, geographical area, personnel structure, or service type.
- Assign VLANs by logical area. For example, VLANs 100 to 199 are used in the core network zone, VLANs 200 to 999 are used in the server zone, and VLANs 2000 to 3499 are used on the access network.
- Assign VLANs by geographical area. For example, VLANs 2000 to 2199 are used in area A, and VLANs 2200 to 2399 are used in area B.
- Assign VLANs by personnel structure. For example, department A uses VLANs 2000 to 2009, and department B uses VLANs 2010 to 2019.
- Assign VLANs by service type. For example, VLANs 200 to 299 are used in the web server zone, VLANs 300 to 399 are used in the app server zone, and VLANs 400 to 499 are used in the database server zone.
If users are sensitive to the voice latency, the voice service must be preferentially guaranteed. It is recommended that the voice VLAN be planned for the voice service. Huawei switches can automatically identify voice data, transmit voice data in the voice VLAN, and perform QoS guarantee. When network congestion occurs, voice data can be preferentially transmitted.
If different users have the same multicast data service, you are advised to plan a multicast VLAN and bind the user VLANs to the multicast VLAN. By doing this, the uplink gateway does not copy multicast data in multiple user VLANs.
|
Management VLAN
|
- Egress network devices: Use Layer 3 service interfaces as management interfaces, without the need to plan a management VLAN.
- Core switches: Plan an independent management VLAN and use the VLANIF interface of the management VLAN as the management interface, through which iMaster NCE-Campus manages core switches.
- Devices below the core layer: Plan one or more management VLANs based on the device scale and use the VLANIF interface of the management VLAN as the management interface. iMaster NCE-Campus manages the devices through this management interface.
- If a small number of devices are deployed, it is recommended that all aggregation switches, access switches, and APs use the same management VLAN.
- If a number of devices are deployed, it is recommended that all aggregation and access switches use the same management VLAN and all APs use the same management VLAN.
- If a great number of devices are deployed, you are advised to plan device groups based on network layers, with each device group assigned one management VLAN. For example, each aggregation switch and its connected downstream devices are grouped into one device group and use the same management VLAN.
|
Interconnection VLAN
|
An interconnection VLAN is usually configured between two Layer 3 switches or between a Layer 3 switch and a router. VLANIF interfaces are created for Layer 3 interconnection.
|
