WCS - coverage hole alert
Hi forum,
I am constantly getting the below coverage hole alert, the AP is used to cover a warehouse area, sometimes the users will carry their notebook out of the warehouse and back in. The radio frequency is set to auto. What could be the cause of this issue?
Thank you,
PN
======================================
An Alert of Category Coverage Hole is generated with severity 3 by Radio KM3_Ship_AP01/1 .
The message of the alert is AP 'KM3_Ship_AP01', interface '802.11b/g' on Controller '10.16.14.3'. Coverage threshold of '12' violated. Total no of clients is '3' and no of failed clients is '2'. Worst signal quality experienced by client='00:19:7d:1e:41:f3' RSSI='-65' dBm SNR='-116', client='00:19:7d:18:12:d6' RSSI='-68' dBm SNR='-65'..
Hi Paul,
If you have users walking out of the Warehouse I would expect you to see these alerts. Here is some info on what causes the "Coverage Hole" alerts;
Coverage Hole Detection and Correction
If clients on a lightweight access point are detected at signal-to-noise ratio (SNR) levels that are lower than the thresholds specified in the Auto RF configuration, the access point sends a "coverage hole" alert to the controller. The alert indicates the existence of an area where clients are continually experiencing poor signal coverage, without having a viable access point to which to roam.
The Coverage Hole Detection and Correction algorithm is primarily aimed at the determination of coverage holes based on the quality of client signal levels.
The algorithm determines if a coverage hole exists when the clients' SNR levels pass below a given SNR threshold. The SNR threshold is considered on an individual AP basis and is based primarily on each AP's transmit power level. The higher the AP power levels, the more noise the APs tolerate as compared to the client signal strength, which means a lower tolerated SNR value.
This SNR threshold varies based on two values: the AP transmit power and the controller Coverage profile value. The threshold is defined by the transmit power (represented in dBm) of each AP, minus the constant value of 17dBm, minus the user-configurable Coverage profile value. The Coverage value is defaulted to 12 dB. The client SNR threshold value is the absolute value, or the positive number, that results from this equation:
Coverage Hole SNR Threshold Equation:
Client SNR Cutoff Value (|dB|) = [AP Transmit Power (dBm) ? Constant (17 dBm) ? Coverage Profile (dB)]
Once the average SNR of a single client dips below this SNR threshold for at least 60 seconds, the AP transmit power of that client is increased to the appropriate level in order to mitigate the SNR violation, and correct the coverage hole. Only one client need violate this threshold in order to trigger a correction.
Each controller runs the Coverage Hole Detection and Correction algorithm for each radio on each of its APs every three minutes. The default value of 180 seconds can be changed, as described in the Monitor Intervals (60 to 3600 secs) section of this document.
From this doc;
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a008072c759.shtml#coverage_correction
The Coverage Hole SNR Threshold Equation:
Client SNR Cutoff Value (|dB|) = [AP Transmit Power (dBm) ? Constant (17 dBm) ? Coverage Profile (dB)]
Note: This equation represents a situation where a client experience signal issues in a poorly covered area of a floor.
In such a scenario, these items can be true:
A client has an SNR of 13dB.
The AP to which it is connected is configured to transmit at 11 dBm (power level 4).
This AP WLC has a Coverage profile threshold set to the default of 12 dB.
In order to determine if the client AP must be powered up, the numbers detailed are plugged into the Coverage Hole Threshold Equation. This is the result:
Client SNR cutoff = 11dBm (AP transmit power) ? 17dBm (constant value) ? 12dB (Coverage threshold) = |-18dB|.
Because a client SNR of 13dB is in violation of the present SNR cutoff of 18dB, the Coverage Hole Detection and Correction algorithm increase the AP transmit power to 17dBm.
When you use the Coverage Hole SNR Threshold Equation, it is evident that the new transmit power of 17dBm yields a Client SNR cutoff value of 12dB, which satisfies the client SNR level of 13 dBm.
This is the math for Step 3:
Client SNR cutoff = 17dBm (AP transmit power) ? 17dBm (constant value) ? 12dB (Coverage threshold) = |-12dB|.
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a008072c759.shtml#c_c_workflow
Hope this helps!
Rob
Similar Messages
-
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
3What 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). -
What's the difference of coverage hole and pre-coverage hole?
Hi All,
Anybody knows what's the difference of coverage hole and pre-coverage hole?
What I can find from Cisco doc is:
"coverage holes are displayed as alarms, pre-coverage holes are displayed as events."
"Gaps or "holes" in an access point radio coverage are the primary cause of poor audio. Client-detected Pre-Coverage Hole events provide ongoing monitoring to ensure that the customer is alerted regarding the existence of these coverage holes."
It seems Pre-coverage hole is client-detected, coverage hole is AP detected? However I'm not sure.
Another question is which trap includes pre-coverage hole alarm in WCS 7.0 alarm and event dictionary? I can only find several coverage related traps:
LRADIF_COVERAGE_PROFILE_FAILED
LRADIF_COVERAGE_PROFILE_PASSED
However both of them have not say if it is for coverage hole or pre-coverage hole. Not sure which trap will be sent by the WCS to a configured notification receiver to indicate a pre-coverage hole event, for example:
Minor --X---- 13:27:52 16/09/10 cisco-WCS WCS SNMP <$2> 0x07 da 09 10 0d 1b 2c 05 2b 0a 00 :10.1.1.12 : Pre-Coverage Hole reported by 00:1f:3c:cd:c8:2a detected by 10.1.1.12: Pre-Coverage Hole reported by '00:1f:3c:cd:c8:2a' was found on Controller
Your valuable input is highly appreciated!Hello !
A pre-coverage hole is when a client stays for 5 seconds in a coverage hole. In other words, when a client is heard for some time at bad signal and it's not roaming, it must mean that this area is a coverage hole. This event is informational
A coverage hole event is when several clients are stuck in the same coverage hole. Then the AP will increase its power if this is possible.
The fact that WLC waits for several clients before raising the power avoids crazy behaviors of increasine/lowering/increasing/lowering.
The parameters for coverage hole events are configurable on the RRM part of WLC (number of clients, etc ...)
Nothing is configurable for pre-coverage hole as this is just "1 client only is reaching the coverage hole tresholds".
Hope this clarifies.
Nicolas -
WLC 4402 and coverage hole error software version 5.2.157.0
Hello!
Can you tel me what RRM coverage hole error:
%RRM-3-RRM_LOGMSG: rrmLrad.c:2462 RRM LOG:
RRM Verify Coverage Hole returned L7_FAILURE
means and how it can be fixed.
Thank you in advanced
LasseI'm interested in with the answer too. I got millions of syslog entries such like this: Verify Coverage Hole returned L7_FAILURE
Ok I can turn of Coverage Hole detection or syslog but it makes no sense :)
Can i Just remuve this message from sending to syslog ? -
Dears,
I use to have wireless infrastructure based on autonomous APs 1142n, auth w/ 802.1x and everything was fine.
My Company decided to implement WLC 5508, and I changed only 2nd floor (2 APs) as lightweight and implement WLC over there as pilot testing...
Now All persons here (around 35 clients) are complaining about disconnections, poor signal...
Both APs are distant each other maximim of 15 meters... Our office has a medium open spaced room, with (20 X 15 meters) only 2 "Pilaster" in the middle of the room.
I am facing this message at WLC logs
Thu Nov 1 16:03:57 2012
Coverage hole pre alarm for client[1] 00:37:6d:eb:67:44 on 802.11a interface of AP 00:26:cb:4c:8e:b0 (AP01-RJOBTF). Hist: 1 0 3 4 1 1 2 7 2 9 10 13 4 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Thu Nov 1 15:55:21 2012
Rogue AP : 7c:4f:b5:ed:27:a1 detected on Base Radio MAC : 1c:aa:07:6e:93:20 Interface no:0(802.11b/g) on Channel 11 with RSSI: -92 and SNR: 1 and Classification: unclassified
Thu Nov 1 15:50:27 2012
Coverage hole pre alarm for client[1] 28:e0:2c:6d:11:58 on 802.11b/g interface of AP 00:26:cb:4c:8e:b0 (AP01-RJOBTF). Hist: 0 0 2 5 11 16 9 2 5 12 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Is there any best practices I should perform over here ?
Any specific configuration with the signal itself ? In my opinion we dont have a big room here .. 2 APs should work very well... but they are not...
I also can see many Rogue APs... I am not sure if that rogues aps have anything to do with this problem.... also I didnt change anything at 3rd floor (not sure if the
Thanks in advance!!!Actually I am using both APs as lightweight in 2nd floor.
How about this power level? where I can find those parameters ?
At 3rd floor all APs are autonomous, I accessed one of them and find this parameter
CCK Transmitter Power (dBm): Max
OFDM Transmitter Power (dBm): Max
Client Power (dBm): Max
is that the parameter you talked about ?
At WLC I found this screen
Tx Power Level Assignment Algorithm
Power Level Assignment Method
Automatic
On Demand
Fixed
1 2 3 4 5
Maximum Power Level Assignment (-10 to 30 dBm)
Minimum Power Level Assignment (-10 to 30 dBm)
Power Assignment Leader
Last Power Level Assignment
Power Threshold (-80 to -50 dBm)
Power Neighbor Count
Should I check anything else ?
Thanks in advance!!! -
Disable Coverage Hole Detection
I have a deployment of about 50 APs in a building. In this scenario we are only trying to provide wireless coverage in conference rooms and public areas, I am not trying to cover the entire building. I expect to have a large number of coverage holes due to this design. My question is can anyone give me a reason that I should NOT disable "coverage hole detection"?
Disabling global or per wlan CHD won't affect maintaining system wide RF blanket among APs.
Wouldn't worry about CHD when all APs on its max power levels, and even RRM also not required in this case.
Coverage hole detected btw APs are RF group wide, TPC compensates when neighbor AP went down. It happens irrespective of chd config.
Coverage hole detected btw AP and Client is per WLC basis, you would see pre-coverage hole and actual coverage hole when it persist. Only this will get disabled on that configured wlc. However, info is still collected but does not processed by wlc. -
Coverage Hole Detection & RF Profiles
Hi Guys,
I've recently started to deploy RF profiles on various sites based on different data rate requirements. I know before the days of RF Profiles that Coverage Hole Detection (CHD) was enabled on the WLAN.
My query is, now that RF profiles exists, can you disable CHD on a specific WLAN and enable it on an RF profile or does it have to be enabled on both for it to function?
Cheers,
NI still need to play with 8.0, that is why I was asking because I am not sure on that version. What I gather from the documentation it is the same... http://www.cisco.com/c/en/us/td/docs/wireless/controller/8-0/configuration-guide/b_cg80/b_cg80_chapter_01011101.html
However, with 7.6 you will need to have it enabled on the WLAN as there is no way to 're-enable' it on the RF Profile. You could tweak it to not be kicked off often though -
Coverage hole error message History
What is the significance of the 31 numbers in the coverage hole history for a 2504 WLC? What does this information tell me?
Coverage hole pre alarm for client[2] 30:f7:0d:6d:7a:7d on 802.11a interface of AP 64:d9:89:d5:03:60 (AP5). Hist: 0 0 0 0 0 0 0 6 44 77 44 53 29 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Coverage hole pre alarm for client[2] 30:f7:0d:6d:7a:7d on 802.11a interface of AP 64:d9:89:d5:03:60 (AP5). Hist: 0 0 0 0 0 9 30 11 7 21 32 52 38 43 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Coverage hole pre alarm for client[2] 30:f7:0d:6d:7a:7d on 802.11a interface of AP 64:d9:89:d5:03:60 (AP5). Hist: 0 0 0 0 0 0 0 0 0 15 30 63 34 18 33 15 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0I am aware of the coverage hole issue but what is the significance of the 31 digits. What do these numbers mean? Why are they different over a very short period of time for a single station?
Coverage hole pre alarm for client[2] 30:f7:0d:6d:7a:7d on 802.11a interface of AP 64:d9:89:d5:03:60 (AP5). Hist: 0 0 0 0 0 0 0 6 44 77 44 53 29 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Coverage hole pre alarm for client[2] 30:f7:0d:6d:7a:7d on 802.11a interface of AP 64:d9:89:d5:03:60 (AP5). Hist: 0 0 0 0 0 9 30 11 7 21 32 52 38 43 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Coverage hole pre alarm for client[2] 30:f7:0d:6d:7a:7d on 802.11a interface of AP 64:d9:89:d5:03:60 (AP5). Hist: 0 0 0 0 0 0 0 0 0 15 30 63 34 18 33 15 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 -
How do WLC's work out coverage holes etc
Hi all
with the cisco wlc and lwapp access points, how do the access points adjust there power settings to compensate, what are they looking for?
do they look for noise / interference from the nearby ap, then increase or backoff the power until there is roughly 50% overlap between access points, can anyone explain how it works here?
cheers
CarlHello Carl,
ok , to make it clear for you how WLC power and channel settings work will explain here how RRM ( radio resource management work).
RRM consist of 3 componenets , DCA ( dynamic channel assignment) , TPC ( transmit power control) , CHD ( coverage hole detection).
1) DCA: once the WLC boot and AP's registered the WLC will force channel configuration to the AP to make sure the least possibile co-channel interference between the AP's.
so this algorithm will configure for each AP at will channel it need to operate.
the DCA can be configured from wireless ->>> 802.11 A/B/G->>> RRM ->>> DCA.
the DCA interval specify how frequent the WLC handle the channel updates on the AP's.
note after boot the WLC will require 6 DCA iterations to stabilize the RF.
2) TPC: this algorithm will configure how much power the AP transmit.
it has levels from 1-7 ( 1 is the maximum level)
note : this algorithm can downgrade the pwoer level if it find it is too high...
how the algorithm determine this is too high? and how much overlapping?
this is based on TPC configuration that can be configured from wireless ->>> 802.11 A/B/G->>> RRM ->>> TPC.Power Threshold (-80 to -50 dBm)
so if you configure here lets say -65 , if the AP hearing other neighbours with signal strongest than -65 (lets say -50)then there is possibility RF issues and the WLC will instruct corresponding AP's to downgrade their power to meet the criteria ( - -65 or less from other neighbours)
this will minimize co-channel interference.
note for TPC/DCA to work fine each AP should be designed (places) to be heraed by 3 other neighbours. with signal no stonger than X ( that is configured as power threshold)
3) CHD: this will increase the power level of the AP in case it notices some clients has bad signal.
when it will instrcut to increase power?
if you go to wireless ->>> 802.11 A/B/G->>> RRM ->>> coverage you can see two components (RSSI and Min Failed Client Count per AP (lets say X).
now if single AP hearing that number of X clients with signal strengh below the configured RSSI . then this is coverage hole and WLC instruc to increase its power to cover those clients with better signal.
for more details about WLC radio managment please refer to:
1) WLAN Radio Frequency Design Considerations
http://tools.cisco.com/squish/1Ea09
2) Deploying Cisco 440X Series Wireless LAN Controllers ( Radio Management and RF Domains section)
http://tools.cisco.com/squish/51a58
hope this helps.
Kind regards
Talal
===========
please rate answers that you find useful , and mark as answered - when it is :-) - so others can find it easily -
Hi forum,
How do i configure the WCS to send alert to syslog server or send via emails?
Thank you,
paulHi Paul,
Here is some info to get you started;
Alarm Email Notification
WCS includes a built-in email notification function that can notify network operators when critical alarms occur. Refer to the WCS Monitor > All Alarms > Email Notification page to view the current alarm notification settings.
From this doc;
http://www.cisco.com/en/US/products/ps6305/products_configuration_guide_chapter09186a008059c9f5.html#wp1073486
Monitor All Alarms > Email Notification
Use Monitor/Alarms, then from Select a command drop-down list select Email Notification, then click GO to access this page.
This page allows you to view the alarm categories with Critical Alarm email notification enabled and disabled, the current From and To email addresses, and the current SMTP server. This page also allows you to enable and disable email notification for any or all of the Alarm Categories, and allows you to access an Alarm Category email notification setup page.
For every category except Coverage Holes, the alarm severity must be critical to trigger the email. Email notification is available only for Alarms, not for events.
Email Notification Overview
Parameter Description
Enabled Check box; Checked = Email Notification ON, Unchecked = OFF.
Alarm Category The category of Critical alarms that generate an email notification. Click any of the entries in this column to go to the Monitor Email Notification for `' page.
From Any valid Transmitting email address.
To Any valid Receiving email address.
SMTP Server The name or IP address of the SMTP server that transmits the email notifications.
From this doc;
http://www.cisco.com/en/US/products/ps6305/products_configuration_guide_chapter09186a00805c546a.html#wp1041196
Note: Non-critical alarms do not generate email notifications.
A WCS administrator currently has no control over which events generate alarms, when they time out, or what severity they are. On the controller, individual types of events can be enabled or disabled (such as management, SNMP, trap controls, etc.).
From this doc;
http://www.cisco.com/en/US/products/ps6305/products_configuration_guide_chapter09186a00806b72fe.html
Hope this helps!
Rob -
WCS/WLC Alerts - Configuration
I can't seem to find where I can make modifications to the alerts that I receive from either the WLC or WCS. The alerts mainly being notifications of possible rogue access points. Can someone direct me to where I can make changes as to what kind of alerts I can get from the WCS and/or WLC?
I finally found this. Administration > Settings > Mail Server Configuration > Configure email notification for individual alarm categories.
-
Rogue AP - Not in sync with WCS and WLC
WCS - 7.0.164.0 and WLC - 7.0.98.0.
For some reason, I am seeing rogue ap alert on WLC and am not seeing on WCS. How do I clean up database and sync with WCS and WLC.
I am seeing same thing with coverage holes.
- Allen -Allen,
On the WLC go to Management > SNMP > Trap Controls, make sure that you have the traps checked.
HTH,
Steve
*Please remember to rate helpful posts* -
No client notifications on WCS
We have two WLC'2 4402(sw 5.2.193.0) and one WCS with sw 5.2.148.0. I have a lot of client warnings in the controllers trap logs but none clients alarms on my WCS. Is there any reason why the WCS does not reports client problems ?
Use Administration > Logging to access the Administer Logging Options page. This logging function is only related to WCS logging and not syslog information. The logging for controller syslog information can be done on the Controller > Management > Syslog page.
Email Notification can be done with WCS. WCS includes a built-in email notification function that can notify network operators when critical alarms occur. Refer to the WCS Monitor > All Alarms > Email Notification page to view the current alarm notification settings.
Use Monitor/Alarms.
From a command drop-down list, choose Email Notification.
Click GO to access this page.
This page allows you to view the alarm categories with the critical-alarm email notification enabled and disabled, the current From and To email addresses, and the current SMTP server. This page also allows you to enable and disable email notification (check box checked = email notification ON; check box unchecked = email notification OFF) for any or all of the alarm categories, and it allows you to access an alarm category email notification setup page.
For every category except Coverage Holes, the alarm severity must be critical to trigger the email. Email notification is available only for alarms, not for events.
Note: If you do not receive emails from WCS, check whether port 25 is blocked.
Note: A WCS administrator currently has no control over which events generate alarms, when they time out, or the degree of their severity. On the controller, individual types of events can be enabled or disabled (such as management, SNMP, trap controls, etc.). -
ISE 1.1.1 cisco-av-pair:Wireless-WCS
Hello,
Has anyone configured ISE yet to authenticate WCS against ISE using RADIUS? I have created the Authorization Profiles with rule0=SuperUsers, tack0=...ect, but I am wondering how everyone has done the authentication and authorization rules. Any lessons learned would be great.
KyleYes, I have patch 1 installed. I am trying to add the following cisco-av-pairs:
Wireless-WCS:role0=Admin
Wireless-WCS:task0=Users and Groups
Wireless-WCS:task1=Virtual Domain Management
Wireless-WCS:task2=Audit Trails
Wireless-WCS:task3=TACACS+ Servers
Wireless-WCS:task4=RADIUS Servers
Wireless-WCS:task5=Logging
Wireless-WCS:task6=License Center
Wireless-WCS:task7=Scheduled Tasks and Data Collection
Wireless-WCS:task8=User Preferences
Wireless-WCS:task9=System Settings
Wireless-WCS:task10=View Alerts and Events
Wireless-WCS:task11=Email Notification
Wireless-WCS:task12=Delete and Clear Alerts
Wireless-WCS:task13=Pick and Unpick Alerts
Wireless-WCS:task14=Ack and Unack Alerts
Wireless-WCS:task15=Configure Controllers
Wireless-WCS:task16=Configure Templates
Wireless-WCS:task17=Configure Config Groups
Wireless-WCS:task18=Configure Access Points
Wireless-WCS:task19=Scheduled Configuration Tasks
Wireless-WCS:task20=Migration Templates
Wireless-WCS:task21=Configure Choke Points
Wireless-WCS:task22=Configure Spectrum Experts
Wireless-WCS:task23=Configure ACS View Servers
Wireless-WCS:task24=Auto Provisioning
Wireless-WCS:task25=Monitor Controllers
Wireless-WCS:task26=Monitor Access Points
Wireless-WCS:task27=Monitor Clients
Wireless-WCS:task28=Monitor Tags
Wireless-WCS:task29=Monitor Security
Wireless-WCS:task30=Monitor Chokepoints
Wireless-WCS:task31=Monitor Spectrum Experts
Wireless-WCS:task32=RRM Dashboard
Wireless-WCS:task33=Mesh Reports
Wireless-WCS:task34=Client Reports
Wireless-WCS:task35=Performance Reports
Wireless-WCS:task36=Security Reports
Wireless-WCS:task37=Compliance Assistance Reports
Wireless-WCS:task38=Voice Audit Report
Wireless-WCS:task39=Config Audit Dashboard
Wireless-WCS:task40=Location Server Management
Wireless-WCS:task41=View Location Notifications
Wireless-WCS:task42=Maps Read Only
Wireless-WCS:task43=Maps Read Write
Wireless-WCS:task44=Client Location
Wireless-WCS:task45=Rogue Location
Wireless-WCS:task46=Planning Mode
Wireless-WCS:task47=High Availability Configuration
Wireless-WCS:task48=Health Monitor Details
Wireless-WCS:task49=Configure WIPS Profiles
Wireless-WCS:task50=Global SSID Groups
Wireless-WCS:task51=WIPS Service
Wireless-WCS:task52=Configure Lightweight Access Point Templates
Wireless-WCS:task53=Configure Autonomous Access Point Templates
Wireless-WCS:task54=Guest Reports
Wireless-WCS:task55=Handover Server Management
Wireless-WCS:task56=Monitor Handover Server
Wireless-WCS:task57=Configure Ethernet Switch Ports
Wireless-WCS:task58=Configure Ethernet Switches
Wireless-WCS:task59=Monitor Interferers
Wireless-WCS:task60=Device Reports
Wireless-WCS:task61=Network Summary Reports
Wireless-WCS:task62=Compliance Reports
Wireless-WCS:task63=CleanAir Reports
Wireless-WCS:task64=Report Launch Pad
Wireless-WCS:task65=Run Reports List
Wireless-WCS:task66=Saved Reports List
Wireless-WCS:task67=Report Run History
Wireless-WCS:task68=Automated Feedback
Wireless-WCS:task69=TAC Case Attachment Tool
Wireless-WCS:task70=Ack and Unack Security Index Issues
Wireless-WCS:task71=View Security Index Issues
Wireless-WCS:task72=Monitor Media Streams
Wireless-WCS:task73=Voice Diagnostics
Wireless-WCS:task74=ContextAware Reports
Thanks,
Kyle -
WLC 5508 (7.4.100) Coverege Hole Detection
Hi,
After upgrading version 7.4.100, I start to receive logs"Coverege Hole Detection" continiously
Before upgrade logs come very rare
Also coverege areas decrease
I cannot rolled back to previous version, because I start to use AP1600 series
Is it possible to use AP1600 with previous versions other then 7.4.100?
Please helpHello Recep,
As per your query i can suggest you the following solution-
This alarm message is raised when a client Signal-to-Noise Ratio (SNR) falls below the SNR threshold value for the particular radio. 12 is the default SNR threshold value for coverage hole detection.
The coverage hole detection and correction algorithm determine if a coverage hole exists when clients’ SNR levels pass below a given SNR threshold. This SNR threshold varies based on two values: AP transmit power and the controller coverage profile value.
In detail, the Client SNR threshold is defined by each AP’s transmit power (represented in dBm), minus the constant value of 17dBm, minus the user configurable Coverage profile value (this value is defaulted to 12 dB).
Client SNR Cutoff Value (|dB|) = [AP Transmit Power (dBm) – Constant (17 dBm) – Coverage Profile (dB)]
This user configurable coverage profile value can be accessed this way:
1.In the WLC GUI, go to the main heading of Wireless and select the Network option for the WLAN standard of choice on the left side (802.11a or 802.11b/g). Then, select Auto RF in the upper right of the window.
2.In the Auto RF Global parameters page, find the Profile Thresholds section. In this section, you can find the Coverage (3 to 50 dbm) value. This value is the user configurable coverage profile value.
3.This value can be edited to influence the Client SNR threshold value. The other way to influence this SNR threshold is to increase the transmit power and compensate the coverage hole detection.
For more information please refer to the link-
http://www.cisco.com/en/US/products/ps6366/products_qanda_item09186a008082c464.shtml
Hope this will help.
Maybe you are looking for
-
Can somebody tell me why my reminders no longer work correctly on 7.1 update on iPhone five every time I post a reminder it would delete the time and date of the reminder and my reminders do not go off.
-
Won't appear on desktop/iTunes, but shows in System Profiler as connected
Hope someone can help... I've been through all the steps. My Nano is connected, charging etc. But I've tried with two computers and although it shows up in the System Profiler as connected to my USB port, it will not show up on the desktop or in iTun
-
Error while running the Dynamically generated forms example
HI, I am getting an error when trying to run the web dynpro example "Interactive Forms Integration into Web Dynpro for Java". I am not able to trace out what exactly is going wrong. So kindly help me in this issue. com.sap.tc.webdynpro.pdfobject.core
-
I need to re download a program
I purchase Photoshop Elements 10 & Premier Elements 10 in Feb, 2012. According to policy, I can re download the programs, which I need to do for a new computer, but cannot find where to do this. In "My Account', I have the SNs of all my products, but
-
Hi, I was wondering how I could use the JSObject to flatten pages via JavaScript using the Adobe SDK. Below is the sample that I'm using. CAcroApp acroApp = new AcroAppClass(); CAcroAVDoc avDoc = new AcroAVDocClass(); if(!avDoc.Open (FORM_NAME, "")