Here are my experiences for you Lee. Another University tried to upgrade to Version 4.1 WCS got a java error when starting and wouldn't continue loading the service. (We use a WLSE upgraded device, they don't.)
This didn't stop us from trying so we upgraded our WISM and Controllers. Problems and notes - It took up to 30 minutes to convert the database from 4.0 to 4.1. - We didn't read the documentation to find the upgrade path for the WLCs - We needed a tftp server that supported greater than 32MB files. Again that was written in the documentation that we forot to read, oops. - One WLC out of four was not able to complete the AP upgrades, it just kept redoing the same Aps. We had to keep trying to move all the Aps from that controller to another controller. - After everything, 10APs refused to come up. Console time. They all had corrupted boot images. We just booted up the emergency image located on the flash and they all came good. But having to locate the Aps, ladders, console, etc, the normal pain. The reporting looks great, TACACS and everything looks very sexy. But some odd behaviour, the client count isn't decreasing, it just keeps adding. An new AP that took over an old AP Ips address was not able to be managed by the WCS, only by the WLCs. We are only about 38 hrs into running the new code. I think we should have been waiting for the update as someone mentioned. One question I have is, on a working AP, can you view and change the rommon set parameters remotely? Anthony QUT ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
