Cisco clean air licensing

With the plus license on WCS, you can locate the interferer and see the statistics through time with graphs, etc MSE will allow to track interferers in "real-time" not exactly real, but close enough on the map.

I know it's possible but I wonder if it is advisable to configure multicast on wireless network. We have 3 WLC with 7. They want to enable multicast for applications like Apple Bonjour and other programs and also for streaming video. I am of the opinion it's not the greatest of ideas.

I see people enabling multicast but not on the scale with the user base we have. CleanAir is a separate chipset in the AP and detects interferences with a dedicated hardware, it can then not have any impact on AP performance at all. Now regarding multicast Let's first explain why it's generally not a good idea and finish with possible alternatives. Over the air, a multicast is pretty much like a broadcast. In the sense that if an AP sends a multicast, it keeps the air busy for all the clients of that AP, so regardless of the amount of clients subscribed to the stream that AP, the performance will be the same.

Because of the horrible consequences if it was the case, the multicast frames are not ACKed by anyone. That's the only way to know if there has been a collision or not. So because there is no ACK, there is no retransmission. And because wireless is a shared medium, collisions do occur as normal part of the medium. So even in good conditions, there will be a bit of packet loss.

In case you have external interferers or high number of clients, then the amount of lost packets will drastically increase and the stream performance is then not acceptable. Furthermore, because the AP doesn't know how far are the multicast-subscribed clients located, it cannot know if the clients will be able to receive the frame at the maximum data rate 54, or Mbps.

Maybe one of the subscribed client is at the border of the coverage cell and can only transmit at 24Mbps due to the distance. When doing unicast, this is acceptable because close clients get their data at mbps and only the far away client is talked to at 24Mbps but in a multicast, Which is often between 1 and 24Mbps but rarely more.

The multicast is still multicast over wired : so only the APs having subscribed clients will received the data. But over the air, the AP unicasts the stream to every subscribed clients. Advantages : Retransmission are possible, data is acknowledged, data is sent at the fastest rate acceptable for that particular client. Inconvenient's : If you have a lot of subscribed clients per AP it might not be good to unicast to all of them from a performance perspective.

Direct Stream usually performs better than normal multicast with 7 or less subscribed client per AP. In this case, you can configure a much higher data rate as "mandatory" so that the multicast stream is sent more rapidly. But be aware that this prevents transmission of the stream to clients that would be a bit far from their AP. Out of experience, the 2. On 5Ghz, it's quite feasible to have a good stream using the "normal" multicast.

I would like to know more on the statement called " This is an opportunity to learn about the last generation of access points from Cisco ". Does this means there will be no more new models? T he "last" in that sentence means "most recent" and not "there won't be any new one after this one". These 3 features are software features available also on non-cleanair AP models.

So those feature stay identical on Cleanair AP models. No change at all. Same goes for the I understand that the spectrum analysis runs in parallel to the regular AP duties so that client connectivity can be maintained. Can you explain the clock cyles involved in simple terms with regards to the AP going off-channel to detect interferers?

Also how this impacts clients, or if there is a hold-off period when the AP is busy? CleanAir is run in parallel with standard client serving processes, so no need for the AP to go off-channel. Interferers will be detected only for the same channel for which you are serving clients, if you are using a local mode AP. If using a monitor mode AP, then the AP will cycle through different channels without serving clients and detect interferers on multiple channels. We can think of CleanAir as of a parallel feature set, but separate with regards to the previous "standard" features of other APs.

For locating interferers, a CleanAir AP in local mode will definitely help to locate interferer, but only on the channel on which it is serving clients. By downloading the recovery image to the AP and let it reload after that. The APs with internal antennas ,,i have a dome-like coverage, so they are designed for ceiling placement. Imagine a dome on an AP placed on a wall, perpendicular to floor, the coverage will be awesome on the floor above and below the AP but 20 meters from the AP on a horizontal plane, you'll get nothing.

For wall placement, a e with antennas correctly oriented is then better. The height of your ceiling is a bit of a concern and that means that the coverage on the ground will not be so exciting. However, it would sound like ceiling placement is recommended rather than wall placement since that would mean higher number of obstacles all the book shelves. The number "20" was a random value. I actually never measured how many meters the coverage goes when the AP is placed on a wall because it's not supposed to I don't know the maximum heigth that people put the AP and still had good coverage.

You can also read the questions he answered during the live event in this FAQ Document. Buy or Renew. Find A Community. Cisco Community. Thank you for your support! We're happy to announce that we met our goal for the Community Helping Community campaign! Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

Showing results for. Search instead for. Did you mean:. All Community This category This board. Labels: Aironet Access Points.

Vinay Sharma. Cisco has taken the bold step to integrate SI directly into the Wi-Fi silicon and infrastructure solution. Unlike previous RRM solutions that could only understand and adapt to other Wi-Fi devices, SI opens the path for a second-generation RRM solution that is fully aware of all the users of the wireless spectrum, and is able to optimize performance in the face of these varied devices.

The first important point that needs to be made is that from a design perspective. Designing for Wi-Fi coverage is the same with both. CleanAir or interference identification processes are a passive process. CleanAir is based on the receiver, and for classification to function, the source needs to be loud enough to be received at 10 dB above the noise floor.

If your network is deployed in such a way that your clients and APs can hear one another, then CleanAir can hear well enough to alert you to troubling interference within your network. The coverage requirements for CleanAir are detailed in this document. There are some special cases depending on the CleanAir implementation route you ultimately choose. The technology has been designed to compliment the current best practices in Wi-Fi deployment.

This includes the deployment models of other widely used technologies such as Adaptive wIPS, Voice, and location deployments. Refer to Cisco Technical Tips Conventions for more information on document conventions. CleanAir is a system, not a feature. CleanAir software and hardware components provide the ability to accurately measure Wi-Fi Channel quality and identify non-Wi-Fi sources of channel interference.

This cannot be done with a Standard Wi-Fi chipset. In order to understand design goals and requirements for successful implementation it is necessary to understand how CleanAir works at a high level.

But, it is a completely new technology in that this is an enterprise-based distributed spectrum analysis technology. As such, it is similar to Cisco Spectrum Expert in some respects but very different in others. The components, functions, and features are discussed in this document. The e designates External Antenna, the I designates Internal antenna. Both are fully functional next generation The Spectrum Analysis hardware is directly integrated into the chipset of the radio.

This addition added over K logic gates to the radio silicon, and has provided exceptionally close coupling of the features. There are many other traditional features, which have been added or improved with these radios. But, it is beyond the scope of this document and these are not covered here. Suffice it is to say, that on its own without CleanAir the series APs pack a lot of features and performance into an attractive and robust enterprise AP. This provides user interfaces for advanced spectrum capabilities such as historic charts, tracking interference devices, location services and impact analysis.

The Cisco WCS provides advanced user interfaces for CleanAir that include feature enabling and configuration, consolidated display information, historic Air Quality records and reporting engines.

The Cisco MSE is required for location and historic tracking of interference devices, and provides coordination and consolidation of interference reports across multiple WLCs. However, it is much more than just a spectrum analyzer. All of this allows extreme accuracy and scales for large numbers of like interference sources, with no penalty in throughput of user traffic. The Wi-Fi chipset is always on line. SAgE scans are performed once per second. If a Wi-Fi preamble is detected, it is passed through to the chipset directly and is not affected by the parallel SAgE hardware.

SAgE is very fast and accurate. Even in a busy environment, there is more than enough scan time to accurately assess the environment. Why does RBW matter? If you need to count and measure the difference between several Bluetooth radios hopping with narrow signals at hops per second, you need to separate different transmitters hops in your sample if you want to know how many there are. This takes resolution. Otherwise, it would all look like one pulse. SAgE does this, and it does this well.

This increases the speed, which allows you to process the data stream in near real time. Near real time means there is some delay, but it is so minimal it takes a computer to measure it. Formats for these messages are listed here:. The Interference Device Report IDR is a detailed report that contains information about a classified interference device.

An IDR is produced for each classified device. An individual radio can track a theoretical infinite number of devices similar to what the Spectrum Expert card does today. Cisco has tested hundreds with success. However, in an enterprise deployment there are hundreds of sensors, and a practical reporting limit is enforced for scaling purposes.

One exception to this rule is the case of the security interferer. A security IDR is always given precedence regardless of severity. Any interference source that is classified can be chosen for a security trap alert.

This sends a security trap to the WCS or another configured trap receiver based on the type of interferer selected. This trap does not contain the same information as an IDR. It is simply a way to trigger an alarm on the presence of the interferer. When an interferer is designated as a security concern, it is marked as such at the AP and is always included in the ten devices that are reported from the AP regardless of severity.

IDR messages are sent in real time. On detection the IDR is marked as device up. If it stops a device down message is sent. An update message is sent every 90 seconds from the AP for all devices currently being tracked. This allows for status updates of tracked interference sources and an audit trail in the event an up or down message was lost in transit.

Air Quality is a rolling average that evaluates the impact of all classified interference devices against a theoretical perfect spectrum. AQ reports are sent independently for each radio. The default is 15 minutes minimum and can be extended to 60 minutes on the WCS. With CleanAir, a different approach is taken. We can also see and understand energy that is For each classified device a severity index is calculated see the Severity section , a positive integer between 0 and — with being the most severe.

AQ then is a measurement of the impact of all classified devices on the environment. There are two AQ reporting modes defined: normal and rapid update. Normal mode is the default AQ reporting mode.

When a request is received, the Controller instructs the AP to change the default AQ reporting period temporarily to a fixed fast update rate 30 sec , which allows near real-time visibility into AQ changes at the radio level.

Multiple entries for each detected device is attached to the report, ordered by device severity. The format for these entries is here:. A Monitor Mode AP collects information for all channels configured under scan options. When an AQ report is received, the Controller performs required processing and store it in the AQ database. While similarities might exist, this is a fresh use of the technology and many new concepts are presented in this section.

Cisco Spectrum Expert introduced technology that was able to positively identify non-Wi-Fi sources of radio energy. This permitted the operator to focus on information such as duty cycle and operating channels, and make an informed decision about the device and its' impact on their Wi-Fi network. Spectrum Expert allowed the operator to then lock the chosen signal into the device finder application and physically locate the device by walking around with the instrument.

The design goal of CleanAir is to go several steps further, by essentially removing the operator further from the equation and automating several of the tasks within system management. Because you can know what the device is and what it is affecting, better decisions can be made at a system level on what to do with the information.

Several new algorithms have been developed to add intelligence to the work that was started with Cisco Spectrum Expert. There are always cases that require physically disabling an interference device, or making a decision about a device and impact that involves humans.

The overall system should heal what can be healed and avoid what can be avoided so that the effort to reclaim affected spectrum can be a proactive exercise instead of a reactive one. Tight silicon integration with the Wi-Fi radio allows the CleanAir hardware to listen between traffic on the channel that is currently being served with absolutely no penalty to throughput of attached clients.

That is line rate detection without interrupting client traffic. There are no CleanAir dwells processed during normal off channel scans. Off channel scans are used for system maintenance such as RRM metrics and rogue detection. The frequency of these scans is not sufficient to collect back to back dwells required for positive device classification, so information gleaned during this scan is suppressed by the system.

Increasing the frequency of off channel scans is also not desirable, as it takes away from time that the radio services traffic. What does this all mean? In normal enterprise densities there should be plenty of APs on the same channel, and at least one on each channel assuming RRM is handling channel selection.

An interference source that uses narrow band modulation operates on or around a single frequency is only detected by APs that share that frequency space. If the interference is a frequency hopping type uses multiple frequencies — generally covering the whole band it is detected by every AP that can hear it operating in the band. A minimum of three detection points is required for location resolution. In 5 GHz, there are 22 channels operating in the United States, thus detection density and sufficient location density is less likely.

However, if interference is operating on a channel occupied by a CleanAir AP, it detects it and alert or take steps to mitigate if those features are enabled.

Most interference seen is confined to the 5. This is where consumer devices live and hence where it is most likely to be encountered. You can limit your channel plan to force more APs to that space if you desire. However, it is not really warranted. Remember, interference is only a problem if it is using spectrum you need. If your AP is not on that channel, it is likely that you still have plenty of spectrum left to move into.

What if the need to monitor all of 5 GHz is driven by security policies? See the Monitor Mode AP definition below. It provides full time scanning of all channels using 40 MHz dwells. CleanAir is supported in monitor mode along with all other current monitor mode applications including Adaptive wIPS and location enhancement. In a dual radio configuration this ensures that all bands-channels are routinely scanned. In a scenario as mentioned above where security is a primary driver, it is likely that Adaptive wIPS would also be a requirement.

There are some distinct differences in how some of the features are supported when deploying as an overlay solution. Thisis covered in the deployment models discussion in this document. The connection between Spectrum Expert and the remote AP bypasses the controller on the data plane.

The AP remains in contact with the controller on the control plane. This mode allows viewing of the raw spectrum data such as FFT plots and detailed measurements. All CleanAir system functionality is suspended while the AP is in this mode, and no clients are served. This mode is intended for remote troubleshooting only. It can be supported in VMWare. In CleanAir the concept of Air Quality was introduced. Air Quality is a measurement of the percentage of time that the spectrum at a particular observed container radio, AP, Band, Floor, Building is available for Wi-Fi traffic.

AQ is a function of the severity index, which is calculated for each classified interference source. The Severity index evaluates each non- Wi-Fi devices over the air characteristics and calculates what percentage of time the spectrum is not available for Wi-Fi with this device present.

Air Quality is a product of the severity indexes of all classified interference sources. Anything that is left is theoretically available to the Wi-Fi network for traffic. This is theoretical because there is a whole science behind measuring the efficiency of Wi-Fi traffic, and this is beyond the scope of this document.

However, knowing that interference is or is not impacting that science is a key goal if your plan is success in identifying and mitigating pain points. What makes an interference source severe? How do I use this information to manage my network? These questions are discussed in this document.

Energy in the channel that is seen by an This is determined by clear channel assessment CCA. Wi-Fi uses a listen before talk channel access method for contention free PHY access. The Duty Cycle is the on time of a transmitter. This determines how persistent an energy is in the channel.

The higher the duty cycle the more often the channel is blocked. In the graph in this figure you can see that as the signal power of the interference decreases, the resulting AQI increases. Technically, as soon as the signal falls below dBm, the AP no longer is blocked. You do need to think abut the impact this has on clients in the cell. AQ rapidly increases once the signal power falls below dBm. So far there are two of the three major impacts of interference defined in the severity based Air Quality metric:.

This is the type of signal most often used in demonstrations of the affect of interference. It is easy to see in a spectrogram, and it has a very dramatic affect on the Wi-Fi channel. This does happen in the real world too, for example in analog video cameras, motion detectors, telemetry equipment, TDM signals, and older cordless phones.

In fact, a lot of the interference that is encountered is interference of this type: variable to minimal. Here it gets a bit tougher to call the severity. Examples of interference of this type are Bluetooth, Cordless Phones, wireless speakers, telemetry devices, older For instance, a single Bluetooth headset does not do much damage in a Wi-Fi environment. However, three of these with overlapping propagation can disconnect a Wi-Fi phone if walked through.

In addition to CCA, there are provisions in the Then you add to this various QOS mechanisms. All of these media reservations are used by different applications to maximize airtime efficiency and minimize collisions. This can be confusing. However, because all the interfaces on the air participate and agree on the same group of standards, it works very well. What occurs to this ordered chaos when you introduce a very specific energy that does not understand the contention mechanisms or for that matter does not even participate in CSMA-CA?

Well, mayhem actually, to a greater or lesser degree. It depends how busy the medium is when the interference is experienced. You can have two identical signals in terms of the Duty Cycle as measured in the channel and amplitude, but have two totally different levels of interference experienced on a Wi-Fi network. A fast repeating short pulse can be more devastating to Wi-Fi than a relatively slow repeating fat one.

Look at an RF jammer, which effectively shuts down a Wi-Fi channel and registers very little duty cycle. In order to do a proper job evaluating, you need a better understanding of the minimum interference interval introduced.

The minimum interference interval accounts for the fact that in-channel pulses interrupt Wi-Fi activity for some period longer than their actual duration, due to three effects:.

If a new packet arrives to be transmitted mid-interference, the Wi-Fi device must additionally back off using a random value between zero and CWmin. This case is typical for lightly loaded networks, where the interference starts before the Wi-Fi packet arrives to the MAC for transmission. If the Wi-Fi device is already transmitting a packet when the interference burst arrives, the whole packet must be retransmitted with the next-higher value of CW, up to CWmax. This case is typical if the interference starts second, partially through an existing Wi-Fi packet.

If the back off time expires without a successful retransmission, then the next back off is double the previous. This continues with unsuccessful transmission up to CWmax is reached or TTL is exceeded for the frame. Therefore, the next best thing is to create a metric that remains constant as a reference point. This is what Severity does.

It measures the impact of a single interferer against a theoretical network, and maintains a constant report of severity regardless of the underlying utilization of the network. This gives us a relative point to look at across network infrastructures. In lightly loaded networks it is quite possible to have levels of non- Wi-Fi interference that go unnoticed by the users and administrators.

This is what leads to trouble in the end. The nature of wireless networks is to become busier over time. Success leads to faster organizational adoption, and to new applications being committed. If there is interference present from day one, it is quite likely that the network have a problem with this when it becomes busy enough. When this happens it is difficult for people to believe that something that has been fine seemingly all along is the culprit.

AQ is used to develop and monitor a baseline spectrum measurement and alert on changes indicating a performance impact. You can also use it for long term trend assessment through reporting. Severity is used to evaluate interference impact potential and prioritize individual devices for mitigation.

Non Wi-Fi transmitters are less than friendly when it comes to unique characteristics that can be used to identify them. That is essentially what made the Cisco Spectrum Expert solution so revolutionary. Now with CleanAir there are multiple APs that potentially all hears the same interference at the same time. Correlating these reports to isolate unique instances is a challenge that had to be solved to provide advanced features, such as location of interference devices, as well as an accurate count.

Because an analog video device does not have a MAC address or, in several cases, any other identifying digital tag an algorithm had to be created to identify unique devices being reported from multiple sources. The function of comparing and evaluating PMACs is called merging. The PMAC is not exposed on customer interfaces. Only the results of merging are available in the form of a cluster ID. This merging is discussed next. Before the assignment of a PMAC and subsequent merging, there is only the device classification, which can be misleading.

PMAC gives us a way to identify individual interference sources, even if they do not have any logical information that can be used such as an address. There are several APs all reporting a similar device. The next step is to combine the PMACs that are likely the same source device to a single report for the system.

This is what merging does, consolidating multiple reports to a single event. Merging uses spatial proximity of the reporting APs. If there are six similar IDRs with five from APs on the same floor, and another one from a building a mile away, it is unlikely this is the same interferer. Once a proximity is established, a probability calculation is run to further match the distinct IDRs that belong and the result is assigned to a cluster.

A cluster represents the record of that interference device and captures the individual APs that are reporting on it. Subsequent IDR reports or updates on the same device follow the same process and instead of creating a new cluster are matched to an existing one. In a cluster report, one AP is designated as the Cluster Center. This is the AP that hears the interference the loudest.

The MSE has this view. In an MMAP overlay model you do not have this information. MMAPs are passive devices and do not transmit neighbor messages. In order to do this, you also need the MSE that knows about the system map and can provide merging functions.

More detail on the different modes of operation as well as practical deployment advice is covered in the deployment models section. You can use the neighbor list created by the received neighbor messages for the MMAP as part of the merging information. Determining the location of a radio transmitter in theory is a fairly straightforward process. You sample the received signal from multiple locations and you triangulate based on the received signal strength.

On a Wi-Fi network clients are located and Wi-Fi RFID tags with good results as long as there is a sufficient density of receivers and adequate signal to noise ratio. Wi-Fi clients and tags send probes on all supported channels regularly. This ensures that all APs within range hear the client or TAG regardless of the channel it is serving.

This provides a lot of information to work with. We also know that the device tag or client subscribes to a specification that governs how it operates. Therefore, you can be certain that the device is using an omni-directional antenna and has a predictable initial transmit power.

Wi-Fi devices also contain logical information that identifies it as a unique signal source MAC address. Note: There is no guarantee of accuracy for location of non- Wi-Fi devices. Accuracy can be quite good and useful. However, there are a lot of variables in the world of consumer electronics and unintentional electrical interference.

Any expectation of accuracy that is derived from current Client or Tag location accuracy models does not apply to non- Wi-Fi location and CleanAir features. Non Wi-Fi interference sources pose a special opportunity to get creative. For instance, what if the signal you are trying to locate is a narrow video signal 1 MHz that is only affecting one channel?

However, in 5 GHz this is more difficult since most non-Wi-Fi devices only operate in the 5. This sounds bad, but remember if you are not detecting it, then it is not interfering with anything. Therefore, is really not a problem from a standpoint of interference.

This is however an issue if your deployment concerns extend to security. If your only concern is securing the operating space you are using, then you can also limit the channels available in DCA and force increased density in the channel ranges you wish to cover.

The RF parameters of non- Wi-Fi devices can and do vary widely. An estimate has to be made based on the type of device that is being detected. The starting RSSI of the signal source needs to be known for good accuracy. You can estimate this based on experience, but if the device has a directional antenna the calculations will be off. If the device runs on battery power and experiences voltage sags or peaks as it operates, this will change how the system sees it.

A different manufacturer's implementation of a known product might not meet the expectations of the system. This will affect the calculations. Fortunately, Cisco has some experience in this area, and non-Wi-Fi device location actually works quite well.

The point that needs to be made is that the accuracy of a non- Wi-Fi device location has a lot of variables to consider, accuracy increases with power, duty cycle, and number of channels hearing the device. This is good news because higher power, higher duty cycle, devices that impact multiple channels is generally what is considered to be severe as far as interference to the network goes.

Cisco CleanAir APs, first and foremost, are access points. What this means is that there is nothing inherently different about deploying these APs over deploying any other currently shipping AP. What has changed is the introduction of CleanAir. These are only available in a Greenfield installation and configured off by default. This section will deal with the sensitivity, density and the coverage requirements for good CleanAir functionality.

These are not all that different from other established technology models such as a Voice, Video, or Location deployment. CleanAir is a passive technology.

All it does is hear things. Because an AP hears a lot farther than it can effectively talk this makes it a simple task to do a correct design in a Greenfield environment. Understanding how well CleanAir hears, and how classification and detection works, will give you the answers you need for any configuration of CleanAir.

CleanAir depends on detection. The detection sensitivity is more generous than Wi-Fi throughput requirements with a requirement of 10 dB SNR for all classifiers, and many operable down to 5 dB. In most conceivable deployments where coverage is pervasive, there should not be any issues in hearing and detecting interference within the network infrastructure. How this breaks down is simple. Raising the noise floor above this level creates a slight degradation in detection dB for dB.

For design purposes it is worth adding a buffer zone by setting the minimum design goal to say This will provide sufficient overlap in most conceivable situations. Note: Bluetooth is a good classifier to design for because it represents the bottom end power wise in devices you would be looking for. Anything lower generally does not even register on a Wi-Fi network. It is also handy and readily available to test with because it is a frequency hopper and will be seen by every AP, regardless of mode or channel in 2.

It is important to understand your interference source. For instance Bluetooth. Here are multiple flavors of this in the market presently and the radios and specification have continued to evolve as most technologies do over time.

A Bluetooth headset that you would use for your cell phone is most likely a class3 or class2 device. This operates on low power and makes ample use of adaptive power profiles, which extends battery life and reduces interference. A Bluetooth headset will transmit frequently on paging Discovery mode until associated. Then it will go dormant until needed in order to conserve power.

CleanAir will only detect an active BT transmission. No RF, then nothing to detect. Therefore, if you are going to test with something, make sure it is transmitting. Play some music across it, but force it to transmit. Spectrum Expert Connect is a handy way to verify if something is, or is not transmitting and will end a lot of potential confusion.

CleanAir was designed to compliment what is largely considered a normal density implementation. This definition of Normal continues to evolve. For instance, just five years ago APs on the same system was considered a large implementation. In a lot of the world — it still is.

Numbers of 3,, APs with many hundreds of them sharing direct knowledge through RF propagation are routinely seen. In most deployments it is hard to image a coverage area that will not have at least three APs within ear shot on the same channel in 2.

If there are not, then location resolution suffers. Add a Monitor Mode AP and use the guidelines. In locations where there is minimal density location resolution is likely not supported. But, you are protecting the active user channel extremely well. Also in such an area, you are generally not talking about a lot of space so locating an interference source does not pose the same problem as a multifloor dwelling. Deployment considerations come down to planning the network for desired capacity, and ensuring that you have the correct components and network paths in place to support CleanAir functions.

Make sure to understand PMAC and the merging process well. If a network does not have a good RF design, the neighbor relations is generally affected. This affects CleanAir performance. If you plan to install CleanAir MMAPs as an overlay to an existing network there are some limitations you need to keep in mind. CleanAir 7. There are limits in the number of MMAPs that can be supported. The maximum number of MMAPs is a function of memory.

The controller must store AQ details for each monitored channel. Use the table below for design guidance. Always refer to the current release documentation for current information by release. Note: The numbers quoted for clusters merged interference reports and device records individual IDR Reports before merging are generous and highly unlikely to be exceeded in even the worst environments.

Suppose you simply want to deploy CleanAir as a sensor network to monitor and be alerted about non- Wi-Fi interference. This of course depends on your coverage model. Quite a bit actually since you are strictly listening. The coverage area is far greater than if you also had to communicate and transmit.

How about you visualize this on a map you can use any planning tool available following a similar procedure as described below? If you have WCS and already have the system maps built, then this is an easy exercise. Use the planning mode in theWCS maps. In the right hand corner of the WCS screen use the radio button to select Planning Mode, then click go. Select the AP type. The heat map populates.

Note: Keep in mind that this is a predictive analysis. The accuracy of this analysis depends directly on the accuracy of the maps used to create it. It is beyond the scope of this document to provide a step by step instruction on how to edit maps within a WCS. All of these applications work with CleanAir enabled APs. For location services ensure that you review and understand the deployment requirements for your technology.

All of these solutions are complimentary with CleanAir design goals. This question pertains to this use case:. This installation would result in indiscriminate coverage of the band. You could well end up with a channel or several that has no CleanAir coverage at all. However with the base installation, you would be using all of the channels available.

Assuming RRM is in control recommended it is entirely possible that all of the CleanAir APs could be assigned to the same channel in a normal installation. You spread them out to try to get the best spatial coverage possible, and that actually increases the odds of this. You certainly can deploy a few CleanAir APs in with an existing installation.

It is an AP and would function fine from a client and coverage standpoint. CleanAir functionality would be compromised and there is no way to really guarantee what the system would or would not tell you regarding your spectrum.

There are far too many options in density and coverage which can be introduced to predict. What would work? AQ would be valid for the reporting radio only. This means it is only relevant for the channel that it is serving, and this could change at any time. Interference alerts and zone of impact would be valid. However, any location derived would be suspect. Best to leave that out all together and assume closest AP resolution.

Mitigation strategies would be ill-advised to operate because most of the APs in the deployment would not operate the same way.