Hi William,
It is an excellent report. God bless your hands.
thanks for your sharing.
On Fri, Sep 22, 2017 at 5:22 AM, Green, William C
wrote:
> Linked is UT Austin's biennial network report:
> https://utexas.box.com/s/drckih61cw8yvom3avihe6j7c8nx972n
>
>
> I encourage others to provide their
We've been chasing bugs all the way down the 6.5 release chain, from
Airgroup bugs, to APs
crashing. We then started the semester with an emergency upgrade to
6.5.3.2 when the first
wave of early student arrivals started triggering bug 159797 (stm
crashes) . We are enjoying
our 303H's and 36
We have been working extensively with our local reps. The version with the STM
crash was the first one thjey recommended. We have been trying to find code we
could move to for about 4 months and don’t feel like we are any closer.
Amel Caldwell
University of Washington UW-IT
Wi-Fi Network Engin
We have been on 6.5.2.1 for a couple months now with no “major issues”.We
have the 3xx dfs bug and we do see a ton of radar hits.
Waiting for the fix release that is due out in another week or two.
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.
Suffolk University in Boston is also running ArubaOS 6.5.4.0 to support model
AP303H and have had no issues so far. We have over 1600 APs deployed a mix of
AP105, AP135, AP225, AP325 and AP303H.
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUS
Did they say what the release will be? Will it be 6.5.2.1 or are they going to
expect you to jump to 6.5.3 or 6.5.4? We often request fixes to be put in
older versions to minimize risk of going to a whole other train of code.
I am curious because I was told 6.5.2 had been “parked”.
Amel Caldw
Rollins College has 6.5.4.0 (for 303h) and no issues.
Some AMON weirdness going to Airwave and the master controller, but nothing
critical -looking at data on the controllers with AP's gives us the data we
need. A known bug.
Ian
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[
We’re running 6.5.2.1 as well, without any issues. That said, we’re running
mostly AP-225’s and a few AP-335’s, and not running the DFS frequencies at all.
-Colin
Colin Randall
Network Manager
Colorado School of Mines
303-384-2208
On Sep 22, 2017, at 9:18 AM, Amel Caldwell mailto:am...@uw.edu>>
I stand corrected… we are experiencing - Reboot Cause: Datapath timeout (SOS
Assert) (Intent:cause:register 54:86:50:2) associated with bug ID: 168710
Cause: "contents in datapath is not freed. New streams are not allocated with
resources to categorize. Due to this duplicate session deletes we
For whatever it is worth, we are going to go from 6.5.2.0 to 6.5.3.2
conservative release per TAC recommendation
Brian
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Michael Hulko
Sent: Friday, September 22, 2017 2:06 PM
To
This summer we added more APs to 8540 controller. Now our 8540 controller has
2350 APs(mainly 1810W and 2802 APs) and 13K (increased from 6k in March/April)
concurrent 802.1X users at peak. We also upgraded the controllers from
8.2.150.0 to 8.2.160.0 during summer. Now the controller has run int
Dennis,
We are running an HA pair of 8510's with 8.0, so not quite the same, but
this week we had the same thing you described happen, where more than half
the APs suddenly disassociated but then came right back up (after a little
back and forth since they found an older controller running newer c
Thank you Jess for your information, but not quite the same as our situation.
In our case, not just the APs are disassociated, the controller can't be pinged
from anywhere, nor the controller can ping it's default gateway. The controller
was totally lost from the network. Its uplink port channel
13 matches
Mail list logo