Wireless Access

Reply
New Contributor

AP cannot join controller when not directly connected

Hi everyone,

 

Just would like to check if someone has experienced this. I have MC-650 running 6.1.x.x and new AP-215. I upgraded the controller to 6.4.3.9 to accommodate the newer AP. I was able to register the AP to the controller. Since I have more than 4 APs already, I made a trunk from one of the controller port going to a trunk port of a switch:

 

Controller <-> PoE Switch <-> AP

 

But in this setup the AP is not able to join back to the controller. Config of the ports joining the controller and PoE Switch is trunk and allow all VLANs. 

 

According to the Data Sheet, the controller supports 16 APs despite 4 PoE ports, so definitely cascading/trunking to a PoE switch should work. I have also read the release notes of 6.4.x but haven't read anything confirming this behavior. Is there a known limitation for MC-650 that requires AP to be directly connected? 

Guru Elite

Re: AP cannot join controller when not directly connected

The AP does not need to be on a Trunk port.  You might want to make that an access port.  Also, what is your access point being used for that AP to discover the controller? (DNS, DHCP Option, Broadcast)



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

New Contributor

Re: AP cannot join controller when not directly connected

Hi Sir,

 

It is in trunk port due to the other VLANs for SSID. It is using DHCP; the controller is configured as DHCP server. Anyhow I will double check my config. Thanks!

 

Guru Elite

Re: AP cannot join controller when not directly connected

What is the default gateway for the VLAN that the access point is on?

Can that VLAN traffic route to the management ip address of the controller?



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Aruba Employee

Re: AP cannot join controller when not directly connected

Hi,

What is the status and flags for APs on controller? <show ap database >?
MVP

Re: AP cannot join controller when not directly connected


It is in trunk port due to the other VLANs for SSID. It is using DHCP; the controller is configured as DHCP server. Anyhow I will double check my config. Thanks!

 


You do not need the user vlans at the access port to the AP. 

If the AP is in a vlan for which the controller has an ip interface it will use broadcast to find it and connect.

If the AP is not in a vlan for which your controller has an ip interface you need (easiest solution) to configure an A record 'aruba-master' on your DNS server and makle sure the AP can resolve that address. It will then set up an ipsec/gre tunnel (with all the user vlans within that tunnel) to the controller.

 

So only on the controller uplink do you need all the vlans. 

The AP just needs a layer 3 connection to the ip adress it receives from resolving aruba-master.

Koen (ACMX #351 | ACDX #547 | ACCP)

-- Found something helpful, important, or cool? Click the Kudos Star in a post.
-- Problem Solved? Click "Accept as Solution" in a post.
New Contributor

Re: AP cannot join controller when not directly connected

Hi everyone, 

 

Sorry for the late reply. I was stuck in a different project. I just went and did A record configuration as suggestion by Koen to make it work immediately. This shows the model I was working on have no limitations (to be directly connected - my assumption before).

 

Thank You everyone for helping me out.

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