09-27-2013 05:53 AM
The development organization are fine tuning things in 6.3.1.x now.
For the present time, the recommended build in 6.3 is 22.214.171.124 (new this week)
Is there a particular item you are looking for in 6.3.1 ?
09-27-2013 07:22 AM - edited 09-27-2013 07:26 AM
I read that there are major AirGroup bugs in 126.96.36.199 and it is recommended that AirGroup be disabled while running this version of the code.
I read the release notes for 188.8.131.52 and wasn't sure if the bugs were fixed. It had to do with mDNS having to be restarted often, every day.
09-27-2013 08:04 AM
I was told by my SE that engineering is working aroud the clock to resolve one final issue in 6.3.1 and that they do not have a firm date for it's release. Based on that he said it would probably be 4 - 6 weeks. 184.108.40.206 was suppose to be released on 9/25.
09-27-2013 09:23 AM
We were experiencing the same exact mDNS bugs as you - rebooting a random controller almost once a day for a few weeks... occurred primary when doing a "sh switchinfo" or "wr mem" on the controllers or the master who then sent it to the locals and caused them to go in their funky state.
We upgraded to 220.127.116.11 last night and things are working well - I can finally do a "wr mem" and not plan to go reboot the thing :)
Been testing all morning random stuff that beore would cause the controllers to break and everything seems solid.
I recommend it. We've been prepping for 6.3.1 for quite some time but that date has been changing for quite some time so to be continued...
09-27-2013 03:29 PM
Derby... the mDNS fix is in 18.104.22.168. It should be documented in the release notes as well if you are ever pondering what's in a release and not.
22.214.171.124 is in the support site folder under current releases.
10-01-2013 11:02 AM
The release notes for 126.96.36.199 doesnt contain any references to the mDNS issues people are having with 188.8.131.52. Just to be clear, you're saying that 184.108.40.206 fixes the issue posted below?
3 weeks ago - last edited 3 weeks ago
I am currently running 220.127.116.11, and I still have to constantly stop and restart Airgroup to get complete Apple TV visibility when Apple TV's drop off from Airgroup. I have an open, lengthy, ongoing case with Aruba, and I was told that version 18.104.22.168 is due out around Sept 19th, 2013 that should fix, among other things, this specific issue.
10-01-2013 11:17 AM
No, he's referring to the fix where Airgroup causes other processes on the controller to crash causing the controller to become unresponsive.
I haven't heard of any complaints with AirGroup servers not beeing seen such as AppleTV's and I know many depts. use them. Never had to reset AirGroup.