A STA Goes Offline Unexpectedly
Symptom
After a STA goes online and obtains an IP address, the STA goes offline unexpectedly.
Possible Causes
- The function of disconnecting weak-signal STAs is configured.
- The STA or the AP associated with the STA is contained by mistake.
- The online STA goes offline during accounting.
- STA roaming fails after the STA goes online.
- The function of disconnecting weak-signal STAs is not configured. However, the surrounding interference increases and signal attenuation is severe.
- The STA does not send DHCP or ARP packets, and is forcibly disconnected due to a traffic exception.
- The AP associated with the STA goes offline unexpectedly.
- The Beacon interval and rate are incorrectly configured.
- Channel interference issues exist, such as high radio channel utilization or channel overlapping between neighboring APs.
- Automatic radio calibration is performed frequently.
Troubleshooting Procedure
- Run the display station offline-record all command in any view or run the display aaa abnormal-offline-record command in the diagnostic view to check the reason why the STA goes offline.
<AC6605> display station offline-record all Reason distribution ---------------------------------------------------------------------------------------- Reason Count Percent ---------------------------------------------------------------------------------------- The VAP goes down because the configuration is modified. 2 100.00% ---------------------------------------------------------------------------------------- Total Count: 2 Recent records Rf/WLAN: Radio ID/WLAN ID ------------------------------------------------------------------------------ STA MAC Device type Device ID Device name Rf/WLAN Last record time Reason ------------------------------------------------------------------------------ 14cf-9208-9abf AP AP-1 AP-area_11 0/2 2015-09-18/09:38:50 The VAP goes down because the configuration is modified. 14cf-9202-13dc AC AC-1 AC-1 -/2 2015-09-18/09:28:52 The VAP goes down because the configuration is modified. ------------------------------------------------------------------------------ Total stations: 2 Total records: 2V200R010 is used as an example. The following table describes the causes and handling suggestions for AP logout. For other versions, see the corresponding command lines in the product documentation.
Reason Why a STA Goes Offline
Suggestion
A STA goes offline properly.
No action is required.
STA entry addition times out or fails.
Check the intermediate network between the AP and AC or reassociate the STA with the network. If this fault persists, contact technical support personnel.
Authentication fails in the association stage.
Reassociate the STA with the network. If this fault persists, contact technical support personnel.
The configuration is modified.
Check whether configuration change records exist.
Roaming check failed (on the eSAP).
Reassociate the STA with the network. If this fault persists, contact technical support personnel.
Roaming failed (because of a roaming entry failure on the forwarding side or a failure to obtain the configuration).
Reassociate the STA with the network. If this fault persists, contact technical support personnel.
The AP is faulty.
Check the reason why the AP goes offline, and rectify the fault accordingly. For reasons why an AP goes offline, see display ap offline-record.
The AP is deleted.
No action is required.
Failed to synchronize user entries between the AP and AC.
Reassociate the STA with the network. If this fault persists, contact technical support personnel.
Failed to synchronize user entries in a mobility group.
Reassociate the STA with the network. If this fault persists, contact technical support personnel.
Failed to synchronize user entries between WMP and eSAP.
Reassociate the STA with the network. If this fault persists, contact technical support personnel.
A tunnel between ACs goes Down.
Check the network between ACs.
The home AP goes offline or a network fault occurs.
Reassociate the STA with another AP. If this fault persists, contact technical support personnel.
The home AP is deleted:.
Reassociate the STA with another AP. If this fault persists, contact technical support personnel.
The home VAP is deleted.
Reassociate the STA with another VAP. If this fault persists, contact technical support personnel.
The AC forcibly disconnects idle STAs.
Check whether this function is required. If so, no action is required. If not, run the undo idle-cut command in the service scheme view to modify the configuration as required.
The STA roams out of the device.
No action is required.
The keepalive packet on the home AP times out.
Check the intermediate network between the AP and AC or reassociate the STA with the network. If this fault persists, contact technical support personnel.
The keepalive packet between ACs times out.
Check the intermediate network between the ACs or reassociate the STA with the network. If this fault persists, contact technical support personnel.
Layer 3 roaming is disabled.
Reassociate the STA with the network or enable Layer 3 roaming.
The STA fails the roaming security check.
Reassociate the STA with the network. If this fault persists, contact technical support personnel.
The STA fails the roaming status check.
Reassociate the STA with the network. If this fault persists, contact technical support personnel.
The STA fails the roaming check due to other reasons.
Reassociate the STA with the network. If this fault persists, contact technical support personnel.
Failed to add FPI item.
Reassociate the STA with the network. If this fault persists, contact technical support personnel.
The STA MAC is added to the STA blacklist.
Check whether the STA needs to be added to the blacklist.
Users go offline due to WDS link disconnection or other unknown reasons (reported by Wi-Fi).
Reassociate the STA with the network. If this fault persists, contact technical support personnel.
The STA disassociates with the network.
Check whether the STA actively goes offline or whether the STA is faulty.
The STA is deauthenticated.
Check whether the STA actively goes offline or whether the STA is faulty.
The STA ages out.
No action is required.
The VAP goes down because the configuration is modified.
Check whether configuration change records exist in the log.
The number of users exceeds the specifications (insufficient key slots).
Expand the AP capacity or reassociate the STA with another AP.
A user exception is detected.
Rectify the fault and reassociate the STA with the network. If this fault persists, contact technical support personnel.
The STA does not respond.
Check whether the STA works properly.
The STA is added to the dynamic blacklist.
Check whether the STA is an attacker.
The signal strength is too low.
Check whether the threshold for quickly disconnecting STAs by smart roaming is correctly configured, and check whether the WLAN coverage area is sufficient.
The STA rate is too low.
Check whether the threshold for quickly disconnecting STAs by smart roaming is correctly configured, and check whether the WLAN coverage area is sufficient.
The STA uses a bogus IP address.
Configure the STA to automatically obtain an IP address.
No control entry exists.
Reassociate the STA with the network. If this fault persists, contact technical support personnel.
The AP goes online again.
Reassociate the STA with the network. If this fault persists, contact technical support personnel.
No Wi-Fi entry exists.
Reassociate the STA with the network. If this fault persists, contact technical support personnel.
The STA roams between ACs.
No action is required.
The STA reassociates with the network but does not send a DHCP request message.
Reassociate the STA with the network. If this fault persists, contact technical support personnel.
Multicast key handshake failure.
Reassociate the STA with the network. If this fault persists, contact technical support personnel.
Reporting the PMK negotiation result to the AC times out.
Reassociate the STA with the network. If this fault persists, contact technical support personnel.
The STA disassociates with the network (delay aging offline).
Check whether the STA actively goes offline or whether the STA is faulty.
The STA is deauthenticated (delay aging offline).
Check whether the STA actively goes offline or whether the STA is faulty.
The STA ages out (delay aging offline).
No action is required.
Layer 3 roaming is disabled (delay offline).
No action is required.
The STA IP address changes after roaming.
Reassociate the STA with the network. If this fault persists, contact technical support personnel.
AP restores connection from escape mode.
No action is required.
RADIUS authentication reject
Check whether the login user name and password are the same as those on the RADIUS server. If not, change them to be the same and re-apply for login.
Failed to synchronize user entries between the local and navi ACs.
Reassociate the STA with the network. If this fault persists, contact technical support personnel.
Higher-priority STAs access the network.
Configure the STA as a high-priority STA, or increase the user CAC threshold or the maximum number of STAs on a VAP.
The number of STAs reached the CAC or VAP threshold.
Increase the user CAC threshold or the maximum number of STAs on a VAP.
The remotely authenticated STA is disconnected after an active/standby switchover in the Local AC dual-link networking.
No action is required.
VAP configurations on the Navi AC is modified.
No action is required.
The PPSK user account is timeout.
Modify the expiration time of the PPSK user account.
The PPSK user account exceed maximum login device.
Increase the maximum number of login devices supported by the PPSK account.
PPSK config modified.
No action is required.
The PPSK account does not exist.
Run the display wlan ppsk-user all command to check whether any PPSK account maps the access SSID. If so, use the PPSK account for access. If not, create a PPSK account and bind it to the SSID.
The softgre tunnel goes down.
Check the network connectivity with the peer end of the Soft-GRE tunnel. If this fault persists, contact technical support personnel.
Common causes are as follows:
- The STA proactively disassociates from the network.
When a STA leaves the network, it may send a disassociation packet. This is a normal logout record. If the STA or the AP associated with the STA is contained, the disassociation packet may be sent by the rogue AP. In this case, the STA goes online and then offline. You can check the trace information. If the STA is contained by the rogue AP, check the source of the rogue AP. If the STA is not contained by the rogue AP, ping the gateway from the STA. If the STA fails to ping the gateway, the STA initiates a disassociation request. In addition to the preceding operations can be used together with packet header obtaining over the air interface for further confirmation.
- The STA initiates an authentication request.
When a STA is deauthenticated or disassociated, the STA goes offline on the AC. If a STA is contained by a rogue AP, the location method is the same as that for disassociation.
- The STA is aged and goes offline.
The STA may not send a disassociation packet after leaving the network, or the STA sends a disassociation packet but the associated AP does not receive the packet. Such an event often occurs on the air interface. In this case, Huawei APs perform proactive detection and proactively age out STAs that do not have traffic within 5 minutes.
- The STA re-associates with the network without sending DHCP request packets.
When the STA initiates a re-association request, the AC sends a re-association response to the AP. If there are DHCP or ARP response packets within 5s, the AC considers that the STA is normal. The AC obtains traffic statistics at an interval of 5s. If there are uplink (unicast and broadcast) statistics but no downlink (unicast) statistics, the AC forcibly disconnects the STA. If there is no packet (no uplink packet) within 5s, the traffic statistics collection continues until the traffic is normal or the STA is forcibly disconnected (the STA is forced to go offline after 5s).
This is because STAs are forced to go offline when they do not send DHCP or ARP packets and traffic is abnormal. In V200R008 and later versions, run the sta-network-detect disable command in the VAP profile to prevent this problem.
- Entries fail to be synchronized between the AP and AC.
The disassociation packet from the STA is sent by the AP to the AC. However, the AC does not receive the disassociation packet from the STA due to intermediate network faults. In this case, the AC still retains the STA entries, but the AP has deleted the STA entries. As a result, the entries on the AC and AP are inconsistent. In this case, the AC and AP must be able to synchronize entries to ensure entry consistency.
- Key negotiation fails.
After sending the first packet during the four-way handshake for three times, the AP does not receive packets from the STA. As a result, key negotiation fails and the AP deletes the STA.
This is because the STA moves fast during roaming. As a result, the STA leaves the network before roaming is complete, or packet loss occurs due to poor air interface environment. This offline reason is recorded because the STA has gone online on another AP and the four-way handshake fails during roaming.
- The STA proactively disassociates from the network.
- Check whether the AP is configured to disconnect weak-signal STAs.
When an AP detects that the STA's signal strength is too low, the AP forces the STA to go offline. If the STA associates with the network within 5s again, the AP does not record the offline cause, but the STA may detect the logout. This function is usually used in high-density scenarios (such as stadiums). It enables STAs to quickly roam to other APs and protects the network quality of other STAs. You are advised not to enable this function in non-high-density scenarios.
- Run the display rrm-profile all command to check the RRM profile name.
<AC6605> display rrm-profile all ------------------------------------------------------------ Profile name Reference ------------------------------------------------------------ huawei 2 ------------------------------------------------------------ Total:1
- Run the display rrm-profile name huawei command to check whether forcible logout of weak-signal STAs is configured in the RRM profile huawei.
<AC6605> display rrm-profile name huawei ------------------------------------------------------------ ...... Smart-roam : enable Smart-roam check SNR : enable Smart-roam standing SNR threshold(dB) : 20 Smart-roam SNR quick-kickoff-threshold(dB) : 15 Smart-roam check rate : disable AMC policy : auto-balance Smart-roam rate threshold(%) : 20 Smart-roam rate quick-kickoff-threshold(%) : 20 ...... ------------------------------------------------------------
If forcible logout of weak-signal STAs is configured in non-high-density scenarios, you are advised to run the following commands to disable this function.
V200R006 to V200R008C00:
<AC6605> system-view [AC6605] wlan [AC6605-wlan-view] rrm-profile name huawei [AC6605-wlan-rrm-prof-huawei] undo smart-roam enable //Disable smart roaming. [AC6605-wlan-rrm-prof-huawei] undo smart-roam quick-kickoff-threshold rate //Restore the default rate-based threshold for quickly disconnecting STAs. [AC6605-wlan-rrm-prof-huawei] undo smart-roam quick-kickoff-threshold snr //Restore the default SNR-based threshold for quickly disconnecting STAs.
V200R008C10 and later versions:
<AC6605> system-view [AC6605] wlan [AC6605-wlan-view] rrm-profile name huawei [AC6605-wlan-rrm-prof-huawei] smart-roam quick-kickoff-threshold disable //Disable the function of quickly disconnecting STAs. [AC6605-wlan-rrm-prof-huawei] undo smart-roam quick-kickoff-threshold rate //Restore the default rate-based threshold for quickly disconnecting STAs. [AC6605-wlan-rrm-prof-huawei] undo smart-roam quick-kickoff-threshold snr //Restore the default SNR-based threshold for quickly disconnecting STAs.
- Run the display rrm-profile all command to check the RRM profile name.
- Check whether the STA or the AP associated with the STA is contained.
If two ACs form a roaming group and the WIDS function is configured, you need to add the APs to the WIDS whitelist. Otherwise, the APs may contain each other, causing STAs to go offline unexpectedly. If there is only one AC, the preceding problem does not occur.
Perform the following operations on the two ACs that form a roaming network. This section uses one AC as an example.
- Run the display wids-profile all command to check whether the WIDS function is configured.
<AC6605> display wids-profile all ------------------------------------------------------------ Profile name Reference ------------------------------------------------------------ default 0 huawei 2 ------------------------------------------------------------ Total: 2
If the WIDS function is configured on the ACs that form a roaming network, check whether a WIDS whitelist profile is bound to the WIDS profile.
- Run the display wids-profile name huawei command to check the WIDS whitelist profile bound to the WIDS profile.
<AC6605> display wids-profile name huawei ------------------------------------------------------------ ...... WIDS spoof profile : huawei WIDS whitelist profile : office //The WIDS whitelist profile office is bound to the WIDS profile. ------------------------------------------------------------
- Run the display wids-whitelist-profile name office command to check whether the AP is added to the WIDS whitelist.
<AC6605> display wids-whitelist-profile name office ------------------------------------------------------------ Type Content ------------------------------------------------------------ OUI dc-d2-fc SSID Huawei-Employee ------------------------------------------------------------ Total: 2
If an AP is not added to the WIDS whitelist, the AP may be contained, causing STAs to go offline. To add an AP to the WIDS whitelist, run the following commands.
<AC6605> system-view [AC6605] wlan [AC6605-wlan] wids-whitelist-profile name office //Create a WIDS whitelist profile named office or enter the WIDS whitelist profile view. [AC6605-wlan-wids-whitelist-office] permit-ap oui dc-d2-fc //Add the AP with the OUI of dc-d2-fc to the WIDS whitelist. [AC6605-wlan-wids-whitelist-office] permit-ap ssid Huawei-Employee //Add the AP with the SSID Huawei-Employee to the WIDS whitelist. [AC6605-wlan-wids-whitelist-office] quit [AC6605-wlan] wids-profile name huawei //Enter the view of the WIDS profile named huawei. [AC6605-wlan-wids-prof-huawei] wids-whitelist-profile office //Bind the WIDS whitelist profile office to the WIDS profile.
- Run the display wids-profile all command to check whether the WIDS function is configured.
- Check whether the STA or the AP associated with the STA is attacked.
- Enable the WIDS attack detection function and provide detailed data about continuous attacks on the device. If an attack source launches attacks repeatedly, a large number of repetitive alarms are generated. To prevent this situation, configure the quiet time function for attack detection. You are advised to disable the attack detection function after fault location. Otherwise, performance loss may occur.
# Configure attack detection.
<AC6605> system-view [AC6605] wlan [AC6605-wlan-view] ap-group name office [AC6605-wlan-ap-group-office] radio 0 [AC6605-wlan-group-radio-office/0] wids attack detect enable all //Enable WIDS attack detection. [AC6605-wlan-group-radio-office/0] quit [AC6605-wlan-ap-group-office] quit [AC6605-wlan-view] wids-profile name huawei [AC6605-wlan-wids-prof-huawei] spoof-detect quiet-time 300 //Set the quiet time for an AP to report the detected spoofing attacks to the AC.
# Check the number of attacks detected.
<AC6605> display wlan ids attack-detected statistics Attack tracking since: 2016-12-27/12:02:11 -------------------------------------------------------------------------------- Type Total -------------------------------------------------------------------------------- Probe request frame flood attack : 0 Authentication request frame flood attack : 0 Deauthentication frame flood attack : 0 Association request frame flood attack : 0 Disassociation request frame flood attack : 0 Reassociation request frame flood attack : 0 Action frame flood attack : 0 EAPOL start frame flood attack : 0 EAPOL logoff frame flood attack : 0 Weak IVs detected : 0 Spoofed deauthentication frame attack : 0 Spoofed disassociation frame attack : 0 Other types of spoofing frame attack : 0 WEP share-key attack : 0 WPA attack : 0 WPA2 attack : 0 WAPI attack : 0 --------------------------------------------------------------------------------
- When detecting flood attacks or brute force password cracking attacks from a device, an AP reports the device to the AC. The AC can be enabled with the dynamic blacklist and adds the device to the dynamic blacklist. Any packets sent from the device are rejected until the dynamic blacklist entry ages.
[AC6605-wlan-wids-prof-huawei] dynamic-blacklist enable
- Enable the WIDS attack detection function and provide detailed data about continuous attacks on the device. If an attack source launches attacks repeatedly, a large number of repetitive alarms are generated. To prevent this situation, configure the quiet time function for attack detection. You are advised to disable the attack detection function after fault location. Otherwise, performance loss may occur.
- Check whether the STA is disconnected due to an accounting failure.
- Run the display aaa abnormal-offline-record mac-address mac-address command in the diagnostic view to check the reason why the STA goes offline unexpectedly.
<AC6605> system [AC6605] diagnose [AC6605-diagnose] display aaa abnormal-offline-record mac-address 60de-4476-e360
If "Start accounting fail" or "Realtime accounting fail" is displayed, the STA goes offline due to an accounting failure.
Possible causes are as follows:
- Check whether the IP address or port number of the RADIUS accounting server on the AC is different from that configured on the RADIUS server.
<AC6605> display radius-server configuration ----------------------------------------------------------- Server-template-name :radius Protocol-version :standard Traffic-unit :B Shared-secret-key :%^%#-YBtX+C'@-Q\&>T~OE~0E%XSH:~PR6D#++Wk[u:%^%# Timeout-interval(in second) :5 Retransmission :3 EndPacketSendTime :3 Dead time(in minute) :5 Domain-included :Original NAS-IP-Address :0.0.0.0 Calling-station-id MAC-format :xxxx-xxxx-xxxx Called-station-id MAC-format :XX-XX-XX-XX-XX-XX Server algorithm :master-backup Authentication Server 1 :192.168.13.1Port:1812Weight:80[UP] Vrf:- LoopBack:NULL Source IP: :: Accounting Server1 :192.168.13.1Port:1813Weight:80[UP] Vrf:- LoopBack:NULL Source IP: :: -----------------------------------------------------------If the IP address or port number of the RADIUS accounting server is different from that on the RADIUS server, perform the following steps to configure the RADIUS accounting server.
<AC6605> system-view [AC6605] radius-server template radius //Enter the RADIUS server template view. [AC6605-radius-radius] radius-server accounting 192.168.13.1 1813 //Configure the IP address and port number for the RADIUS accounting server.
- Check whether the RADIUS server supports accounting and whether accounting is enabled. If accounting is not enabled on the RADIUS server, disable accounting in the corresponding accounting template or configure an online policy for accounting failures. After the accounting fails, the user is kept online.
- Disable the accounting function in the accounting scheme view.
<AC6605> system-view [AC6605] aaa [AC6605-aaa] accounting-scheme test [AC6605-aaa-accounting-test] undo accounting-mode
- Configure a policy to allow user to go online if accounting fails.
- If the cause is "Start accounting fail", configure a policy to allow users to go online if accounting-start fails.
<AC6605> system-view [AC6605] aaa [AC6605-aaa] accounting-scheme test [AC6605-aaa-accounting-test] accounting start-fail online
- If the cause is "Realtime accounting fail", configure a policy to keep users online if real-time accounting fails.
<AC6605> system-view [AC6605] aaa [AC6605-aaa] accounting-scheme test [AC6605-aaa-accounting-test] accounting interim-fail online
- If the cause is "Start accounting fail", configure a policy to allow users to go online if accounting-start fails.
- Disable the accounting function in the accounting scheme view.
- Run the display aaa abnormal-offline-record mac-address mac-address command in the diagnostic view to check the reason why the STA goes offline unexpectedly.
- Check whether the STA goes offline due to a roaming failure after going online.
If a STA goes online successfully but goes offline unexpectedly during roaming, perform the following operations to locate the fault.
- Check whether the security profile configurations before and after roaming are the same and whether Layer 3 roaming is disabled according to STA Roaming Fails.
- If 802.1X authentication is configured and STAs frequently roam, the roaming check on the device may fail. As a result, STAs are disconnected or fail to access the network.
Possible causes of frequent STA roaming are as follows:
- APs are deployed in corridors, and STAs are located in offices. As a result, the signals received by STAs are poor. In this case, it is recommended that APs be re-planned and deployed.
- The roaming sensitivity of STAs is high. In this case, you can adjust the roaming sensitivity of the STAs. For PCs running the Windows operating system, you only need to set the roaming sensitivity to medium in advanced settings of the network adapter. For handheld terminals, the roaming sensitivity is generally not adjustable.
- Check whether the AP associated with the STAs is disconnected.
Run the display ap offline-record all command on the AC to check whether the AP associated with the STA is offline. If so, rectify the fault by referring to An AP Goes Offline Unexpectedly.
- Check whether the signal interference is strong.
Rectify the fault by referring to Signal Interference Occurs.
- Check whether the signal strength of STAs is weak.
Rectify the fault by referring to The Received Signal Strength of a STA Is Weak.
- Check whether the IP address obtained by the STA conflicts with the IP address of an online STA.
- Run the display aaa abnormal-offline-record all command to check the reason why the STA goes offline. If the cause is "IP address conflict", the IP address obtained by the STA conflicts with the IP address of an online STA. Check whether the STA is configured with a static IP address. If so, delete or change the static IP address of the STA.
<AC6605> display aaa abnormal-offline-record all ... User offline reason : IP address conflict ...
- Check whether the DHCP server plan is proper and optimize the improper DHCP server plan.
- Run the display aaa abnormal-offline-record all command to check the reason why the STA goes offline. If the cause is "IP address conflict", the IP address obtained by the STA conflicts with the IP address of an online STA. Check whether the STA is configured with a static IP address. If so, delete or change the static IP address of the STA.
- Check whether the AC fails to synchronize information with the Portal server and forces users to go offline.
- Run the display aaa abnormal-offline-record all command to check the reason why the STA goes offline. If the cause is "WEB user synchronize fail", the AC fails to synchronize information with the Portal server and forces the user to go offline. In this case, check whether information synchronization is enabled on the Portal server. If not, enable information synchronization.
<AC6605> display aaa abnormal-offline-record all ... User offline reason : WEB user synchronize fail ...
- If the Portal server does not support information synchronization, you need to disable information synchronization for Portal authentication users on the AC.
<AC6605> system-view [AC6605] web-auth-server abc [AC6605-web-auth-server-abc] undo user-sync
- Run the display aaa abnormal-offline-record all command to check the reason why the STA goes offline. If the cause is "WEB user synchronize fail", the AC fails to synchronize information with the Portal server and forces the user to go offline. In this case, check whether information synchronization is enabled on the Portal server. If not, enable information synchronization.
- Check whether the Beacon frame sending configuration in the radio profile is proper.A long interval for sending Beacon frames lengthens the dormancy time of STAs, while a short interval for sending Beacon frames increases air interface costs. Therefore, you are advised to set the interval for sending Beacon frames for an AP based on the number of VAPs. The following intervals for sending Beacon frames are recommended for APs with different VAP quantities on a single radio:
- No more than 4 VAPs: about 100 TUs
- 5 to 8 VAPs: about 200 TUs
- 9 to 12 VAPs: about 300 TUs
- 13 to 16 VAPs: about 400 TUs
<AC6605> system-view [AC6605] wlan [AC6605-wlan-view] radio-2g-profile name default [AC6605-wlan-radio-2g-prof-default] beacon-interval 200
- Check whether the status of the radio associated with the STA is normal.
If radio calibration is not performed, some radios on the network may have a high channel usage or adjacent APs may have overlapping channels.
- Run the display radio all command to check whether the radio status is abnormal (for example, the channel usage is high or channels of neighboring APs are the same).
<AC6605> display radio all CH/BW:Channel/Bandwidth CE:Current EIRP (dBm) ME:Max EIRP (dBm) CU:Channel utilization ST:Status WM:Working Mode (normal/monitor/monitor dual-band-scan/monitor proxy dual-band-scan) ------------------------------------------------------------------------------------ AP ID Name RfID Band Type ST CH/BW CE/ME STA CU WM ------------------------------------------------------------------------------------ 1 60de-4474-9640 0 2.4G bgn on 6/20M 24/24 0 55% normal 1 60de-4474-9640 1 5G an on 56/20M 25/25 0 3% normal ------------------------------------------------------------------------------------ Total:2
- If channel interference is severe, you can use the radio calibration function to solve the problem.
You are advised to configure scheduled calibration. If automatic calibration is configured, check whether the calibration interval is properly configured. Frequent calibration increases the service data delay and may cause STAs to go offline.
<AC6605> display channel switch-record all Old/New: Old channel/New channel RfID : Radio ID ---------------------------------------------------------------------------------------------- AP ID AP name RfID Old/New Switch reason Switch time ---------------------------------------------------------------------------------------------- 1 L2-4f 0 1/6 calibration 11:03:30 2014/9/28 ---------------------------------------------------------------------------------------------- Total : 1, printed : 1
- Run the display radio all command to check whether the radio status is abnormal (for example, the channel usage is high or channels of neighboring APs are the same).
- Check whether DHCP snooping is configured on the intermediate network device (for example, a switch).
If DHCP snooping is configured, the switch stops forwarding DHCP packets when the number of entries reaches the maximum. As a result, the STA is immediately disconnected from the network after connecting to the network. You are advised to run the undo dhcp snooping enable command to disable DHCP snooping if this function is not required.
- Check whether the STA is an Apple device.
An apple device will go offline when the screen is locked due to the power saving mechanism of the lock screen. You can view the trace information to check whether the STA sends a disassociation packet. If so, the STA goes offline due to this mechanism.
In V200R008 and later versions, you can enable the STA offline delay function to resolve this problem. After the STA offline delay function is enabled, if a STA initiates a disassociation request and goes offline normally, and then goes online again within the aging time, the STA does not need to be authenticated by the authentication server (including the external and built-in authentication servers). This prevents the STA from being authenticated multiple times.
This function takes effect only for the STAs that use Portal authentication, MAC address authentication, or MAC address-prioritized Portal authentication.
<AC6605> system-view [AC6605] wlan [AC6605-wlan-view] sta-offline-delay enable
- Collect fault information.
- STA's MAC address: xxxx-xxxx-xxxx
- Check AC version information.
[AC-diagnose] vrbd
- Check the AC configuration.
<AC> display current-configuration
- Check AP version information.
[Huawei-diagnose] vrbd
- Check user logout records on the AC.
<AC> display station offline-record
- Run the following commands in the diagnostic view to check the causes of abnormal logout.
[AC-diagnose] display aaa abnormal-offline-record all
- Collect AP information by one click.
<Huawei> display diagnostic-information saved-file <Huawei> display diagnostic-information
- Collect trace information on the AC.
[AC] trace object mac-address mac-address [AC] trace enable
Delete all trace instances after collecting the trace information.
[AC] undo trace object all [AC] undo trace enable
Collect trace information on the STA.
[AC] diagnose [AC-diagnose] station-trace sta-mac mac-address
- Collect trace information on the AP.
<AP> terminal debugging <AP> terminal monitor <AP> system-view [AP] diagnose [AP-diagnose] station-trace assoc station mac-address [AP-diagnose] station-trace key-protocol station mac-address
- Collect kernel logs of the AP.
[Huawei-diagnose] display kernel-logbuf record-range 1 [Huawei-diagnose] display kernel-logbuf record-range 2 [Huawei-diagnose] display kernel-logbuf record-range 3
If the problem persists for a long time, run the following commands to export logs on the AP or AC.
<fce3-3cb6-47e0> save logfile [fce3-3cb6-47e0-diagnose] save diag-logfile <fce3-3cb6-47e0> cd logfile/ <fce3-3cb6-47e0> dir Directory of flash:/logfile/ Idx Attr Size(Byte) Date Time(LMT) FileName 0 -ro- 1,113,850 Aug 31 2015 11:26:57 2015-08-31.12-29-00.dblg 1 -ro- 1,113,970 Aug 31 2015 19:45:02 2015-08-31.23-14-59.dblg 2 -ro- 1,113,920 May 06 2016 08:42:07 2016-05-06.08-47-07.dblg 3 -ro- 1,113,472 May 11 2016 16:19:54 2016-06-09.17-15-52.dblg 4 -ro- 1,114,104 Jun 14 2016 17:55:56 2016-06-14.18-29-52.dblg 5 -ro- 1,114,031 Jun 14 2016 22:22:06 2016-06-14.22-54-08.dblg 6 -ro- 1,113,835 Jun 17 2016 17:29:24 2016-06-17.18-08-54.dblg 7 -ro- 1,113,843 Jun 17 2016 20:34:50 2016-06-17.20-47-59.dblg 8 -ro- 1,113,743 Jun 22 2016 20:06:19 2016-06-22.20-50-06.dblg 9 -ro- 1,113,271 Jun 28 2016 16:58:37 2016-06-28.19-58-45.dblg 10 -ro- 1,113,494 Jun 29 2016 17:33:23 2016-06-29.18-32-36.dblg 11 -ro- 1,113,824 Jun 30 2016 01:22:38 2016-06-30.02-19-21.dblg 12 -ro- 1,113,773 Jun 30 2016 09:10:31 2016-06-30.10-09-39.dblg 13 -ro- 1,125,418 Jun 30 2016 09:26:03 2016-06-30.12-25-03.log 14 -ro- 1,113,801 Jul 11 2016 09:59:38 2016-07-11.10-13-26.dblg 15 -ro- 1,113,732 Jul 13 2016 15:41:02 2016-07-13.15-54-31.dblg 16 -ro- 1,129,531 Jul 13 2016 19:55:33 2016-07-15.10-37-46.dblg 17 -ro- 1,113,787 Nov 26 2018 21:54:45 2018-11-27.01-02-52.dblg 18 -ro- 1,113,604 Nov 27 2018 22:56:38 2018-11-28.00-20-24.dblg 19 -ro- 1,113,723 Nov 28 2018 07:37:57 2018-11-28.08-40-58.dblg 20 -ro- 1,113,744 Nov 28 2018 15:14:40 2018-11-28.16-10-55.dblg 21 -rw- 384,570 Jul 19 2016 10:07:11 log.dblg 22 -rw- 681,533 Jul 19 2016 10:06:57 log.log 11,144 KB total (1,512 KB free)You must log in to the AP to collect AP logs.
From V200R008C10 and later versions, you only need to run the save logfile command to save logs. After the logs are saved, use FTP or TFTP to export .log and .dblg log files in the corresponding time period.
Information collection is mainly performed in the diagnostic view. To enter the diagnostic view, run the following commands.
<Huawei> system-view [Huawei] diagnose
