Reply
Member
Posts: 138
Registered: ‎02-22-2016
Kudos: 50
Solutions: 11
Accepted Solution

Re-establishing UAP contact with cloud controller after port change

Looking for some advice on what I might be missing here. 

 

I have a hotel site where I've verified that port 8080 is blocked by ISP functions, and this cannot change. It is run by a cloud controller that I also have two other sites on with no problem at all (one is my office the other is another hotel next door). Had no trouble setting up either of them (different ISPs obviously).

 

So after much reluctance I've tried changing the default port on the controller that the UAPs use to reach the controller. I've found the steps for that, modifying system.properties file and so on. No trouble. I change that and restart and then all my APs drop off the controller at all three sites.

 

This is where the problems really start. I'm perfectly willing to believe that my problem site is still have port problems, but when I try to re-establish contact with the controller on my successful sites -- by set-inform to the same controller with a new port -- nothing seems to work. I can't re-establish the link to the controller or get a set-inform command or basically anything to work to get the APs back online.

 

So anywhere I should go? It seems that the working sites should re-establish easily, but it seems the process of getting the UAPs back on the same controller with a different port just isn't working for me.


Accepted Solutions
Member
Posts: 215
Registered: ‎06-19-2015
Kudos: 38
Solutions: 4

Re: Re-establishing UAP contact with cloud controller after port change

Is the controller on site or offsite. I honestly suggest just a cloud key on site, for larger sites it just makes management easier. Then all you need is a vpn tunnel to the same subnet as the cloud key or port forward through the router to the cloud key. 

You will probably need to ssh into the aps and do a "set-inform https://controlerIPhereORfqdn:NEWINFORMPORTHERE/inform"

"set-inform https://192.168.0.2:8888/inform"

or 

"set-inform https://mycontroller.com:8888/inform"

if 8888 is the inform port

View solution in original post


All Replies
Member
Posts: 215
Registered: ‎06-19-2015
Kudos: 38
Solutions: 4

Re: Re-establishing UAP contact with cloud controller after port change

Is the controller on site or offsite. I honestly suggest just a cloud key on site, for larger sites it just makes management easier. Then all you need is a vpn tunnel to the same subnet as the cloud key or port forward through the router to the cloud key. 

You will probably need to ssh into the aps and do a "set-inform https://controlerIPhereORfqdn:NEWINFORMPORTHERE/inform"

"set-inform https://192.168.0.2:8888/inform"

or 

"set-inform https://mycontroller.com:8888/inform"

if 8888 is the inform port
Veteran Member
Posts: 4,919
Registered: ‎09-26-2013
Kudos: 1334
Solutions: 351

Re: Re-establishing UAP contact with cloud controller after port change

 

Have you established whether you can make a link to the cloud controller on the new port?

 

To do this, open a web browser and navigate to http://<cloudaddress>:<newinformport>

 

 

Member
Posts: 138
Registered: ‎02-22-2016
Kudos: 50
Solutions: 11

Re: Re-establishing UAP contact with cloud controller after port change


@ncscomm wrote:

Is the controller on site or offsite. I honestly suggest just a cloud key on site, for larger sites it just makes management easier. Then all you need is a vpn tunnel to the same subnet as the cloud key or port forward through the router to the cloud key. 

You will probably need to ssh into the aps and do a "set-inform https://controlerIPhereORfqdn:NEWINFORMPORTHERE/inform"

"set-inform https://192.168.0.2:8888/inform"

or 

"set-inform https://mycontroller.com:8888/inform"

if 8888 is the inform port

The controller is offsite and that's sort of the problem -- it should work fine but at this particular site it just isn't. Believe me I'm strongly considering just going with a cloud key but their budget is low and their understanding of how all this works is even lower, so that's really my last resort scenario (but believe me, I'm almost there).

 

I have been sshing into the UAPs and using set-inform -- has not worked at the trouble site but even at the successful sites trying to set-inform again with a different controller port has been troublesome too. Was wondering if there was any other way to do it. I've wondered if resetting the APs would allow it, but there's so many questions on that and I'm not really keen on completely breaking the working sites either. 

 

Thanks.

SuperUser
Posts: 8,192
Registered: ‎01-05-2012
Kudos: 2176
Solutions: 1080

Re: Re-establishing UAP contact with cloud controller after port change

The set-inform command must be executed (twice ..) with the APs in factory default state.
Member
Posts: 138
Registered: ‎02-22-2016
Kudos: 50
Solutions: 11

Re: Re-establishing UAP contact with cloud controller after port change

[ Edited ]

To cut to the solution I've just decided to go with a cloud key onsite -- I agree it's much easier to deal with, especially if there's any problems with the Internet connection onsite. The export site from one controller and import it into another function is particularly useful. 

 

Thanks all. 

Reply