Reporting MSE (WCS)

Hi@all,
we have a small problem with the "Client Location Tracking"-report in WCS.
If we make create a job for this kind and activate the schedule, we get empty reports. If we open the job and press "run", we get all clients listed. (eport is possible, too).
If the job is running via the schedule, we get "Report ran successfully and the run result has no data" but this is impossible.
Our infrastructure:
  MSE 3355 (7.0.240)
  WCS     (7.0.240)
   WLC 4404 (7.0.240).
I hope anybody could help.
kind regards
  René

So, yesterday we cleared the database of the MSE via WCS.
After this procedure we got our reports.
Now, round about 24h later, they are corrupt.
If we look at the CPU-Status of the MSE, we see that some oracle -instances have 100%CPU (also 1 core full) and a report takes ~ 10 Minutes.
If execute the report now, we get it in 20-30 sec.
Also it seems a bug. TAC case is opened, but it looks like that we don´t get help, missing contract *argh*
Edit:
What i have been realized, that the DB disk memory is 4199696000. It seems, that the db, couldn´t be larger than 4GB, because yesterday we have nearly the same amount of data befoor we cleaned the database. This couldn´t be correct, or?

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.

  • Reporting in WCS 6.0.132

    I recently upgraded from WCS 5.2 to 6.0. I have a number of Client Count reports set up, which are run weekly to generate PDF graphs of usage on all APs in each building. Since the conversion, all of them fail with the message "Failed to run report". I've tried deleting and re-defining them, but get the same result. Running them manually makes no difference. Has anyone seen anything similar? Is there anything I can do, or is reporting just broken in 6.0? The message is singularly unhelpful
    Regards
    Max Caines
    University of Wolverhampton

    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.

  • Detailed client Report in WCS

    Hi,
    what exactly mean the fields of the traps  that appear in the Detailed Client report of the WCS?
    07/08/10 08:09,"00:04:23:71:67:bf",,"Campus> Ome > CN.OM.P03","XSFK2MP345","10.120.205.25",07/08/10 08:09,"0 secs","0.0.0.0",0,-128,"802.11b","N/A",0,0,0,0,"No","Associated","Client '00:04:23:71:67:bf' is associated with AP '00:23:eb:2d:8a:e0', interface '0'."
    which means many  associations of  "0Sec" with no IP assigned?
    Thanks!

    Hi,
    Are you still facing this issue?
    thanks,
    Vinay

  • Interpretations of 802.11 counters report on WCS

    Dear Sir,
    My customer recently deployed WLCs and WCS in their environment. However, recently they experienced slow performance. To futher finding out the root cause, I generated the 802.11 counters report from the WCS and noticed the following parameters is shown.
    Tx/Rx Fragment Count/Sec and FCS Error Count/Sec
    1. Can I make the assumptions that the overall transfer of packet rate in that interval is the Total of Tx/Rx Fragment Count/Sec and FCS Error Count/Sec?
    2. If the output rate of Tx/Rx Fragment Count/Sec and FCS Error Count/Sec are the same, does it mean that 50% of the packet are corrupted and this high FCA Error Count/Sec will cause performance degradation to the wireless througphput?
    3. What is the baseline of the FCS Error Count/Sec that is acceptable? As for the case with wired, 1% error rate is acceptable. Will wireless have the same baseline?
    Thanks
    -delon

    FCS error count is the number of frames that were transmitted/received with a bad checksum (CRC value) in the ethernet frame. These frames are dropped and not propagated onto other ports. Usually we check FCS errors at the asic level so they never even hit the backplane. Few of these errors are OK, but could also be an indication of bad cables, NICs,etc.
    Catalyst keeps track of Tranmit FCS and Receive FCS. The Receive FCS is normal since its coming from the cable, Transmit FCS errors, however, should not occur and are an indication of bad hardware in the Catalyst. The FCS counter is a sum of Tx and Rx FCS errors.

  • Generation of Client summary report on WCS

    Hi,
    I have four WLCs running the IOS  version 7.0 at different locations. All these WLCs are joined to the WCS at one location.
    I am trying to generate the client summary report. But i am not able to generate the report as per the requirements.
    Please let me know is it possible to generate the client summary report for each controller.(i.e) The report providing the details of the users at each location. If so, Please let me know the procedure.

    Hi,
    Client summary cannot be narrowed down to Controller ip.. However, the "Client session report" will help you out in getting the report per Controller and this gives the client TX, RX and you can custpmize it as well!!
    here is the link to do it..
    http://www.cisco.com/en/US/docs/wireless/wcs/7.0/configuration/guide/7_0reps.html#wp1135765
    lemme know if this answered ur question!!
    Regards
    Surendra

  • MFP Error reported in WCS

    I've searched for the following errors but cant find anything on the MFP Invalid Sequence Number error
    I have just enabled Management Frame Protection (MFP) under AP Authentication / Wireless Protection Ploicies.  Since then I have seen the follwoing MFP related errors on WCS.
    MFP Anomaly Detected - 11 'Invalid Sequence Number' violation(s) have  originated from the AP with BSS '00:11:20:8e:91:50'.  This was detected  by the radio with Slot ID '0' of the AP with MAC '00:1a:e3:76:fd:50'  when observing 'Deauthentication' frames.
    MFP Anomaly Detected - 20 'No MIC' violation(s) have originated from the  AP with BSS '00:26:cb:ac:7e:71'.  This was detected by the radio with  Slot ID '0' of the AP with MAC '00:26:cb:d1:b2:b0' when observing  'Deauthentication' frames.
    The WLC's are running 6.0.196.0 and WCS is on 6.0.170.0.
    My question is what do these errors refer toand how do I get rid of them??  What caveats are there for impleementing this globally or on a per WLAN basis?
    Any ideas?
    Thanks
    Martin

    Hello,
    I have exact the same error message 8 or 10 times per days, but we have MFP enabled on our system from long time and we have WLC Version 7.0.98.0 and WCS 7.0.164.0.
    Did you get solutions for that?
    Thanks for your help

  • Rogue reporting in WCS

    Can anybody tell me what the difference is between the following 2 default Security reports:
    Rogue APs
    Rouge APs Event
    WE run both of these nightly, but the Rogue APs Event report usually is about 20 pages or so, and the information there has way more than what I see when I compare to my controller. The Rogue APs report usually matches what I see on my controller regarding current rogues. Does the Rogue APs Event report just detail everything that the access points have seen in the reporting time period? Some clarification on this would be greatly appreciated.
    Thank you.

    Rogues Detected by APs Report displays information about specific rogue access points detected on the network, rather than having to look into each rogue alarm and manually assemble a list. The data that is returned includes but is not limited to the following: the name of the detecting access point, the MAC address of the rogue, and the location of the rogue.
    and Security Summary Report shows the number of association failures, rogues access points, ad hocs, and access point connections or disconnections over one month.

  • Reporting problems with Cisco WCS

    hi all,
    I was wondering whether anyone has experienced the following symptoms on Reporting.
    WCS Rogue AP reports do not run and show up as 'Expired'
    this does not occur to all the Rouge AP  reports though (they are being created based on floor areas; one report per campus)
    customer is using the following
    WCS Version: 7.0.230.0
    any idea on this, could this be a software bug?
    thanks a lot
    with kind regards,
    Lancellot

    Hi,
    The report expires when it is scheduled report and configured for some specific time. After the time passed the report expires. re-schedule the report time and change the start-date time of the schedule and that should resolve your issue.
    HTH
    Amjad
    Rating useful replies is more useful than saying "Thank you"

  • WCS Busiest Client Report Problem

    We are using Wism 4.0.155.5 and WCS 4.0.81.0. Everytime I run "busiest client report" on WCS, I get some clients with throughput more than 70Mbps and utilization more than 600%!!! It is very weird. Anyone see this as well? Thanks.

    zhenningx:
    I see it too. It definitely appears to be a bug, but I will do some checking. Mine show upwards of 2000% and most of my top 25 show an almost identical tx/tx amount of 4gb.
    If I make any headway with TAC, I'll let you know.

  • WCS Unique Client report problem

    If I run a "Unique Client" report in WCS (based on 4 controllers) using the range "last 1 day", I get plenty of data.  But if I choose a specific range of time, even within the last 24 hours, I don't get any data.  Seems like a bug.  Anyone else experience this issue?
    It's WCS 7.0.172

    Seems you are facing below bug and needs a patch uniqueclients.xml which can be provided by TAC.CSCtq64813
    Apply the workaround which done by the following steps:  1. Stop WCS 2. cd to /webnms/classes/com/cisco/server/reports/conf 3. Backup UniqueClients.xml 4. Copy the attached file to UniqueClients.xml (batch file attached in the case) 5. Restart the server

  • WCS reporting -128db

    I have a WISM LWAPP deployment with 4 WISM blades (2 are for backup), 400 1231 and 1242 AP's. I use WCS to monitor the WLAN. My problem is tracking down why stationairy clients are frequently reporting through WCS a -128db signal strength when the client is located less than 50 feet from an AP. This is happening on all SSID's and in multiple buildings. It does not happen to all of the clients on a given AP, and does not seem to happen on all clients. It happens at random times. My thought is that WCS only polls clients every 10 minutes (I changed this from the default 15 minutes) so the signal loss indicated by -128db is probably happening much more frequently. This is happening to iPAQ's, tablets, symbol mc70's, laptops both windows and MAC.
    I am also seeing very high MIC and FCS error counts.
    Any suggestions on a command to monitor a client to see whats goiing on.
    Thanks

    You can use the WCS navigator. The Cisco WCS Navigator provides network administrators with easy, cost-effective access to information from multiple geographically diverse Cisco WCS management platforms. This innovative platform allows network managers to partition the unified wireless network at the management level.

  • WCS coverage hole report explanation

    Hi All,
    I just ran  the coverage hole report in WCS. The report shows below. Can anybody explain to me if there is a coverage hole in our production? I have no idea aobut what the state means and all the client counts are 0. We have some clients connected to these APs everyday. Thanks in advance.
    Generated: Thu Jul  07 10:13:21 EDT 2011
    Report By: AP By  Controller
    Access Point: XX.XX.199.140 ->  h2200-8-lap1131-1;h2200-8-lap1131-2;h2200-8-lap1131-3;h2200-8-lap1131-4
    Reporting Period: Last 7  days
    Coverage  Holes in the Network
    Time
    State
    AP  Name
    Radio  Type
    Failed  Clients
    Total  Clients
    Worst  Client RSSI
    07/06/2011  10:29:46 EDT
    Clear  
    h2200-8-lap1131-1   
    802.11b/g   
    0
    0
    0
    07/06/2011  10:24:09 EDT
    Active   
    h2200-8-lap1131-1   
    802.11b/g   
    0
    0
    0
    07/04/2011  14:13:03 EDT
    Clear  
    h2200-8-lap1131-1   
    802.11b/g   
    0
    0
    0
    07/04/2011  14:08:01 EDT
    Active   
    h2200-8-lap1131-1   
    802.11b/g   
    0
    0
    0
    06/30/2011  14:22:03 EDT
    Clear  
    h2200-8-lap1131-1   
    802.11a   
    0
    0
    0
    06/30/2011  14:17:01 EDT
    Active   
    h2200-8-lap1131-1   
    802.11a   
    0
    0
    0
    07/07/2011  10:12:33 EDT
    Active   
    h2200-8-lap1131-3   
    802.11b/g   
    0
    0
    0
    07/06/2011  15:15:36 EDT
    Clear  
    h2200-8-lap1131-3   
    802.11b/g   
    0
    0
    0
    07/06/2011  15:05:31 EDT
    Active   
    h2200-8-lap1131-3   
    802.11b/g   
    0
    0
    0
    07/06/2011  14:14:21 EDT
    Clear  
    h2200-8-lap1131-3   
    802.11b/g   
    0
    0
    0
    07/06/2011  14:09:12 EDT
    Active   
    h2200-8-lap1131-3   
    802.11b/g   
    0
    0
    0
    07/06/2011  11:15:40 EDT
    Clear  
    h2200-8-lap1131-3   
    802.11b/g   
    0
    0
    0
    Page 1  of
    3
    Time
    State
    AP  Name
    Radio  Type
    Failed  Clients
    Total  Clients
    Worst  Client RSSI
    07/06/2011  11:10:37 EDT
    Active   
    h2200-8-lap1131-3   
    802.11b/g   
    0
    0
    0
    07/06/2011  10:49:57 EDT
    Clear  
    h2200-8-lap1131-3   
    802.11b/g   
    0
    0
    0
    07/06/2011  10:44:54 EDT
    Active   
    h2200-8-lap1131-3   
    802.11b/g   
    0
    0
    0
    07/05/2011  14:24:46 EDT
    Clear  
    h2200-8-lap1131-3   
    802.11b/g   
    0
    0
    0
    07/05/2011  13:57:24 EDT
    Active   
    h2200-8-lap1131-3   
    802.11b/g   
    0
    0
    0
    07/04/2011  14:18:06 EDT
    Clear  
    h2200-8-lap1131-3   
    802.11b/g   
    0
    0
    0
    07/04/2011  14:13:03 EDT
    Active   
    h2200-8-lap1131-3   
    802.11b/g   
    0
    0
    0
    06/30/2011  14:53:01 EDT
    Clear  
    h2200-8-lap1131-3   
    802.11a   
    0
    0
    0
    06/30/2011  14:47:59 EDT
    Active   
    h2200-8-lap1131-3   
    802.11a   
    0
    0
    0
    07/06/2011  15:50:58 EDT
    Clear  
    h2200-8-lap1131-4   
    802.11b/g   
    0
    0
    0
    07/06/2011  15:40:53 EDT
    Active   
    h2200-8-lap1131-4   
    802.11b/g   
    0
    0
    0
    07/06/2011  15:00:28 EDT
    Clear  
    h2200-8-lap1131-4   
    802.11b/g   
    0
    0
    0
    07/06/2011  14:55:17 EDT
    Active   
    h2200-8-lap1131-4   
    802.11b/g   
    0
    0
    0
    07/06/2011  14:50:14 EDT
    Clear  
    h2200-8-lap1131-4   
    802.11b/g   
    0
    0
    0
    07/06/2011  14:45:11 EDT
    Active   
    h2200-8-lap1131-4   
    802.11b/g   
    0
    0
    0
    07/06/2011  11:10:37 EDT
    Clear  
    h2200-8-lap1131-4   
    802.11b/g   
    0
    0
    0
    07/06/2011  11:05:34 EDT
    Active   
    h2200-8-lap1131-4   
    802.11b/g   
    0
    0
    0
    Page 2  of
    3
    Time
    State
    AP  Name
    Radio  Type
    Failed  Clients
    Total  Clients
    Worst  Client RSSI
    07/04/2011  14:43:21 EDT
    Clear  
    h2200-8-lap1131-4   
    802.11b/g   
    0
    0
    0
    07/04/2011  14:38:19 EDT
    Active   
    h2200-8-lap1131-4   
    802.11b/g   
    0
    0
    0
    07/04/2011  13:57:55 EDT
    Clear  
    h2200-8-lap1131-4   
    802.11b/g   
    0
    0
    0
    07/04/2011  13:52:52 EDT
    Active   
    h2200-8-lap1131-4   
    802.11b/g   
    0
    0
    0
    07/04/2011  12:27:00 EDT
    Clear  
    h2200-8-lap1131-4   
    802.11b/g   
    0
    0
    0
    07/04/2011  12:21:56 EDT
    Active   
    h2200-8-lap1131-4   
    802.11b/g   
    0
    0
    0
    07/04/2011  11:21:21 EDT
    Clear  
    h2200-8-lap1131-4   
    802.11b/g   
    0
    0
    0
    07/04/2011  11:16:19 EDT
    Active   
    h2200-8-lap1131-4   
    802.11b/g   
    0
    0
    0
    06/30/2011  16:55:16 EDT
    Clear  
    h2200-8-lap1131-4   
    802.11b/g   
    0
    0
    0
    06/30/2011  16:50:13 EDT
    Active   
    h2200-8-lap1131-4   
    802.11b/g   
    0
    0
    0
    06/30/2011  15:49:02 EDT
    Clear  
    h2200-8-lap1131-4   
    802.11b/g   
    0
    0
    0
    06/30/2011  15:33:36 EDT
    Active   
    h2200-8-lap1131-4   
    802.11b/g   
    0
    0
    0
    Page 3  of
    3

    What is exactly a coverage hole ?
    If the WLC detects that a client is on an AP with a bad signal strength and stick with that AP, it notes it down. that means there is no other AP to roam to logically.
    But because most clients are not so smart in roaming, the default treshold before taking an action is to detect 3 clients on the same AP with bad signal strength. Only then will the AP increase its transmit power (if it's not at the max already).
    When the client limit is not reached, it's a "pre coverage hole" alert. The coverage hole itself is when the right number of clients are detected.
    Clear is when the clients left or if the AP increased its power (so the clients are at a better signal). Active is that the clients are still there at bad signal (then either there is no enough clients to take action or the AP is already at max power).

  • WCS Client Reporting

    Hi All,
    hoping this is the right sub-forum for this query!
    WCS is missing entries from it's client details report.  on our firewall logs I had an IP I wanted to check for it's MAC address, I could see the log entry in our firewall and the time and date stamp along with the wireless IP Address.
    I ran the Client Details report in WCS on the date and specified the times between 12:00 noon and 6:00pm and it failed to find the associated IP address in the log.
    I know for certain that the IP was active at that point in time and it should appear in a our client details report, but it's not getting logged.
    We are using version 7.0.172.0 of Cisco WCS if that makes any odds

    You can use the WCS navigator. The Cisco WCS Navigator provides network administrators with easy, cost-effective access to information from multiple geographically diverse Cisco WCS management platforms. This innovative platform allows network managers to partition the unified wireless network at the management level.

  • Report on AP Failover Priority

    Does anyone know of a way or place that the AP Failover setting on the AP is reported in WCS.  I can't seem to find anywhere this setting appears in any inventory report.  The only way I seem to be able to look this up is to go AP by AP and look at the config screen.
    Thanks for any guidence.
    JC

    Rats! I was just about to ask the same thing. Sorry to see that there were no answers to the original post.
    (Will it bump this question up if I ask again here, or will I need repost the whole question to get new answers?)
    Basically, I'd like a Monitor screen or a report that gives a table with each AP and its failover setting. I have only 75 APs, on a -25 and -50 4402. I think I've set my favorite 25 APs to "High", and then then next most important 25 to "Medium" and then the rest should be low. That way, if either my -25 or -50 WLC fails, I still have the best coverage possible.
    But, I can't find any way to easily check these settings, except by individually selecting each AP one by one from the Configure>Access Points table.
    This is tedious even on my small system, and I can't imagine it would be any fun at all on a bigger one. (Maybe those big systems have full redundancy so the failover is not an issue?)
    Thanks for any insights,
    Steve

Maybe you are looking for