We have just moved to the LWAPP with the WISMs. We've had a few interesting problems but nothing of this magnitude. We've only upgraded once so far, to 4.0.179.11, and that went off without problems. Recently I've enabled them with WLAN override and rebooted all the 323 APs and they managed to all come up without a problem (well if you don't include the expected CDP/Injector problems).
The only major problems we have experienced were after the initial upgrade to lightweight. One night, after migration, we noticed about 15 of the APs had come up the same IP address and an incorrect subnet mask. As they were either statically configured or had dhcp previously, this was strange. We have about five cases where one would come up with the an IP address on a totally different network. And about three cases where we would reboot the AP and have to wait for about an hour before it actually worked, and stayed working. None of these problems have come back since. At the moment only one AP is having problems and we suspect a power/cable issue. Admittedly we only have about about 6 weeks experience with LWAPP in production. In the last week we have rolled out a PEAP WLAN to specific locations without an issue. Reading these issues that others are having, I consider myself lucky...so far. :) The only thing I can suggest is getting one of the APs, connect to it with the console, and enter debug commands as it boots. I've done that to verify dhcp option 43 was being received correctly. Anthony ---- Original message ---- >Date: Fri, 2 Feb 2007 12:06:25 -0500 >From: Lee Badman <[EMAIL PROTECTED]> >Subject: Re: [WIRELESS-LAN] LWAPP APs Disassociating From Controllers >To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU > >Turns out that 4.0.179.11, which was the bug fix for the controllers >randomly rebooting, has it's own set of issues along the lines of >"Unexpected Layer 2 Traffic Can Make APs Disassociate", so the bug fix >here is to go to either 4.0.2.0.6 or 4.0.2.0.7 to resolve the problem. > >What's unfortunate for us, is we have lost many of the WiSMs we've had >to upgrade for previous bugs- they didn't survive the upgrade process >and scrambled their flash. Cross fingers we don't repeat that again on >this go round... > >If anyone is just starting to go down this road, I urge you to be very >cautious. > >Lee > ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
