Wireless Access

Reply
MVP
Posts: 112
Registered: ‎01-05-2016

Why some AP cannot connect to the controller if manually set the master IP and AP own IP

Hi, when we do AP provisioning, after we manually set IP address of controller and AP own IP address and netmask ,gateway, some AP cannot talk to the controller , but some AP can. AP same model, and IP addresses setting are correct on AP. Please advise the possible cause. Thanks in advance. 

MVP
Posts: 344
Registered: ‎07-26-2011

Re: Why some AP cannot connect to the controller if manually set the master IP and AP own IP

There's a few places i'd check first to see the issue. Have you attached a console cable to an AP yet, is there any errors being show on here? Do you see any error flags when you run "show ap database" ? Are these RAP's or CAP's, might be worth checking to see if a firewall is between the AP and controller? Can you ping the AP from the controller and vice versa? Also check the logs (show log all | include XXXX) to see if there is any errors in the logs? Are you also running Control Plane Security?

ACMA, ACMP
If my post addresses your query, give kudos:)
MVP
Posts: 112
Registered: ‎01-05-2016

Re: Why some AP cannot connect to the controller if manually set the master IP and AP own IP

Thanks for reply.

 

We  use the same network connection for all the new AP to do provisioning. Control panel security is enabled and ap auto install certificate.  Some AP can connect to the controller, some cannot. Can ping the APs from controller. Very strange.

MVP
Posts: 112
Registered: ‎01-05-2016

Re: Why some AP cannot connect to the controller if manually set the master IP and AP own IP

Tomorrow I try again, currently I am not onsite. Thanks a lot

Search Airheads
Showing results for 
Search instead for 
Did you mean: