FYI: Beware of running v4.2 in a system where other WLCs are still running on older versions of code. If you do, then the mobility paths will quit working.
In my tests running either 4.2.61 or 4.2.99 one one WLC in a lab setup with a second WLC running 4.1.185.0 results in mobility path failures. Note that checking the mobility status through the WLC Web interface will *not* show any problems. Running the mobility member ping test through the Web interface doesn't show the failure either, since the test only uses an IP ping instead of the "eping" or "mping" that would show the real problem. However, logging into the WLC and running the command "show mobility summary" will show the status of "Control and Data Path Down" per mobility member. Cisco informs us that all WLCs in a system must run the same code version at all times or mobility paths will fail. -Charles Charles E. Spurgeon / UTnet UT Austin ITS / Networking [EMAIL PROTECTED] / 512.475.9265 On Wed, Feb 13, 2008 at 04:39:43PM -0600, John Watters wrote: > We have two CAT6506s, one with a single WiSM (our backup platform) and the > second with three WiSMs. > > > The first CAT6506/single Wism has no users and is only used to test new code > levels and act as a > set of spares for the other box (soon to be several more). The WiSM on this > box is running > 4.0.206.0. > > The second CAT6505/three WiSMs supports what little wireless we have moved to > the lightweight stuff > -- 319 LWAPPs with 300-400 users so far. The WiSMs on this box are running > 4.0.206.0 & 4.0.219.0. > > I will move them all up to 4.1 (maybe 4.2) at the end of the semester so I > have some breathing room > to fight problems. > > The first/almost idle CAT6506 shows a CPU utilization of 0-1% all the time. > The second CAT6506 > shows an average utilization of 0-1% with peaks of 4%. Not much difference > between the two. > > -jcw > ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
