So Cisco LWAPP people,
Currently we're on 4.1.185.0. It's a 4402 controller, with 1131AG access
points.
Anyone made the leap to one of the 4.2, 5.0 , or 5.1 trains without
seriously regretting it?
We've had some random disconnects with clients. It's pretty common,
happening to most all users.
Mike,
We run 4.2.130. I was told by Cisco Engineer to downgrade to this version
as we had a nightmare with 5.x. However we still get Clients disconnected
at random intervals(Radio seems to reset somehow forcing clients to roam
to nearby LAP's). Cisco has no clue and i wonder why not many
I have also heard to downgrade to the 4.x code from the 5.x code but I have had
great success with my 5.x code. I am using 1121, 1131, and 1230s. I have
almost 100 APs and have on average 400 people connected at one time.
Justin Dover
Harpeth Hall School
615-346-0082
The EDUCAUSE Wireless
Hi Mike,
We run 4.2.130 on our WISM blades.
Our 4404 stand alone controllers are running 4.2.60 where we have at
least one WLAN using WPA2-PSK AES and TKIP without any issues.
Other WLANs are Open and no issues are experienced there.
Our APs are 1010s (very few), 1242s and 1131s.
Daniel Foerst
Hi Mike,
We were running the 4.1.185.0 code for a while with no real issues. Once
we upgraded to 4.2.130 (which was supposed to be the stable version of
the code) we started having spontaneous controller reboots. The TAC
diagnosed the issue as a memory leak, but we were never able to find the
Manoj,
I'm so glad you mentioned it. I thought we were the only ones. We run
4.2.130 also and have the same issue. We've been working with TAC for
the past two months and they still can't figure out what causes that
behavior.
Louisiana State University
Hector Rios
From: The
I have seen the radios reset. You can configure the controller to have APs to
individually syslog to a desktop syslog tool like the Kiwi Syslog Daemon to
verify this. Its a good way to see if anything odd is happening.
We run 4.2.112. We also disabled Traffic Stream Metrics where we have a
This information may now be outdated, but I ran into a similar problem
when working at the University of Iowa with version 4.1.185.0. We had
many AP reboots every day. Periodically, the AP reboots would continue
en masse for several hours. I disabled RRM, and the reboots stopped.
There
Contrary to this thread, we are running 4.2.112 on 14 WiSM controllers
without any noticeable difficulty - no memory leaks and no complaints of
random disconnects. We have these divided into two roaming domains, one for
general campus use and one for ResNet (they pay for their stuff out of a
We've been running a Engineering Special version of 4.2.130.0 since
August and it's been stable so far. We had several problems with
4.2.185.0 including controller reboots and lockups. The general release
version of 4.2.130.0 fixed all the major problems we were seeing except
two and the
Bear in mind the controllers are designed to remove associations (and save
resources) if there hasn't been any traffic seen from the clients. The User
Idle Timeout is responsible for this behavior.
You can increase this value from its default of 300s to a higher value. This
will keep the
11 matches
Mail list logo
