WCS question

Guys currently we have one ACS server for all wirless authentication.....we are putting another one for redundancy....i will be config replication from primary to secondary.....while i was suring arojund in WCS i have noticed that when adding another authentocation server it asked abt shared secret.....now where i can find that in ACS....or shd i copy and past the exsisting one from primary ACS.......guys i am stuck plz help me

Thanks for your prompt reply.....now i will explain bit more as reading the doco didnt solve my problem.....the WCS server which i connect through web has all access point listed all over country's offices...so it has a list.....they all do authentication from ACS primary which authntoicate them with windows AD.....now i went to primary ACS server all the Access point are listed but the server address is not there from which i can add things for all Acesss points so i guess it a managment server.....now i will be putting redundant ACS i have already installed the server and as recommended by cisco i have already ping all the access point across and it works now when i will do replication i will get all the info from primary ACS server......i am thinking plz correct me if i am wrong i will add secondry ACS in authentication list servers in WCS and will apply to all of the wirless access points am i right or wrong???? there when i was making a second templete it ask abt password and shared secret what shd i put in.....swhd i copy from primary ACS which is already present in WCS and paste it in secondaty as well???? i am confuse abt this plesase help me out thanks

Similar Messages

Reporting in WCS Question

Is there any way to generate report in WCS for clients associated / authenticated by AP's. I was able to get Client count by controller, What I need is client count by Access Point.
If anyone has any suggestions please contribute. WCS Version 7.0.172.0
Thanks
Anil Jacob

Have you used a beta version or earlier pre release version?
You have an issue that is related some how to entries that were in beta codes of WCS.
A few things to try, first make a backup of your db.
Then, go on the CLI, bin folder of WCS and after run:
1.StopWCS
2.dbamin checkschema
3.StartWCS
See if this helps.
I dont want to push you for opening a TAC case and would like to avoid it, but if you are concerned about keeping the same db and not loose any data, we need a TAC case to be opened. That will involve that you upload me your database so we can try to fix this manually.
If you dont care about the DB and you are ok to rebuild it then from the CLI
1. StopWCS
2. dbadmin reinitdb
3. StartWCS
Reconfigure your WCS, the issue will be gone.
If you decide that you can not loose the db and the previous steps did not help, open a TAC SR between now and the next couple of hours and ask for lavramov, I can help you out.

WLC/WCS question...

I have inherited some minor admin tasks for one WCS and 4 WLC. The issue is that when onsite techs run reports it shows an AP down say in room 101. The real issue I think is that in room 101 the MAC address listed for that room in the WLC is not that same as the one listed in the WCS, how do these get updated?

Ok. When you say the mac addy is different do you mean the addy of the hardwire ethernet adapter or the radios? They will show as different based on the base address and then the radio base addresses. If non of those match then you have assigned the wrong AP to the maps section of the WCS. Verify the serial number as a quick way to make sure the right AP is in the right physical location. You can get it in the WCS and then compare it to the label on the actual AP in the room.

WebCenter Sites (WCS) Community Application infrastructure questions

Essentially, we are looking to perform the most basic, bare-bones installation of WCS Community. After reading through the Community installation guide, I have gathered that the following infrastructure will be necessary, and I am hoping you can either confirm or correct me if I am wrong. We will be deploying on WebLogic. Figure 3 on page 11 of the Community install guide diagrams the most basic infrastructure as I understand it to be, which is:
1. Two separate physical servers, one for the Production Stack, and one for the Management Stack.
2. Deployment of a Production Delivery instance of WCS on the Production Stack (the Co-Resident Satellite Server that comes out-of-the-box with WCS install is not enough).
3. Deployment of a Management instance of Community on the Management Stack (but on a separate WebLogic managed server instance than the WCS Management deployment).
4. Deployment of a Production instance of Community on the Production Stack (but on a separate WebLogic managed server instance than the WCS Delivery deployment).
I understand that all 4 deployments need to happen on separate WebLogic application (managed) server instances. But to dig a little deeper, I guess my main question is, do the Production and Management Stacks need to be on separate virtual machines (we are using VMs to house WebLogic), or can we have 4 WebLogic managed servers on the same VM and house all 4 deployments on the same WebLogic domain?
Thanks, and your advice will be greatly appreciated,
Somen

Hi Somen -
Sorry for the delay in responding.
There's no need to install WebLogic on separate domains, just be careful that they don't collide. If you get creative, you'll also see that you can actually configure CoS on far fewer WL instances than those called out in the spec. Support issues may ensue, however. But for dev purposes, no need to torture yourself with 4 app servers unless you want to.
Tony

Upgrade WCS 5.1.64 to 6.0.196 Questions

Hi,
Im currently testing the WCS upgrade from 5.1.64 to 6.0.196 and I have a couple of questions that I cant find the answers to.
1. Will I require a new license to move from 5 to 6 or even to 7?
2. Will I need to reinstall the license files I have for the 150+ AP's I have or will all licenses be handled as part of the automated upgrade process?
Cheers
Dylan

Hi,
The current licenses will work on the upgraded version.
Simply follow the upgrade procedure and the licneses will be ok on the new version.
HTH,
Tiago
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.

WCS/Redhat Upgrade Question

Hello all,
I recently migrated from the WLSE appliance to WCS Version 4.1.83.0 as well as Redhat Linux 4.0 (via the 2 CD's that were shipped). I would like to upgrade my WCS to the latest version (7.0), with the following upgrade path in mind:
4.1.83.0
to
4.2.62.0
to
5.2.110.0
to
7.0.164.0
My question is do I need to upgrade my Redhat to 5.0 Enterprise version as well in order to support this upgrade? My understanding is that the WLSE appliance is no longer an appliance and is now a full fledge WCS SERVER, in which case I do need to upgrade Redhat. If so, is Redhat 5.0 free to upgrade?
Thanks for the help as always.
Bobby Grewal

Hi Bobby:
Yes, in order to run WCS versions beyond 4.2, you'll need a Red Hat upgrade on a converted WLSE. Because the conversion process brought Red Hat provided by Cisco, the converted WLSE is indeed an appliance (it's just not called that) and Cisco does indeed provide the Red Hat upgrade. You can open a service request with TAC and they'll post the ISO image of the Red Hat upgrade CD for you, or give me your Cisco.com ID and I'll post it for you without an SR.
As for your proposed upgrade path, if this was *my* WCS installation to address, I'd go:
4.1.83.0 to 4.2.128.0 then run Data Cleanup
4.2.128.0 to 6.0.181.0
6.0.181.0 to 7.0.164.0
Long and short, avoiding some bugs and letting 4.2 executables clean a 4.2 database before exiting the train, then bypassing 5.* altogether.
Sincerely,
Rollin Kibbe
Network Management Systems Team

WCS and Controller upgrade questions

Hi,
with the WCS should I install both the EXE file and the BIN fil or just the BIN file?
Also, for upgrading the Controllers where can I find the ER file. I have downloaded the 4.2.209.0 image but, can't find the 4.2.205.0 ER.aes. Does anyone know where this is?
where on the controller can I tell if I already have the ER file?
Thanks, Pat.

Hi Patrick,
The link which i posted is for 4404.. for 4402 here is the link..
http://www.cisco.com/cisco/software/release.html?mdfid=279911193&flowid=7586&softwareid=280926587&release=4.2.112.0%20BOOT&rellifecycle=&relind=AVAILABLE&reltype=all
The latest ER that we hav for 4402 is 4.2.112..
Q1>> To get the software image I goto wireless, Wireless LAN Controllers, standalone Controllers, Cisco 4400 Series Wireless LAN Controllers, 4402, Software on Chassis hten Wireless LAN Cotroller software, but don't see the ER file.
ANS - Yes you are right.. the above is the procedure to download the image.. "ER is nothing but the BOOT IMAGE, if you click on BOOT then the image will pop up as ER, the non BOOT will be in .aes format or something..
lemme know if this answered your question..
Regards
Surendra
====
Please dont forget to rate the posts which answered your question and mark it as answered or was helpfull

Questions about database access in WCS 7.x version

Hello,
In WCS version 7.x, events from controllers are stored in database. The limits for these events are 7 days and 40000 events. Does anyone know where we could change these limits?
In the other hand, we can´t access to database because we don´t know user and password to access database. Can anyone pass me default credentials for database?
What is the procedure to change database password in WCS version 7.x?
Thnaks in advance.

Don't know about username and password for the database, but this might help:
http://www.cisco.com/en/US/products/ps6305/products_qanda_item09186a00807a60f0.shtml
Q. How many alarms are kept in the WCS when are they cleared, and what is the average size of each alarm?
A. The WCS keeps the last 40,000 events in the system and clears them up after seven days. An event or alarm can have 1000 bytes on average.
A. Under the <WCS_INSTAL_DIR>/webnms/conf folder, there is a file called NmsProcessesBE.conf. Within this file, the user needs to modify the parameter CLEAN_EVENT_INTERVAL (default value is seven days) and the parameter EVENT_WINDOW_SIZE (default value is 40,000). The server needs to be stopped and restarted after the user makes the modifications.

WLC Audits on WCS - Configuration names question

Hi Everyone,
I've been clearing up the config differences between my WCS and the WLCs and for the most part I've identified what each line in the audit report refers to. However the following has me stumped:
Configuration Name Audit Status Attribute Value in WCS Value in Controller
150.3.40.240/1 Mismatch interval 1 10
150.3.40.240/4 Mismatch interval 1 10
150.3.40.240/5 Mismatch interval 1 10
150.3.40.240/6 Mismatch interval 1 10
150.3.40.240/7 Mismatch interval 1 10
150.3.40.240/8 Mismatch interval 1 10
150.3.40.240/9 Mismatch interval 1 10
150.3.40.240/10 Mismatch interval 1 10
150.3.40.240/11 Mismatch interval 1 10
150.3.40.240/12 Mismatch interval 1 10
150.3.40.240/HR Not Present In WCS - - -
150.3.40.240/OM Not Present In WCS - - -
150.3.40.240/PK Not Present In WCS - - -
150.3.40.240/EG Not Present In WCS - - -
150.3.40.240/KZ Not Present In WCS - - -
150.3.40.240/BH Not Present In WCS - - -
150.3.40.240/VN Not Present In WCS - - -
150.3.40.240/EC Not Present In WCS - - -
150.3.40.240/KW Not Present In WCS - - -
150.3.40.240/PY Not Present In WCS - - -
150.3.40.240/PR Not Present In WCS - - -
150.3.40.240/CR Not Present In WCS - - -
150.3.40.240/DO Not Present In WCS - - -
It would be really easy to just do a "restore values from controller" to reslove the differences but I'd really like to find these within the configuration pages in order to increase my understanding of the CUWN.
Can anyone tell me what these entries are?
Many Thanks
Scott

Hi Sam,
Is that relevant? I was really looking for the location of these configuration options/parameters within either WCS or the WLCs.
thanks
Scott

Simple Question about 'Monitor Clients' on WCS

Hello
When I use WCS and go the 'Clients' tab on the Home page and then click 'Associated Clients' it shows me a whole list of usernames/MAC adresses/ip addresses/ etc.
One of these column titles is 'Protocol'.
On some of my entries there is an AP with a MAC of 00:00:00:00:00:00 (which I know is a cosmetic bug that is not resolved by Cisco) but its 'Protocol' state is show as 'Mobile' rather than 802.11b or 802.11g.
Does anyone know why the 'Protocol' is classed as Mobile? What does it mean, if anything?
thanks
Bryn

Hi I read your post. I see the "mobile" status of clients on my network when they are being forwarded from another wireless controller via a mobility group. I use this feature for our guest network. Do you have any of your WLC's in the same mobility group or any kind of guest network?

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

Question on migrating production WLCs to a new WCS

I'm working for a client that has probably 8 or 9 sites, each with a
4402 WLC. They're now talking about implementing a WCS. Is there a way
to add these production WLCs easily, or do we need to wipe their
configurations and add them to the WCS server as if they were new?
Thanks!

You shouldnt have a problem but some things you want to keep in mind:
1) Make sure the WCS license is enough to cover all the access points for all 8 - 9 sites
2) Make sure the WLC can route to the the WCS server
You will not need to clear the configs of the WLCs. When you bring up WCS and add the controllers you can sync the controllers to WCS where WCS will learn the config of the controller...

WCS vs Controller License Question - 5500 series.

In the WCS License Center, there are two sets of license options: WCS and Controller. Am I to understand correctly that:
- WCS License count is how many APs can be monitored by WCS?
- Controller License count is how many APs can be connected to a WLC?
Thanks!
-Robert

Think of each controller license as independent license. Although you have 2 AP licenses at 25 each you can aggregate 50 access points to the controllers (25 each). This would of course negate full redundancy.
But you can steer access points incase of failure in the above example.
Suppose you have 30 access points ( 15ap location 1 and 15ap location 2). You are over 5 access points over for full redundancy.
Suppose location 1 is a higher priority then location 2 and you want to make sure you have all the aps up at location 1. You can add a priority to the access points at location 1 so they connect to the controller before aps at location 2.
Just an fyi

WLSE - WCS upgrade license question

Hello,
We need to upgrade our WLSE to WCS but our sales people bought the wrong license (WCS-Standard-K9) Is it possible to upgrade the WLSE to WCS with this license and just get the conversion CDs needed from you ?

Hi Gudmundur,
This will not work, plus you have probably paid more that is necessary as the Upgrade Licenses are le$$ to encourage this migration. You should,as noted by Dennis contact your SE or;
[email protected]
Converting Existing CiscoWorks WLSE to Cisco WCS Licenses
CiscoWorks WLSE (Models 1130-19 or 1133) can be converted into a server that runs Cisco WCS. This allows customers of CiscoWorks WLSE to migrate to the Cisco Unified Wireless Network architecture using their existing CiscoWorks WLSE platform. CiscoWorks WLSE conversion SKUs are price-adjusted to make transitioning from CiscoWorks WLSE to Cisco WCS cost-effective.
Once converted, a CiscoWorks WLSE is no longer a self-contained appliance; it becomes a server that runs Cisco WCS software using RedHat Linux ES v. 4.0. The converted CiscoWorks WLSE operates as a brand new Cisco WCS installation and supports only lightweight access points and wireless LAN controllers that are running Lightweight Access Point Protocol (LWAPP). Stand-Alone (autonomous) access points are not supported by a converted CiscoWorks WLSE.
All WCS-WLSE-UPG-K9 SKUs ship with two special conversion CDs. These CDs will check to make sure that a CiscoWorks WLSE is installed prior to beginning the Cisco WCS conversion process. The conversion software will not install if the CiscoWorks WLSE software check, performed by the conversion software, does not pass.
Note: Please take note of the following special considerations for CiscoWorks WLSE conversions.
CiscoWorks WLSE Express (Model 1030) and CiscoWorks WLSE (Models 1105) are not supported with this SKU. Do not install the CiscoWorks WLSE CDs on to the CiscoWorks WLSE Express (Model 1030) appliance or CiscoWorks WLSE (Model 1105). This conversion is not supported and will not work.
A CiscoWorks WLSE that has been converted to Cisco WCS cannot be reverted back to operate as a CiscoWorks WLSE.
To find the model number of a CiscoWorks WLSE, look at the compliance label on the bottom of the chassis front bezel. Only CiscoWorks WLSE with a compliance label that says 1130-19 or 1133 can be converted to Cisco WCS.
Please see Appendix C for information about receiving support for existing SMARTnetÂ® (hardware support) contracts for CiscoWorks WLSE.
Customers that are migrating their existing CiscoWorks WLSE to operate as a Cisco WCS server should select from the WCS-WLSE-UPG-K9 SKU family and then select one of the sub-SKU options based on the following:
Base or Location
Access point quantity. (The CiscoWorks WLSE conversion CD's do not automatically provide support for a set number of access points or location services. The number of lightweight access points supported as well as Cisco WCS location is selected by the customer based on the WCS-WLSE-UPG-K9 family sub-SKU. Customers can select the sub-SKU that contains the access point count and Cisco WCS option that they wish to support.)
A Cisco Ordering Tool sample for WCS-WLSE-UPG-K9 is displayed in Link.
PAK Certificate, Instructions and CD
Customers that purchase the SKU family WCS-WLSE-UPG-K9 will automatically receive, by U.S. mail, two special CDs containing the CiscoWorks WLSE to Cisco WCS conversion software, as well as the PAK certificate, instructions on how to register the PAK and links to Cisco WCS manuals and release notes. CiscoWorks WLSE conversion software cannot be downloaded.
http://www.cisco.com/en/US/products/ps6305/products_data_sheet0900aecd804b4646.html
Hope this helps!
Hi Gudmundur,
This will not work, plus you have probably paid more that is necessary as the Upgrade Licenses are le$$ to encourage this migration. You should,as noted by Dennis contact your SE or;
[email protected]
Converting Existing CiscoWorks WLSE to Cisco WCS Licenses
CiscoWorks WLSE (Models 1130-19 or 1133) can be converted into a server that runs Cisco WCS. This allows customers of CiscoWorks WLSE to migrate to the Cisco Unified Wireless Network architecture using their existing CiscoWorks WLSE platform. CiscoWorks WLSE conversion SKUs are price-adjusted to make transitioning from CiscoWorks WLSE to Cisco WCS cost-effective.
Once converted, a CiscoWorks WLSE is no longer a self-contained appliance; it becomes a server that runs Cisco WCS software using RedHat Linux ES v. 4.0. The converted CiscoWorks WLSE operates as a brand new Cisco WCS installation and supports only lightweight access points and wireless LAN controllers that are running Lightweight Access Point Protocol (LWAPP). Stand-Alone (autonomous) access points are not supported by a converted CiscoWorks WLSE.
All WCS-WLSE-UPG-K9 SKUs ship with two special conversion CDs. These CDs will check to make sure that a CiscoWorks WLSE is installed prior to beginning the Cisco WCS conversion process. The conversion software will not install if the CiscoWorks WLSE software check, performed by the conversion software, does not pass.
Note: Please take note of the following special considerations for CiscoWorks WLSE conversions.
CiscoWorks WLSE Express (Model 1030) and CiscoWorks WLSE (Models 1105) are not supported with this SKU. Do not install the CiscoWorks WLSE CDs on to the CiscoWorks WLSE Express (Model 1030) appliance or CiscoWorks WLSE (Model 1105). This conversion is not supported and will not work.
A CiscoWorks WLSE that has been converted to Cisco WCS cannot be reverted back to operate as a CiscoWorks WLSE.
To find the model number of a CiscoWorks WLSE, look at the compliance label on the bottom of the chassis front bezel. Only CiscoWorks WLSE with a compliance label that says 1130-19 or 1133 can be converted to Cisco WCS.
Please see Appendix C for information about receiving support for existing SMARTnetÂ® (hardware support) contracts for CiscoWorks WLSE.
Customers that are migrating their existing CiscoWorks WLSE to operate as a Cisco WCS server should select from the WCS-WLSE-UPG-K9 SKU family and then select one of the sub-SKU options based on the following:
Base or Location
Access point quantity. (The CiscoWorks WLSE conversion CD's do not automatically provide support for a set number of access points or location services. The number of lightweight access points supported as well as Cisco WCS location is selected by the customer based on the WCS-WLSE-UPG-K9 family sub-SKU. Customers can select the sub-SKU that contains the access point count and Cisco WCS option that they wish to support.)
A Cisco Ordering Tool sample for WCS-WLSE-UPG-K9 is displayed in Link.
PAK Certificate, Instructions and CD
Customers that purchase the SKU family WCS-WLSE-UPG-K9 will automatically receive, by U.S. mail, two special CDs containing the CiscoWorks WLSE to Cisco WCS conversion software, as well as the PAK certificate, instructions on how to register the PAK and links to Cisco WCS manuals and release notes. CiscoWorks WLSE conversion software cannot be downloaded.
http://www.cisco.com/en/US/products/ps6305/products_data_sheet0900aecd804b4646.html
Hope this helps!

WLC/WCS upgrade questions

Hi, we have 2 4402 controllers running with system software 4.2.130.0. The WCS is running 4.2.110.0.
I would like to upgrade but are a bit confused about all the different versions.
Is it recomended that I upgrade directly to the latest 6.0.182(WCS)/132(WLC) ?
And how do I upgrade ? the controllers first and then the WCS ?
Regards
Johann Folkestad

If you are considering upgrading to 6.0, here is the section of the release notes for the WCS that concerns that:
http://www.cisco.com/en/US/docs/wireless/wcs/release/notes/WCS_RN6_0.html#wp44448
As for the WLC, here is that section:
http://www.cisco.com/en/US/partner/docs/wireless/controller/release/notes/crn601820.html#wp472449
As already stated, be sure to read the release notes to find which version is best for you.
List of Release Notes for WCS Versions:
http://www.cisco.com/en/US/products/ps6305/prod_release_notes_list.html
List of Release Notes for WLC Versions:
http://www.cisco.com/en/US/products/ps6366/prod_release_notes_list.html

WCS question

Similar Messages

Maybe you are looking for