Hello everyone!
4.2.1 Common Misconfigurations
4.2.1.1 STAs Fail to Obtain IP Addresses Because the Management VLAN and Service VLAN Are Set to the Same VLAN
Fault Description
When the management VLAN and service VLAN are set to the same VLAN, STAs fail to obtain IP addresses. In actual configuration, you are advised to set the management VLAN and service VLAN to different VLANs.
You can check the service VLAN configured in a service set using the display service-set name service-set-name command and check the management VLAN based on the network planning data, and then compare whether the two VLANs are the same.
Procedure
Run the system-view command to enter the system view.
Run the vlan batch { vlan-id1 [ to vlan-id2 ] } &<1-10> command to create different VLANs used as the management VLAN and service VLAN, respectively.
Run the wlan command to enter the WLAN view.
Run the service-set { name service-set-name | id service-set-id }* command to enter the service set view.
Run the service-vlan vlan-id command to configure a service VLAN.
Configure the management VLAN according to network planning. Set the management VLAN and service VLAN to different VLANs.
4.2.1.2 STAs Obtain Incorrect IP Addresses When the Service VLAN Is Set to VLAN 1
Fault Description
When the service VLAN is set to VLAN 1, STAs may obtain IP addresses of the management VLAN. You are advised not to set the service VLAN to VLAN 1.
You can run the display service-set name service-set-name command to check whether the service VLAN configured in the service set is VLAN 1.
Procedure
Run the system-view command to enter the system view.
Run the vlan batch vlan-id command to create a VLAN.
Run the wlan command to enter the WLAN view.
Run the service-set { name service-set-name | id service-set-id }* command to enter the service set view.
Run the service-vlan vlan-id command to set the service VLAN to the created VLAN.
4.2.1.3 Service Configuration Is Not Committed and Therefore Does Not Take Effect
Fault Description
After completing the WLAN service configuration, users sometimes forget to commit the configuration. As a result, the configuration does not take effect. After completing the WLAN service configuration, you are advised to run the commit { all | ap ap-id } command to commit the configuration so that the configuration can take effect.
Procedure
Run the system-view command to enter the system view.
Run the wlan command to enter the WLAN view.
Run the commit { all | ap ap-id } command to commit the configuration.
4.2.1.4 Multiple Service Sets Are Configured on an AP, and They Have the Same SSID but Different Service VLANs, Causing Unstable Wireless Network Connections
Fault Description
Multiple service sets are configured on an AP, and they have the same SSID but different service VLANs. Such configuration results in an unstable wireless network on which problems such as frequent network disconnections and SSID switching often occur. You are advised to configure different SSIDs for service sets of the same AP.
You can run the display service-set name service-set-name command to check whether different SSIDs are configured for different service sets.
Procedure
Run the system-view command to enter the system view.
Run the wlan command to enter the WLAN view.
Run the service-set { name service-set-name | id service-set-id }* command to enter the service set view.
Run the ssid ssid command to configure different SSIDs in different service sets.
4.2.1.5 After Direct Forwarding Is Configured for MPs on a Mesh Network, STAs Cannot Go Online
Fault Description
In Mesh scenarios, STAs cannot go online when MPs work in direct forwarding mode and go online normally when MPs work in tunnel forwarding mode.
The most possible cause for this fault is that no service VLAN is configured on the MPP's wired interface. You can run the display ap id ap-id lineate-port interface-type interface-num command to check VLANs displayed in the lineport vlan tagged and lineport vlan untagged fields.
The display ap id ap-id lineate-port interface-type interface-num command is supported only in V200R005.
Procedure
Run the system-view command to enter the system view.
Run the wlan command to enter the WLAN view.
Run the ap id ap-id command to enter the AP view.
Specify the service VLAN to which the MPP's wired interface is added.
By default, an AP's wired interface is not added to any VLAN. An AP's wired interface can be added to a maximum of 256 VLANs.
In direct forwarding mode, an MPP's wired interface must be added to service VLANs so that packets from the VLANs can pass through the MPP's wired interface.
V200R003: run the lineate-port vlan { tagged | untagged } { vlan-id1 [ to vlan-id2 ] } &<1-10> command.
V200R005: run the lineate-port interface-type interface-num vlan { tagged | untagged } { vlan-id1 [ to vlan-id2 ] } &<1-10> command.
From group: WLAN
This is what I want to talk about/share with you today, thank you!
