This is aimed at the WiSM crowd on the list:
We are currently running 4.2.61.0 on our WiSMs, and are newly enjoying
the afterglow of random controller reboots from a bug. TAC guidance is
that 4.2.112.0 fixes our bug. But given the intrusiveness of upgrading
almost 2000 APs and 24 controllers,
Please reply on list. We are also facing the same problem and would like to see
suggestions.
-jcw
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
From: Lee H Badman [EMAIL PROTECTED]
Date: Thu, 1 May 2008 09:36:27 -0400
Subject: [WIRELESS-LAN] Latest Stable WiSM Code?
Reply-To: The
We are also on 4.2.61.0. I had chuckle when you said you didn't want to
touch it again for 6 months. It seems like there is always some gotcha
bug that we get hit by in whatever release we are on. At least TAC
usually knows which bug it is sigh. I was thinking of going up to
4.2.112.0 as well,
The 4.2.112.0 version may well fix the bug that you are working with
TAC, but be advised that 4.2.112.0 is crashing for us every few days
on a production controller.
It has never crashed in the lab, but started crashing once it had been
installed in our first real world test of it. This WiSM
For what it's worth, we are still running 4.1.185 and have been since August.
From our experience, it has been rock solid. Given our experience with
previous versions, we don't want to touch the code. Still, we are considering
an upgrade this summer so we don't fall too far behind, but we
Heck, we're at 4.0.219.0 with 5 controllers and ~300 access points, and
we have been going all academic year with no issues what-so-ever. I
don't even have plans to upgrade this summer right now, because no one
is forcing it down my throat.
-Rick
Yantis, Jonathan wrote:
For what it’s
We are running 4.2.112.0 on 10 of 22 Wism controllers. These 10
controllers were upgraded from 4.1.185.0 (very stable, did not want to
upgrade) to facilitate the installation of the AP1252 pre N. By the
way, the 5.0.148.0 is not the latest code and if loaded you will have
to physically
One more question on WiSMs, to check my own sanity. I'm starting to see
what appears to be a trend. Where I have WLAN override selected and
applied and in use for a while with no issues, it seems that randomly
SSIDs are either dropping from the list of selected SSIDs and need to be
reapplied, or
We are seeing the exact same issue. It seems as the settings are just not being
saved. In the beginning we thought it might have been an issue with WCS not
saving the settings on the WiSMs, but we discarded this after applying the
settings directly on the WiSMs. I haven´t found anything on the
I did too. We had this same problem when I upgraded to WiSM code 5.0.148.0.
From the information I could gather, it seemed to be most prevalent in new
Macs and those PCs running some form of Vista.
We also found that pings, both to and from the wireless client, would stop
responding. When
10 matches
Mail list logo
