Lee, We are in the same process as you. We have 3 WiSM blades and WCS, + ~500 1131's, soon to be almost 800. I definitely see some of the same issues, and I think that a lot of the information that everyone is looking for in Airespace is available, it's just that there is either no way to get it out of the controller or the controller does not offer it.
Maybe I can offer some help: 2. I think that Cisco is assuming that you are ONLY using WCS to configure the controllers, meaning that you are deploying the same config changes across your controllers at once all of the time, so the controllers will never have different configs, yeah, maybe in a perfect world :) 3. There are wild card searches, when searching by mac use a % sign, i.e. 00:18:18:% When search by name just put the part of the name that you are searching for. 5, 9 & 10. I definitely agree on these. We need to be able to see what the AP's are seeing. Also, what ver or WCS are you running? We are running 4.0.66.0. In 3.0.x.x I believe the wild card searches were using a "*". Another thing that I would like to see are association graphs by SSID. --Joe -----Original Message----- From: Lee Badman [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 19, 2006 7:53 PM To: [email protected] Subject: [WIRELESS-LAN] Cisco LWAPP Now that we are into a Cisco LWAPP conversion/rollout, wondering if anyone else has found these issues to be obstacles to deployment/support, or if in the grand scheme you've found them to be non-issues: 1. Can't schedule configuration jobs- is no scheduling provision from WCS 2. No master view from WCS of all controllers configurations to compare for uniformity of config 3. No wild card searches for clients or APs when searching in WCS 4. AP radios come up in transmit, before proper vlan is assigned to them- meaning that clients might associate to a non-functional cell (meaning there might be confusion and help-desk calls) 5. No view of the Ethernet port on the AP from the WCS or controller, which means you can't tell if it negotiated speed or duplex correctly 6. ACLs in the WCS have to be built line by line, no copy and edit or text file input 7. MAC address searches have to be colon delimited 8. Mispellings in the WCS GUI, usually on error popups 9. Difficult debugging, like from an AP you have no knowledge of what controller it associated to or tried to associate to 10. No view from the AP or WCS on what switch and port the AP is on (CDP type view) 11. Inconsistant AP association behavior, certificate issues on converted APs (mostly 1200s) not registeriing with controllers and having to be manually added 12. Converted APs drop their pre-conversion system names and go to mac address for name 13. No ability for AP groups VLAN templates for multiple controllers 14. Cannot use static WEP and AirFortress clients together on an SSID/VLAN as you can in the autonomous world There are more... and I'm not bashing the product, believe it or not. We bought it and will squeeze great value out of it. But I am wondering if others see these issues as problems, or if I'm expecting too much as I move from the autonomous world to this new LWAPP stuff. Even better- are there any here that I am wrong about? Please do not take this as an invitation to call me about WLAN management products! Regards- Lee Lee H. Badman Network Engineer CWNA, CWSP Information Technology and Services Syracuse University 315 443-3003 ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
