display ap online-fail-record

MAC

MAC address of the AP that fails to go online.

Last fail time

Time of the AP online failure.

Reason

Reason why the AP fails to go online. For description of AP online failure reasons and handling suggestions, see Table 2.

For troubleshooting methods, see AP Online Failure.

Insufficient license resources.

Expand the license capacity. Note that RUs do not occupy license resources of the AC.

The AP is not in the SN whitelist.

Run the ap whitelist sn ap-sn1 [ to ap-sn2 ] command to add the AP to the whitelist or run the ap-confirm command to enable the AP to pass authentication.

The AP is not in the MAC whitelist.

Run the ap whitelist mac ap-mac1 [ to ap-mac2 ] command to add the AP to the whitelist or run the ap-confirm command to enable the AP to pass authentication.

The AP is added to the AP blacklist.

Check whether the AP needs to be added to the blacklist. To delete the AP from the blacklist, run the undo ap blacklist command.

The MAC address and SN of the AP do not match.

Check whether the MAC address and SN of the AP match.

DTLS negotiation for CAPWAP tunnel setup fails.

Check whether the PSK used for DTLS encryption is correctly configured.

DTLS negotiation failed, because of negotiation timeout or inconsistent PSKs on two ends.

• Check whether the shared keys of the AC and AP are the same. If not, change them to the same or run the capwap dtls psk-mandatory-match enable command to enable the AP to establish a DTLS session with the AC using the default PSK.
• Check whether ping packets are normal on the network. If not, negotiation timeout occurs because of a network exception during the DTLS negotiation. In this case, check the network.
• If the fault persists, contact technical support personnel.

CAPWAP tunnel negotiation fails.

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

APs cannot go online during data backup.

Wait until backup is complete.

The upgrade fails.

Run the display ap update configuration command to check whether the AP's upgrade file is correct. If so, rectify the fault by referring to Fit AP Upgrade Fails in the Troubleshooting Insights.

The CAPWAP tunnel fails to be established.

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

The configuration fails to be delivered.

The device attempts to deliver the configuration again. If the fault persists, contact technical support personnel.

The versions of the AP and AC do not match.

• The AC does not support the AP type.
• Unsupported AP type, AC version may need to be upgraded.

Replace the AP with that supported by the AC or replace the AC with one that supports this AP type.

The AP name conflicts.

Run the ap-rename command to rename the AP.

The number of central APs reaches the upper limit.

Check whether the number of central APs reaches the maximum value.

The number of common APs reaches the upper limit.

Check whether the number of common APs reaches the maximum value. If the number of normal APs is smaller than the maximum, to allow the AP to go online, run the undo ap command to delete APs that are not in normal state to release resources.

The central AP is not in normal state.

Run the display ap command to check the central AP status and take measures accordingly.

The CAPWAP sensitive-info PSK is different on the two ends of the CAPWAP tunnel.

Ensure that the PSK for encrypting CAPWAP sensitive information is the same on the AP and AC. Alternatively, enable the AP to set up a DTLS session with the AC using the default PSK.

The CAPWAP integrity-check PSK is different on the two ends of the CAPWAP tunnel.

Ensure that the PSK for checking CAPWAP packet integrity is the same on the AP and AC. Alternatively, enable the AP to set up a DTLS session with the AC using the default PSK.

The configured and reported AP types are different. The real AP type is XXXX.

Ensure that the configured AP type is the same as the reported one.

The AC license is not active.

Activate the AC license.

Too many APs go online concurrently, leading to a failure to create sufficient DBSS interfaces.

No action is required. The APs will attempt to go online again. If the APs still fail to go online, contact technical support personnel.

The country codes of the AP and AC are inconsistent, and the country code of the AP is locked.

The country code of some AP models cannot be modified. For example, an AP model with the suffix -US is used only in the United States, and its country code is fixed as US. Configure the country code on the AC to be the same as that on the AP.

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.

Configuration synchronization is in progress, leading to the system busy.

No action is required.

Backing up HA data.

Wait till HA data backup ends.

Insufficient LPU resources.

All the resources of the card are occupied. Go online through another card.

Invalid port on the switch connected to the AP.

Check whether a card does not support AP access or the cards are in different working groups.

Insufficient trunk resources.

The trunk resources are released.

The number of distribute APs reaches the upper limit of the central AP.

Re-plan the network and expand the network capacity by adding central APs.

The number of CAPWAP tunnels reaches the upper limit.

Run the display as command to check whether any online AS occupies CAPWAP resources. If so, properly allocate CAPWAP resources.

This AP type is not supported. Add it or upgrade the AC version.

Add the AP type or upgrade the AC version.

The type ID carried by the AC is different from that configured on the AC.

Modify the AP type ID to be the same as that on the AC.

The AC version is not supported by the AP.

Upgrade the AC version.

Failed to add the reported AP type parameters.

Upgrade the AC version.

During roaming association, 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.

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.

During roaming association, the STA fails to associate with the AP due to other reasons.

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

Failed to check the configuration during STA association.

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.

Reassociation denied.

No action is required.

The AP is forcibly disconnected

No action is required.