Adding Controller to WCS

I currently have a 4400 controller and I am looking at implementing WCS. Will adding the controller to WCS change the controller settings? I don't want to take down my production network.

Hi Mike,
Simply adding the WLC to WCS will not change any settings on the WLC itself.
Settings on the WLC can be changed afterwards through WCS with specific operations/configuration templates.
Regards,
Fede
If this helps you and/or answers your question please mark the question as "answered" and/or rate it, so other users can easily find it.

Similar Messages

Adding more than one controller to WCS at the same time

We are about to start a 585 location deployment with a Wireless LAN Controller (WLC) at each facility. Currently, I can only see a way to add controllers to the Wireless Control System (WCS) one at a time through the GUI. Does anyone know a proven method of adding multiple WLC's to WCS at the same time?

Presently WCS does not have any feature through which mulitple controllers can be added to the WCS. Controllers can be added one at a time only.

Autocomplete does not work after adding controller to LOV

Hi experts ,
Autocomplete does not work after adding controller to LOV Region, i have checked the fnd_compatialbe mode it is fine.validation proprty is also false, stilll it is not working.
can anyone help me its very urgent
regards
vamsi

Hi Tapash,
This resolved the problem. Many thanks for your help with this it has been driving me mad for the last few days.
I could not understand why the standard Apps LOV regions had controller's attached to them and the autocomplete would function but with my pages it would not.
I actually raised a TAR about this and got nothing back so have updated it with the resolution.
Thanks again.
Regards,
David

Adding another floor WCS & 4404 WLAN Controller

Dear Support,
Just after some advise or direction as preparing to add another floor to our hq directly above or existing floor.
We already have a WLAN (100 AP) and WCS running, with 15 APs on the current floor. Due to expansion we have now taken rent out on the floor above from the owners.
As I never set up the existing WCS and WLAN controller, I just after some advice or configuring it for another 15 APs for the new floor. These are all 1000 LWAPPs units.
Questions I need to answer is how difficult to add another floor map to WCS and if we need the APs in the same vlan to deal with the seapage / radiation between the floors.
Thanks in advance.
Regards, Adrian.

Hi Rob,
Many thanks for the link, this is exactly what I'm after for the floor plans.
Just now need to find out if I should have both floors on the same wireless VLAN or to utilise another port on the 4404 ... think it is only using one of the 4 at the moment.
I know their is a mention somewhere in the documentation that if you go above 25 aps (and we'll have 30 once upgrade is complete) that you need to use more than 1 port on the WLAN controller.
Thanks again, regards, Adrian.

3504 Wireless Lan Controller and WCS

Hi Pals,
I need to know if any version of Cisco WCS supports 3504 Wireless lan controllers. The latest 3.2.4 doesn't seem to have 3504 listed in its release notes.
Any help would be highly appreciated.
Cheers,
Rajesh

Hi SmalKeric,
Thnx for the reply. But was wondering why ? Would appreciate you can point me to some links which describe this.
Cheers,
Rajesh

Adding a second WCS-4402-12

Sorry if this is already awnsered elsewhere but i could not find an awnser to the following question:
Is it possible to add another WCS-4402-12 to an existing WLAN (Already using 1 WCS-4402-12) to support more AP's?

Hi Philemon,
I think that you are referring to the WLC 4402-12 :) It is very possible to add another WLC to your existing infrastructure to support additional AP's. Try to plan for the future so if you need 10 new AP's now but may need 10 more next year order the WLC 4402-25 instead of a 12 now and a 12 in a year from now. You will save a bit of $$ this way.
Hope this helps!
Rob

Can't add Controller over VPN in WCS v6.0.132.0

Hi
I use WCS v6.0.132.0 to manage my 4402 and 2106 controller both running version 6.0.182.0
When I try to add another 2106 over DM-VPN it fails with the following errors:
”No response from device, check SNMP communities, version or network for issues”
If I move the new 2106 controller to LAN with same config there is no problem.
I found this note in the in “Cisco Wireless Control System Configuration Guide, Release 6.0”
“Note If you are adding a controller into WCS across a GRE link using IPsec or a lower MTU link with multiple fragments, you may need to adjust the MaxVar Binds PerPDU. If it is set too high, the controller may fail to be added into WCS. To adjust the MaxVarBindsPerPDU setting, do the following:
1) Stop WCS.
2) Go to the location of the Open SnmpParameters.properties file on the server that is running WCS.
3) Edit MaxVarBindsPerPDU to 50 or lower.
4) Restart WCS.”
On my system I have the “SnmpParameters.properties” file is located //WCS6.0.132.0\webnms\classes\com\cisco\server\resources
But I don’t have “MaxVarBindsPerPDU” settings in the file.
Beside some # explanations text, the only settings I have in the “SnmpParameters.properties” file is:
DebugEnabled                         false
SerializeRequests                    true
MaxRepetitions                       10
MaxRetryTimeout                      60
WlanTimeoutMsecsPerAP                 50
I have tried to add “MaxVarBindsPerPDU” settings, but it have no effect.
Anyone have an idea what to do?
TIA

Thank you so much!
Step 1 solved the issue.
I changed “Maximum VarBinds per Get PDU” from 30 to 20 and “Maximum VarBinds per Set PDU” from 50 to 20.
Thanks

WCS Error when adding WLC

We have successfully been managing all our WLC's via WCS. Last week one of the 6500 WiSM Controllers stopped responding to config refreshes from the WCS. When re-freshing the WCS config from the controller got the error message - failed (see logs). Removed controller from WCS and re-added - now get different error - see attachment.
WCS version is 4.2.97
WLC version is 4.2.112
Doco says they are compatible.
WCS is successfully managing other WLC's on the same code.
Can any one help?

What I would do next is to go to the WLC that is having the issue. Delete all the community strings and recreate it. Make sure that you allow the network that the WLC is on. Also, you should change your RW from private..... it's like the first and default snmp RW string that tools use. Along with public as the RO.

Is WCS a must with 4400 LAN controller

Hi,
We're looking at the 4400 series wireless LAN controller with Lite APs. It's not clear if the WCS is required or if the 4400 has management capabilities in it and the WCS may not be required. So, can we run a 4400 series without a WCS and still maintain management of our wireless network. If so, what capabilities would we be missing...if any?
...thanks in advance.....J

Hi Jamie,
The WCS is not required to run any WLC or WiSM. It is a very nice management tool but it is not a must. We have been running LWAPP for a few years now without the WCS and we are just now getting ready to deploy it;
Deploying Cisco 440X Series Wireless LAN Controllers
http://www.cisco.com/en/US/docs/wireless/technology/controller/deployment/guide/dep.html
Managing the Controller with WCS
http://www.cisco.com/en/US/prod/collateral/wireless/ps5755/ps6301/ps6305/product_data_sheet0900aecd802570d0.html
Cisco Wireless Control System Configuration Guide
http://www.cisco.com/en/US/products/ps6305/products_configuration_guide_book09186a00806b57ec.html
Hope this helps!
Rob

Can't add AP to new controller

Morning,
I just added a new controller to our wireless environment to support AP's in our remote offices. These offices will host public hotspots so we wanted to use a 2125 controller so we could apply different security policies around it. Our corporate office uses two WiSM modules for wireless connectivity.
I setup the controller, trunk the vlan we use for our controllers and the new public hotspot vlan to it as well. Added the controller into WCS and applied a new controller template to it so I could change a few settings. After that I did an audit on the controller just to make sure everything matched up before adding an AP to test connectivity.
For some reason, I can not get an AP to join at all. The AP will join the master controller, then we I change the AP settings to use to the 2125 controller (in WCS), restart, it still will not join. I turned on debug on the 2125 and it doesn't even look like the AP attempts to join because I don't see anything come across the LWAPP debug.
If I assign the new 2125 as the primary controller to the AP and a controller on one of my WiSM modules as a secondary controller, the AP will always join the secondary controller, no matter which one I say to use. If I set the AP to use the 2125 as all three controllers, it will default back to the controller in master controller mode....
What is going on????

Make sure that your AP regulatory domain matches the country selected on the WLC.
AFAIK if multiple countries are selected on the WLC then it will work but the AP is limited only to the common channel of the selected countries. I did not try that in practice though.
Btw, can you try to connect your AP to the wlc via a wire and male sure it joins (in either briedge or local mode) before trying to connect it as a MAP?
Regards,
Amjad
Sent from Cisco Technical Support iPad App

Failed to add device to WCS Reason: Object not found in device

Hi i am adding wlc (ver 7.0.116.0) to WCS (ver 7.0.164.0) and getting bellow error message.
Failed to add device to WCS Reason: Object not found in device
This controller was successfully added to the WCS before upgrading WLC ios to 7.0.116. Now i am unable to communicate with the controller thru WCS. The controller itself work ok and serve all WAPs with no issue.
Any ideas would be appreciated.
Regards.

You will need to upgrade WCS to Version 7.0.172.0. WCS version 7.0.64.0 does not support or manage WLC version 7.0.116.0. Hope this helps.

WCS -- WLC "Device un reachable"

Added WLC to WCS. Rebooted WLC from WLC and WCS cant reach WLC eventhough I can ping and access WLC. Verified SNMP and looks fine. Happened on two WLC's. I am waiting for almost 2 hours for WCS to talk WLC...

Please update the following informations
'show run-config' from the WLC and 'show run' from Switch connected to WLC while specifying the ports of Switch that connect to WLC in 2 separate text files.
=> Show msglog after the problem happens.
=> Check if there is crashes file available (WLC GUI ->Management ->Controller Crash)
=> 'show port summary' from the WLC when such problem happens.
=> 'show ip int br' from Switch connected to the WLC when such problem happens.
=> 'show arp switch' form WLC when such problem happens.
=> 'show arp' from Switch when such problem happens
The following URL will help you:
http://www.cisco.com/warp/public/707/cisco-amb-20070412-wlc.shtml

WLC 5508 & Aironet 3502 questions CleanAir, AP modes, WCS

We currently have several 1230, 1240, & 1250 series LWAPPs in our environment being controlled by a 5508WLC. We are going to upgrade all of the access points in our environment to the 3502 access points. We are having a site survey performed to determine the best placement of the access points and where additional access points are needed. Is there anything else required to successfully run and mainatain CleanAir? Currently all of are access point are in local mode. Will there need to be a few dedicated monitor access points? Is there a certian ratio of monitor APs to local APs that should be followed? We've had to deploy a couple of our 3502 access points because the existing ones failed and I noticed that the WCS would not predict the RF heatmap of the 3502 access point. Is that something that will be addresses in a later version of the WCS software?
TIA

Hi Jason,
Just to add a note to the good tips from the Wireless Jedi master (+5 Nicholas)
The Cisco "best practice" for the WCS is to be at an equal or greater version
release than the WLC. In your case;
WCS Version = 7.0.164.0
Supported Controller Versions
7.0.98.0
6.0.196.0
6.0.188.0
6.0.182.0
6.0.108.0
5.2.193.0
5.2.178.0
5.2.157.0
4.2.209.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
You will see support for the 3500 series was added in this WCS version as well;
Cisco Unified Wireless Network Solution Components
The following components are part of the Cisco UWN Solution and are compatible in this release:
•Operating system (Wireless LAN Controller and Cisco Aironet Lightweight Access Point)
•Cisco Wireless Control System (Cisco WCS)
•Cisco Mobility Services Engine
•Cisco WCS Navigator
•Cisco 2700 Series Location Appliance
•Cisco 2000 Series Wireless LAN Controllers
•Cisco 2100 Series Wireless LAN Controllers
•Cisco 4400 Series Wireless LAN Controllers
•Cisco 5500 Series Wireless LAN Controllers
•Catalyst 3750G Wireless LAN Controller Switches
•Cisco Wireless Services Modules (WiSMs) for Cisco Catalyst 6500 Series Switches
•Cisco WLAN Controller Network Modules for Cisco Integrated Services Routers
•Cisco Aironet 1000, 1040, 1100, 1130, 1140, 1200, 1230, 1240, 1250, 1260, 1310, 1500, 1524, 3500i, and 3500e Series Lightweight Access Points
•Cisco Aironet 801, 1100, 1130, 1200, 1240, 1250, 1141, and 1142 Autonomous Access Points
•Autonomous Access Points for 1801, 1802, 1803, 1811, 1812, 851, 857, 871, 876, 877, and 878 Cisco Integrated Services Routers
http://www.cisco.com/en/US/docs/wireless/wcs/release/notes/WCS_RN7_0.html#wp44347
Cheers!
Rob

Issues with AP's showing up in WCS

Hello,
I have some ap's here that are connected to the controller and I'm connected to those ap's and surfing the web with no problem. However, they will not show up in the WCS. I can search for the ap's mac and ip, nothing. I've also searched for my username and my laptop's mac/ip and still nothing. I can see my username and mac on the controller. I'm running version 4.2.81.0 WCS. I was wondering if anyone else has every ran into this problem and if so what they did. Thanks, any help would be appreciated.

I'm using snmp v2. If an access point goes down that has been associated for a while, then the WCS says that the radio interfaces are down, but it will not say that it has disassociated. I had a testwap and took it offline and it wouldn't say it disassociated, i tried to remove it from the WCS but it wouldn't let me since it was still associated, even though it wasn't. Also, I had some access points go down a few weeks ago and they are back up and working, you can see them from the controller, the WCS still does not see them, it still reports them as being down. As well as adding new access points, they will associate to the controller, but they do not appear in the WCS.
I did an audit on one of the controllers, which had ap's up that they wcs saw as being down. And in the audit, it would see the access point, but would report back that the access point is not present in the WCS. Also if the WCS saw the ap as being up, even though it wasn't. The audit would report back that the ap is not associated with this base. Kind of weird. It's kind of like something happened when I upgraded the version of WCS. Hopefully this gives a little more explanation of what is going on. Any thoughts would be appreciated.
Thanks

WCS Global Telnet/SSH Parameter Change

I have almost 700 Wireless LAN Controllers in my environment, and due to security compliance, I need to update the local administrator account for each one of them. My concern is that when I push a template with a new admin password, WCS will lose Telnet/SSH access to all 700 controllers, because the Telnet/SSH Parameters for each controller are currently set as the local administrator.
Is it possible to update the Telnet/SSH parameters for every WLC? I know it is possible to update them one at a time through Configure > Controller and updating it via the Properties tab, but there doesn't seem to be a way to push a template to WCS itself which would update the telnet/ssh access globally.
The closest thing I can think of is re-adding every single controller via CSV file and changing the Telnet/SSH Parameters that way, but I would need to remove every controller from WCS first, and that's not really an acceptable solution.

I don't know is it right answer for u or not:)
1. Choose Configure > Controller Template Launch Pad.
2. Click Local Management Users or choose Management > Local Management Users from the left sidebar menu.
Here create a new template with new username and password (with RW or RO) and apply to all controllers and if you want then delete old user from wlc.
Regards
Dont forget to rate helpful posts

Adding Controller to WCS

Similar Messages

Maybe you are looking for