An AP Fails to Go Online
Symptom
An AP fails to go online.
Possible Causes
- The AP is not assigned an IP address, or the static IP address of the AP is incorrectly configured.
- The network between the AP and AC is disconnected due to incorrect configurations.
- The AP fails MAC address or SN authentication.
- Restricted by license resources, the number of APs connected to the AC reaches the upper limit.
- The MAC address, SN, and type configured for the AP are inconsistent with the actual information.
- The AP is faulty.
- The PSK used for DTLS encryption configured on the AP is inconsistent with that configured on the AC.
- The AC does not support this AP type.
Troubleshooting Procedure
- Check AP onboarding failure records.
# Run the display ap online-fail-record command to check the reason why the AP fails to go online.
<AC> display ap online-fail-record mac 1047-80b1-56a0 ------------------------------------------------------------------------------ MAC Last fail time Reason ------------------------------------------------------------------------------ 1047-80b1-56a0 2015-01-20/15:48:06 The AP is added to the AP blacklist. ------------------------------------------------------------------------------ Total records: 1
The following table uses V200R010 as an example to describe the causes and handling suggestions for AP onboarding failures. For other versions, see the corresponding command lines in the product documentation.
Reason Why an AP Fails to Go Online
Suggestion
Insufficient license resources.
Expand the license capacity. Note that RUs managed by the AC do not occupy license resources of the AC.
Huawei's Electronic Software Delivery Platform (ESDP) is accessible from the Internet and Huawei intranet.
- Internet: http://app.huawei.com/isdp
- Huawei intranet: http://w3.huawei.com/sdp
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 SN 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 MAC 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 pre-shared key (PSK) used for DTLS encryption is correctly configured.
DTLS negotiation failed, because of negotiation timeout or inconsistent PSKs on two ends.
- Check whether the AC and AP use the same PSK. If not, configure the same PSK on the AC and AP or adjust DTLS parameters. In versions earlier than V200R021C00, run the capwap dtls psk-mandatory-match enable command to enable APs to establish DTLS sessions with the AC using the default PSK. In V200R021C00 and later versions, run the capwap dtls no-auth enable command to enable APs to establish DTLS sessions with the AC in none authentication mode.
- Check whether the ping operation is normal. If not, the network is abnormal during DTLS negotiation, resulting in negotiation timeout. 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 the 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.
Log in to Huawei technical support website and download the release notes. Based on the version mapping, upgrade the AP or AC to the matching version.
- Enterprise technical support website: http://support.huawei.com/enterprise
- Carrier technical support website: http://support.huawei.com
The AC does not support the AP type.
Replace the AP with one supported by the AC or change the AC version to one that supports the AP. In V200R019C00 and later versions, you can also run the ap-type command on the AC to manually add an AP type as required. For the mapping between AP type names and IDs, go to https://support.huawei.com/enterprise/en/doc/EDOC1000146039.
Unsupported AP type, AC version may need to be upgraded.
The AP name conflicts.
Run the ap-rename command to change the AP name.
The number of central APs reaches the upper limit.
Check whether the number of central APs has reached the upper limit.
The number of common APs reaches the upper limit.
Check whether the number of common APs has reached the upper limit.
The central AP is not in normal state.
Run the display ap command to check the central AP status and take measures based on the corresponding suggestion.
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 type of the AP added offline is the same as that reported by the AP.
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.
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.
Reset for the AC mode switching.
No action is required.
The WAC license expires.
Purchase a new license and load it to the cloud management platform.
The device has been disconnected from the Agile Controller-Campus for more than 90 days.
Verify the cloud management platform address configured on the AC, and check network connectivity.
The device is deleted from the Agile Controller-Campus.
No action is required.
The Agile Controller-Campus does not deliver AP information.
- Verify that AP information is correctly added to the cloud management platform, the AP is associated with the AC, and the AC is online.
- Verify the cloud management platform address configured on the AC, and check network connectivity.
- Check whether the cloud management platform fails to deliver AP information. If so, manually deliver AP information again.
Configuration synchronization is in progress, leading to the system busy.
No action is required.
The IP version of this AP does not match.
Run the ap ip version command to modify the IP version of the AP or assign an IP address with a different version to the AP.
Backing up HA data.
Wait until the HA processing is complete.
Insufficient LPU resources.
Replace an LPU for the AP to go online.
Invalid port on the switch connected to the AP.
Check whether any LPU that is not supported connects to the AP access port or whether the LPU is in a different working group.
Insufficient trunk resources.
Release trunk resources.
The number of distribute APs reaches the upper limit of the central AP.
Re-plan the network, expand the capacity, and add central APs.
The number of CAPWAP tunnels reaches the upper limit.
Reallocate CAPWAP resources properly.
DTLS negotiation failed by using the preset certificate.
If a newly added AP fails to go online due to compatibility issues, enable the AP to establish a CAPWAP DTLS session in none authentication mode so that the AP can obtain a security credential. After the AP goes online, disable this function immediately after the AP goes online again to prevent unauthorized APs from accessing the network.
- Check the AP status.
# Log in to the AC and run the display ap all command to check the AP status.
<AC> display ap all Total AP information: idle : idle [1] nor : normal [2] -------------------------------------------------------------------------------------------------- ID MAC Name Group IP Type State STA Uptime -------------------------------------------------------------------------------------------------- 0 60de-4476-e360 L1_003 default 192.168.109.254 AP6010DN-AGN nor 0 2D:5H:48M:44S 1 dcd2-fc04-b500 dcd2-fc04-b500 default - AP7110DN-AGN idle 0 - 2 dcd2-fc9d-0bb0 area_3 default 192.168.109.253 AP7110SN-GN nor 0 2D:5H:52M:38S -------------------------------------------------------------------------------------------------- Total: 3
An AP is usually in either of the following states:- normal: The AP has successfully registered with the AC.
- fault: The AP fails to register with the AC. If an AP is in fault state, go to the next step.
- download: The AP is loading the system software during the upgrade. Wait until the AP upgrade is complete and check the AP status again.
- committing: The AC is delivering services to the AP.
- config-failed: The AP fails to initialize the configuration. If an AP is in config-failed state, check whether the network connection is normal. Configure the AP and AC to ping each other. Check whether packet loss occurs and use large ping packets (greater than 1600 bytes) to check whether the MTU value of the intermediate network is small. If NAT traversal is configured on the intermediate network, check whether NAT communication is normal. Run the display cpu-defend statistics wired command to view the value of Drop Packets of capwap packets in the statistics on packets sent to the CPU. If a large number of packets are lost, check whether the threshold is set properly. If the fault persists for a long time, collect related information and contact technical support.
- name-conflicted: The AP name conflicts with that of another AP. If an AP is in name-conflicted state, the AP name already exists. In this case, run the ap-rename ap-id ap-id new-name ap-name command in the WLAN view to change the AP name.
- ver-mismatch: The AP version does not match the AC version. If an AP is in ver-mismatch state, run the display ap version all command to check the AP version, and run the display version command to check the AC version. Check whether the AC version matches the AP version. If their versions do not match, see section "Software Version Compatibility" in AC Release Notes. Download the matching AP system software package, upgrade a single AP according to the upgrade guide, and check the AP status after the upgrade. For details about the version mapping between ACs and APs, see Quick Reference for WLAN AP Version Mapping and Models.
If the AP is upgraded in automatic or online mode, ensure that the AP's upgrade file is correct and is available on the AC or in the FTP/TFTP directory. Otherwise, the AP may fail to go online.
- standby: AP status on the standby AC.
- idle: After an AP is added offline, it is in idle state. If an AP is in this state, check whether the AP is properly connected to the network.
- Check whether AP MAC address flapping occurs.
If AP entries cannot be queried by running the display ap all or display ap online-fail-record command on the AC, the possible cause is that AP MAC address flapping occurs or the destination port is the same as the source port in the DHCP Offer message sent by the DHCP server.
It is recommended that you observe the port from which the AP MAC address is learned and check whether the port changes. Then, trace the MAC address back to the switch to query MAC address flapping records.
# Log in to the AC and run the display mac-address command multiple times to check the port from which the AP MAC address is learned. If the port changes, MAC address flapping may occur.[AC] display mac-address | include 9017-acb9-39e0 ------------------------------------------------------------------------------- MAC Address VLAN/VSI Learned-From Type ------------------------------------------------------------------------------- 9017-acb9-39e0 2009/- GE0/0/1 dynamic -------------------------------------------------------------------------------
# Trace the MAC address back to the switch and run the display mac-address flapping record command to check MAC address flapping records.
[Switch] display mac-address flapping record Info: The mac-address flapping record does not exist.
If AP MAC address flapping occurs, check the networking.
- Check whether the AP is a Fit AP.
# In V200R019C00 or later: Log in to the AP and run the display image command in the diagnostic view to check the activated software version.
[AP-diagnose] display image ImageStatusVersion ============================================================== Image A(Active)AP8030DNV200R006C10SPC300B031(FAT) Image B(Backup)AP8030DNV200R003C00SPCc00B100(FAT) ==============================================================
# In V200R019C10 or later: Log in to the AP, and the AP mode is displayed.
... Info: Current mode: Fit (managed by the AC). ...
If it is a Fat AP, refer to AP Mode Switching to switch the AP to the Fit mode.
- Check whether the AP has obtained an IP address.
A CAPWAP tunnel can be established between an AP and an AC only after the AP has obtained an IP address. Generally, a DHCP server is used to assign IP addresses to APs. You can check whether an IP address is assigned to the AP on the DHCP server. You can also configure a static IP address for the AP to go online.
- AP going online using a static IP addressIf the AP is configured to go online using a static IP address, perform the following steps:
- Log in to the AP, and run the display ap-address-info command to check whether the static IP address that takes effect on the AP is correct as well as verify the uniqueness of the AP IP address, IP gateway, and AC IP address.
<AP> display ap-address-info ============================================================== Active AP Address Info AP Mode : static //The AP goes online using a static IP address. Ip Address : 20.1.1.100 //Static IP address of the AP Ip Version : 4 Mask : 255.255.255.0 //Subnet mask of the AP IP address Gateway : - //Gateway of the AP AC 0 ip : 10.1.1.111 //AC IP address AC 1 ip : - AC 2 ip : - AC 3 ip : - --------------------------------------------------------------.
- If the AP IP address is incorrect, run the ap-address mode dhcp command in the system view to change the IP address obtaining mode to DHCP, and then restart the AP to make the configuration take effect.
[AP] ap-address mode dhcp Info: The configuration takes effect after the AP is restarted.
Alternatively, run the ap-address static ip-address ip-address subnet-mask command in the system view to change the static IP address of the AP, and then restart the AP to make the configuration take effect.
[AP] ap-address static ip-address 10.1.15.253 255.255.240.0 Info: The configuration takes effect after the AP is restarted.
- Check whether the AP diagnosis log contains the following record: AP ip mode[static], ip version[4], ip address[], mask[], gateway[], AC ip number[], and AC ip list[]. If the record is not found, the problem occurs when the AP obtains the static IP address information from the flash memory or when the interface information is configured. Check whether the log contains related error records, and rectify the fault based on the error messages.
[AP-diagnose] display diag-logfile buffer logfile configuration and contents in the buffer: CRC : 0x4d3f9e94 LogBufLength : 25089 ...... Jul 27 2005 19:02:37+08:00 ap-2 %%01WSRV/6/WSRV_INFO(D)[86]:Start capwap link:AP ip mode[dhcp], ip version[4], ip address[0x6c6c6cfe], mask[0xffffff00], gateway[0x0], AC ip number[0], AC ip list[]. ......
- Log in to the AP, and run the display ap-address-info command to check whether the static IP address that takes effect on the AP is correct as well as verify the uniqueness of the AP IP address, IP gateway, and AC IP address.
- AP going online in DHCP mode
If the AP does not obtain an IP address, check whether the DHCP server and related device interfaces are correctly configured.
If the AP fails to obtain an IP address, check whether:
- The link between the AP and AC is properly connected.
- The management VLAN is created on intermediate devices between the AP and AC.
- The configurations of AC interfaces to which AP packets are sent are correct, and all the interfaces allow packets of the management VLAN to pass through.
- The Option 43 field is configured in the IP address pool when a Layer 3 network exists between the AP and AC. You are advised to use the option 43 sub-option 2 ip-address ip-address &<1-8> command to configure this field. In VRRP hot standby (HSB) scenarios, the virtual IP address configured as the CAPWAP source address on the AC must be specified in the Option 43 field.
- option 43 hex hex-string
- option 43 sub-option 3 ascii ascii-string
- option 43 sub-option 2 ip-address ip-address &<1-8>
- option 43 sub-option 1 hex hex-string
You are advised to run only one of the following commands: option 43 sub-option 3 ascii ascii-string, option 43 sub-option 2 ip-address ip-address &<1-8>, and option 43 sub-option 1 hex hex-string. If you run two or three commands at the same time, only the last one takes effect.
# Run the following commands on the DHCP server to check whether the AP is assigned an IP address. In this example, the AC functions as a DHCP server.
- Run the display ip pool { interface interface-pool-name | name ip-pool-name } used command to check allocated IP addresses. Check whether the AP has obtained an IP address based on the MAC address.
[AC] display ip pool interface Vlanif1219 used Pool-name : Vlanif1219 Pool-No : 4 Lease : 1 Days 0 Hours 0 Minutes Domain-name : - DNS-server0 : - NBNS-server0 : - Netbios-type : - Position : Interface Status : Unlocked Gateway-0 : 10.1.1.2 Network : 10.1.0.0 Mask : 255.255.240.0 VPN instance : -- Conflicted address recycle interval: - ----------------------------------------------------------------------------- Start End Total Used Idle(Expired) Conflict Disable ----------------------------------------------------------------------------- 10.1.0.1 10.1.15.254 4093 4 4084(0) 5 0 ----------------------------------------------------------------------------- Network section : ----------------------------------------------------------------------- Index IP MAC Lease Status ----------------------------------------------------------------------- 4085 10.1.15.246 dcd2-fc9a-c800 7375 Used 4086 10.1.15.247 1047-80af-fbc0 7369 Used 4087 10.1.15.248 dcd2-fcf4-6420 7929 Used 4090 10.1.15.251 dcd2-fc22-d880 9368 Used -----------------------------------------------------------------------You can also run the display arp command to view all ARP mapping entries. Check whether the AP has obtained an IP address based on the MAC address, and run the ping command to ping the IP address.[AC] display arp IP ADDRESS MAC ADDRESS EXPIRE(M) TYPE INTERFACE VPN-INSTANCE VLAN/CEVLAN PVC ------------------------------------------------------------------------------ ...... 10.1.1.2 0200-0000-0017 I - Vlanif1219 10.1.15.251 dcd2-fc22-d880 2 D-0 GE0/0/1 1219/- 10.1.15.247 1047-80af-fbc0 16 D-0 GE0/0/1 1219/- 10.1.15.246 dcd2-fc9a-c800 15 D-0 GE0/0/1 1219/- 10.1.15.248 dcd2-fcf4-6420 6 D-0 GE0/0/1 1219/- 10.1.1.219 4c1f-cc6b-c248 16 D-0 GE0/0/1 - Run the ping command to test the IP address corresponding to the MAC address. If the ping operation succeeds, the AP has obtained an IP address. If the ping operation fails, the IP address obtained by the AP has expired or the AP fails to obtain an IP address.
[AC] ping 10.1.15.251 PING 10.1.15.251: 56 data bytes, press CTRL_C to break Reply from 10.1.15.251: bytes=56 Sequence=1 ttl=255 time=1 ms Reply from 10.1.15.251: bytes=56 Sequence=2 ttl=255 time=1 ms Reply from 10.1.15.251: bytes=56 Sequence=3 ttl=255 time=1 ms Reply from 10.1.15.251: bytes=56 Sequence=4 ttl=255 time=1 ms Reply from 10.1.15.251: bytes=56 Sequence=5 ttl=255 time=1 ms --- 10.1.15.251 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 1/1/1 ms - If no address pool is configured, you can run the trace enable command to enable the full-process tracing function. The following sample output shows that the AP keeps sending DHCP Discover messages.
[AC] trace enable //Enable the full-process tracing function. [AC] trace object mac-address dcd2-fc22-d880 //Enter the MAC address of the object to be traced. [BTRACE][2015/06/18 15:12:37][DHCPS][dcd2-fc22-d880]:Receives DHCP DISCOVER message from interface Vlanif1219.(chaddr=dcd2-fc22-d880, ciaddr=0.0.0.0, giaddr=0.0.0.0, serverid=0.0.0.0, VPN=-, expect leasetime=0) [BTRACE][2015/06/18 15:12:37][DHCPS][dcd2-fc22-d880]:Gateway=10.1.1.2, mask=255.255.240.0. [BTRACE][2015/06/18 15:12:37][DHCPS][dcd2-fc22-d880]:Get pool Vlanif1219 by gateway 10.1.1.2 and vrf 0. [BTRACE][2015/06/18 15:12:37][AM][dcd2-fc22-d880]:Receive REQUEST message. (MacAddress=dcd2-fc22-d880, Subnet=10.1.1.2/255.255.240.0, VRF=0, ExpectLease=0, UserType=20) [BTRACE][2015/06/18 15:12:37][AM][dcd2-fc22-d880]:Get pool Vlanif1219. [BTRACE][2015/06/18 15:12:37][AM][dcd2-fc22-d880]:Try allocate leased ip for mac dcd2-fc22-d880.(pool:4) [BTRACE][2015/06/18 15:12:37][AM][dcd2-fc22-d880]:Request successfully.(mac:dcd2-fc22-d880, ip:10.1.15.254, vrf:0) [BTRACE][2015/06/18 15:12:37][AM][dcd2-fc22-d880]:Offer ip 10.1.15.254 to mac dcd2-fc22-d880. [BTRACE][2015/06/18 15:12:37][DHCPS][dcd2-fc22-d880]:Assigned address 10.1.15.254 for dcd2-fc22-d880. [BTRACE][2015/06/18 15:12:37][DHCPS][dcd2-fc22-d880]:Send DHCP OFFER packet.(Chaddr=dcd2-fc22-d880, Offer IP=10.1.15.254). [BTRACE][2015/06/18 15:12:37][DHCPPRO][dcd2-fc22-d880]:DHCP server protocol stack ends with stop. [BTRACE][2015/06/18 15:12:37][DHCPPRO][dcd2-fc22-d880]:Receive DHCP packet (srcif:null orgif:null length:346 mflg:UC/BC). [BTRACE][2015/06/18 15:12:37][DHCPPRO][dcd2-fc22-d880]:Receive DHCP OFFER message.orgif:null srcif:null L3if:null srcmac:0200-0000-0017 dstmac:dcd2-fc22-d880 vsi:- vlan:1219/0 srcip:10.1.1.2 dstip:10.1.15.254 VPN:- src-port:67 dst-port:68 msgtype:BOOT-REPLY dhcp msgtype:DHCP OFFER bflag:uc chaddr:dcd2-fc22-d880 ciaddr:0.0.0.0 reqip:0.0.0.0 giaddr:0.0.0.0 serverid:10.1.1.2
- AP going online using a static IP address
- Check whether the CAPWAP link has been created.# Display CAPWAP link information.
- For versions earlier than V200R007, run the display capwap link state command in the user view to check whether a CAPWAP link has been created.
<AP> display capwap link state ------------------------------------------------------------------------------ LINK AP AP AP InIf FSM ID IPAddr CPort DPort Index State ------------------------------------------------------------------------------ 0 10.1.7.250 63399 52737 0 RUN ------------------------------------------------------------------------------ - In V200R007 and later versions, run the display capwap link all command in the diagnostic view to check whether a CAPWAP link has been created.
[AP-diagnose] display capwap link all Info: This operation may take a few seconds. Please wait for a moment.done. ------------------------------------------------------------------------------------------ ID MAC CPort DPort Type State Role VPN DstAddr SrcAddr ------------------------------------------------------------------------------------------ 0 7079-90ba-8ea0 5246 5247 AC RUN Client - 120.120.1.1 120.120.5.60 1 7079-90ba-8ea0 5246 5247 AC RUN Client - 120.120.1.2 120.120.5.60 2 4cfa-caff-f560 55450 65535 INAP RUN Server - 120.120.7.6 120.120.5.60 ------------------------------------------------------------------------------------------
Pay attention to the link whose DstAddr is the CAPWAP source address of the destination AC. If the CAPWAP link information of the destination AC is not available, check the status of other links whose Type is AC. If the CAPWAP link information exists and the link status is RUN, the AP goes online on another AC. You can find the AC through the DstAddr field.
# If the CAPWAP link is not created, run the display capwap configuration command on the AC to check whether the AC's CAPWAP source address is correct.
If the CAPWAP source address is displayed as an interface, check whether the interface is correctly configured with an IP address and whether it is incorrectly shut down.In VRRP HSB scenarios, the CAPWAP source address on the AC must be set to a virtual IP address.
[AC] display capwap configuration ---------------------------------------------------------- Source interface : vlanif118 Source ip-address : - Echo interval(seconds) : 25 Echo times : 6 Control priority(server to client) : 7 Control priority(client to server) : 7 Control-link DTLS encrypt : disable DTLS PSK value : ****** PSK mandatroy match switch : disable Control-link inter-controller DTLS encrypt : disable Inter-controller DTLS PSK value : ****** IPv6 status : disable ---------------------------------------------------------- [AC] interface Vlanif 118 [AC-Vlanif118] display this # interface Vlanif118 ip address 118.118.1.1 255.255.255.0 dhcp select interface #
- For versions earlier than V200R007, run the display capwap link state command in the user view to check whether a CAPWAP link has been created.
- Check whether the management VLAN is configured on the AP.
Log in to the AP, and run the display system-information command to check whether the management VLAN is available on the AP.
<AP> display system-information System Information =============================================== ...... System Name : AP Country Code : CN MAC Address : 10:47:80:af:fb:c0 Radio 0 MAC Address : 10:47:80:af:fb:c0 Radio 1 MAC Address : 10:47:80:af:fb:d0 IP Address : 10.1.15.254 Subnet Mask : 255.255.240.0 Default Gateway : 0.0.0.0 IPv6 IP Address : IPv6 Default Gateway : Management VLAN ID(AP) : 1219 IP MODE : static ...... ===============================================If the management VLAN is incorrectly configured, run the undo management-vlan command in the AP system view to delete the management VLAN and restart the AP.
If the management VLAN needs to be configured, check the intermediate network to ensure that the management VLAN is allowed and that the AC and AP can ping each other.
If the AP cannot go online due to incorrect management VLAN configuration, remove the VLAN tag from the interface on the access switch. After the AP goes online, restore the configuration.
For more information, see APs Cannot Go Online After a Management VLAN Is Configured.
- Check whether the AP's uplink interface works in endpoint or middle mode. The wired interface connecting the AC to the root AP must work in root mode.
For more information, see After the AP's Uplink Wired Interface Is Configured to Work in Endpoint Mode, the AP Cannot Go Online After a Restart.
- Skip this step in Fit AP scenarios. In "Fit central AP + RU" scenarios, perform this step.
- Check whether the Fit central AP to which the RU belongs has gone online on the AC.
[AC] display ap all | include f02f-a706-4ba6 Info: This operation may take a few seconds. Please wait for a moment.done. Total AP information: fault: fault [2] idle : idle [9] nor : normal [2] vmiss: ver-mismatch [2] ----------------------------------------------------------------------------------------------------------- ID MAC Name Group IP Type State STA Uptime ----------------------------------------------------------------------------------------------------------- 2 f02f-a706-4ba6 f02f-a706-4ba6 default 118.118.1.235 AD9430DN-24 nor 0 2D:18H:9M:26S -----------------------------------------------------------------------------------------------------------
If the status of the Fit central AP is not normal, follow the troubleshooting procedure for common APs' failure to go online, and ensure that the Fit central AP goes online successfully.
- Check whether the RU has gone online on the Fit central AP.
If the Fit central AP is in normal state, you can Telnet or STelnet to the Fit central AP from the AC to check the RU status and the link status between the RU and Fit central AP.
[AC] stelnet 118.118.1.235 Please input the username:admin Trying 118.118.1.235 ... Press CTRL+K to abort Connected to 118.118.1.235 ... The server is not authenticated. Continue to access it? [Y/N]:y Save the server's public key? [Y/N]:y The server's public key will be saved with the name 118.118.1.235. Please wait... Enter password: Info: Current mode: Fit (managed by the AC). Info: You are advised to change the password to ensure security. <f02f-a706-4ba6> system-view [f02f-a706-4ba6] diagnose [f02f-a706-4ba6-diagnose] display wsrv ap all //In V200R019C10 or later, this command is not supported, so this step can be skipped. ---------------------------------------------------------------------- Record ID Type MAC State Uptime ---------------------------------------------------------------------- 0 R250D 4cfa-caff-f560 normal 2D:18H:27M:33S 1 R240D 70d9-313c-3120 ver-mismatch - ---------------------------------------------------------------------- Authorized: 2 Unauthorized: 0 [f02f-a706-4ba6-diagnose] display capwap link all ------------------------------------------------------------------------------------------ ID MAC CPort DPort Type State Role VPN DstAddr SrcAddr ------------------------------------------------------------------------------------------ 10 f02f-a706-4ba6 5246 5247 AC RUN Client - 118.118.1.1 118.118.1.235 11 4cfa-caff-f560 19706 19706 SAP RUN Server - 202.255.245.96 167.6.75.166 12 70d9-313c-3120 28889 28889 SAP RUN Server - 49.60.49.32 167.6.75.166 ------------------------------------------------------------------------------------------ Total number: 3
If the RU is in normal state on the Fit central AP and the CAPWAP link between the RU and Fit central AP is in RUN state, but the RU still cannot go online on the AC, contact technical support personnel.
- If the Fit central AP is directly connected to the RU, check whether the corresponding interface on the Fit central AP is Up and whether the interface can learn the MAC address of the RU.
[f02f-a706-4ba6] display mac-address | include 4cfa-caff-f560 ------------------------------------------------------------------------------- MAC Address VLAN/VSI Learned-From Type ------------------------------------------------------------------------------- 4cfa-caff-f560 1/- GE0/0/13 dynamic ------------------------------------------------------------------------------- Total items displayed = 5 [f02f-a706-4ba6] display interface GigabitEthernet 0/0/13 GigabitEthernet0/0/13 current state : UP Line protocol current state : UP Description:HUAWEI, AP Series, GigabitEthernet0/0/13 Interface Switch Port, PVID : 1, TPID : 8100(Hex), The Maximum Frame Length is 1800 IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is f02f-a706-4ba6 Last physical up time : 2018-10-14 23:05:47 Last physical down time : 2018-10-14 23:05:30 Current system time: 2018-10-15 11:29:53 Port Mode: COMMON COPPER Speed : 100, Loopback: NONE Duplex: FULL, Negotiation: ENABLE Mdi : AUTO Last 300 seconds input rate 776 bits/sec, 0 packets/sec Last 300 seconds output rate 840 bits/sec, 0 packets/sec Input peak rate 52335600 bits/sec,Record time: 2018-10-14 23:05:53 Output peak rate 93666120 bits/sec,Record time: 2018-10-14 23:05:53 Input: 63010 packets, 24043933 bytes Unicast: 54684, Multicast: 8101 Broadcast: 225, Jumbo: 0 Discard: 0, Total Error: 0 CRC: 0, Giants: 0 Jabbers: 0, Throttles: 0 Runts: 0, Alignments: 0 Symbols: 0, Ignoreds: 0 Frames: 0 Output: 110554 packets, 39818748 bytes Unicast: 44491, Multicast: 8320 Broadcast: 57743, Jumbo: 0 Discard: 0, Total Error: 0 Collisions: 0, ExcessiveCollisions: 0 Late Collisions: 0, Deferreds: 0 Buffers Purged: 0 Input bandwidth utilization threshold : 100.00% Output bandwidth utilization threshold: 100.00% Input bandwidth utilization : 0.01% Output bandwidth utilization : 0.01% - If the Fit central AP is not directly connected to the RU, the fragment threshold for Layer 2 packets exchanged between the Fit central AP and RU must be greater than or equal to 1600 bytes. It is recommended that the threshold be set to a value greater than 2000 bytes.
- By default, the uplink interface of a Fit central AP works in root mode. If the interface is used as a downlink interface, change the interface mode to middle, which is not recommended.
- Check whether the Fit central AP to which the RU belongs has gone online on the AC.
- Check whether the network between the AP and AC is normal.# Run the ping command on the AC and AP to check whether they can ping each other.
- If the ping operation fails, check whether the IP address expires, whether the links of the intermediate network devices are normal, and whether the links are configured correctly.
- If a long delay or packet loss occurs during the ping operation, check the statistics of each interface to determine whether loops occur on the intermediate network.
- If no packet is lost and the delay is normal, go to the next step.
During the deployment, if an AP fails to go online, the problem is caused by incorrect configurations between the AC and intermediate network devices. The following configuration is for your reference:- Typically, one management VLAN, and one or more service VLANs need to be configured during WLAN service configuration.
- Packets sent by the AP, including packets for obtaining an IP address from the DHCP server and CAPWAP control packets sent between the AP and AC, do not contain VLAN tags by default. The packets are tagged with the management VLAN ID on the switch interface that is directly connected to the AP. Then, these packets are sent to the DHCP server or the AC through the VLAN and routing control on the network.
- The packets sent by STAs do not carry a VLAN tag, and the service VLAN tag is added by the AP to the packets.
- When direct forwarding is used, ensure that packets from the service VLANs are allowed from the AP's uplink interface to the user gateway. Configure the interface as a hybrid or trunk interface, not as an access interface, and allow packets from the service and management VLANs to pass through. In direct forwarding mode, VLAN configuration must be allowed on the switch connected to APs. Do not connect APs to the switch that does not support VLAN configuration.
In the following example, VLAN 10 and VLAN 20 are configured as the management VLAN and service VLAN respectively on the switch interface directly connected to the AP.
<Switch> system-view [Switch] interface gigabitEthernet 0/0/1 [Switch-GigabitEthernet0/0/1] port link-type trunk [Switch-GigabitEthernet0/0/1] port trunk pvid vlan 10 [Switch-GigabitEthernet0/0/1] port trunk allow-pass vlan 10 20
Or
<Switch> system-view [Switch] interface gigabitEthernet 0/0/1 [Switch-GigabitEthernet0/0/1] port link-type hybrid [Switch-GigabitEthernet0/0/1] port hybrid pvid vlan 10 [Switch-GigabitEthernet0/0/1] port hybrid untagged vlan 10 [Switch-GigabitEthernet0/0/1] port hybrid tagged vlan 20
- When tunnel forwarding is used, the AP's uplink interface only allows packets from the management VLAN to pass through, because the service packets are encapsulated in CAPWAP packets. In tunnel forwarding mode, the interface can be configured as an access, trunk, or hybrid interface.
In the following example, VLAN 10 and VLAN 20 are configured as the management VLAN and service VLAN respectively on the switch interface directly connected to the AP.
<Switch> system-view [Switch] interface gigabitEthernet 0/0/1 [Switch-GigabitEthernet0/0/1] port link-type access [Switch-GigabitEthernet0/0/1] port default-vlan 10
Or
<Switch> system-view [Switch] interface gigabitEthernet 0/0/1 [Switch-GigabitEthernet0/0/1] port link-type trunk [Switch-GigabitEthernet0/0/1] port trunk pvid vlan 10 [Switch-GigabitEthernet0/0/1] port trunk allow-pass vlan 10
Or
<Switch> system-view [Switch] interface gigabitEthernet 0/0/1 [Switch-GigabitEthernet0/0/1] port link-type hybrid [Switch-GigabitEthernet0/0/1] port hybrid pvid vlan 10 [Switch-GigabitEthernet0/0/1] port hybrid untagged vlan 10
- When an AP is connected to an AC through a Layer 3 network, the AP cannot discover the AC and register with it after obtaining an IP address, because CAPWAP packets are broadcast packets by default. In this case, configure the Option 43 field of the DHCP packets to transmit the AC IP address to the AP when the AP obtains an IP address. The AP can then discover the AC by sending CAPWAP unicast packets and register with it. Alternatively, the Option 15 field can be used to notify the AP of the AC's DNS domain name. For details, see Configuring the DHCP Server.
- IP addresses of APs are statically configured or obtained from a DHCP server. Dynamic IP address allocation by a DHCP server is more commonly used.
- After changing the WDS mode (root, middle, or leaf) of an AP, restart the AP for the configuration to take effect. Otherwise, the AP may fail to register.
- When an AC and an AP are connected through a Layer 3 network, you can add a static AC address to enable the AP to go online.
- Check whether the switch and AP are connected through an Eth-Trunk.
- In V200R008 and earlier versions, you need to configure an Eth-Trunk before connecting physical cables. Otherwise, loops may occur on the network, causing the AP's failure to go online.
- In V200R009 and later versions, you can connect physical cables and then configure an Eth-Trunk.
- Check whether the AP is authenticated by the AC.
- Run the display ap global configuration command to check the current authentication mode. The default authentication mode is MAC address authentication.
[AC-wlan-view] display ap global configuration -------------------------------------------------------------------------------- AP auth-mode : MAC-auth AP LLDP swtich : disable AP username/password : -/****** AP data collection : disable AP data collection interval(minute): 5 --------------------------------------------------------------------------------
If the authentication mode is MAC address authentication or SN authentication, run the display ap unauthorized record command to check whether there are APs that fail to be authenticated.
[AC] display ap unauthorized record Unauthorized AP record: -------------------------------------------------------------------------------- AP type: AP7110DN-AGN AP SN: 210235555310D1000067 AP MAC address: dcd2-fc22-d800 AP IP address: 10.1.7.251 Record time: 2015-11-17 10:36:43 -------------------------------------------------------------------------------- AP type: AP3010DN-AGN AP SN: 210235582910D1000741 AP MAC address: dcd2-fc9a-c800 AP IP address: 10.1.7.249 Record time: 2015-11-17 10:36:43 -------------------------------------------------------------------------------- AP type: AP5010SN-GN AP SN: 201235567710D4000022 AP MAC address: e468-a352-7a10 AP IP address: 10.1.7.252 Record time: 2015-11-17 10:36:28 -------------------------------------------------------------------------------- AP type: AP7110DN-AGN AP SN: 210235555610D1000023 AP MAC address: dcd2-fcf4-6420 AP IP address: 10.1.7.250 Record time: 2015-11-17 10:34:42 -------------------------------------------------------------------------------- Total number: 4
If so, run the ap-confirm command in the WLAN view to allow the specific AP to pass authentication.
[AC-wlan-view] ap-confirm mac dcd2-fc22-d880
Alternatively, run the ap-whitelist { mac mac-address | sn ap-sn } command to add the specific AP to the whitelist.
[AC-wlan-view] ap whitelist mac dcd2-fc22-d880
You can also run the ap-id ap-id ap-mac mac-address command in the WLAN view to add the AP offline.
[AC-wlan-view] ap-id 10 ap-mac dcd2-fc22-d880
- Run the display ap-type all command to check whether the AC supports the current AP model.
[AC-wlan-view] display ap-type all ------------------------------------------------------------------------------ ID Type ------------------------------------------------------------------------------ 17 AP6010SN-GN 19 AP6010DN-AGN 21 AP6310SN-GN 23 AP6510DN-AGN 25 AP6610DN-AGN 27 AP7110SN-GN 28 AP7110DN-AGN 29 AP5010SN-GN 30 AP5010DN-AGN 31 AP3010DN-AGN 33 AP6510DN-AGN-US 34 AP6610DN-AGN-US 35 AP5030DN 36 AP5130DN 37 AP7030DE 38 AP2010DN 39 AP8130DN 40 AP8030DN 42 AP9330DN 43 AP4030DN 44 AP4130DN 45 AP3030DN 46 AP2030DN 47 AP9131DN 48 AP9132DN 49 AP5030DN-S 50 AP3010DN-V2 ------------------------------------------------------------------------------ Total number: 27
If the AP model is not in the list, the AC of the current version does not support the AP model. In this case, upgrade the AC by referring to the corresponding upgrade guide. For details about the version mapping between ACs and APs, see Quick Reference for WLAN AP Version Mapping and Models.
If the authentication mode is non-authentication or the AP has been added to the whitelist and the AP model is supported by the AC, go to the next step.
- Run the display ap global configuration command to check the current authentication mode. The default authentication mode is MAC address authentication.
- Check whether the number of APs connected to the AC reaches the upper limit.The number of APs that can be connected to an AC depends on the following factors:
- License resource items: The total number of common APs and central APs cannot exceed the number of license resource items. RUs do not occupy license resources.
- Maximum number of APs that can be managed by an AC:
- The total number of common APs and RUs does not exceed the maximum number that can be managed by an AC.
- The total number of central APs does not exceed the maximum number that can be managed by an AC.
- Run the display license resource usage command to check the license resource usage. If the current resource usage reaches the authorized value specified in the license file, new APs cannot go online.
<AC> display license resource usage Activated License: flash:/LIC92680232*****_*****5396810CB000006.dat FeatureName | ConfigureItemName | ResourceUsage CRFEA1 LH85WLANAP01 0/256
If the number of resources exceeds the authorized value, apply for and load a new license file.
- If the number of resources does not exceed the authorized value, run the display ap all command to check whether the number of APs in normal state exceeds the maximum number of APs supported by the AC.
AC Model
Number of Central APs Supported
Number of Common APs and Agile Distributed APs Supported
AC6003
6
48
AC6005
32
256
AC6605
218
1024
ACU2
256
2048
AC6800V
1280
10240
AC6507S
32
128
AC6508
32
256
AC6805
768
6144
AirEngine 9700S-S
16
64
AirEngine 9700-M
256
2048
AirEngine 9700-M1
2048
2048
Re-plan the WLAN based on the maximum number of APs that can be managed by the AC.
- Check whether the MAC address and SN of the AP are consistent with the actual ones.
Run the display wlan wdev ap-information ap-id ap-id command in the diagnostic view of the AC to check the MAC address and SN of the AP.
[AC-diagnose] display wlan wdev ap-information ap-id 4 Ap profile Info: aucName: dcd2-fc22-d880 APID_AVL: 4 APID: 4 aucSn: 210235555310D1000067 //AP's SN configured on the AC group name: default aucMac: dcd2-fc22-d860 //AP's MAC address configured on the AC ......If the AP information is different from the actual AP information, run the undo ap ap-id ap-id command in the WLAN view to delete the AP, and then run the ap-id ap-id ap-mac mac-address ap-sn ap-sn command to add an AP offline.<AC> system-view [AC] wlan [AC-wlan-view] undo ap ap-id 4 //Delete the AP. [AC-wlan-view] ap-id 10 ap-mac dcd2-fc22-d880 //Add an AP offline.
- Enable the full-process tracing function and view the related messages.
Run the trace enable command in the global view of the AC to enable the full-process tracing function, and then enter the MAC address of the object to be traced (MAC address of the AP or STA) by using the trace object mac-address ap-mac command.
[AC] trace enable //Enable the full-process tracing function. [AC] trace object mac-address dcd2-fc22-d880 //Enter the MAC address of the object to be traced.
Full-process tracing can be performed based on the MAC address or IP address of an object. The command output displays the interaction between the traced object and the AC or AP as well as fault information.
In normal cases, the AP online process is as follows:
[BTRACE][2015/11/17 13:43:33][DHCPPRO][dcd2-fc22-d880]:Receives DHCP DISCOVER packet from interface GigabitEthernet0/0/1. [BTRACE][2015/11/17 13:43:33][DHCPS][dcd2-fc22-d880]:Get pool Vlanif1219 by gateway 10.1.1.2 and vrf 0. [BTRACE][2015/11/17 13:43:33][AM][dcd2-fc22-d880]:Get pool Vlanif1219. [BTRACE][2015/11/17 13:43:33][DHCPS][dcd2-fc22-d880]:Send DHCP OFFER packet.(Chaddr=dcd2-fc22-d880, Offer IP=10.1.15.252). [BTRACE][2015/11/17 13:43:33][DHCPPRO][dcd2-fc22-d880]:Receives DHCP REQUEST packet from interface GigabitEthernet0/0/1. [BTRACE][2015/11/17 13:45:36][WLAN_AC][dcd2-fc22-d880]:[CAPWAP] Process discovery request message. [BTRACE][2015/11/17 13:45:36][WLAN_AC][dcd2-fc22-d880]:[CAPWAP]Discovery Request Process : Send discovery response successfully. MAC: dcd2-fc22-d880 [BTRACE][2015/11/17 13:45:41][WLAN_AC][dcd2-fc22-d880]:[CAPWAP] Process join request message. MAC: dcd2-fc22-d880 [BTRACE][2015/11/17 13:45:41][WLAN_AC][dcd2-fc22-d880]:[CAPWAP] Send join response successfully. MAC: dcd2-fc22-d880 [BTRACE][2015/11/17 13:45:45][WLAN_AC][dcd2-fc22-d880]:[CAPWAP] Process config status request message. MAC: dcd2-fc22-d880 [BTRACE][2015/11/17 13:45:45][WLAN_AC][dcd2-fc22-d880]:[CAPWAP] Send configuation state response successfully. MAC: dcd2-fc22-d880 [BTRACE][2015/11/17 13:45:45][WLAN_AC][dcd2-fc22-d880]:[CAPWAP] Process change state event request message and status id CONFIGURE. MAC: dcd2-fc22-d880 [BTRACE][2015/11/17 13:45:45][WLAN_AC][dcd2-fc22-d880]:[CAPWAP] Send change state event response successfully. MAC: dcd2-fc22-d880
You can compare this process with the normal one for further troubleshooting.
Generally, a message will be displayed if the license, MAC address, or SN does not match with the actual one during the AP online process. The sample command outputs in the trace results are displayed as follows:
- A blacklist is configured on the AC, and APs in the blacklist cannot go online.
[BTRACE][2015/11/17 14:04:46][WLAN_AC][dcd2-fc22-d880]:[CAPWAP] Process discovery request message. [BTRACE][2015/11/17 14:04:46][WLAN_AC][dcd2-fc22-d880]:[WDEV] AP's Mac is in Mac black list, so AP authorization is been rejected.
- The AP's MAC address and SN do not match.
The trace result shows that the MAC address and SN do not match, as shown in the following figure.
[BTRACE][2015/11/17 14:08:59][WLAN_AC][dcd2-fc22-d880]:[CAPWAP] Process discovery request message. [BTRACE][2015/11/17 14:08:59][WLAN_AC][dcd2-fc22-d880]:[WDEV] AP's Mac does not match with SN number, so AP authorization is been rejected.
- A blacklist is configured on the AC, and APs in the blacklist cannot go online.
- Check the reason why the AP fails to go online.
You can also run the display wlan debuginfo type 1 1000 command in the diagnostic view of the AC to check the actions of the AP. Search for the following information and use the keywords Oristate and CouseID to preliminarily determine the reason why the AP cannot go online.
[AC-diagnose] display wlan debuginfo type 1 from 0 to 1000 Debug at File:wdev_ap.c Line:9115 Sn :72 Debug Info: ApNotifyStateChange:WCWP_FSM_STAT_DTLS_TEARDOWN LinkID:19 <Time : 2015-11-17 14:21:48.940 > Debug at File:wdev_ap.c Line:8790 Sn :73 Debug Info: WDEV ApStateChangeNotifyProc Start... LinkID=19, State:6 <Time : 2015-11-17 14:21:48.940 > Debug at File:wcwp_fsm.c Line:7931 Sn :74 Debug Info: Device[10]TearDown Oristate[RESET] CouseID[21] Link[19] PeerMac[e468-a352-7a10] <Time : 2015-11-17 14:21:48.940 >
The format of the display wlan debuginfo command varies according to the version.
- V200R005C00 to V200R008C10: display wlan debuginfo type type-id [ from start-value to end-value | value ]
- V200R009C00 and later versions: display wlan debuginfo process process-id type type-id [ from start-value to end-value | value ]
Table 7-1 lists the causes of AP online failure and its solutions based on CouseID.Table 7-1 Causes and solutions based on CouseIDCouseID
Cause
Solution
0
Hardware is faulty.
Replace the AP.
1
Setting hardware information for the CAPWAP tunnel fails.
Replace the AP.
2
The AP releases the IP address.
Wait for the AP to obtain an IP address and go online.
3
The AP restart timer expires.
Wait for the AP to go online again.
4
Heartbeat timeout occurs.
Check the intermediate network.
5
The data verification timer expires.
Check the intermediate network.
6
The state transition timer expires.
Check the intermediate network.
7
The DTLS timer expires.
Check the intermediate network.
8
Discovery timed out.
Check the intermediate network.
9
Join packet timeout occurs.
Check the intermediate network.
10
Keepalive packet timeout occurs.
Contact technical support personnel.
11
An exception occurs during the padding of AP restart packets.
Contact technical support personnel.
12
An exception occurs during the padding of Join Response packets.
Contact technical support personnel.
13
An exception occurs during the padding of Discovery Response packets.
Contact technical support personnel.
14
An exception occurs during the padding of Keepalive packets.
Contact technical support personnel.
15
An exception occurs during the padding of Echo Response packets.
Contact technical support personnel.
16
An exception occurs during the padding of Change State Event Response packets.
Contact technical support personnel.
17
An exception occurs during the padding of Config Status Response packets.
Contact technical support personnel.
18
DTLS connection failed.
Contact technical support personnel.
19
DTLS handshake is aborted.
Contact technical support personnel.
20
The AP is automatically upgraded.
Wait until the AP is upgraded and goes online again.
21
Response message exception occurs after an AP restarts.
Wait for the AP to go online again.
22
The received Change State Event Request packet is abnormal.
Wait for the AP to go online again or contact technical support personnel.
23
APTYPE in the received Join Request packet is abnormal.
Contact technical support personnel.
24
APSN information in the received Join Request packet is abnormal.
Contact technical support personnel.
25
SessionID in the received Join Request packet is abnormal.
Contact technical support personnel.
26
An AP with the same MAC address or SN is online.
Check whether the AP information is correct.
27
Authentication fails
Add the AP to the whitelist.
28
Factory settings are restored.
Wait for the AP to go online again.
30
Discovery timeout occurs.
Check the intermediate network.
31
The MAC address and SN reported by the AP conflict with the current device configuration.
Check the MAC address and SN of the AP added offline.
32
Failed to obtain the AP ID in the link entry.
Contact technical support personnel.
34
The link restarts.
Wait for the AP to go online again.
35
The radio of the wall plate AP fails to be switched.
Contact technical support personnel.
37
The client link is forcibly deleted.
Contact technical support personnel.
38
Authorization fails.
Check whether the client is valid and whether it is in the whitelist.
39
The AP is forced to go offline.
Contact technical support personnel.
41
The DTLS function is not enabled on the client AC.
Enable DTLS on the client AC.
42
The IP address obtained by the AP is different from the static IP address configured on the AC.
Change the static IP address of the AP or configure the AP to obtain an IP address dynamically.
43
The hash table of MAC -> LinkID fails to be added.
Contact technical support personnel.
44
The hash table of SN -> LinkID fails to be added.
Contact technical support personnel.
- Check whether the AP is faulty.
Check whether the power indicator and network cable indicator of the AP blink normally. For details about indicators, see WLAN Hardware Installation and Maintenance Guide.
If the indicators are abnormal, check whether the power cables and network cables are correctly connected.
- Replace components to locate faults.
If the fault cannot be located using the preceding methods, replace components to locate faults.
- Replace network cables with high-quality 8-core network cables. Test and check whether the fault is rectified.
- Replace the AP with a new one, restore the factory settings (by pressing and holding the default button), and check whether the new AP can go online.
- Connect the AP directly to the AC and modify the port configuration. Check whether the AP can go online.
- If the AP is an outdoor AP, use the Ethernet port to connect to the AC. Check whether the AP can go online.
- Collect the diagnostic information of the AC and AP as well as user logs and diagnostic logs in the corresponding time range, and contact technical support personnel.