No relevant resource is found in the selected language.
Enterprise
Worldwide
Huawei Global - English
Support Documentation
S7700 V200R019C10 Log Reference

This document provides the explanations, causes, and recommended actions of logs on the product.

Rate and give feedback:
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).
WLAN

WLAN

WLAN/4/AC_AUTHENTICATE_FAIL

Message

WLAN/4/AC_AUTHENTICATE_FAIL: Failed to authenticate services with the peer device. (local address=[STRING], peer address=[STRING], service=[STRING])

Description

The local device failed to authenticate services with the peer device.

Parameters

Parameter Name Parameter Meaning

local address

Indicates the IP address of the local device.

peer address

Indicates the IP address of the peer device.

service

Indicates the type of the service to be authenticated.

Possible Causes

Cause 1:

The service type is Roam, and no peer member is configured for the mobility group.

Cause 2:

The service type is Election, and the number of STAs connected to the elected Leader AP has reached the maximum.

Procedure

  1. Check whether the corresponding configuration is correct based on the service type.

    • If the alarm is cleared, go to 4.
    • If not, go to 2

  2. Correct the configuration and then check whether the service is recovered.

    • If the alarm is cleared, go to 3.
    • If not, go to 4

  3. Run the display wlan wlkm link-info command in the diagnostic view to check whether the service link is successfully established.

    • If the alarm is cleared, go to 5.
    • If not, go to 4

  4. Collect alarms, logs, and configurations, and contact technical support personnel.
  5. End.

WLAN/4/AP_CHANNEL_CONTIGUOUS

Message

WLAN/4/AP_CHANNEL_CONTIGUOUS:When the two 5G radios work on neighboring channels, user experience is affected.(MAC=[OPAQUE], ApID=[ULONG], Sysname=[STRING], Reason=[STRING])

Description

5G radios of an AP work on adjacent channels, affecting user experience.

Parameters

Parameter Name Parameter Meaning

MAC

Indicates the MAC address of the AP.

ApID

Indicates the AP ID.

Sysname

Indicates the AP name.

Reason

Indicates the reason that the 5G radios work on adjacent channels.

Possible Causes

There are not sufficient calibration channels for 5G radios of an AP. If three radios of an AP work on the 5 GHz band, at least five calibration channels are required. If two radios of an AP work on the 5 GHz band, at least three calibration channels are required. If there are not sufficient calibration channels, the interval between calibration channels is smaller than one channel.

Procedure

  1. Increase the number of channels in a calibration channel set.

    The following assumes five channels in a calibration channel set.

    <HUAWEI> system-view
[HUAWEI] wlan 
[HUAWEI-wlan-view] regulatory-domain-profile name domain1
[HUAWEI-wlan-regulate-domain-domain1] dca-channel 5g channel-set 149,153,157,161,165

  2. Check whether the log is generated after radio calibration.

    • If so, go to 3
    • If not, go to 4

  3. Collect the related alarm, log, and configuration information, and contact Huawei technical support personnel.
  4. End

WLAN/3/AP_NORMAL_TO_FAULT

Message

WLAN/3/AP_NORMAL_TO_FAULT: AP changed from normal to fault. (MAC=[OPAQUE], ApID=[ULONG], Sysname=[STRING], Reason=[STRING])

Description

The AP state changed to fault.

Parameters

Parameter Name Parameter Meaning

MAC

Indicates the AP's MAC address.

ApID

Indicates the AP ID.

Sysname

Indicates the AP's system name.

Reason

Indicates the reason why the AP state changed to fault. For details, see Table 169-1.

Possible Causes

For details, see Table 169-1.

Procedure

  1. Handle faults according to handling suggestions in Table 169-1.

    Table 169-1 Possible reasons and suggestions for APs to go offline

    Reason Why an AP Goes Offline

    Suggestion

    The AC country code is modified.

    The AP goes offline due to normal configuration changes, and no action is required.

    The AP is replaced.

    The AP goes offline due to normal configuration changes, and no action is required.

    Reboot by ap update reset command.

    The AP is reset automatically after the upgrade.

    The AP resets to load the new version file after the upgrade, and no action is required.

    A command is delivered to reboot an AP.

    The AC delivers a reboot command to the AP, and no action is required.

    An AP is deleted.

    The AP is deleted on the AC, and no action is required.

    The license expires.

    Apply for a new license.

    Huawei's Electronic Software Delivery Platform (ESDP) is accessible from the Internet and Huawei intranet.

    Insufficient license resources.
    Choose one of the following handling suggestions based on the networking:
    • If license control is deployed, check whether the link between the license server and client is disconnected. If so, restore the link.
    • If N+1 or dual-link backup is deployed, check whether the active and standby link is disconnected. If so, restore the link.
    • If the number of APs on the network exceeds the total number of license resources, apply for a new license.

    The AP is added to the blacklist.

    Check whether the AP needs to be added to the blacklist.

    A CAPWAP tunnel is faulty (due to inconsistent link IDs).

    The AP will automatically attempt to recover the link, and no action is required.

    The DTLS configuration of the CAPWAP tunnel changes.

    The AP goes offline due to normal configuration changes, and no action is required.

    The AP's factory settings are restored.

    The AP goes offline due to normal configuration changes, and no action is required.

    The radio type is inconsistent between the AC and AP.

    Run the display ap config-info command to verify the AP radio configuration.

    Heartbeat packet transmission for the CAPWAP data tunnel between the AC and AP times out.

    Check the intermediate network between the AP and AC.

    Heartbeat packet transmission for the CAPWAP control tunnel between the AC and AP times out.

    Check the intermediate network between the AP and AC.

    The dual-link networking configuration is modified.

    The configuration change causes the AP to automatically reboot, and no action is required.

    The AP name is modified.

    The AP goes offline due to normal configuration changes, and no action is required.

    The AP group name is modified.

    The AP goes offline due to normal configuration changes, and no action is required.

    The management VLAN is modified.

    The AP goes offline due to normal configuration changes, and no action is required.

    AP provisioning parameters are set.

    The AP goes offline due to normal configuration changes, and no action is required.

    The CAPWAP source IP address is deleted.

    The AP goes offline due to normal configuration changes, and no action is required.

    The central AP goes offline.

    Check the reason why the central AP goes offline.

    The central AP proactively reboots RUs.

    The AP goes offline due to normal configuration changes, and no action is required.

    The AP is powered off and restarts.

    If the AP restarts repeatedly, check whether the AP power supply mode matches the actual power supply.

    An internal error (KP) occurs.

    Contact technical support personnel.

    An internal error (VOS signal error) occurs.

    Contact technical support personnel.

    An internal error (forwarding error monitored by MFPI) occurs.

    Contact technical support personnel.

    An internal error (PKO error monitored by MSC) occurs.

    Contact technical support personnel.

    An internal error (reset due to timer expiration) occurs.

    Contact technical support personnel.

    An internal error (reset of the write CPLD register) occurs.

    Contact technical support personnel.

    The reset button is pressed to reset the AP.

    Check whether the AP is manually reset.

    The AP restarts due to a CANBUS reset.

    Contact technical support personnel.

    The AP restarts due to AP interference.

    Contact technical support personnel.

    The AP restarts due to a chip exception.

    The AP restarts due to a firmware exception.

    Contact technical support personnel.

    The CAPWAP sensitive-info PSK is modified.

    The configuration change causes the AP to automatically reboot, and no action is required.

    The CAPWAP integrity-check PSK is modified.

    The configuration change causes the AP to automatically reboot, and no action is required.

    The country code is inconsistent on the AC and AP.

    Check the country code configuration on the AC and AP.

    The AP is forcibly disconnected.

    No action is required.

    The wideband status change.

    The AP goes offline due to normal configuration changes, and no action is required.

    Reset for a configuration delivery failure.

    Check network connectivity. If no problem is found, contact technical support personnel.

    Reboot for the branch group of AP change.

    The AP goes offline due to normal configuration changes, and no action is required.

    The AC license expires.

    Re-activate the AC license.

    A CAPWAP tunnel is faulty (due to a CAPWAP link entry verification failure).

    The AP will automatically attempt to recover the link, and no action is required.

    Batch delete

    Check whether the active AC runs properly. When the active AC is restored, the AP switches to this active AC to go online.

    Switch service radio to proxy scanning radio.

    The configuration change causes the AP to automatically reboot, and no action is required.

    Switch proxy scanning radio to service radio.

    The configuration change causes the AP to automatically reboot, and no action is required.

    The WAC license expires.

    Purchase a new license and load it to iMaster NCE-Campus.

    The device has been disconnected from the iMaster NCE-Campus for more than 90 days.

    Verify the iMaster NCE-Campus address configured on the AC, and check network connectivity.

    The device is deleted from the iMaster NCE-Campus.

    No action is required.

    The iMaster NCE-Campus does not deliver AP information.
    1. Verify that AP information is correctly added to iMaster NCE-Campus, the AP is associated with the AC, and the AC is online.
    2. Verify the iMaster NCE-Campus address configured on the AC, and check network connectivity.
    3. Check whether iMaster NCE-Campus fails to deliver AP information. If so, manually deliver AP information again.

    An internal error (Reset for firmware abnormal) occurs.

    Contact technical support personnel.

    An internal error (Reset for abnormal network port self-healing) occurs.

    Contact technical support personnel.

    An internal error (Reset for the forcible AP disconnection in specific scenarios) occurs.

    Contact technical support personnel.

    An internal error (Reset for slow task switching) occurs.

    Contact technical support personnel.

    An internal error (Reset for MFPI detect CAP PBUF use out) occurs.

    Contact technical support personnel.

    An internal error (Reset for ap abnormal self-healing) occurs.

    No action is required.

    An internal error (Reset for exception(redis-server exit)) occurs.

    Contact technical support personnel.

    An internal error (Reset for exception(confd exit)) occurs.

    Contact technical support personnel.

    An internal error (Reset for exception(callhome exit)) occurs.

    Contact technical support personnel.

    An internal error (Reset for an abnormal process) occurs.

    Contact technical support personnel.

    N+1 switchover of APs.

    No action is required.

    During inter-AC roaming, the SSID is inconsistent with that before roaming.

    Check whether the SSID is consistent before and after roaming. If this fault persists, contact technical support personnel.

    An internal error (Reset for an NP heartbeat message exception) occurs

    Contact technical support personnel.

    An internal error (exceed the extreme temperature) occurs.

    Take proper measures to lower the ambient temperature, for example, by lowering the air conditioner temperature and ventilate the equipment room.

    An internal error (memory use out) occurs.

    Contact technical support personnel.

    An internal error (dophi-server exit) occurs.

    Contact technical support personnel.

    An internal error (Wi-Fi SDK self-healing failure) occurs.

    Contact technical support personnel.

    Reconnect by command.

    No action is required.

    Reset for the radio mode change.

    No action is required.

    Reset for RTU license activation.

    No action is required.

  2. Collect traps, logs, and configurations, and contact technical support personnel.
  3. End

WLAN/3/AP_PROVISION_COMMIT_FAIL

Message

WLAN/3/AP_PROVISION_COMMIT_FAIL: Failed to commit AP provision. (MAC=[OPAQUE], ApID=[ULONG], Sysname=[STRING], Reason=[STRING])

Description

Failed to commit the AP configuration.

Parameters

Parameter Name Parameter Meaning
MAC Indicates the AP's MAC address.
ApID Indicates the AP ID.
Sysname Indicates the AP's system name.
Reason
Indicates the reason why the AP provision failed to be committed.
  • AP decode fail: The AP fails to parse the configuration delivered by the AC.
  • Message send fail: The AC fails to deliver the AP configuration.
  • Message timeout: AP configuration delivery by the AC times out.

Possible Causes

The link between the AP and AC was faulty or the link environments were bad. As a result, the provision configuration packet sent from the AC to the AP was lost.

Procedure

  1. Check whether the link between the AP and AC is working properly.

    • If so, go to 2.
    • If not, go to 3.

  2. Restart the AP and check whether the log is still generated.

    • If so, go to 3.
    • If not, go to 4.

  3. Collect traps, logs, and configurations, and contact technical support personnel.
  4. End

WLAN/3/AP_RESET

Message

WLAN/3/AP_RESET: AP would be reset. (MAC=[OPAQUE], ApID=[ULONG], Sysname=[STRING], Reason=[STRING])

Description

The AP restarted.

Parameters

Parameter Name Parameter Meaning
MAC AP's MAC address.
ApID AP ID.
Sysname AP's system name.
Reason Reason for an AP restart. If the reason is config-fail, the AP is restarted because configuration delivery fails.

Possible Causes

The configuration fails to be delivered to an AP when it goes online, and the AP then restarts.

Procedure

  1. Check whether the AP can go online after the restart.

    • Yes => 3
    • No => 2

  2. Collect traps, logs, and configurations, and contact technical support personnel.
  3. End

WLAN/3/AP_RESET_FAIL

Message

WLAN/3/AP_RESET_FAIL: AP reset failed. (MAC=[OPAQUE], ApID=[ULONG], Sysname=[STRING], Reason=[STRING])

Description

The AP failed to be restarted.

Parameters

Parameter Name Parameter Meaning
MAC Indicates the AP's MAC address.
ApID Indicates the AP ID.
Sysname Indicates the AP's system name.
Reason
Indicates the reason for an AP restart failure.
  • update reset: The AP is upgraded.
  • clear config: The AP configuration is cleared.
  • reset timeout: The AP configuration command execution times out because the port is down.
  • other reason: Other reasons.

Possible Causes

The link between the AP and AC was faulty or the link environments were bad. As a result, the restart packet sent from the AC to the AP was lost.

Procedure

  1. Check whether the link between the AP and AC is working properly.

    • If so, go to 2.
    • If not, go to 3.

  2. Restart the AP and check whether the log is still generated.

    • If so, go to 3.
    • If not, go to 4.

  3. Collect traps, logs, and configurations, and contact technical support personnel.
  4. End

WLAN/5/WLAN_DETECT_ROGUE_DEVICE

Message

WLAN/5/WLAN_DETECT_ROUGE_DEVICE: Detected rogue device. (Device MAC=[OPAQUE], Device type=[INTEGER], Device channel=[INTEGER], Device RSSI =[LONG], Device SSID=[OCTET], Monitor AP name=[OCTET], Monitor AP MAC=[OPAQUE], Monitor AP radio =[INTEGER], Monitor AP IP=[OCTET], Monitor AP channel=[INTEGER], Monitor AP ID =[INTEGER])

By default, this log is not recorded. If it needs to be recorded, run the rogue-device log enable command in the WLAN view.

Description

An AP detects a rogue device.

Parameters

Parameter Name Parameter Meaning

Device MAC

Indicates the MAC address of a rogue device.

Device type

Indicates the type of a rogue device.

  • 1: rogue AP
  • 2: rogue Ad-hoc
  • 3: rogue bridge
  • 4: rogue STA

Device channel

Indicates the channel of a rogue device.

Device RSSI

Indicates the RSSI of a rogue device.

Device SSID

Indicates the SSID of a rogue device.

Monitor AP name

Indicates the name of the monitoring AP.

Monitor AP MAC

Indicates the MAC address of the monitoring AP.

Monitor AP radio

Indicates the radio of the monitoring AP.

Monitor AP IP

Indicates the IP address of the monitoring AP.

Monitor AP channel

Indicates the channel of the monitoring AP.

Monitor AP ID

Indicates the ID of the monitoring AP.

Possible Causes

An AP detects a rogue device.

Procedure

  1. Check parameters in the hwWlanWidsRogueDeviceTrap alarm to figure out the number of rogue devices and impacts on services.

    • If only a few rogue devices exist and services are not affected, no action is required.
    • If services are affected, go to step 2.

  2. Run the display wlan ids device-detected all command to check the detected rogue devices.
  3. Contain the detected rogue devices and configure WIDS rogue device containment.
    1. Run the wids contain enable command in the AP group radio view or AP radio view to enable rogue device containment.
    2. Run the contain-mode command in the WIDS profile view to configure the rogue device containment mode for APs.
  4. Check whether the log persists.

    • If so, go to step 6.
    • If not, go to step 7.

  5. Collect alarm, log, and configuration information, and contact technical support personnel.
  6. End.

WLAN/6/WLAN_DETECT_ROGUE_DEVICE_CLEAR

Message

WLAN/6/WLAN_DETECT_ROUGE_DEVICE_CLEAR: Clear Rogue device. (Device MAC=[OPAQUE], Device type=[INTEGER], Device channel=[INTEGER], Device RSSI =[LONG], Device SSID=[OCTET], Monitor AP name=[OCTET], Monitor AP MAC=[OPAQUE], Monitor AP radio =[INTEGER], Monitor AP IP=[OCTET], Monitor AP channel=[INTEGER], Monitor AP ID =[INTEGER])

By default, this log is not recorded. If it needs to be recorded, run the rogue-device log enable command in the WLAN view.

Description

An AP detects that a rogue device is cleared.

Parameters

Parameter Name Parameter Meaning

Device MAC

Indicates the MAC address of a rogue device.

Device type

Indicate the type of a rogue device.

  • 1: rogue AP
  • 2: rogue Ad-hoc
  • 3: rogue bridge
  • 4: rogue STA

Device channel

Indicates the channel of a rogue device.

Device RSSI

Indicates the RSSI of a rogue device.

Device SSID

Indicates the SSID of a rogue device.

Monitor AP name

Indicates the name of the monitoring AP.

Monitor AP MAC

Indicates the MAC address of the monitoring AP.

Monitor AP radio

Indicates the radio of the monitoring AP.

Monitor AP IP

Indicates the IP address of the monitoring AP.

Monitor AP channel

Indicates the channel of the monitoring AP.

Monitor AP ID

Indicates the ID of the monitoring AP.

Possible Causes

A rogue device is cleared.

Procedure

  1. This log is informational only, and no action is required.

WLAN/3/DTLS_PSK_SET_FAIL

Message

WLAN/3/DTLS_PSK_SET_FAIL: Failed to deliver DTLS PSK. (LinkID=[ULONG], ClientMac=[OPAQUE], Reason=[STRING])

Description

Failed to deliver the PSK when the CAPWAP tunnel is encrypted using DTLS.

Parameters

Parameter Name Parameter Meaning
LinkID Indicates the CAPWAP tunnel ID.
ClientMac Indicates the MAC address of DTLS negotiation packet receiver.
Reason
Indicates the reason why DTLS encryption failed.
  • Message send fail: The sender fails to send packets.
  • Response message decode error: The sender fails to parse the received response packet because the response packet is invalid.
  • Response message return error: The sender receives a notification indicating that the receiver fails to parse packets.
  • Message timeout: The sender does not receive any response packet.

Possible Causes

The link between the sender and receiver was faulty.

Procedure

  1. Check whether the link between the sender and receiver is working properly.

    • If so, go to 2.
    • If not, go to 3.

  2. Restart the receiver and check whether the log is still generated.

    • If so, go to 3.
    • If not, go to 4.

  3. Collect traps, logs, and configurations, and contact technical support personnel.
  4. End

WLAN/4/WCWP_LOG_USER_WARN

Message

WLAN/4/WCWP_LOG_USER_WARN: %s, the user choose %c

Description

Users performed interactive operations.

Parameters

Parameter Name Parameter Meaning
%s
  • When deciding whether to change dtls switch, the user choose: The device asks whether to enable DTLS encryption.
  • When deciding whether to delete capwap source, the user choose: The device asks whether to delete the CAPWAP source interface.
  • When deciding whether to change default psk, the user choose: The device asks whether to change the default PSK of the CAPWAP tunnel.
  • When deciding whether to change capwap share-key, the user choose: The device asks whether to change the PSK for encrypting sensitive information.
%c
  • y: Users entered y.
  • n: Users entered n.

Possible Causes

Interactive operations between the device and users were recorded.

Procedure

  1. This log is informational only, and no action is required.

WSTA/5/IWAP_LOG_CLIENT_INFO_ROAM_OR_OFFLINE_INFO

Message

WSTA/5/IWAP_LOG_CLIENT_INFO_ROAM_OR_OFFLINE_INFO:[IWAP_CLIENT_INFO_ROAM_INFO]ACMAC:[STRING1];ACNAME:[STRING2];CurrentAPMAC:[STRING3];CurrentAPNAME:[STRING4];CurrentRSSI(dBm):[LONG];APMAC:[STRING5];APNAME:[STRING6];RADIO:[ULONG];BAND:[STRING7];SSID:[STRING8];ACCESS TYPE:[STRING14];USER:[STRING9];MAC:[STRING10];TIME:[STRING11];ZONE:UTC+[ULONG];DAYLIGHT:[STRING12];ERRCODE:[ULONG];RESULT:[STRING13];OnlineTime(s):[ULONG];UpPacketNum:[UINT64];UpByte:[UINT64];DownPacketNum:[UINT64];DownByte:[UINT64];RSSI(dBm):[LONG];

WSTA/5/IWAP_LOG_CLIENT_INFO_ROAM_OR_OFFLINE_INFO:[IWAP_CLIENT_INFO_OFFLINE_FLOW_INFO]ACMAC:[STRING1];ACNAME:[STRING2];APMAC:[STRING3];APNAME:[STRING4];RADIO:[ULONG];SSID:[STRING5];ACCESS TYPE:[STRING14];USER:[STRING6];MAC:[STRING7];TIME:[STRING8];ZONE:UTC+[ULONG];DAYLIGHT:[STRING9];ERRCODE:[ULONG];RESULT:[STRING10];OnlineTime(s):[ULONG];UpPacketNum:[UINT64];UpByte:[UINT64];DownPacketNum:[UINT64];DownByte:[UINT64];AvgRSSI(dBm):[LONG];AvgSNR(dB):[ULONG];Band:[STRING11];VLAN:[ULONG];IP:[STRING12];

When there are a large number of users, this log is frequently recorded, affecting system performance and overwriting other log information. Therefore, this log is not recorded by default. To enable the system to record this log, run the report-sta-info enable command in the WLAN view.

Description

Information about STA roaming or going-offline was recorded.

Parameters

Parameter Name Parameter Meaning

ACMAC

Indicates the AC's MAC address.

ACNAME

Indicates the AC's system name.

CurrentAPMAC

Indicates the MAC address of the AP to which a user roams.

CurrentAPNAME

Indicates the system name of the AP to which a user roams.

CurrentRSSI

Indicates the RSSI of the AP to which a STA roams.

RSSI

Indicates the RSSI of the AP from which a STA roams.

APMAC

Indicates the AP's MAC address.

APNAME

Indicates the AP's system name.

RADIO

Indicates the radio ID.

BAND

Indicates the working frequency band of a radio.

SSID

Indicates the SSID.

ACCESS TYPE

Indicates the STA authentication mode.

USER

Indicates the user name.

MAC

Indicates the user's MAC address.

TIME

Indicates the system time.

ZONE:UTC+

Indicates the time zone.

DAYLIGHT

Indicates whether the daylight saving time is used.

  • true: The daylight saving time is used.
  • false: The daylight saving time is not used.

ERRCODE

Indicates the failure/state error code.

RESULT

Indicates the failure reason.

OnlineTime(s)

Indicates the online duration of the user.

UpPacketNum

Indicates the number of upstream packets.

UpByte

Indicates the number of upstream bytes.

DownPacketNum

Indicates the number of downstream packets.

DownByte

Indicates the number of downstream bytes.

AvgRSSI(dBm)

Indicates the user's average RSSI.

AvgSNR(dB)

Indicates the user's average SNR.

Band

Indicates the user's band.

VLAN

Indicates the user's accessed VLAN.

IP

Indicates the user's IP address.

Possible Causes

  • Users roamed between different APs on a WLAN.

  • Users could not connect to the WLAN and got offline.

Procedure

  1. This log is informational only, and no action is required.

WSTA/6/WLAN_LOG_USER_WLAN_STA_INFO_AP_ASSOCIATE

Message

WSTA/6/WLAN_LOG_USER:[WLAN_STA_INFO_AP_ASSOCIATE]ACMAC:[STRING1];ACNAME:[STRING2];APMAC:[STRING3];APNAME:[STRING4];APIP:[STRING5];RADIO:[UCHAR];BAND:[STRING6];SSID:[STRING7];ACCESS TYPE:[STRING13];USER:[STRING8];MAC:[STRING9];ASSOCDURATION:[STRING14];TIME:[ULONG];ZONE:UTC[STRING10];DAYLIGHT:[STRING11];ERRCODE:[ULONG];RESULT:[STRING12]

Description

A user is associated with an AP.

Parameters

Parameter Name Parameter Meaning

ACMAC

Indicates the AC's MAC address.

ACNAME

Indicates the AC's system name.

APMAC

Indicates the AP's MAC address.

APNAME

Indicates the AP's system name.

APIP

Indicates the AP's IP address.

RADIO

Indicates the radio ID.

BAND

Indicates the working frequency band of a radio.

SSID

Indicates the SSID.

ACCESS TYPE

Indicates the user authentication mode.

USER

Indicates the user name.

MAC

Indicates the user's MAC address.

ASSOCDURATION

Indicates the association time, in µs.

TIME

Indicates the system time.

ZONE:UTC

Indicates the time zone and daylight saving time.

DAYLIGHT

Indicates whether the daylight saving time is used.

  • true: The daylight saving time is used.
  • false: The daylight saving time is not used.

ERRCODE

Indicates the failure/state error code.

RESULT
Indicates the login success or failure cause of a user.
  • Success: A user goes online successfully.
  • FailType is Reason code, a user has gone offline unexpectedly: User went offline unexpectedly.
  • FailType is Reason code, assoc timeout: User association fails.
  • FailType is Reason code, other reason: Other reasons cause the user online failure.
  • FailType is Status code, the STA does not support the basic rate set required by the AP: The user's basic rate set do not match.
  • FailType is Status code, ap reach max user: The number of users associated with the AP reaches the upper limit.
  • FailType is Status code, encryption mode error: The authentication algorithm is not supported when the user sends authentication requests.
  • FailType is Status code, STA WMM capability mismatch: The user WMM capability does not match.
  • FailType is Status code, STA ESS capability mismatch: The network type flag carried by the user is not ESS.
  • FailType is Status code, STA SST capability mismatch: The user does not support short slot time.
  • FailType is Status code, STA spectrum capability mismatch: In the 802.11h only mode, the user does not support dynamic frequency selection.
  • FailType is Status code, STA of 802.11b is forbidden to access: The access of STAs that support 802.11b is rejected.
  • FailType is Status code, other reason: Other reasons cause the user online failure.
  • FailType is AC code, exceeded the maximum number of access users to the AC: The number of users associated with the device exceeds the upper limit. The error code is predefined on the AC.
  • FailType is AC code, assoc global whitelist isn't match: The user does not match the global user whitelist.
  • FailType is AC code, assoc global blacklist match: The user matches the global user blacklist.
  • FailType is AC code, assoc vap whitelist isn't match: The user does not match the VAP whitelist.
  • FailType is AC code, assoc vap blacklist match: The user matches the VAP blacklist.
  • FailType is AC code, assoc dynamic blacklist match: The user matches the dynamic user blacklist.
  • FailType is AC code, refused by load balance: The association failure is caused by the load balancing function.
  • FailType is AC code, refused by association element error: The length of association messages is incorrect, causing an association failure.
  • FailType is AC code, inconsistent security policies for SSIDs before and after STA roaming: The user security policy check fails, so roaming is rejected.
  • FailType is AC code, refused by roam check fail(state): The user state is not stable, so roaming is rejected.
  • FailType is AC code, refused by roam check fail(others): Other user information check fails, so roaming is rejected.
  • FailType is AC code, refused by vap reach max user(AC): The number of users associated with VAPs on the device reaches the upper limit.

Possible Causes

A user is associated with an AP.

Procedure

  • This log is informational only, and no action is required.

WSTA/6/WLAN_LOG_USER_WLAN_STA_INFO_ONLINE_FAIL

Message

WSTA/6/WLAN_LOG_USER:[WLAN_STA_INFO_ONLINE_FAIL]ACMAC:[OPAQUE1];ACNAME:[OCTET1];APMAC:[OPAQUE2];APNAME:[OCTET2];APIP:[IPADDR];RADIO:[INTEGER1];BAND:[OCTET3];SSID:[OCTET4];USER:[OCTET5];MAC[OPAQUE3];TIME:[INTEGER2];ZONE:[OCTET6];DAYLIGHT:[OCTET7];RESULT[OCTET8]

By default, this log is not recorded. To enable the system to record the log, run the report-sta-assoc enable command in the WLAN view.

Description

A STA fails to go online.

Parameters

Parameter Name Parameter Meaning

ACMAC

Indicates the AC's MAC address.

ACNAME

Indicates the AC's system name.

APMAC

Indicates the AP's MAC address.

APNAME

Indicates the AP's system name.

APIP

Indicate the AP's IP address.

RADIO

Indicates the radio ID.

BAND

Indicates the working frequency band of a radio.

SSID

Indicates the SSID.

USER

Indicates the user name.

MAC

Indicates the user's MAC address.

TIME

Indicates the system time.

ZONE

Indicates the time zone.

DAYLIGHT

Indicates whether the daylight saving time (DST) is used.

RESULT

Indicates the reason why the STA fails to go online. For details, see Table 169-2.

Possible Causes

For details, see Table 169-2.

Procedure

  1. Rectify the fault based on the handling suggestions in Table 169-2.

    Table 169-2 STAs' going-online failure reasons and handling suggestions

    Reason Why a STA Fails to Go Online

    Handling Suggestion

    STA authentication times out.

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Invalid association request packet.

    Reassociate the STA with the network. If this fault persists, the STA may be incompatible. Contact technical support personnel.

    The encryption mode is inconsistent on the STA and AP.

    Check whether the encryption mode is consistent on the STA and AP.

    Authentication fails in the association stage.

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    The STA is not authenticated.

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    The AP does not support the rate set specified in the association request packet of the STA.

    Reassociate the STA with the network or modify the basic rate set in the radio profile.

    The encryption algorithm is inconsistent on the STA and AP.

    Check whether the encryption algorithm is consistent on the STA and AP.

    Failed to decrypt the challenge packet.

    Reassociate the STA with the network or check whether the STA works properly. If this fault persists, contact technical support personnel.

    Access from legacy STAs is denied.

    Check whether the configuration for denying access of legacy STAs is required. To modify this configuration, run the undo legacy-station disable command to permit access of legacy STAs.

    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 WMM is forcibly enabled in the radio profile or check the specified configuration of the STA.

    STAs have a compatibility issue(Incorrect network type flag carried by STAs) .

    Check whether the STA works properly. If so, reassociate the terminal with the network. If this fault persists, contact technical support personnel.

    STAs have a compatibility issue(STAs do not support short timeslots).

    Check whether the STA supports the 802.11g protocol.

    STAs have a compatibility issue(STAs do not support DFS.)

    Check whether the STA supports the 802.11h protocol.

    The number of associated STAs exceeds the maximum allowed by the AC.

    Expand the WLAN capacity.

    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 load balancing configuration is proper.

    The STA is in the dynamic blacklist.

    View the attack record to check whether the STA is an attacker.

    The association or reassociation packet check fails.

    Reassociate the STA with the network. If this fault 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 Navi AC status is abnormal.

    Check the configuration and the network to Navi AC.

    VAP configurations on the Local AC and Navi AC are different.

    Check the VAP configurations on the Local AC and Navi AC. Check items are as follows:

    • STA authentication access mode.
    • SSID.

    The number of associated STAs exceeds the maximum specifications of the Navi AC.

    Expand the WLAN capacity.

    Failed to check the configuration during STA association.

    Please contact technical support personnel.

    Batch backup is in progress. STA access is denied.

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    STA access failed due to other reasons.

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Reassociation denied.

    No action is required.

    During roaming association, the SSID is inconsistent with that before roaming.

    Check whether the SSID is the same before and after roaming. If this fault persists, contact technical support personnel.

    During roaming association, the authentication mode is inconsistent with that before roaming.

    Check whether the authentication mode is the same before and after roaming. If this fault persists, contact technical support personnel.

    During roaming association, the STA status is abnormal.

    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.

    The STA uses a static IP address.

    Check whether the static IP address is configured by the user. If so, configure the STA to dynamically obtain an IP address.

    The STA's SNR is below the user CAC threshold.

    Check whether the SNR-based user CAC threshold is properly set. To modify this threshold, run the uac client-snr threshold command and reassociate the STA with the WLAN. Alternatively, determine the STA location and provide coverage to the location.

    The number of STAs exceeds the UAC threshold of the radio.

    Check whether the CAC threshold based on the number of users is properly set. To modify this threshold, run the uac client-number threshold command and reassociate the STA with the WLAN.

    The channel utilization of the radio has reached the upper threshold.

    Check whether the user CAC threshold based on the channel utilization is properly set. To modify this threshold, run the uac channel-utilization threshold command and reassociate the STA with the WLAN.

    The number of STAs exceeds the maximum allowed by the AP.

    Configure load balancing or expand the network capacity.

    The number of STAs exceeds the maximum allowed in the VAP reported by the AP.

    Increase the maximum number of users on the VAP or expand the WLAN capacity.

    The STA does not send an authentication request before associating with the network.

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Exceeded the maximum number of users on the central AP.

    Expand the WLAN capacity.

    Authentication fails.

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    The encryption mode used by STAs is different from that used by the VAP.

    Check the encryption modes used by STAs and the VAP.

    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 STA version or Wi-Fi module 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 and 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 and reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Invalid group cipher.

    Forget the network and reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Invalid pairwise cipher.

    Forget the network and reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Invalid MDE.

    Forget the network and reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Invalid FTE.

    Forget the network and reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Others reason.

    Contact technical support personnel.

    The key is incorrect or the STA uses the cached PMK.

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Failed to receive the handshake packet (2/4) from the STA.

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Failed to receive the handshake packet (4/4) from the STA.

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    802.11r EAPOL Msg 2/4 did not contain R1 name.

    Check whether the station has some compatibility problems and please disable dot1x reauthenticate when enable 802.11r. If this fault persists, contact technical support personnel.

    Key negotiation fails(the length of the key data 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(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.

    The MAC address of the access user is different from that configured for the PPSK account.

    Run the display wlan ppsk-user all command to check whether a PPSK account allows the access from this MAC address. If so, use this PPSK account for access. If not, configure a PPSK account mapping this MAC address and use the new PPSK account for access.

    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 not, create the PPSK account and bind it to the SSID.

    The number of PPSK users exceeds the maximum value.

    Run the display wlan ppsk-user all command to query the maximum number of access users supported by the PPSK account, and then modify the maximum number of access users as required.

    The PPSK account expires.

    Run the display wlan ppsk-user all command to check the timeout period of the PPSK account, and change it to a valid time.

    Key negotiation fails (message 2/4 processing error).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (message 4/4 processing error).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (message 1/2 processing error).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (start unicast negotiation fails because of incorrect input parameters).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (start multicast negotiation fails because of incorrect input parameters).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (message 2/4 authentication mode or encryption type mismatch).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (message 4/4 authentication mode or encryption type mismatch).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid length of the message 2/2).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid length of WPA data packets).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid length of the message 2/4).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid length of the message 4/4).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (mismatched packet descriptor of the message 2/4).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (mismatched packet descriptor of the message 4/4).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (mismatched packet descriptor of the message 2/2).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid length of the message 4/4 packet key).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid length of the message 2/2 packet key).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid key information in the message 2/4 packet).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid key information in the message 4/4 packet).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid key information in the message 2/2 packet).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (message 2/4 handshake status mismatch).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (message 4/4 handshake status mismatch).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (message 2/2 handshake status mismatch).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid number of message 2/4 replay times).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid number of message 4/4 replay times).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid number of message 2/2 replay times).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (message 4/4 MIC verification failure).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (message 2/2 MIC verification failure).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (packet length calculation failure).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (the EAP packet length is 0).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (the EAP packet is too long).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (the key body length of EAP packets is 0).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid length of the EAP packet key).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (incorrect EAP packet descriptor).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid EAP packet type).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (PMK parse failure).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (mismatch between the PMK and PMKR1Name).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (the type is not FTIE).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid FTIE length).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (mismatch between Anonce and FTIE).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (mismatch between Snonce and FTIE).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (MIC generation failure).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (failure to modify the rsnie field).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (failure to fill FTIE data).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    WAPI authentication times out.

    Check the network quality or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    WAPI authentication fails.

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Re-authentication fails (re-authentication failure).

    Check the intermediate network between the AP and AC or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Re-authentication fails (failure to fill the start negotiation message).

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Re-authentication fails (start negotiation failure).

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Authentication fails (authentication failure).

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Authentication fails (failure to fill the start negotiation message).

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Authentication fails (start negotiation failure).

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Authentication fails (failure to receive EAP key packets).

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Authentication fails (MAC address authentication processing error).

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Authentication fails (MAC address authentication failure).

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    The authentication request times out.

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (WPA key negotiation failure).

    Verify that the correct password is entered on the STA. If this fault persists, contact technical support personnel.

    Key negotiation fails (access security processing failure).

    Verify that the correct password is entered on the STA. If this fault persists, contact technical support personnel.

    Key negotiation fails.

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

  2. Collect alarm, log, and configuration information, and contact technical support personnel.
  3. End.

WLAN/4/WLAN_LOG_USER_WARN

Message

WLAN/4/WLAN_LOG_USER_WARN: %s, the user choose %c

Description

Users performed interactive operations.

Parameters

Parameter Name Parameter Meaning
%s
  • When deciding whether to commit configuration: Whether to deliver the configuration to the AP.
  • When deciding whether to delete AP: Whether to delete the AP.
  • When deciding whether to reset AP: Whether to restart the AP.
  • When deciding whether to reset AP to the manufacturing default configuration: Whether to restore the factory settings of the AP.
  • When deciding whether to run AP ping command: Whether to run the ping command on the AP.
  • When deciding whether to modify AP: Whether to modify AP information.
  • When deciding whether to clear unauthen AP record: Whether to clear the unauthenticated AP list.
  • When deciding whether to change the country code: Whether to modify the country code.
  • When deciding whether to change the ap update filename: Whether to modify the upgrade file of the AP.
  • When deciding whether to delete the ap update schedule-task: Whether to delete scheduled upgrade tasks of the AP.
  • When deciding whether to modify the work mode: Whether to change the radio working mode.
  • When deciding whether to change radio-frequency: Whether to change the radio frequency band.
  • When deciding whether to reset AP boot count: Whether to reset AP restart statistics.
  • When deciding whether to delete radio 0's vap: Whether to delete the VAP of radio 0 from the AP.
  • When deciding whether to delete radio 1's vap: Whether to delete the VAP of radio 1 from the AP.
  • When deciding whether to delete radio2's vap: Whether to delete the VAP of radio 2 from the AP.
  • When deciding whether to delete all radio's vap: Whether to delete VAPs of all radios from the AP.
  • When deciding whether to commit provision-apc: Whether to modify AP online parameters.
  • When deciding whether to configure fat (or fat&cloud) update file: A Fat AP software package is specified for the AP upgrade.
  • When deciding whether to change wideband switch: Whether to enable the wideband function.
  • When deciding whether to change scan switch: Whether to enable the air scan function.
  • When deciding whether to change the capwap message integrity check PSK: Whether to change the PSK for checking integrity of CAPWAP packets.
  • When deciding whether to change the CAPWAP message integrity check status: Whether to enable integrity check of CAPWAP packets.
  • When deciding whether to change the CAPWAP message integrity check status between controllers: Whether to enable integrity check of CAPWAP packets between controllers.
  • When deciding whether to change the CAPWAP message integrity check PSK between controllers: Whether to change the PSK for checking integrity of CAPWAP packets between controllers.
%c
  • y: Users entered y.
  • n: Users entered n.

Possible Causes

Interactive operations between the device and users were recorded.

Procedure

  1. This log is informational only, and no action is required.

WSTA/6/WLAN_LOG_STA_ONLINEFAIL_OR_OFFLINE_INFO

Message

WSTA/6/WLAN_LOG_STA_ONLINEFAIL_OR_OFFLINE_INFO:[WLAN_STA_OFFLINE_INFO]STAMAC:[OPAQUE];APNAME:[STRING1];RADIOID:[INTEGER];WLANID:[INTEGER];TIME:[STRING2];SSID:[STRING3];ACCESS TYPE:[STRING4];OfflineReason:[STRING5];

Description

A STA goes offline.

Parameters

Parameter Name Parameter Meaning

STAMAC

Indicates the MAC address of the STA.

APNAME

Indicates the AP's system name.

RADIOID

Indicates the radio ID.

WLANID

Indicates the WLAN ID.

TIME

Indicates the system time.

SSID

Indicates the SSID.

ACCESS TYPE

Indicates the user authentication mode.

OfflineReason

Indicates the reason why the STA goes offline. For details, see Table 169-3.

Possible Causes

A STA goes offline.

Procedure

  1. Rectify the fault based on the handling suggestions in Table 169-3.

    Table 169-3 Possible reasons and suggestions for STAs to go offline

    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 modification 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 the ACs.

    The home AP goes offline or a network fault occurs.

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    The home AP is deleted.

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    The home VAP is deleted.

    Reassociate the STA with the network. 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.

    Roaming check failed because the user left the current AC during inter-AC roaming.

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    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 AP and AC or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    A STA goes offline unexpectedly.

    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.

    During inter-AC roaming, the SSID is inconsistent with that before roaming.

    Check whether the SSID is the same before and after roaming. If this fault persists, contact technical support personnel.

    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.

    Verify that the STA needs to be added to the blacklist.

    The device in NAT mode does not support roaming.

    Reassociate the STA with the network or reconfigure the network mode.

    Layer 3 roaming is disabled(delay offline).

    Reassociate the STA with the network or enable Layer 3 roaming.

    Fail to send IPC to UCM reporting auth request.

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Fail to send IPC to UCM reporting roam request.

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Station roam between normal and backup AP.

    No action is required.

    The PPSK configuration is modified.

    Check whether the modification record can be found in the log.

    Exceeded the maximum number of login STAs supported by the PPSK account.

    Check the maximum number of login STAs supported by the PPSK account.

    Failed to synchronize user entries between Local AC and Navi AC.

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    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.

    Inter-ac roaming is disabled.

    No action is required.

    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 offline).

    Check whether the STA actively goes offline or whether the STA is faulty.

    The STA is deauthenticated (delay offline).

    Check whether the STA actively goes offline or whether the STA is faulty.

    The STA ages out (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.

    The soft-GRE tunnel goes down.

    Check the connectivity to the peer end of the soft-GRE tunnel. 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 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 key is incorrect or the STA uses the cached PMK.

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Failed to receive the handshake packet (2/4) from the STA.

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Failed to receive the handshake packet (4/4) from the STA.

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    802.11r EAPOL Msg 2/4 did not contain R1 name.

    Check whether the station has some compatibility problems and please disable dot1x reauthenticate when enable 802.11r. If this fault persists, contact technical support personnel.

    Key negotiation fails(the length of the key data 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(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.

    The MAC address of the access user is different from that configured for the PPSK account.

    Run the display wlan ppsk-user all command to check whether any PPSK account allows the access from this MAC address. If so, use this PPSK account for access. If not, configure a PPSK account mapping this MAC address and use the new PPSK account for access.

    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 not, create the PPSK account and bind it to the SSID.

    The number of PPSK users exceeds the maximum value.

    Run the display wlan ppsk-user all command to query the maximum number of access users supported by a PPSK account, and then modify the maximum number of access users as required.

    The PPSK account expires.

    Run the display wlan ppsk-user all command to check the timeout period of a PPSK account, and change it to a valid time.

    Key negotiation fails (message 2/4 processing error).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (message 4/4 processing error).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (message 1/2 processing error).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (start unicast negotiation fails because of incorrect input parameters).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (start multicast negotiation fails because of incorrect input parameters).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (message 2/4 authentication mode or encryption type mismatch).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (message 4/4 authentication mode or encryption type mismatch).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid length of the message 2/2).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid length of WPA data packets).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid length of the message 2/4).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid length of the message 4/4).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (mismatched packet descriptor of the message 2/4).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (mismatched packet descriptor of the message 4/4).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (mismatched packet descriptor of the message 2/2).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid length of the message 4/4 packet key).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid length of the message 2/2 packet key).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid key information in the message 2/4 packet).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid key information in the message 4/4 packet).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid key information in the message 2/2 packet).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (message 2/4 handshake status mismatch).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (message 4/4 handshake status mismatch).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (message 2/2 handshake status mismatch).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid number of message 2/4 replay times).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid number of message 4/4 replay times).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid number of message 2/2 replay times).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (message 4/4 MIC verification failure).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (message 2/2 MIC verification failure).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (packet length calculation failure).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (the EAP packet length is 0).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (the EAP packet is too long).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (the key body length of EAP packets is 0).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid length of the EAP packet key).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (incorrect EAP packet descriptor).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid EAP packet type).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (PMK parse failure).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (mismatch between the PMK and PMKR1Name).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (the type is not FTIE).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (invalid FTIE length).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (mismatch between Anonce and FTIE).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (mismatch between Snonce and FTIE).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (MIC generation failure).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (failure to modify the rsnie field).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (failure to fill FTIE data).

    Check whether the key is correct or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    WAPI authentication times out.

    Check the network quality or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    WAPI authentication fails.

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Re-authentication fails (re-authentication failure).

    Check the intermediate network between the AP and AC or reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Re-authentication fails (failure to fill the start negotiation message).

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Re-authentication fails (start negotiation failure).

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Authentication fails (authentication failure).

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Authentication fails (failure to fill the start negotiation message).

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Authentication fails (start negotiation failure).

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Authentication fails (failure to receive EAP key packets).

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Authentication fails (MAC address authentication processing error).

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Authentication fails (MAC address authentication failure).

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    The authentication request times out.

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

    Key negotiation fails (WPA key negotiation failure).

    Verify that the correct password is entered on the STA. If this fault persists, contact technical support personnel.

    Key negotiation fails (access security processing failure).

    Verify that the correct password is entered on the STA. If this fault persists, contact technical support personnel.

    Key negotiation fails.

    Reassociate the STA with the network. If this fault persists, contact technical support personnel.

  2. Collect alarm, log, and configuration information, and contact technical support personnel.
  3. End.

IPLRN/6/IPLRN-USERLOG

Message

IPLRN/6/IPLRN-USERLOG: Conflict with the IP address of an existing user.(Old User Mac=[OPAQUE], IP=[IPADDR], LearnType=[OCTET], New User Mac=[OPAQUE], IP=[IPADDR], LearnType=[OCTET])

Description

The IP address of a new user conflicts with that of an existing user.

Parameters

Parameter Name Parameter Meaning
Old User Mac Indicates the MAC address of the existing user.
IP Indicates the user's IP address.
LearnType Indicates the address learning mode of the new user.
New User Mac Indicates the MAC address of the new user.

Possible Causes

A static IP address is configured for a user. The configured IP address conflicts with the IP address of an existing user. Alternatively, a conflicting IP address is incorrectly allocated to the new user from the DHCP address pool.

Procedure

  1. If a static IP address is configured, plan a new IP address to prevent the configured IP address from conflicting with the IP address of another user. If an IP address is allocated to the new user using DHCP, configure the user to go online again to trigger the DHCP server to allocate another IP address to the user.
  2. Check whether the log persists.

    • If so, go to 3.
    • If not, go to 4.

  3. Collect alarm, log, and configuration information, and contact technical support personnel.
  4. End.

WMP_RFM/7/WLAN_RFM_INFO_RADAR_INFO

Message

WMP_RFM/7/WLAN_RFM_INFO_RADAR_INFO: Detected radar. (ACMAC=[OPAQUE], APMAC=[OPAQUE], APName=[STRING], RadioID=[INTEGER], CurrentChannel=[INTEGER], PreviousChannel=[INTEGER], CurrentSecondChannel=[INTEGER], PreviousSecondChannel=[INTEGER])

Description

An AP detected radar signals.

Parameters

Parameter Name Parameter Meaning

ACMAC

Indicates the AC's MAC address.

APMAC

Indicates the AP's MAC address.

APName

Indicates the AP name.

RadioID

Indicates the radio ID.

CurrentChannel

Indicates the current actual channel.

PreviousChannel

Indicates the channel used before channel switching.

CurrentSecondChannel

Indicates the current second channel

PreviousSecondChannel

Indicates the second channel before channel switching.

Possible Causes

The AP detected radar signals on its working channel, and the dynamic frequency selection (DFS) mechanism triggers channel switching.

Procedure

  1. This log is informational only, and no action is required.
Translation
简体中文
Download
Updated: 2022-01-25

Document ID: EDOC1100126883

Views: 34837

Downloads: 18

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Digital Signature File

Digital Signature Authentication Mode
Share
Previous Next
Huawei e+ App Huawei e+

Copyright © 2021 Huawei Technologies Co., Ltd. All rights reserved.

You are going to visit :