Aruba Instant & Cloud Wi-Fi

Reply
Occasional Contributor II
Posts: 17
Registered: ‎12-16-2013

One AP not auto joined!

Hi,

 

I have a D-Link switch with 7 AP's 105 attached to it. I created 4 different wireless networks, each with a different VLAN, ...  everything works fine here.

 

The D-Link switch is connected to a HP Procurve switch (on port 48, all the VLAN's I use for the wireless networks are tagged here). There is also one Aruba AP connected to port 46 of the HP switch. The same VLAN's are set as on port 48, but the AP is not showing up in the list with the other AP's, and I cannot access it. Seems it is not autojoining en take over the settings like the other AP's.

 

Anyone an idea why not?

 

Thanks.

Guru Elite
Posts: 20,366
Registered: ‎03-29-2007

Re: One AP not auto joined!

- Check to make sure the AP is getting an ip address, either by tracking the mac address in your DHCP server or looking at the AP's console using a console cable

- Make sure the IAP is getting on the same VLAN as the other IAPs

- Make sure the IAP can get to the internet, just in case it has to upgrade.

 

These are all IAPs, right?

 



Colin Joseph
Aruba Customer Engineering

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

Occasional Contributor II
Posts: 17
Registered: ‎12-16-2013

Re: One AP not auto joined!

It is working again. Thx.

MVP
Posts: 1,404
Registered: ‎10-25-2011

Re: One AP not auto joined!

do you mind sharing what solved the problem so others can benefit from this post?
Pasquale Monardo | Senior Network Solutions Consultant
ACDX #420 | ACMP
[If you found my post helpful, please give kudos!]
Occasional Contributor II
Posts: 17
Registered: ‎12-16-2013

Re: One AP not auto joined!

So I had one AP (an Instant 103) that was connected to a HP switch. That AP that did not work. All the other AP's (Instant 105) on the D-Link switch worked. I changed the AP, so an Instant 105 was connected to the HP switch and the AP 103 that dit not worked ,I connected to the D-Link and that solved it. Very strange, but now it works.

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