Hi, We have been running 5.2 for a few weeks also. The main reason we upgraded was for support of the new 1142N aps. An issue the I noticed immediately after the upgrade is a lot of log messages for Potential honeypot rogues. The controller seems to think that different ssids on the some of our valid aps are rogues. This causes the controller to disable the radio interface briefly.
Below is what the TAC engineer said about this issue: I found a bug filed by my teammate last month, for too many honeypot trap events on WLCs. Reported in code prior to 5.2.157.0, the good news is that DE have apparently determined the cause and coded a fix. The bad news is that they show apply-to: and integrated-in: fields of 6.0.x.0 which is not out until later this month or early Mar09. The other issue we encountered was the removal of the wlan override feature. This wasn't too big a problem in our case. AP Grouping is now the required method of limiting the distribution of wlans. By default all aps are in the default-group which advertises all wlans on the controller. We are going to use 3 groups, Production ( all our regular wlans ), Conference and Development. From the controller it is quite simple to move the ap's between groups, in the WLANS> Advanced menu. Is anyone else using version 5.2 ? Regards, Peter. Peter Arbouin Network Engineer Network Operations Centre, ITS Queensland University of Technology Brisbane, QLD, Australia PH: (07) 313 81030 -----Original Message----- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Jeffrey Sessler Sent: Tuesday, 3 February 2009 1:58 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] WIRELESS-LAN Digest - 19 Jan 2009 to 20 Jan 2009 (#2009-8) Lee, For #2, I ran into this "feature" two months ago. TAC case already open. Bug filed CSCsw21394. There is a engineering fix for this, but there is also a maint release for 5.2 due any moment now, and I would highly recommend updating as soon as it's released. Jeff >>> Lee Weers <wee...@central.edu> 02/02/09 7:15 AM >>> I have been running 5.2 for a few weeks and I have recently found a couple of undocumented features with WCS and the use of AP groups. In 5.2 they no longer support the wlan override feature and instead want you to use AP Groups to turn on and off SSID's and assign them to a particular interface. 1. WCS accepts spaces in the AP group name, however, the controller does not 2. WCS doesn't necessarily assign the correct interface name to the controller using and AP group. SSID name XY interface XY on the ap group template. Push it to the controllers and SSID name XY interface ZZ. So be careful with #2 in using AP Groups. I had to go back through and delete the wlan profile in each ap group and recreate it on each controller. From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Manoj Abeysekera Sent: Thursday, January 22, 2009 9:59 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] WIRELESS-LAN Digest - 19 Jan 2009 to 20 Jan 2009 (#2009-8) We are also running 4.2.130 for sometime now. However we do have a problem of WLC not forwarding traffic for some users in a totally random order. Cisco has found a bug (Hopefully the right bug -Bug ID is CSCsq41327) so we need to move away from the 4.2.130 code. Having heard all the concerns about 5.x code I'm not sure what code we should upgrade... It seems, only option would be at this time is to go with 4.2.176. Thanks Manoj A. American University "WALLACE, DAVID" <dwall...@kent.edu> Sent by: The EDUCAUSE Wireless Issues Constituent Group Listserv <wireless-lan@listserv.educause.edu> 01/21/2009 09:20 AM Please respond to The EDUCAUSE Wireless Issues Constituent Group Listserv <wireless-lan@listserv.educause.edu> To WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU cc Subject Re: [WIRELESS-LAN] WIRELESS-LAN Digest - 19 Jan 2009 to 20 Jan 2009 (#2009-8) We are running 4.2.130 since last December. Very stable with no issues so far. We have this code running on both WiSM's and stand alone 4400's and one 2106. We have just under 1200 ap's in production. We are running 5.1.151.0 code on our testbed controller. We are still not comfortable going to the 5 code train yet. David Wallace Associate Network Designer Kent State University -----Original Message----- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of WIRELESS-LAN automatic digest system Sent: Wednesday, January 21, 2009 12:00 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: WIRELESS-LAN Digest - 19 Jan 2009 to 20 Jan 2009 (#2009-8) There are 7 messages totalling 1055 lines in this issue. Topics of the day: 1. WiSM Code- Revisited (5) 2. WISM Stability and Load (2) ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ---------------------------------------------------------------------- Date: Tue, 20 Jan 2009 12:4</wireless-lan@listserv.educause.edu></wireless-lan@listserv.educause.edu></dwall...@kent.edu></wee...@central.edu> ********** 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/.
