AP3805i-ROW won't register with V2110 anymore (same VLAN)

[Dusan_K_]

AP's in the same subnet as the physical topology (esa0, PHY, AP Registration checked).
APs were already registered with EWC (initially deployed with .ova 10.11), but after upgrade to 10.31.x APs won't register anymore.
APs have regular IPs, respond to ping and can be accessed via ssh;
# cget config global shows correct lastAcIp
esa0 responds to ping from AP.

Please advise.

[Dusan_K_]

Solved.

Option 78 was needed.

Any idea how to enter the second controller in Option 78?

[Umut_Aydin]

Hi Dusan,

if this doesn't work please check if somehow the AP went to a older code ..e.g 9.xx maybe this cause that the AP can't get the EWC?

# cat /etc/ap_version.txt

Regards
Umut

[Dusan_K_]

APs were successfully registered with 10.11 and currently still running this code:

AP3805i-ROW 10.11.03.0004 interactive shell for service personnel only
# cat /etc/ap_version.txt
export AP_VERSION=10.11.03.0004
...

V2110 is currently running 10.31.07.0002 and all APs are online. (Option 78 was needed).

[Ronald_Dvorak]

Try it with a static controller IP just so we know that the problem is the discovery...

ssh to the AP
cset authip 1 x.x.x.x
capply
csave

x.x.x.x is the controller IP

[Dusan_K_]

Hi Umut,

have tried that as well, but it does not work.
AP gets IP, is pingable from EWC and back, but won't register ...