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


Userlevel 1
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.

12 replies

Userlevel 1
I have not set any DHCP Option nor DNS entry.
Is DHCP Option also mandatory with APs in the same subnet as the physical topology?
We have DHCP relay.
Userlevel 7
Here the information from the Wireless Getting Started Guide.....

Determine the method of AP controller discovery used by the APs to find the controller(s) to which the AP registers to provide network service. The AP supports:

• SLP-DA Discovery: Configure the segment settings for the DHCP server that provides IP assignment to the APs to include a reference to the SLP-DA to which WLAN controllers are registered. This allows the AP to obtain a list of eligible controllers.

• DNS: Configure the controller. entry to resolve to the IP address of a
specific controller.

• Multicast: Verify that the switching gear and interconnecting VLANs are provisioned so as to allow
multicast traffic, and IGMP snooping allows for the establishment of multicast trees, allowing the
APs to subscribe to SLP-DA server advertisements. The SLP-DA server sends queries to determine
the list of registered controllers.

So it should work via multicast if that is allowed on the infrastructure BUT I'd use DHCP#78 anyway - it's just one entry.

-Ron
Userlevel 4
Hi,

log in to the (SSH) AP and set it to factroy default.
login:admin
password:new2day
#cset f

Clear the AP in the EWC to be sure and it should be abel again to connect to the EWC.

Regards
Umut Aydin
Userlevel 1
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 ...
Userlevel 7
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
Userlevel 4
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
Userlevel 1
Umut Aydin wrote:

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

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).
Userlevel 1
Solved.

Option 78 was needed.

Any idea how to enter the second controller in Option 78?
Userlevel 7
could you provide a screenshot of your 78 option settings - there is more then one way to do it and I don't want to provide a wrong answer
Userlevel 1
Please advise for "Data Entry Byte: Decimal" scenario.
We entered one controller by setting Values: "1" and then "10" Add + "1" Add + "11" Add + "4" Add being 10.1.11.4 an IP addr of EWC's PHY port. The PHY port of second EWC is 10.1.11.5.
Each single number in its line, looks like this:
1
10
1
11
4
Userlevel 3
You can set up the new address right under that one in the array (without another leading 1) so it would look like:

1
10
1
11
4
10
1
11
5
Userlevel 5
Hi Dusan,

I think that the following article will help you.

How To Configure an AP to Find the IdentiFi Wireless Controller with DHCP Option 78 on a Windows Server
https://gtacknowledge.extremenetworks.com/articles/How_To/How-To-Configure-an-AP-to-Find-the-IdentiF...

Best regards,
Bin

Reply