Wireless Access

I have an Aruba 7210 WLAN controller with AP225's and 275's.  I have set up each AP with a static IP.  I can ping from the console connection to each AP with a good reply.  My issue is I can't get the APs to connect to the controller. 

 

Controller IP:     10.79.11.5              Gateway:  10.79.11.1                   Subnet:  255.255.255.0

 

AP IP range:  10.79.11.10- 10.79.11.49

 

Control Plane is diabled

 

This is a system that is stand alone on my desk for testing purposes.  I can't find any info to set up 7210 with static ip addresses assigned to the APs.

#7210
#AP225

Did you set the controller-ip address for the acces points during provisioning so that it can find the controller?  

#7210

While in console and watching the AP boot it runs ADP and finds the master as 10.79.11.5 which is the 7210

#7210

Type "show ap database" and see what the controller thinks about those access points.

 

Also, type "show log syste 50" to see if there are any messages about those access points.

#7210

Where would I type that command in?  Console of the AP or the 7210?

#7210

How did you provision those access points?  If you use the console, it would be "setenv master <ip address of master>".  If you used the GUI, it would be the master ip address.  But you say that the access points are finding the master, according to the console...

#7210

I consoled into each one and used these commands.

 

setenv ipaddr 10.79.11.x

setenv netmask 255.255.255.0

setenv gatewayip 10.79.11.1

save

boot

 

I watched the AP boot up and start ADP and all of them found the master as 10.79.11.5.

#7210

You need to type "setenv master <ip address of master>" if you are not using DHCP.

 

Well, you need to type "show datapath session table <ip address of acess point>"  on the controller to see if it is sending the controller any traffic.  That is the first step.

 

Next, you need to type "show log system 50" to see if there are any problems with that access point, if it is already sending traffic.

 

#7210

 

Here is the response I get from that command on the console of the 7210

 

(DEWLAN) User: admin Password: ********

(DEWLAN) >show datapath session table 10.79.11.48                                      

^ % Invalid input detected at '^' marker.

(DEWLAN) >show datapath session table                                

^ % Invalid input detected at '^' marker.

(DEWLAN) >show datapath session table10.79.11.48                                

^ % Invalid input detected at '^' marker.

#7210

You need to be in enable mode to run that command.

#7210

He is the snip of what it told me

 

#7210

AP 275s require ArubaOs 6.4 and above..http://www.arubanetworks.com/products/access-points/270-series/

 

It looks like the AP is requesting a binary that does not exist on the controller that suggests you are not running 6.4 and above.

#7210

The controller came with 6.2.0.0

#7210

As long as you purchased or have a valid support contract go to support.arubanetworks.com and download the latest 6.4.x (I believe it's currently 6.4.0.3) and flash the controller with that. This will allow both APs to function. The 225 requires a minimum 6.3.x and the 275 requires 6.4.x. 

#7210

Thanks all.  I will complete and let you know if there are any issues

#7210

FYI:  you cannot upgrade from 6.2.0.0 directly to 6.3

#7210

Yes, and you need to upgrade it with 6.4 or above or The 225s and 275s will not work.
#7210

I have the upgrade completed and the access points can now be provisioned.  FYI I used TFTP to transfer because the 7200 series will not let you upgrade from local file option

#7210

did you use eval license? check in controller license page if they are active. I sometimes find that eval license became inactive, after i change my controller's clock.
#7210

Did the AP275 and AP225 show up as active?

#AP225
#7210

Hello again,

 

#7210

Hello again.

 

         We have installed our AP 225's and AP 275's.  The WLAN has been up for a while but we have yet to get more than 1 AP 275 working.  The symptoms we are having are that the 275"s boot up and find the master but they don't broadcast no matter how many times we provision them.  I have consoled into the AP and watched it boot and it gets to the "Welcomne to the AP275" and "watchdog process finished nanny will restart."  Then Nothing.  Some 275's show blinking Green light and some show solid red.  Only 1 is letting clients connect and it has no light.  These are very confusing sysmptoms and I am having a hard time nailing down the culprit.  I am going to be very discriptive, see below

 

We have a 1gigabit uplink to a Cisco 2960 in a parking deck with 6 AP275's patched to it.  I also have an AP 275 coming from the MDF.  We ended up buying 30W POE injectors so we can rule out POE power from the switch being an issue.  The only AP275 that clients can connect to is in the parking deck.  It is plugged int o port 1 on the cisco switch.  All of the ports on the 2960 have been duplicated to match the 1 port that AP275's work on.  Any AP275 I put  on port 1 of the 2960 works.  Why don't the others?  The AP275 in the MDF is off of a Cisco 3750X.  There are 35 APs connected to a stack of 9 3750X's without any issue.  275's from MDF don't broadcast either. 

 

i have attached what console shows.

 

#7210

Think you captured the "insuffiecient POE Voltage" issue :)

 

Now to solve it... 

 

Cheers,

Michael

#7210

You need to enable LLDP on the switches.

#7210

sorry i have not read all the comment

 

have you ugrade your controller to 6.4 as suggested before,  are you always recieving the message "Shutting down eth1 due to insufficient POE voltage",

is the security plan disable or not.

#7210

I don't know if the issue was found in your case but I'm currently deploying AP-275 in a big manufacture to replace old Cisco Autonomus AP-1231. Our switch stack all around is standardized with Cisco 3750X 48ports. I just realized that on some stack the AP-275 once provisionned will appear as Inactive and in some other stack they will show as Active without the I flag. It's running on M3 with AOS 6.4.2.9. I started to dig into this issue during this week and yesterday I found that there is common denominator to those with the I flag. There are connected on stack running Cisco IOS 15.0(1)SE2 . The other AP-275 that work fine are on stack running Cisco IOS 15.0(2)SE2. All the stack have LLDP enabled. So it must be a bug with Cisco IOS version. 

 

Anyway I will continue to dig into this next week. If someone have other information related please share!

#7210