Wireless Access

Hi,

 

I have a 651 controller that can not see it's own antennas and the AP's I have attached.... The setup worked fine earlier but after FW update to 6.2.0.3 I lost the connection to the AP's

 

- I Tried to reset the controller and the AP's but still no connection.

 

- The AP93 receives an IP address from the DHCP server (normal ISP router) no internal DNS on the network.

 

- The controller is setup for "automatic provision".

 

- AP database is emty.

 

What happened??

 

/Stfn

Did you wait long enough?

After the upgrade of the controller, the ap's also have to upgrade.

It takes time.

Hi Peter,

 

It have been running all day - so I hope not, time factor is an issue ;)

 

Thank you for your input.

 

/Steffen

The only reason for this is that the AP cannot find the controller...

You dont have an internal DNS server so is not finding the controller...

You will have to go to site and configure that statically via console otherwise it will never work...

The issue you are facing is that your ap does not have the ip of the controller server ip....

 

 

Question before doing the upgrade did you have statically configured the server ip? thats the ip that he use to upgrade the firmware as far i know

Regarding the 651's internal AP -- that is disabled if you upgrade to AOS 6.2 and above as per the 6.2 Release Notes.  The 651 effectively becomes a 650.

Ohhh he mean the internal antenans

i did read wrong his message :(

 

Hi I have some information from the startup log from the AP. That indicate that the AP knows who is the controller and it got an IP address

 

***************

ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
bonding: bond0: link status definitely up for interface eth0.
bonding: bond0: making interface eth0 the new active one.
AG7240: enet unit:0 is up...
RGMii 1000Mbps full duplex
AG7240: done cfg2 0x7215 ifctl 0x0 miictrl
ADDRCONF(NETDEV_CHANGE): ethsw: link becomes ready
192.168.0.41 255.255.255.0 192.168.0.1
Running ADP...Done. Master is 172.16.0.254
ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.17.1 (AR5416, AR9380, REGOPS_FUNC, PRIVATE_DIAG, WRITE_EEPROM, 11D)
ath_rate_atheros: Copyright (c) 2001-2005 Atheros Communications, Inc, All Right                                                       s Reserved

 

***************

 

/Steffen

So your problem is the integrated antena not the AP 93?

 

It just aht the tittle says something but then in the context of the message ti seeems you are taliking just of the integrated antenna

If its just teh integrated antenna issue... and thats tehy only tihng you canno provision, marcus already gave you what is it :)  if not then what is it at the end? :) im confuse

Hi,

 

It was actually both issues I have... or had. The issue with the antenna is solved (don't upgrade firmware to 6.2.x.x) but the issue with the 93 AP's are still pressent :\

 

Sorry for the confusion :)

 

/Steffen

Did you try what i said on my post?

Hi,

 

I can see log that the AP can see the controller and it has an IP address. Wouldn't that be enough for the controller to identify the AP?

 

/Steffen

IF you not upgrading yes

If you upgrading no... you need the server address

If you doing it via console which is what you will need to do you need to add this entry also

setenv serverip 172.16.3.221

If i have to configure it manually i put both...

 

 

A example of how it should look like all the config

 

setenv ipaddr 172.16.3.223
setenv netmask 255.255.255.0
setenv gatewayip 172.16.3.1
setenv serverip 172.16.3.221
setenv master 172.16.3.221

 

 

 

 

Now if you are for any change using DHCP which i guess you are using... on the DNS server put a record of aruba-master on it and put the ip address of the master controller and he wil get the master ip address and the server ip addresss automatically unless you did hardcoded it.

Hi NightShade,

 

The solution you offered would have worked with the manually configured AP's but a setup with a 100 AP's or more - I would have had too much work on my hands.

 

Anyways, Thanks for your input - this could be an option in an other setup.

 

/Steffen

Dont worry the real solution was the one that gave Collin, anways good to know its fixed!

Hello.
Here your log is:
192.168.0.41 255.255.255.0 192.168.0.1
Running ADP...Done. Master is 172.16.0.254

...so AP has not IP from same subnet as controller.
Check if you have not routing issue.

Jaroslav

---

@Jaroslav wrote:
Hello.
Here your log is:
192.168.0.41 255.255.255.0 192.168.0.1
Running ADP...Done. Master is 172.16.0.254

...so AP has not IP from same subnet as controller.
Check if you have not routing issue.

Jaroslav

---

That is your problem.  Remove the "default" ip address from VLAN  (172.16.0.254) and it should work.

 

The controller usually has something called the "controller-ip" which is the management ip address of the controller.  It is normally the lowest vlan number ip address.  Even if your AP found the controller by sending a broadcast on the 192.168.0.x vlan, it will be redirected to the "controller-ip".  Remove the ip address and you should be fine.

 

@Jaroslav

 

That worked, I changed my controller IP to the local range.... then it worked.... Thanks :)

 

/Steffen