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
[email protected]
630 W. 168th Street
PH18-126
NY, NY 10032

On Jun 30, 2009, at 8:14 AM, Bentley, Douglas wrote:

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 | 727 Elmwood Ave.| Rochester, NY 14620
T: 585.275.6550 | Email: [email protected]

      <image002.jpg>

From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[email protected] ] On Behalf Of Justin Hao
Sent: Monday, June 29, 2009 11:50 PM
To: [email protected]
Subject: Re: [WIRELESS-LAN] 3750G and 1131

Howdy,

regarding 4.2.176 i can absolutely positively NOT recommend it as a stable code base, 4.2.205 is a direct release containing a critical bugfix that we had a direct hand in "motivating" cisco to fix promptly.

4.2.176 contains a memory leak in involving mobility groups of size (our setup is approximately 1700 APs with 18 controllers). This memory leak is fatal, the general gist is that stateful information regarding mobility clients isn't released properly from memory as clients come/go, thus driving memory usage on controllers constantly up until they crash ungracefully with little or no crash/log information, controllers also take an inordinate (20+ minutes) amount of time to recover from the crash, i presume because they're attempting to log crash data and there isn't any memory available for that. We observed controllers cycle to 98-99% memory every 8 weeks until they crashed. Working with the dev engineer they tested and monitored two of our controllers for several weeks to identify the issue. I don't know the "critical" size or number of APs/ controllers required to have this be a noticeable issue, but ungraceful controller reboots occurred every 8 weeks with our setup.

We are currently running 4.2.205 and haven't experienced an "event" anymore, so i'd recommend 4.2.205 if you need to run 4.2.x code, we haven't had any experience with any 5.x code at all at this time, since cisco pulled support for the 10xx series APs from anything newer than 4.x.

--------
Justin Hao
Texas A&M University
Network Group
(979)862-2162
[email protected]
--------

On Jun 29, 2009, at 7:50 PM, Mike King wrote:


Both 4.2.205 and 4.2.176 have been designated as:

AssureWave The Cisco® AssureWave program focuses on satisfying customer quality requirements in critical vertical markets in the wireless space. This program links and expands on product testing conducted within development engineering, regression testing, and systems test groups within Cisco. AssureWave certification marks the successful completion of extensive integrity testing that validates targeted releases. In addition, Cisco’s AssureWaveprogram ensures compatibility with major device and application vendors through established partnerships. Cisco’s partners perform extensive testing at their own facilities to ensure broader interoperability with our ongoing new releases. Learn More

So I'd feel safe with them. No higher releases have been certified under this program..

(Assurewave replace Safeharbor testing for wireless)

On Mon, Jun 29, 2009 at 4:31 PM, Pham, Loc <[email protected]> wrote:
   Guys: I am ready to config and test 3750G on a 4.2.205 code

Beside this bug, any other good stuffs that I should look for ? CSCsu02630

I am also ( tempted ) to go with the 5.2 for CWAPP functionality if time permit....

Regards,


Loc Pham, CCIE # 17030 - Sr. Network Staff,

IT Enterprise Security & Services, UCSF Medical Center.

Office 415-353-4492 Pager 415-443-9014


********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/ .


********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/ .


********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/ . ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/ .




--------------------

This electronic message is intended to be for the use only of the named 
recipient, and may contain information that is confidential or privileged.  If 
you are not the intended recipient, you are hereby notified that any 
disclosure, copying, distribution or use of the contents of this message is 
strictly prohibited.  If you have received this message in error or are not the 
named recipient, please notify us immediately by contacting the sender at the 
electronic mail address noted above, and delete and destroy all copies of this 
message.  Thank you.

**********
Participation and subscription information for this EDUCAUSE Constituent Group 
discussion list can be found at http://www.educause.edu/groups/.

Reply via email to