We're not using 4.2.176, but we've had 30 WLCs on 4.2.130 code since July 08 with a current load of 3,000 APs and a client peak load of over 9,000 concurrent users.
WLC operations have been stable, but we don't run any Web services on the WLCs and our WLC configs are non-standard WRT RF Groups due to RRM issues that pre-date the 4.2 code. Based on the bugs I've seen documented in the Cisco bug tool for v5.2 CAPWAP code, I wouldn't deploy it in a production system. -Charles Charles E. Spurgeon / UTnet UT Austin ITS / Networking c.spurg...@its.utexas.edu / 512.475.9265 On Tue, Jan 20, 2009 at 12:46:16PM -0500, Lee H Badman wrote: > > After a weekend full of problems on 4.2.112... We are being instructed > to move from 4.2.112 to 4.2.176, and to avoid 5 code. Could use some > input from anyone running 4.2.176. > > > > How big is your environment, and are you either experiencing or aware > of any major bugs? > > > > For us on 4.2.112, we are having random spates of controllers losing > both management and service IP addresses. > > > > Thanks much- > > > > Lee > > > > Lee H. Badman > > Wireless/Network Engineer > > Information Technology and Services > > Syracuse University > > 315 443-3003 > > > > ********** 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/.
