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
root cause. I eventually ended up downgrading the code back to 4.1.185.0
and haven't had any more controller reboots.
My advice if you do upgrade is definitely to get backups of all your
controller configs because the 4.1 code is stored in binary format and
the 4.2 is in XML. If you do have to rollback you lose the config.
We also have seen this "randomly disconnects" issue with users and also
issues with users not seeing our ssid at all. It's hard to diagnose
because once you get out there, it seems to work fine.
Not to hijack this post, but I would be interested in hearing about
anyone else's strange LWAPP issues.
20 WiSMs
1230, 1242
Open Network
~ Kristina
Mike King wrote:
So Cisco LWAPP people,
Currently we're on 4.1.185.0 <http://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. We're running WPA-PSK, so it's not an
802.1x issue. Before we involve TAC, we figured we should upgrade to
a new code train.
Mike
********** Participation and subscription information for this
EDUCAUSE Constituent Group discussion list can be found at
http://www.educause.edu/groups/.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kristina Gasca, Wireless Network Engineer
North Carolina State University
Communication Technologies
919.515.0107 (office)
919.515.1641 (fax)
[EMAIL PROTECTED]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
**********
Participation and subscription information for this EDUCAUSE Constituent Group
discussion list can be found at http://www.educause.edu/groups/.
