I found an email from our TAC engineer giving a brief explanation of what was patched:
>The fix was related to mobility/roaming and the clients pmkcache entry not being processed
>properly. This is a function within the controller and not a feature so functionality
>should be gained, not lost
Howdy,
This issue was not fixed in 4.2.176. This wasn't an already identified
bug as far as Cisco revealed to us, they tried to blame our controller
crashes on an possible SSH problem (which they've fed to us before),
but we were adamant about them finding the real reason this time since
it oc
I believe they fixed the memory issue in 4.2.176 but broke other
functionality. According to Cisco, the memory fix was in 4.2.176.
I could be wrong. I cannot find any memory bugs in 4.2.176 only in
4.2.130.
-Original Message-
From: The EDUCAUSE Wireless Issues Constituent Group Listser
Ouch: thanks Justin for the head up. I do have some prod. boxes on 4.2.176
... Time for schedule maint
I will also scan over the 4.2.205 release doc.
Best Regards,
Loc Pham, # 17030 , office 415-353-4492
IT Enterprise Security & Services, UCSF Medical Center
Where self-healing network
yes, it was with 4.2.176, i don't have the bugid information, i only
have our tac case, if i get some time i'll parse through the release
notes for 4.2.205 and see if i can mark which one was ours.
Justin Hao
Texas A&M University
Network Group
(979)862-2162
j...@net.tamu.edu
Oh, OK. Sounds like Justin has a memory leak issue with 4.2.176
though. Is that correct Justin?
On Jun 30, 2009, at 10:27 AM, Bentley, Douglas wrote:
CSCsq87549/CSCsq63106(memory leaks) Sorry that is the issue within
4.2.130
CSCsx07878—Client devices no longer intermittently fail to log
CSCsq87549/CSCsq63106(memory leaks) Sorry that is the issue within
4.2.130
CSCsx07878-Client devices no longer intermittently fail to log into a
WLAN with web authentication (webauth). This one broke us in 4.2.176.
We are using the internal web re-direct for authentication. This does
not wor
Does anyone have a BugID for the memory leak issue in 4.2.176? Thanks,
--
B.J. Pinsky
Manager, Core Resources
New York Presbyterian Hospital
Columbia University Medical Center
(o): 212-305-9021
(m): 917-626-9485
b...@nyp.org
630 W. 168th Street
PH18-126
NY, NY 10032
On Jun 30, 2009,
I completely agree with the 4.2.176 statement. We are having the same
issue with the memory leak on our 14 controllers. After a month of
testing, we are upgrading to 4.2.205 at 5am tomorrow.
-Doug
Douglas Bentley | University IT/NC Network Engineering
University of Rochester |
