unify cant access access points to chaange channel (or owt else)

[sted]

ive been looking at the unifi stuff here as i realised that its old firmware and as the school is currently having a new building built out back i suspect the new aps will need a better firmware/software on the controller. I noticed all the aps are set to the same channel but when i click the ap which is supposed to open up the properties nothing happens. Tried this on ie and firefox on the server that has the controller software and my laptop and nothing happens. Any ideas as i suspect its something really dumb im just missing but my googlefu is letting me down

 

hovering over it just says javascript:void(0);

 

[jonnykewell1]

with it running an older firmware, have you tried it with an older version of JAVA?

[fairm010]

I always use IE with the UniFi controller. Ive had problems with it in Chrome and Firefox

[Meldrew]

I always use IE with the UniFi controller. Ive had problems with it in Chrome and Firefox

 

Strangely, I always use Chrome as I've had problems with IE. As they say, your mileage may vary...

 

Meldrew

[andyrite]

Upgrade the controller software to the latest version. Are the AP using zero handoff?

[sted]

just installed a newer version 3.2.7 on another box and used teh restore backup option and i can now click on them just waiting for it to say anything other than disconnected on any ap lol

[m25man]

Java may well be your viewing issue however all UAPs on the same 2.4Ghz channel is either a misconfiguration or you have Zero Hand Off set up on the 2Ghz band.

 

Check Settings, WLAN, Groups.

 

Here you can designate a channel for use by all APs and the controller will handle the ZHO for seamless roaming (single channel blanket) for use by VoiP or similar.

When set as ZHO changes must be made at the group level not AP.

[sted]

ust waiting for it to find any aps lol they are all listed as disconnected even the one i powercycled

[sted]

restarted service on "old" server (after disabling on new one)and finds them all straight away hmmm might try upgrading current server but going to leave it till next week now

[m25man]

There is more to switching controllers than just restoring the config.

 

Each AP will have the controllers L3 address in its boot sequence.

 

You should have upgraded/installed and restored the config on the same machine.

 

In order to get the APs back online you will need to sort out the L3 discovery.

 

To do this you will need to know what url the AP's are searching for by ssh into one of them.

Then you can create a cNAME record on your DNS so that the APs can find the controller.

 

At present when your APs boot they are looking for http://old controller:8080

 

You need to redirect all AP discovery to http://new controller:8080

[sted]

installed 3.2.7 on the same server as 2.4.1 was installed and its working now and I can rename the access points etc and they seem to be picking their own channels though they do seem to like 1 still at least I can now change it