Higher Education

6.3.1.0 has been released. If anyone has updated and can provide their feedback: pros, cons, version coming from, etc... It would be much appreciated.

 

If you are on another version of 6.3.0.X and have no plans to update in the near future please share your version/reasons.

 

I'm currently running 6.3.0.0 and am already working towards updating in our next maintenance window. My SE recommends getting off .0 code and the resolved issues make it worth early update.

We have to upgrade to the v6.3.1.X code to be able to provision the pallet of AP-115s we received yesterday.

 

I'm highly interested in this info as well.

 

One particular comment in the release notes that worries me since we have a good amount of AP-125 is:

 

ArubaOS 6.3.1.0 is not recommended for customers with AP-120 Series APs that routinely see over 70 clients
associated to an AP. Please contact support if you have any questions.

 

Will this also apply to future 6.3.x GA releases?

 

If that is the only warning that worried you, you missed this one.

 

ArubaOS 6.3.x.x will be the last release to support the a/b/g only APs as well as the RAP-5 and AP-120 Series.
ArubaOS 6.3 will be supported at least through October 31st 2018.

 

So, for AP-125s, the end is near.

Hopefully the lifetime of of 6.3 is longer than 6.2..

 

I will be very surprised/disappointed if ArubaOS support for AP-125, an 802.11n AP that has a end of sale date of just a few month ago will be dropped so soon.(6.4 will probably be around the corner looking at current ArubaOS release timeframes)

Just because 6.4, etc., won't support AP-120 series doesn't mean you have to run that ArubaOS. There are hundreds of customers out there (I'm sure) running 3.4 and 5.x code. It makes perfect sense that as software evolves, new/beefier hardware is required.

Everyone's talking APs . . . what about when the M3 is significantly crippled from running new code . . .

M3 EOL for Support id 10/1/2018, so 6.3 may be the last version supporting them too.

Note that 6.3 is supported until 10/31/2018.

Just to be clear, that's the M3 with the embedded 128 AP license. All of the controllers with embedded licenses are going end-of-life due to centralized licensing. You can view the products here: http://www.arubanetworks.com/support-services/end-of-life-products/

 

thanks,

-awl

I missed that detail.

 

Thanks for the clarification, Andy

Andy,

 

Does that mean that M3 controllers without embedded licening will be supported under 6.4?

 

Thanks,

MIke

I'm starting to see a trend with Windows 8 devices not being able to connect to either the 802.1x or the Open networks without power cycling the APs. There is no station-table or user-table data when this occurs. I don't see anything in the auth-tracebuf or user-debug logs. We are working on an AP-125 issue at the same time so there could be a correlation as all of these Windows 8 login issues are with AP-125s.

 

If anyone else has taken the 6.3.1.0 code are you having Windows 8 issues?

We have also had some AP-125 issues with 6.3.1.0 code.

I believe 6.3.1.1 will be released soon with some more AP-125 fixes. The fixes in this version should help greatly.

We have been testing these fixes. We still have some AP-125 issues, but not nearly as many as before.

BTW, many here have been using Windows 8 fine with an EAP-PEAP-MSCHAPv2 WPA2 SSID.

6.3.1.1 has been out for awhile now. Has anyone upgraded and seen a resolution to any problems they were having?

Upgraded to 6.3.1.1 this weekend and saw the same issue that we saw with the 6.3.1.0 upgrade, clients not being able to do anything.  Aruba TAC identified a problem with the validuser ACL:

 

(Aruba) (config) #ip access-list session validuser

(Aruba) (config-sess-validuser)#any any any permit position 3 ß-----corrected one

(Aruba) (config-sess-validuser)#no any any any deny  ß-------wrong one

 

What is strange is that, that deny line has been in our config for sometime, at least 6 months, and was not affecting clients in the previous code we were running, 6.1.3.6-Airgroup.

E

We upgraded to 6.3.1.1 over the weekend as well and have not discovered any problems yet.  Previously we were running 6.1.3.6 code and were experiencing VRRP flaps on our locals.  We have also noticed marked improvement in the consistency of airgroup/airplay.

We upgraded from 6.1.3.6-Airgroup to 6.3.1.0 the week after 6.3.1.0 was released. The new release did resolve a number of our reported issues with 6.1.3.6, the only issue which is new for us under 6.3.1.0 is a number of our APs are showing DOWN on the Master controller but are shown as UP and working on their Local Controllers (and are indeed up and servicing wireless clients OK. Aruba TAC has been able to reproduce our issue I am told (Case 1469382 for those interested), and we are seeing this with AP-125 and AP-134/135 APs. Out of our 205 or so APs, about 135 are showing DOWN on the Master but are indeed working and shown as UP on their local. Other than that, so far so good on 6.3.1.0 for us.

Mike

You may want to restart your STM process on the Master. #process restart STM. 

This will disconnect any users connected to the master if you do. It shoud resink your databases.

Brian:

TAC tried this, we also ran debugging on STM processes and AP communications while we did this, issue persisted. TAC was able to reproduce so hopefully a resolution is in the near future. At least the APs are functioning and AirWave is showing correct status so at least I have a way to see any AP issues without having to look at the local controllers individually.

Mike

I have seen this a few times immediately following upgrades on 6.1x code (and maybe also on 6.2.x code).

 

I typically clear the gap-db on the master controller based on all of my local controller addresses (clear gap-db lms x.x.x.x).  All happy and functioning APs will immediately re-register in the Master's gap-db so if everything is up and running it is a no-harm action.  I will say that I use Airwave as a litmus test to ensure that all of my APs are actually up  (if there is an actually down AP and you clear the gap-db, your master won't report the "Down" AP).

 

Here's a CJoseph write up on the cmd.

http://community.arubanetworks.com/t5/Command-of-the-Day/COTD-clear-gap-db-access-point-housekeeping/td-p/1774

 

Kevin

We tried to upgrade to this, from 6.1.3.6-Airgroup.  The environment is a 6000 with one M3, just under 300 APs mixed 105,125 and 135.  Everything came back up as you would expect but connected clients to any of our 3 SSIDs had no connectivity beyond their gateway. 

 

Had a very short maintenance window so we rolled back without having done detailed troubleshooting.  Very strange, was hoping someone else had seen this and could explain.

EMH,

 

You should schedule your upgrade window with support so that they can make sure everything goes smoothly.  Since you reverted back, we do not have much to go on, but hopefully with support's assistance you can get to the bottom of it.

 

When we first moved from 6.2. to 6.3 the vlans in our vlan pooled were removed. It was a quick fix but an initial scare. We just upgraded to 6.3.1.0 from 6.3.0.0 and haven't noticed a problem but we're still monitoring.

With 6.3 I'm noticing that there are sporadic user entries in the user-table where a user has two separate IPs from two different VLANs. One fo the vlans isn't even listed for the ESSID when I run "show ap essid". I have a case opened and this morning the enabled "aaa user fast-age" and am monitoring the tables manually. Has anyone else seen this?

---

@rosie wrote:

With 6.3 I'm noticing that there are sporadic user entries in the user-table where a user has two separate IPs from two different VLANs. One fo the vlans isn't even listed for the ESSID when I run "show ap essid". I have a case opened and this morning the enabled "aaa user fast-age" and am monitoring the tables manually. Has anyone else seen this?

---

Rosie,

 

That would happen if a user has his wired and wireless connected or traffic from the LTE/HSPDA/EVDO radio on a phone "leaks" traffic through the wireless LAN interface.  You could also enable "Enforce DHCP" on the AAA profile so that only devices that get their ip addresses from your DHCP server are allowed in the user table.  That would of course eliminate you from having any devices on that WLAN that are statically addressed, so choose wisely.

 

aaa user fast-age will attempt to age those addresses out, but they will still appear for a short while.