WCS 7.0.172.0 is stopped.

I rebooted the WCS server yesterday and now it is not working anymore.
Here is WCS Status :
Health Monitor is running with an error.
WCS is stopped.
Database server is running
Apache server is running
Logs from hm_launchout.txt
Starting Health Monitor as a primary
Checking for Port 8082 availability... OK
Key entry exists; Update Apache config from Keystore
Configuring Apache server for key
Starting Health Montior Web Server...
Health Monitor Web Server Started.
Starting Health Monitor Server...
Health Monitor Server Started.
Starting WCS Server
Could not create the Java virtual machine.
Unrecognized VM option ''
Failed to start WCS server.  Check launchout.txt for details.
Log files are located under webnms\logs in the WCS install directory.
launchout.txt - it is empty
How can I proceed Now.
Regards

Here are collections of the Cisco WCS fails to start up.
Case 1: Apache server is not running.
Case 2: If the WCS were installed as a service, try to rebooted the machine.
Case 3: Check if the scripts are manually run from the bin directory. You must not manually run scripts from the bin directory. You must use the links from the Windows WCS programs menu or the scripts from Linux <Install Dir> (that is, /usr/local/bin/WCS22/StartWCSServer).
Case 4: Make sure the following ports are available to WCS.
*Checking for Port 1299 availability... OK
*Checking for Port 80 availability... OK
*Checking for Port 443 availability... OK
*Checking for Port 8009 availability... OK
*Checking for Port 8456 availability... OK
*Checking for Port 8457 availability... OK
*Checking for Port 8005 availability... OK
*Checking for UDP Port 69 availability... OK
*Checking for Port 21 availability... OK
Case 5: WCS does not start if the database is corrupt. If you reinitialize or restore the database, it fixes the issue. Navigate to the WCS installation directory and issue the dbadmin.bat reinitdb command from the command prompt to reinitialize the database.
case 6: Collect the log files from the <WCS Installation Dir>\webnms\logs. These log files can be used to identify the root cause of the issue.
Case 7: Check if the Windows SNMP trap service is active on the server. Disable the service because it uses Port 162 that is required by WCS. For more information on list of ports used by WCS, refer to the

Similar Messages

  • Import WCS 7.0.164.0 Database into WCS 7.0.172.0

    We are experiencing some issues while upgrading from WCS  7.0.164 to 7.0.172. For some reason, everytime we try to import the 7.0.164 database, the 7.0.172 restore process aborts with:
    Waiting for database to become idle
    To Version 7.0.172.0
    Invoking upgrade_general.sql
    From Version 7.0.164.0
    Updating Schema. This may take a while.
    java.sql.SQLException: [Solid JDBC 04.50.0176] Data source rejected establishment of connection
    Failed to export Hibernate schema
    Hiblog.txt shows the following:
    NFO 2011-07-05 10:55:03,143 [main] (TableMetadata.java:43) - indexes: [$$rrmauditdot11bconfig_primarykey_10795, rrmauditdot11bconfig_eventindex, fk254609e9ebca074c]
    WARN 2011-07-05 10:55:03,175 [main] (JDBCExceptionReporter.java:77) - SQL Error: 25214, SQLState: 08003
    ERROR 2011-07-05 10:55:03,175 [main] (JDBCExceptionReporter.java:78) - [Solid JDBC 04.50.0176] Connection not open
    ERROR 2011-07-05 10:55:03,175 [main] (SchemaUpdate.java:165) - could not complete schema update
    org.hibernate.exception.JDBCConnectionException: could not get table metadata: RrmConfig
    at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:74)
    at com.cisco.server.persistence.hibernate.dialect.SolidDialect$2.convert(Unknown Source)
    at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
    at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:29)
    at org.hibernate.tool.hbm2ddl.DatabaseMetadata.getTableMetadata(DatabaseMetadata.java:105)
    at org.hibernate.cfg.Configuration.generateSchemaUpdateScript(Configuration.java:948)
    at org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:140)
    at com.cisco.server.persistence.util.PersistenceUtil.beginUpdateSchema(Unknown Source)
    at com.cisco.packaging.DBAdmin.beginUpdateSchema(Unknown Source)
    at com.cisco.packaging.MigrateOldDbToNewDb.upgradeDatabase(Unknown Source)
    at com.cisco.packaging.SelectDirAndRestoreDb.restoreDatabase(Unknown Source)
    at com.cisco.packaging.DBAdmin.restoreDB(Unknown Source)
    at com.cisco.packaging.DBAdmin.runMain(Unknown Source)
    at com.cisco.packaging.DBAdmin.main(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.zerog.lax.LAX.launch(DashoA10*..)
    at com.zerog.lax.LAX.main(DashoA10*..)
    Caused by: java.sql.SQLException: [Solid JDBC 04.50.0176] Connection not open
    at solid.jdbc.SolidError.s_Create(Unknown Source)
    at solid.jdbc.SolidConnection.s_AddAndThrowError(Unknown Source)
    at solid.jdbc.SolidConnection.s_Chk(Unknown Source)
    at solid.jdbc.SolidResultSet.s_Chk(Unknown Source)
    at solid.jdbc.SolidResultSet.close(Unknown Source)
    at com.mchange.v2.c3p0.impl.NewProxyResultSet.close(NewProxyResultSet.java:2999)
    at org.hibernate.tool.hbm2ddl.DatabaseMetadata.getTableMetadata(DatabaseMetadata.java:101)
    ... 15 more
    WARN 2011-07-05 10:55:03,175 [main] (NewProxyStatement.java:835) - Exception on close of inner statement.
    java.sql.SQLException: [Solid JDBC 04.50.0176] Connection not open
    at solid.jdbc.SolidError.s_Create(Unknown Source)
    at solid.jdbc.SolidConnection.s_AddAndThrowError(Unknown Source)
    at solid.jdbc.SolidConnection.s_Chk(Unknown Source)
    at solid.jdbc.SolidStatement.s_Chk(Unknown Source)
    at solid.jdbc.SolidStatement.close(Unknown Source)
    at com.mchange.v2.c3p0.impl.NewProxyStatement.close(NewProxyStatement.java:831)
    at org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:171)
    at com.cisco.server.persistence.util.PersistenceUtil.beginUpdateSchema(Unknown Source)
    at com.cisco.packaging.DBAdmin.beginUpdateSchema(Unknown Source)
    at com.cisco.packaging.MigrateOldDbToNewDb.upgradeDatabase(Unknown Source)
    at com.cisco.packaging.SelectDirAndRestoreDb.restoreDatabase(Unknown Source)
    at com.cisco.packaging.DBAdmin.restoreDB(Unknown Source)
    at com.cisco.packaging.DBAdmin.runMain(Unknown Source)
    at com.cisco.packaging.DBAdmin.main(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.zerog.lax.LAX.launch(DashoA10*..)
    at com.zerog.lax.LAX.main(DashoA10*..)
    WARN 2011-07-05 10:55:03,175 [main] (NewPooledConnection.java:425) - [c3p0] A PooledConnection that has already signalled a Connection error is still in use!
    WARN 2011-07-05 10:55:03,175 [main] (NewPooledConnection.java:426) - [c3p0] Another error has occurred [ java.sql.SQLException: [Solid JDBC 04.50.0176] Connection not open ] which will not be reported to listeners!
    java.sql.SQLException: [Solid JDBC 04.50.0176] Connection not open
    at solid.jdbc.SolidError.s_Create(Unknown Source)
    at solid.jdbc.SolidConnection.s_AddAndThrowError(Unknown Source)
    at solid.jdbc.SolidConnection.s_Chk(Unknown Source)
    at solid.jdbc.SolidStatement.s_Chk(Unknown Source)
    at solid.jdbc.SolidStatement.close(Unknown Source)
    at com.mchange.v2.c3p0.impl.NewProxyStatement.close(NewProxyStatement.java:831)
    at org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:171)
    at com.cisco.server.persistence.util.PersistenceUtil.beginUpdateSchema(Unknown Source)
    at com.cisco.packaging.DBAdmin.beginUpdateSchema(Unknown Source)
    at com.cisco.packaging.MigrateOldDbToNewDb.upgradeDatabase(Unknown Source)
    at com.cisco.packaging.SelectDirAndRestoreDb.restoreDatabase(Unknown Source)
    at com.cisco.packaging.DBAdmin.restoreDB(Unknown Source)
    at com.cisco.packaging.DBAdmin.runMain(Unknown Source)
    at com.cisco.packaging.DBAdmin.main(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.zerog.lax.LAX.launch(DashoA10*..)
    at com.zerog.lax.LAX.main(DashoA10*..)
    ERROR 2011-07-05 10:55:03,175 [main] (SchemaUpdate.java:177) - Error closing connection
    java.sql.SQLException: [Solid JDBC 04.50.0176] Connection not open
    at solid.jdbc.SolidError.s_Create(Unknown Source)
    at solid.jdbc.SolidConnection.s_AddAndThrowError(Unknown Source)
    at solid.jdbc.SolidConnection.s_Chk(Unknown Source)
    at solid.jdbc.SolidStatement.s_Chk(Unknown Source)
    at solid.jdbc.SolidStatement.close(Unknown Source)
    at com.mchange.v2.c3p0.impl.NewProxyStatement.close(NewProxyStatement.java:831)
    at org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:171)
    at com.cisco.server.persistence.util.PersistenceUtil.beginUpdateSchema(Unknown Source)
    at com.cisco.packaging.DBAdmin.beginUpdateSchema(Unknown Source)
    at com.cisco.packaging.MigrateOldDbToNewDb.upgradeDatabase(Unknown Source)
    at com.cisco.packaging.SelectDirAndRestoreDb.restoreDatabase(Unknown Source)
    at com.cisco.packaging.DBAdmin.restoreDB(Unknown Source)
    at com.cisco.packaging.DBAdmin.runMain(Unknown Source)
    at com.cisco.packaging.DBAdmin.main(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.zerog.lax.LAX.launch(DashoA10*..)
    at com.zerog.lax.LAX.main(DashoA10*..)
    WARN 2011-07-05 10:56:03,518 [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] (BasicResourcePool.java:1841) - com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@ea58e3 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30). Last acquisition attempt exception:
    java.sql.SQLException: [Solid JDBC 04.50.0176] Unable to connect to data source
    at solid.jdbc.SolidConnection.s_AddAndThrowError(Unknown Source)
    at solid.jdbc.SolidConnection.serverConnect(Unknown Source)
    at solid.jdbc.SolidConnection.<init>(Unknown Source)
    at solid.jdbc.SolidDriver.connect(Unknown Source)
    at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:135)
    at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182)
    at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171)
    at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137)
    at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014)
    at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32)
    at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810)
    at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)
    OS is Windows Server 2003 Enterprise, 32bit, PAE Enabled  
    The strange thing is, we had a case open and the TAC-Engineer was actually able to import the database, since it looked like a issue with our virtual machine we agreed to close the case and continue testing on another server. However after moving to a proper server the problem still exists.
    Also it doesnt matter if we try a direct upgrade install with automated migration or a fresh install with manual db import, its always the same error during the hibernate export.
    I think i will reopen the case later but maybe there is a more simple solution to that problem?
    Thanks a lot
    Kind regards
    Christian

    Hi Jorge,
    It looks like such a level of granularity may not be achievable yet.
    Should you need such a feature to be evaluated for potentially being included in future software releases, I would recommend to contact your local Cisco account team.
    They should be able to follow up and submit a product enhancement request (PER).
    Business units will evaluate PERs and, if feasible for the market, they may consider implementing such an enhancement in future versions of the SW/HW.
    Regards,
    Fede

  • WCS 5.2.130 apache stopped

    Hi,
    I've an installation of WCS 5.2.130 with a win2003 server ( with 8G RAM and 3.4GHz proc ).
    I found several time the APACHE SERVER and WCS stopped while DATABASE and HEALTH MONITOR are running
    I've seen a bug related a logon/logout from the phisical console, but it's not this the situation.
    The workaround is to logon ( via remote desktop ) into the server and sto/restart the WCS.
    Any idea / suggest ?
    Many thanks in advance
    Luigi

    What does eventviewer indicate?
    Also, do you have iis running as well?
    there may be a conflict.
    Given the fact that is on windows, do you have automatic updates enabled and/or are there local or domain policies that could affect system users that are used for services?
    Another workaround would be to create a script that monitors the service and restarts it if the service is down. It has been a while since I messed with windows, but there are many ways to do this

  • Migrate from WCS 7.0.172.0 to Cisco Prime NCS

    Is there anyway to migrate off of WCS to Prime NCS? We have a fully built WCS system with maps and all configs and was wondering if there was a way to restore to NCS.

    Yes, this is possible.  Here is the link from the NCS release notes on the process.
    http://www.cisco.com/en/US/docs/wireless/ncs/1.0/release/notes/NCS_RN1.0.0.html#wp83675
    Steve

  • WCS 7.0.172.0 Feedback Broken

    I am trying to use the feedback tool from within WCS but when it opens the page, whatever Cisco product you choose it directs you to leave feedback for NCS.
    Just thought i'd let Cisco know this is broken.

    I haven't been able to make it work like it was in prior versions.  I have found you can initiate the session from monitor-->access points--->ap name and selecting the radio type.  802.11b/g/n, or 802.11a/n.  The icon is under cleanair management operation.

  • Migrate WCS 7.0.172 to Prime 1.3

    Hi all,
    I need to migrate from WCS to Prime in order to support WLC 7.4.
    I'm a little bit confused about license migration procedure, I have read that it is necessary to move trought Prime1.2, so the license code that I need is:
    R-W-PI12-M-K9
    WCS 7.0 to Cisco Prime   Infrastructure 1.2 Migration
    R-PI12-BASE-K9
    Prime Infrastructure 1.2 Base   License and Software
    L-PI12-LF-1K-LIC
    Prime Infrastructure 1.2 -   Lifecycle - 1K Device Lic PAK
    L-PILMS42-1K-M
    Prime Infrastructure LMS 4.2 -   1K Device Upgrade Lic
    L-W-PI12-1K-M
    WCS to Prime Infrastructure 1.2   Migration 1K Device
    How I can obtain .lic file for Prime from license present on my WCS installation?
    The export from CLI procedure on WCS, export also the actual License?
    Where is the procedure? I think there are some steps on the machine and others on the Cisco site
    NOTE: I also change the position of the software from a virtual machine to another one
    An additional request, in some document I read that it is possible to migrate directly to Prime1.3, is it true?
    Thanks
    Valerio

    Has anyone seen an error message when trying to import WCS 7.0.230 maps into Prime Infrastructure 1.3.0.20?
    WCS generated a .tar file, but when importing into Prime, it says:
    XML Import: 'ImportExport_b8d18562d25d0f6f.tar' has an unsupported Mime Type. Mime Type sent by Browser: 'application/x-tar' Possible causes/workarounds: 1. Check File [Associations/Types/Extensions], 2. Ensure appropriate application launches file, 3. Try a different browser, 4. If File [Associations/Types/Extensions] are correct try closing the browser and relaunch. Supported file format mime types are 'application/gzip-compressed', 'multipart/gzip-compressed', 'multipart/x-zip-compressed', 'application/x-gzip-compressed', 'application/zip', 'multipart/zip', 'application/x-zip-compressed', 'multipart/x-gzip', 'application/x-zip', 'application/gzip', 'application/x-gzip', 'multipart/x-gzip-compressed', 'multipart/gzip', 'multipart/x-zip'

  • Copy AP Configuration Templates-WCS 7.0.172.0

    I am wondering if anyone has seen a way to copy an AP configuration template. We have several distribution centers and the templates are essentially identical other than the Template name and the AP Group VLAN (different for each DC). We set up a new template for each new DC. Being able to copy a template, rename it and change the Group VLAN setting would save a lot of time.

    I haven't been able to make it work like it was in prior versions.  I have found you can initiate the session from monitor-->access points--->ap name and selecting the radio type.  802.11b/g/n, or 802.11a/n.  The icon is under cleanair management operation.

  • WCS 7.0.172.0 gui timeout

    Is there anyway to increase the timeout value for the gui?
    I have an intern positioning AP's on various map's and he gets booted off the gui at random times.  He isn't idle either.
    Thanks

    I haven't been able to make it work like it was in prior versions.  I have found you can initiate the session from monitor-->access points--->ap name and selecting the radio type.  802.11b/g/n, or 802.11a/n.  The icon is under cleanair management operation.

  • WCS running 7.0.172.0 crashing

    We've been running WCS 7.0.172.0 since the end of last year and during that time it has crashed twice. You get to the login-page but when attempting to log in the page just keeps loading untill it times out. When checking in the server it says that the Database is down.
    In order to get it up and running again the you have to first stop WCS service and then start it again. It isn't enough to just start it.
    Anyone else having this problem?

    I've run into similar problems with WCS 7.0.172.0.  Happens every time the server admins apply patches & reboot the server without shutting down WCS cleanly first.
    Once I had to uninstall, reinstall & restore my most recent snapshot to get it running again.  Most recently I've been able to stop WCS completely & restart it.
    This is on Windows Server 2003 R2 Std Ver SP2 on a VM.
    HTH.

  • ERROR: invalid backup file version. Exception: Error while unzipping invalid wcs 7.x export file

    Hi,
    I'm having a serious issue with your brend new Cisco Prime Network Control System (NCS) and i would appreciate if someone could give me good answers.
    After a background backup task failure, the database was entirelly corrupted and the oracle server no longuer wanted to start. And because of that the NCS web server is unusable, since no one can log in.
    We tryed to restore to last known backup obtained after a former suucessful backup. But we get this error:
    "ERROR: invalid backup file version. Exception: Error while unzipping invalid wcs 7.x export file"
    All the lost data was previously migrated from the former WCS 7.x server. Before this issue everything was working fine.
    So we think that the appliance is seeing the backup file from NCS as a WCS backup.
    We need to find rapidly a solution. Here is our configuration:
    We formerly had WCS 7.0.172.0 hosted on Microsoft Windows Server 2003  SP2 with the above caracteristics: 
    Intel(R)Xeon(R) CPU  5120 @ 1.86Ghz 1.87Ghz 16GB of RAM.
    We now have NCS  Version 1.1.1.24 running under Cisco Application Deployment  Engine
    OS Release:  2.0
    ADE-OS Build Version: 2.0.1.038
    ADE-OS System Architecture:  x86_64

    I was getting this error too. TL;DR: When you transfer the wcs.zip file to your FTP server, make sure you are using BINARY mode... which is often NOT the default FTP mode.
    Long Version:
    TO GET THIS ERROR, what I had done was use the Windows CLI FTP command to transfer my "wcs.zip" to the NCS FTP server.
    -----BEGIN WRONG STEPS-----
    C:\ftp
    ftp> open x.x.x.x
    Connected to x.x.x.x.
    220 Service ready for new user
    User (x.x.x.x:(none)): ftp-user
    331 User name okay, need password for ftp-user
    Password:
    230 User logged in, proceed
    ftp> put wcs.zip
    200 Command PORT okay
    150 File status okay; about to open data connection
    226 Closing data connection
    ftp: 526768949 bytes sent blah blah etc
    -----END WRONG STEPS-----
    I would then run "ncs stop" and "ncs migrate" and get the "ERROR: invalid backup file version. Exception: Error while unzipping invalid wcs 7.x export file".
    I remembered something from my misspent youth: Windows, for no good reason, likes to transfer files in ASCII mode. UNIX (which LINUX comes from) prefers BINARY, and the two do not like to negotiate.
    TO FIX THIS, I had to just FTP in Binary mode.
    -----BEGIN RIGHT STEPS-----
    C:\ftp
    ftp> open x.x.x.x
    Connected to x.x.x.x.
    220 Service ready for new user
    User (x.x.x.x:(none)): ftp-user
    331 User name okay, need password for ftp-user
    Password:
    230 User logged in, proceed
    ftp> binary
    200 Command TYPE okay
    ftp> put wcs.zip
    200 Command PORT okay
    150 File status okay; about to open data connection
    226 Closing data connection
    ftp: 526768949 bytes sent blah blah etc
    -----END RIGHT STEPS-----
    NOW when I enter "ncs stop" (actually... had to restart them... then stop them... x.x) and then the proper "ncs migrate" commands, I get a happy output and don't have to go home late troubleshooting this.
    "  Stage 1 of 5: Decompressing backup ...
      -- complete.
      Stage 2 of 5: Restoring Support Files ...
                  : Restoring the Domain Maps ...
                  :  -- complete.
                  : Restoring the License files ...
                  :  -- complete.
      -- complete.
      Stage 3 of 5: Restoring Data ...
    I hope this helps anyone banging their head against the WCS->PI1.3 install wall.
    (Note, WCS needs to be migrated to NCS 1.1.1.24 (NOT NCS 1.1.3!!!!!) before you can migrate to Prime Infrastructure 1.2 or 1.3, because for no readily apparent reason the "ncs migrate" command was removed from PI 1.2 and up. Also note, there is no "Prime Infrastructure 1.1;" they just renamed NCS to Prime Infrastructure after NCS 1.1 because. Yes, the sentence ends there. Great products, all 3, just... agonizing to migrate.)

  • Getting alert in WCS- DoS: CTS flood

    Hi  Experts ,
    I have WCS 7.0.172.0 where as i have very frequent alert about DoS : CTS flood
    In channel 60, the system has detected 212 CTS frames in the last minute, which matches the traffic pattern of the form of denial-of-service attack, CTS (Clear-To-Send) attack. A wireless denial-of-service attacker may suspend the wireless media for communication by taking advantage of the privilege of CTS frame to reserve RF medium for transmission. By transmitting back to back CTS frames, an attacker can force other wireless devices sharing the RF medium to hold back its transmission until the attacker stops transmitting the CTS frames.
    The system detects the abuse of CTS frames for denial-of-service attack.
    I dont know , how can stop getting this alert.
    Please suggest me for the same.

    If you go security-->wireless protection policy-->standard signature
    You will see a list of signatures. Your CTS alert is in one of them, which one is the question. Is my guess ... Unless you have custom one set up ?

  • AP mesh info in WCS not show bridge links.

    Hi guys,
    I would like to know if any of you following problem has occurred. I have implemented 3 wireless mesh with 1262 AP WLC 5508 v 7.0.116.0 and WCS 7.0.172.0 base lic, all has been running perfect, the problem arises when I want to see on the map graphically bridge links, I have enabled AP Messh info but it not shows the bridge links, in hierarchical Mesh Parent-Child View only shows the RAP. To load the maps we used Campus> Outdoor area> AP.
    I will appreciate any comments.
    Greetings.

    Are you loading 4.0? With WCS 4.x you need to generate a license with the PAK you should have received from Cisco. If you did not receive a PAK, read the following excerpt from the following url:
    Existing Cisco WCS customers that have not received their PAK certificate from Cisco should contact their Cisco sales representative or send an e-mail to the [email protected] alias to notify Cisco that they need their PAK certificate. Cisco will attempt to respond to requests to this alias within 48 hours Monday-Friday 9AM-5PM Pacific Standard Time.
    http://www.cisco.com/en/US/products/ps6305/products_data_sheet0900aecd804b4646.html
    I hope this helps.
    -Eric

  • WLC Custom Web Auth Bundle sample .tar file is not on WCS

    The WLC documentation would make it appear (or maybe previously) you should download a sample web auth bundle code from the WCS Templates. I was never able to find a sample .tar file on the WCS 7.0.172.0 templates.
    However I found on Cisco.com under Support > Downloads > Products >Wireless> Wireless LAN Controller Standalone Controllers> Cisco 5500 Series Wireless Controllers > Cisco 5508 Wireless Controller > Wireless Lan Controller Web Authentication Bundle-1.0.2  > webauth_bundle-1.0.2.zip
    It was updated in June 2011, some pretty good sample html code.
    The readme.html in the sample webauth_bundle-1.0.2.zip file has been very helpful , almost as good as the suppport community web page on custom web auth.
    https://supportforums.cisco.com/docs/DOC-13954

    WCS config guide 7.0.172 is correct
    http://www.cisco.com/en/US/docs/wireless/wcs/7.0MR1/configuration/guide/temp.html#wp1129979
    The bundle in WCS is downloaded through :
    configure->controller
    "select a command"-> download customized webauth bundle.
    Just tested it and it was there.
    The one on cisco.com is better though

  • WCS showing APs that don't exist

    Hi,
    I'm doing a demo for a customer and I have a small "bug" on my WCS. The WCS is showing fault information on the home page. It says: "Total APs not yet assigned to Maps : 2". When I open the link, it says "None detected". There are also two unknown MACs on the client tab of the home page.
    I have one controller and five access points at the moment. All the APs have been placed on a map. I've done an audit for the controller and refreshed the config to WCS. Is there any way I could erase the old database and get rid off these "ghost APs"?
    I'm running WCS v. 6.0.132.0 and WLC v. 6.0.188.0.
    Thank you,
    Petri

    This is a cosmetic issue that can be corrected by editing the database of WCS.
    Before doing so, stop wcs service, run on the cli dbadmin.bat checkschema (from the wcs bin folder) and then restart wcs to see if this fixed the db.
    If not please open a TAC case as we manually need to edit your database to remove the 2 aps from the list.

  • WCS: Bug with unique client report?

    I'm running WCS 7.0.172.0 and have run into the situation where a Unique Client Report, when run for the last day, shows lots of clients (properly).  When you select a specific date range, you get no records, regardless of the date range (you can even select the last 24 hours with the drop-downs).  Is this a bug?

    I've gone back and forth with TAC on this, and it's been explained to me that the function of the report has changed recently and the description for what it does is no longer valid.  I STILL think there is a bug in this, however, as it appears whenever I run this report, it only shows me the unique clients RIGHT NOW, even if I pick "last day" which I'm told is really the only valid criterion... something is definitely broken here.

Maybe you are looking for