Hi Dexter,
Late last evening, Cisco's senior engineers said we could expect fix code by
this Monday, and provided this input:
To give you a little background on this bug - this issue is mainly due race
condition with rogue task and double call/release of a function causing crash.
Unfortunate
I definitely had that issue. Lee that bug search sounds exactly like what I
was experiencing. At the bottom of this response is my 12/9/14 response on
this list describing our experience. I eventually had to downgrade to 7.6.130
to get things stable. We have 6 controllers and I RMA'd 4 of th
Not sure we have hit that issue, but still seeing some crash issues since May
last year
We have had 5 PRD controllers on 110.0 since 1st Feb and another 1(dev) since
December last year. One of the PRD crashed 2 days ago, but that is all we have
seen. I'm not sure if ours is related to memory, i
Thanks, Linchuan. We have hundreds of 11ac access points and rely on the latest
NBAR protocol pack. Going back is not an option… I find that to be a pretty
ludicrous “solution” given the adoption rate of 11ac.
-Lee
Lee Badman
Wireless/Network Architect
ITS, Syracuse University
315.443.3003
(Blo
Dear Lee
We had the same issue. And Cisco engineer suggested to downgrade to version 7
because all of the codes in version 8 have this bug. We are waiting for an
update that they solve this bug in version 8.
Have a nice day.
Linchuan Yang (Antony)
Wireless Networking Analyst
Network Assess
"PLEASE PLEASE PLEASE
Stability over features. "
Amen to that one bruthuh!
I would add: Transparency and proactive communicate would also really help!
Pete Morrissey
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Trent H
Do I need to get escalation image from TAC to fix this? I have had a few
reboots on different 5508's that I have on 8.0.110.0 The bug page shows this
version as fix 8.1(10.191) Are they offering to give you that?
Also I know that there are many cisco folks that monitor this listserv. This
me
