display station online-fail-record

Function

The display station online-fail-record command displays records of STAs' failures to go online.

Format

display station online-fail-record { all | ap-name ap-name | ap-id ap-id | sta-mac sta-mac-address }

Parameters

Parameter	Description	Value
all	Displays going-online failure records of all STAs.	-
ap-name ap-name	Displays records of STAs' failures to go online on the AP with a specified name.	The AP name must exist.
ap-id ap-id	Displays records of STAs' failures to go online on the AP with a specified ID.	The AP ID must exist.
sta-mac sta-mac-address	Displays online failure records of the STA with the specified MAC address.	The STA's MAC address must exist.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

If a STA fails to go online, you can run the command to check the failure reason, which helps locate the fault.

After the number of records of STAs' failures to go online reaches the maximum that can be stored, new records overwrite existing ones.

Example

# Display online failure records of all STAs.

<HUAWEI> display station online-fail-record all
Reason distribution
----------------------------------------------------------------------------------------
Reason                                                                 Count Percent
----------------------------------------------------------------------------------------
The key is incorrect or the STA uses the cached PMK.                   1     100.00%
----------------------------------------------------------------------------------------
Total Count: 1

Recent records
Rf/WLAN: Radio ID/WLAN ID
------------------------------------------------------------------------------
STA MAC         AP ID Ap name  Rf/WLAN    Last record time
                Reason
------------------------------------------------------------------------------
14cf-9202-13dc  0     area_11  0/1        2018-04-11/15:53:18
                The key is incorrect or the STA uses the cached PMK.
------------------------------------------------------------------------------
Total stations: 1 Total records: 1

**Table 1** Description of the **display station online-fail-record** command output
Item	Description
Reason distribution	Distribution of STA going-online failure reasons.
Count	Number of times that a reason is displayed.
Percent	Percentage of a reason.
Recent records	Recent STA going-online reason records.
Radio ID/WLAN ID	Radio/VAP to which the STA fails to connect.
STA MAC	MAC address of the STA that fails to go online.
AP ID	ID of the AP on which the STA fails to go online.
Ap name	Name of the AP on which the STA fails to go online.
Last record time	Last time when the STA failed to go online.
Reason	Reason for the STA's failure to go online. For details about STAs' going-online failure reasons and handling suggestions, see Table 2. For troubleshooting methods, see STAs Fail to Associate with a WLAN.

**Table 2** STAs' going-online failure reasons and handling suggestions
Reason Why a STA Fails to Go Online	Remarks	Handling Suggestion
STA authentication times out.	-	Reassociate the STA with the network. If the failure persists, contact technical support personnel.
Invalid association request packet.	-	Reassociate the STA with the network. If the failure persists, the STA may be incompatible with the AP. Contact technical support personnel.
The encryption mode is inconsistent on the STA and AP.	-	Ensure that the encryption mode is consistent on the STA and AP.
Authentication fails in the association stage.	-	Reassociate the STA with the network. If the failure persists, contact technical support personnel.
The STA is not authenticated.	-	Reassociate the STA with the network. If the failure persists, contact technical support personnel.
The AP does not support the rate set specified in the association request packet of the STA.	-	Change the basic rate set in the radio profile and reassociate the STA with the network.
The encryption algorithm is inconsistent on the STA and AP.	-	Ensure that the encryption algorithm is consistent on the STA and AP.
Failed to decrypt the challenge packet.	-	Verify that the STA works properly and reassociate the STA with the network. If the failure persists, contact technical support personnel.
Access from legacy STAs is denied.	-	Verify that access from legacy STAs is denied. To allow access from legacy STAs, run the undo legacy-station disable command.
The number of STAs exceeds the physical specifications allowed by the AP.	-	Expand the network capacity or retain the current configuration as required.
The WMM capability of the STA and VAP does not match.	-	Check whether the VMM function is enabled in the radio profile or check the WMM configuration on the STA.
STAs have a compatibility issue (Incorrect network type flag carried by STAs).	-	Verify that the STA works properly and reassociate the STA with the network. If the failure persists, contact technical support personnel.
STAs have a compatibility issue (STAs do not support short timeslots).	-	Check whether the STA supports 802.11g.
STAs have a compatibility issue (STAs do not support DFS).	-	Check whether the STA supports 802.11h.
The number of associated STAs exceeds the maximum allowed by the AC.	The number of associated STAs on the AC exceeds the maximum.	Expand the network capacity or retain the current configuration as required.
The STA is not in the global whitelist.	-	Check whether the STA needs to be added to the global whitelist.
The STA is in the global blacklist.	-	Check whether the STA needs to be added to the global blacklist.
The STA is not in the VAP's whitelist.	-	Check whether the STA needs to be added to the VAP's whitelist.
The STA is in the VAP's blacklist.	-	Check whether the STA needs to be added to the VAP's blacklist.
The STA associates with a heavily loaded radio.	-	Check whether the threshold for load balancing is proper.
The STA is in the dynamic blacklist.	-	Check the attack records and check whether the STA has initiated attacks.
The association or reassociation packet check fails.	-	Reassociate the STA with the network. If the failure persists, contact technical support personnel.
The number of users exceeds the maximum allowed on the VAP defined by the AC.	-	Expand the network capacity or run the max-sta-number command to increase the maximum number of STAs associated with the VAP.
The number of STAs exceeds the maximum allowed in the VAP reported by the AP.	-	Expand the network capacity or run the max-sta-number command to increase the maximum number of STAs associated with the VAP.
The STA uses a static IP address.	-	Check whether the STA uses a static IP address. If not required, configure the STA to obtain an IP address dynamically.
The STA's SNR is below the user CAC threshold.	-	Check whether the SNR-based user CAC threshold is proper. To change the threshold, run the uac client-snr threshold command. Reassociate the STA with the network. Alternatively, determine the STA location and provide coverage to the location.
The number of STAs exceeds the UAC threshold of the radio.	The number of associated STAs exceeds the user CAC threshold based on the number of users.	Check whether the user CAC threshold based on the number of users is properly set. If not, modify the threshold by running the uac client-number threshold command and reassociate the STA with the network.
The number of STAs exceeds the band steering threshold of the radio.	-	Verify that the band steering configuration is proper, and reassociate the STA with the network.
The STA does not send an authentication request before associating with the network.	-	Reassociate the STA with the network. If the failure persists, contact technical support personnel.
The key is incorrect or the STA uses the cached PMK.	-	Ensure that the STA uses the correct key and reassociate the STA with the network. If the failure persists, contact technical support personnel.
Failed to receive the handshake packet (2/4) from the STA.	-	Ensure that the STA uses the correct key and reassociate the STA with the network. If the failure persists, contact technical support personnel.
Failed to receive the handshake packet (4/4) from the STA.	-	Ensure that the STA uses the correct key and reassociate the STA with the network. If the failure persists, contact technical support personnel.
WAPI authentication times out.	-	Check the network quality and reassociate the STA with the network. If the failure persists, contact technical support personnel.
WAPI authentication fails.	-	Reassociate the STA with the network. If the failure persists, contact technical support personnel.
Reauthentication fails.	-	Check the intermediate network connectivity between the AP and AC, and reassociate the STA with the network. If the failure persists, contact technical support personnel.
Authentication fails.	-	Reassociate the STA with the network. If the failure persists, contact technical support personnel.
The authentication request times out.	-	Reassociate the STA with the network. If the failure persists, contact technical support personnel.
Key negotiation fails.	-	Ensure that the STA uses the correct key and reassociate the STA with the network. If the failure persists, contact technical support personnel.
Exceeded the maximum number of users on the central AP.	The number of associated STAs exceeds the maximum allowed by the central AP.	Expand the network capacity or retain the current configuration as required.
Key negotiation fails (the length of the key data(2/4) is invalid).	-	Verify that the correct password is entered on the STA. If this fault persists, contact technical support personnel.
Key negotiation fails (the length of the key data(4/4) is invalid).	-	Verify that the correct password is entered on the STA. If this fault persists, contact technical support personnel.
Key negotiation fails (fail to send the handshake packet).	-	Verify that the correct password is entered on the STA. If this fault persists, contact technical support personnel.
Key negotiation fails (the key information of the handshake packet is invalid).	-	Verify that the correct password is entered on the STA. If this fault persists, contact technical support personnel.
The radio type is inconsistent between the AC and AP.	-	Run the display ap config-info command to verify the AP radio configuration.
The local eap server is up but has no reply.	The local EAP server is Up but does not respond.	Check whether the local EAP configuration is correct.
Local eap authentication reject.	The local EAP server responds with a reject packet.	Check whether the user name and password are correct.
Local Authentication user block.	The local user is locked.	Run the local-user user-name state active command to activate the user.
Wireless access is not supported	Wireless access is not supported in traditional mode.	Switch the NAC configuration mode to unified mode.
The possible cause is that the STA configuration is incorrect, the signal quality on the air interface is low, or the AC forces the STA to reassociate with the network to ensure uninterrupted STA services.	-	Reassociate the STA with the network. If this fault persists, contact technical support personnel.
The client capability does not match.	-	The client capability does not meet the requirements. Upgrade the client version or Wi-Fi version.
Compatibility problems exist on the wireless client. (The HT capability carried by the client is incorrect).	-	Upgrade the client version or Wi-Fi version, or run the undo legacy-station disable command to permit access of non-HT STAs.
The client access is restricted temporarily.	-	To allow a wireless client to access a better AP, temporarily restrict the client to access this AP. It is normal if the terminal can connect to a better AP. If a client fails to connect to an AP for multiple consecutive times, check whether APs need to be added.
Received an Authentication frame with authentication transaction sequence number out of expected sequence.	-	Reassociate the STA with the network. If this fault persists, contact technical support personnel.
Invalid RSNE capabilities.	-	Forget the network, reassociate the STA with the network. If this fault persists, contact technical support personnel.
Cipher suite rejected because of security policy.	-	Check whether the encryption mode and key configurations on the wireless terminal are correct. If this fault persists, contact technical support personnel.
Invalid pairwise master key identifier(PMKID).	-	Forget the network, reassociate the STA with the network. If this fault persists, contact technical support personnel.
Invalid group cipher.	-	Forget the network, reassociate the STA with the network. If this fault persists, contact technical support personnel.
Invalid pairwise cipher.	-	Forget the network, reassociate the STA with the network. If this fault persists, contact technical support personnel.
Invalid MDE.	-	Forget the network, reassociate the STA with the network. If this fault persists, contact technical support personnel.
Invalid FTE.	-	Forget the network, reassociate the STA with the network. If this fault persists, contact technical support personnel.
Roaming check failed because the user left the current AC during inter-AC roaming.	The STA goes offline during inter-AC roaming.	If there are a large number of such records, run the display cpu-defend statistics wired command to check whether packets between ACs are lost.
Others reason.	-	Contact technical support personnel.