How to troubleshooting if the ruijie AP can not online on the AC?

Possible cause

•        AP cannot be powered

•        AP port has issue( port cannot UP)

•        network cable issues

•        AP doesn't get ip address

  ￮        wired environmental issues

    ▪        The corresponding VLAN is not enabled.

    ▪        enable DHCP snooping(but not set the port to trust)

  ￮        configuration issues

    ▪        option 138 not be configured on DHCP server

•        tunnel address issues

  ￮        small packet can not reach

  ￮        big packet can not reach

  ￮        port 5246/5247 is not allowed on the middle device

•        insufficient license from AC


Troubleshooting Procedure

1.        Check whether AP can get ip address

On gateway: show arp  | inc APmac+1

For example, if the mac address of the AP is 8005.8868.6492, show on the gateway will be 8005.8868.6493



2.        After confirming the AP ip address, ping the AP ip address from the AC or the AP gateway. (If the AC cannot be pinged, ping the AP gateway.)

2.1 If can not ping:

On uplink switch:  show mac add | inc APmac+1 (Confirm AP is connecting to which switch)



1) If you can find the POE port connected to the AP based on the AP mac address, change the port to a Layer-3 port, set the port address to 192.168.110.2, and ping 192.168.110.1 to check whether the port can communicate with the AP. If yes, telnet to the AP to check the AP mode and configuration

Ruijie(config)#int g0/2

Ruijie(config-if-GigabitEthernet 0/2)#no switchport

Ruijie(config-if-GigabitEthernet 0/2)#ip add 192.168.110.2 255.255.255.0

Ruijie(config-if-GigabitEthernet 0/2)#end

Ruijie#ping 192.168.110.1

2) if ping fails, you need to check on AP( you can check LED status)


2.2 On AP connecting switch:

1) check configuration: whether trunk native vlan is AP vlan, whether access is AP vlan

2) if snooping is configured, you can use this command to check: show snooping log | inc APmac+1



2.3 If it can ping, move to step 3

3.        Telnet to the AP and check the AP version (Check whether the AP version and AC version are both 11.x versions. The AP 10.x version does not support online on AC 11.x version)

4.        Ping AP address with length 1500, source AC tunnel address(option 138 address)

AC#ping 192.168.5.1 source x.x.x.x length 1500



Notice: The default tunnel address of ac is loopback 0. If "capwap ctrl-ip xxxx" is configured under "ac-controller", the latter address is used as the tunnel address

1) if ping succeeds but ping with length 1500 fails:

You need to check the MTU of the intermediate device

If the MTU cannot be changed on the intermediate device, you can check how many bytes can be pinged from the AC to AP can succeed and change the value on AC:

conf

ac-con

capwap ctrl-mtu 1400


2) ping fails:

You need to tracert the AC address on AP, determine which device the packet goes to, and check whether the route configuration of the corresponding device is normal


3) if ping with length 1500 can succeed:

On AP:

debug syslog limit number 0 time 0

y

debug syslog limit reset

debug capwap  packet

ter moni

(Check whether the AP sends a capwap discover packet to the AC address)



show capwap client status



show ip f f | inc apipadd

(Check AP ip address and whether port 5246 have information)



5.        show ap-config sum deny-ap    --->Check the reason of deny

6.        show logging |  inc apmac(change to AP mac address)   --->Check the reason of deny