From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:[EMAIL PROTECTED] On Behalf Of Lee H Badman
Sent: Thursday, May 08, 2008 7:26 AM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: [WIRELESS-LAN] RE: [WIRELESS-LAN] WLAN Override- Again a
WiSM question
Hi Hector,
"
EMAIL PROTECTED]
-Original Message-
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:[EMAIL PROTECTED] On Behalf Of Lee H Badman
Sent: Thursday, 8 May 2008 10:26 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: [WIRELESS-LAN] RE: [WIRELESS-LAN] WLAN Override- Again a
WiSM ques
s on all
controllers.
-Lee Badman
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:[EMAIL PROTECTED] On Behalf Of Hector J Rios
Sent: Wednesday, May 07, 2008 7:52 AM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] WLAN Override- Again a WiSM questi
I found out a couple of things. First, there seems to be a bug that
causes this problem if the WLAN profile name and the WLAN SSID name are
not the same. So just make sure those names are exactly the same.
Second, and most exiting, APs download configuration from controllers
they join. If you have
From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL
PROTECTED] On Behalf Of Phill Solomon
Sent: Monday, May 05, 2008 4:05 AM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] WLAN Override- Again a WiSM question
I am not sure if this is related but I f
-LAN] WLAN Override- Again a WiSM question
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
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 p
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 r
Yes. That's one of the bugs we're currently dealing with on 4404
controllers running 4.1.185.0. To my knowledge, Cisco hasn't assigned a
bug ID to it yet.
Todd Lane
ITS Telecommunications/Networking
University of North Carolina at Chapel Hill
Lee H Badman wrote:
One more question on WiSMs, to
