We were running 5.0 code and were having problems related to Rogue Detection. One device would crash every 10 minutes, another every 3 hours and our other two devices were okay. We disabled rogue detection and didn't have any further crashing problems. When 5.1.151.0 came out we upgraded and reactivated Rogue Detection and have been stable every since.
Kevin Semrau Network Specialist Millersville University -----Original Message----- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Earl Barfield Sent: Thursday, December 04, 2008 9:58 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] - Cisco WiSM > From: Leo Song <[EMAIL PROTECTED]> > Subject: Cisco WiSM > > Hi, folks. > >Which WiSM code are you running, 4.1.185 (we are), 4.2.173 or 4.2.130, > etc, etc? we've been suffering the prolong crash bug, the response from > Cisco is not promising, thanks. We're running 4.2.112.0 without any known problems. We were running 4.1.185.0 and had severe problems with the WiSMs de-prioritizing ARPs. 4.2.112.0 fixed that and we're happy with it so far. -- Earl Barfield -- Academic & Research Tech / Information Technology Georgia Institute of Technology, Atlanta Georgia, 30332 Internet: [EMAIL PROTECTED] [EMAIL PROTECTED] ********** 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/.
