Wireless Access

Hello,

 

We're considering deploying 6.3.0.1 on a pair of 7240s for our campus wlan. We have about 800 APS and 4,500 concurrent users. Is anyone here doing something similar? The license pooling feature is something we could use today and that is why we are considering the jump from the GA train to the Early Deployment code. We get the impression that the Early Deployment code is not really "beta", but I don't understand what keeps it from being GA. If you've done this I'd love to hear from you about your experience, positive or negative. We're also curious how long it typically takes for Early Release code to make it to GA.

 

Thanks!

 

Troy

I just deployed a 3400 and 2 M3's ~400 APs with the 6.3.01 code in order to get the centralized licensing and fast failover features. Both work great and I have not experienced any issues yet. 

We currently have 6.3.0.1 on test environment with 3 M3s :
- one acting as a master / license server (vrrp setup)
- one acting as local / license backup (vrrp setup)
- one acting as local

It works really well so far no issues with the license pooling .

We only have about 40 APs attach and like 15 users , ClientMatch its been working well for most clients after doing some tweaking in the arm ClientMatch thresholds (SNR / signal ).

Our plan is to test the code for 3/4 weeks before deploying it in production .

Thanks to you both for your input. Glad to hear the license pooling is working well for you.

Hello All,

 

I just recently upgraded to Release 6.3.0.1 and I noticed that the built in/pre-defined ACLs associated with logon-control, captive portal and so on, don't exist.

 

So if you try applying the captive portal firewall policy to a Role, I noticed that no ACLs exist. Is that the case with you all? Is this a bug on the Code? Or does Aruba require us to implement the ACLs on our own?

 

 

My bad! Completely forgot to reboot my Controller after the License was installed.

I can't say I've moved on to 6.3.0.1 or even 6.3.0.0.  But my experience with moving to the ED of 6.2.0.0 was really bad.  It was quite buggy and unstable in my environment.  Once the 6.2.0.x release went ot stable all my problems were gone.  I will never upgrade to an ED release again.  I only have 200 APs and not nearly as many connected users.

 

 

Sorry to hear that. What you describe is exactly what we are concerned about. Were you able to get support from Aruba on ED 6.2?

---

morrisch@alliancecityschools.org wrote:

I can't say I've moved on to 6.3.0.1 or even 6.3.0.0.  But my experience with moving to the ED of 6.2.0.0 was really bad.  It was quite buggy and unstable in my environment.  Once the 6.2.0.x release went ot stable all my problems were gone.  I will never upgrade to an ED release again.  I only have 200 APs and not nearly as many connected users.

 

 

---

the good news is that the folks at aruba seemed to realize this too so it should not be as bad as 6.2 ever again.. or so we hope :)

That said.. I'm holding of any customers from upgrading to an ED release unless for very good reasons.

I was but the eventual fix was getting the stable release which was well over a month since I had my issues of my controllers randomly crashing.

Guys!

 

I couldn't agree more. There are a few concerns that I have with 6.3.0.1 at this point (especially with Wired 802.1x). Currently have a Ticket with TAC on the issue. But, it might just be a working as designed issue, however, I and TAC found it quite strange.

 

As much as it's doing most of what I expect it to do, I still have some reservations and I will definitely ask my Client to upgrade as soon as a Code becomes GA.

What kind of problems are you seeing with wired 802.1x? We are also installing a new cluster of 7240s running 6.3.0.1. Wired 802.1x for us is a must.

Something to do with the fact that once you are authenticated via Wired 802.1X and you unplug and plug back into another Port (within seconds), I seem not to be able to authenticate again. 

 

However, I doubt this might be related to a Code issue. And I believe it has something to do with a timer on the Controller.

 

Because, anytime I unplug my Laptop and wait for about 2minutes and plug back in, I have no issues whatsoever.

One thing I was thinking about, has anyone tried 6.3 with legacy waps? I have many 65s and 61s. They work with 6.2.

According to the EOL listing (http://www.arubanetworks.com/support-services/end-of-life-products/#AccessPoints), AP-61 and -65s are supported in 6.3 although it is the last where they will be.

 

Long live 6.3 !

I have been on 6.3.00 since it came out.  The features were just to tempting for me to wait.  I am still ushering out many ap65's but the ones that are still here work just fine.  One feature which I was really excited about was lldp, so I could see my AP's on my HP procurve network easily, unfortunately it does not look like the 65's got that feature, so i would assume there may be other things they did not get.  They still work fine though.  I really miss the maps though, they are gone.  Looks like aruba is pushing customers to switch to airwave.

Our controllers (3600/3400) are on 6.3.0.1. I've had to deactivate Monitor/Police CP Attack rate (per sec) in global firewall settings since dozens of stations were ending up on the blacklist because of CP-flood (rate was set at 1000 !!). That's the only problem (so far).

 

Removing RF plan is a bad move imho. Airwave's Visual RF is giving me a headache atm :smileysad:

 

Does anyone know if there is a timeframe when 6.3.0.1 will be put into GA?

Good day, We are a school with 2x 3600s, 160x 135s, 40x 105s, and 25 of the new 225s, with 1600 concurrent users. We upgraded to 6.3.0.0 in May, and 6.3.0.1 three weeks ago.

When we made the jump to 6.3.0.1, that's when the problems started. Our main symptom was iPads took anywhere from 30 seconds to 10 minutes (yes I said 10 minutes!) to connect. Every other wifi device had no issues (iPod, Android, Win XP and 7 laptops, iMacs). And this affected EVERY iPad. We spoke with TAC as well as our Aruba reps and we found Client Match to be the issue. Turned it off and everything worked fantastically! But, that's why it's called a beta... We kept our syslog server on debug from our two controllers just in case.

Also, I too miss the VisualRF. At first, I thought that after the map was completed, the controller would use that information to better calculate roaming and Client Match type of stuff. That would be awesome, huh!? But now I'm having a hard time getting the beta Airwave to work...

Ohh well, I'm just happy to say I can serve 802.11AC clients, alongside my 1600 daily users.

I love Aruba!!!

Good to know about 6.3..0.1. I have several of my sites at 6.3.0.0 as a test for the last month and no issues but was considering upgrading to the newer release. Will stay away from it just in case it cause me problems