Cómo cambiar los canales WiFi para evitar interferencias

Esta guía técnica exhaustiva proporciona a los gerentes de TI, arquitectos de red y directores de operaciones de recintos un enfoque definitivo y paso a paso para identificar las fuentes de interferencia WiFi y cambiar estratégicamente los canales WiFi para eliminarlas. Cubre la planificación de bandas de 2.4 GHz y 5 GHz, el análisis de espectro, la gestión de recursos de radio (Radio Resource Management) y las consideraciones de DFS, basándose en los estándares IEEE 802.11 y escenarios de implementación reales. La implementación de estas estrategias ofrece mejoras medibles en el rendimiento de la red, la estabilidad del cliente y el ROI de la infraestructura sin requerir gastos de capital en nuevo hardware.

📖 7 min de lectura📝 1,647 palabras🔧 2 ejemplos prácticos❓ 3 preguntas de práctica📚 9 definiciones clave

Escuchar esta guía

Ver transcripción del podcast

Welcome back to the Purple enterprise networking briefing. I'm your host, and today we are tackling one of the most persistent and costly issues in wireless networking: WiFi interference. If you're an IT director managing a hotel, a stadium, or a large retail chain, you know that poor WiFi isn't just an IT problem — it's a business problem. It impacts guest experience, disrupts mobile point-of-sale systems, and generates a massive volume of helpdesk tickets. Today, we're going to break down exactly how to strategically change WiFi channels to eliminate interference, optimise your RF environment, and get the most out of your infrastructure investment.

Let's start with the context. Why is channel planning so critical? The radio frequency spectrum is a shared medium. When multiple devices try to talk at the same time on the same frequency, they interfere with each other. This interference generally falls into two buckets: Co-Channel Interference, or CCI, and Adjacent-Channel Interference, or ACI.

CCI happens when access points or clients are on the exact same channel. The 802.11 protocol handles this relatively well using a mechanism called CSMA/CA — Carrier Sense Multiple Access with Collision Avoidance. Essentially, devices listen before they talk. They take turns. However, if too many devices are on the same channel, they spend all their time waiting for clear airtime, which means throughput drops and latency spikes. It's essentially a congestion issue — not unlike rush-hour traffic on a motorway.

ACI, on the other hand, is far more destructive. This occurs when devices are on overlapping frequencies — say, channel 2 and channel 4 in the 2.4 GHz band. Because the transmissions overlap but aren't perfectly aligned, the protocol can't decode them. It just sees them as pure RF noise. This raises the noise floor, causes packet collisions, and forces constant retransmissions. In a busy venue, ACI can reduce effective throughput by 60 to 70 percent.

Now, let's get into the technical deep-dive, starting with the 2.4 GHz band. The 2.4 GHz band is excellent for range and wall penetration, which is why it remains popular for IoT devices and legacy hardware. But it is severely spectrum-constrained. The entire band spans roughly 83.5 megahertz. A standard 20 MHz WiFi channel takes up around 22 MHz when you account for the spectral mask. Do the maths, and you'll see there are only three truly non-overlapping channels: Channel 1, Channel 6, and Channel 11.

This is a hard rule. If you are deploying multiple access points, you must only use channels 1, 6, and 11. Full stop. If you try to be clever and use channel 3 because it looks empty on your spectrum scan, you are guaranteeing ACI for yourself and your neighbours. I see this mistake regularly in deployments that have been configured by well-meaning but under-briefed engineers. Furthermore, ensure your channel widths on 2.4 GHz are strictly set to 20 MHz. Some controllers default to 40 MHz on 2.4 GHz, which is a configuration error in any multi-AP deployment.

Now, let's look at the 5 GHz advantage. The 5 GHz band gives us significantly more spectrum and many more non-overlapping channels. This is where you want the bulk of your enterprise traffic. The band is divided into UNII sub-bands — UNII-1, UNII-2, UNII-2e, and UNII-3 — providing access to over 20 non-overlapping 20 MHz channels in most regulatory domains. However, there are two key considerations: channel width and DFS.

First, channel width. Vendors love to market gigabit WiFi speeds, which are achieved by bonding multiple 20 MHz channels together into 40, 80, or even 160 MHz channels. While this gives a single client impressive throughput, it drastically reduces the number of independent channels available for your venue. In a high-density environment like a conference centre, a stadium, or a busy hospital ward, using 80 MHz channels will cause massive Co-Channel Interference. The best practice? Default to 20 MHz channel widths in high-density deployments. You prioritise overall network capacity and stability over peak single-client speed. Think of it this way: it's better to have 20 lanes of traffic moving at 60 miles per hour than 5 lanes moving at 100 miles per hour — the aggregate throughput is far greater.

Second, DFS — Dynamic Frequency Selection. Many 5 GHz channels share spectrum with radar systems, such as weather radar and aviation radar. If an access point on a DFS channel detects a radar signal, it must legally vacate that channel immediately and remain off it for a period of time. This causes client disconnections and what we call channel churn. If your venue is near an airport, a weather station, or a military installation, you need to carefully audit your DFS channel usage or exclude those channels entirely from your channel plan.

So, what does the implementation look like in practice? Let me walk you through the key steps.

Step one: never guess. Before you touch a single configuration, use a spectrum analyser to get an empirical baseline of your RF environment. This could be a dedicated hardware tool or a software-based survey tool integrated into your wireless LAN controller. You need to identify rogue access points, neighbouring networks, and non-WiFi interferers like microwave ovens, Bluetooth devices, and DECT phones. Establish your baseline noise floor on both bands.

Step two: formulate your channel plan. For 2.4 GHz, restrict the channel pool to 1, 6, and 11 only, and set widths to 20 MHz. If your AP density is very high, consider disabling the 2.4 GHz radio on alternating APs in a checkerboard pattern to reduce Co-Channel Interference. For 5 GHz, use 20 MHz widths in high-density areas. Evaluate DFS channels carefully based on your location. Spread your APs across as many unique channels as possible.

Step three: configure your access points. Most enterprise wireless LAN controllers offer Radio Resource Management, or RRM, which dynamically adjusts channel and power settings. While this is a useful baseline, in highly complex environments — a multi-floor hotel, a stadium with 50,000 concurrent devices, a busy transport hub — a manual, static channel plan based on a predictive site survey often yields the most stable and predictable results. Automated algorithms can sometimes react to transient interference events and cause unnecessary channel changes, which disrupts clients.

And critically: don't forget transmit power. Channel planning and power tuning are inseparable. If your access points are transmitting at maximum power, their RF cells will overlap significantly, causing Co-Channel Interference regardless of how well you've planned your channels. Reduce transmit power to create smaller, more efficient cell sizes. In a dense deployment, aim for access point transmit power in the range of 10 to 14 dBm on 5 GHz.

Step four: validate and monitor. After applying your changes, conduct a post-implementation walkthrough survey to verify the new channel plan is working as intended. Monitor your key performance indicators — retry rates, airtime utilisation, client association counts per AP, and roaming behaviour. A good WiFi analytics platform will surface these metrics clearly and alert you to emerging issues before they become complaints.

Now, let's move to some common pitfalls and a rapid-fire Q&A.

Pitfall one: 'My clients have strong signal but terrible throughput.' This is classic Co-Channel Interference. Your access points are likely transmitting at too high a power, causing significant cell overlap, or your channel widths are too wide. Reduce transmit power and drop channel widths to 20 MHz to free up airtime.

Pitfall two: 'Clients keep dropping off the network randomly, particularly in one zone.' Check your DFS event logs immediately. Your access points may be detecting radar and jumping channels. Identify which DFS channels are triggering and exclude them from your configuration for that zone.

Pitfall three: 'We deployed Auto-RF and the channel plan keeps changing.' This is channel churn. Your RRM algorithm is reacting to transient interference events. Constrain the Auto-RF sensitivity settings or switch to a static channel plan based on your survey data.

Quick question: should I use WiFi 6E's 6 GHz band to avoid all of this? Absolutely, if your client devices support it. The 6 GHz band is pristine spectrum with no legacy devices and no DFS requirements. However, it has shorter range due to higher frequency attenuation, so it requires denser AP deployments. It's the right long-term direction, but it doesn't replace the need for proper 2.4 and 5 GHz channel planning for your existing estate.

To summarise today's briefing: optimising your WiFi channels is fundamentally a zero-cost infrastructure upgrade that delivers immediate, measurable returns. By enforcing the 1-6-11 rule on 2.4 GHz, managing channel widths intelligently on 5 GHz, tuning transmit power, and validating with proper tooling, you can dramatically reduce helpdesk tickets, improve application performance, and extend the lifecycle of your existing hardware.

The key takeaways are these: interference is a spectrum management problem, not a hardware problem. You don't need to buy new access points — you need to configure the ones you have correctly. Prioritise capacity over peak speed in high-density environments. And always, always base your decisions on empirical spectrum data, not assumptions.

For detailed implementation guides, architecture references, and WiFi analytics tooling, visit the Purple resources hub at purple dot ai. Thank you for joining this briefing, and we'll see you in the next session.

Conclusiones clave

✓Interference is the primary cause of poor WiFi performance in enterprise environments, manifesting as Co-Channel Interference (CCI — congestion) or Adjacent-Channel Interference (ACI — noise).
✓In the 2.4 GHz band, strictly use only channels 1, 6, and 11 with 20 MHz widths. Any other channel configuration in a multi-AP deployment guarantees destructive ACI.
✓Prioritise the 5 GHz band for enterprise client traffic due to its abundance of non-overlapping channels, but carefully manage DFS channel usage near radar sources such as airports.
✓In high-density environments, enforce 20 MHz channel widths to maximise the number of independent channels and aggregate network capacity, rather than optimising for peak single-client throughput.
✓Channel planning and transmit power tuning are inseparable. Reducing AP TX power in dense deployments improves spatial reuse and reduces CCI, counter-intuitively increasing overall throughput.
✓Always base channel planning decisions on empirical spectrum analysis data, not assumptions. Validate changes with a post-implementation survey and ongoing KPI monitoring.
✓Correct RF configuration is a zero-cost upgrade that frequently eliminates the perceived need for additional AP hardware, delivering direct ROI from existing infrastructure investment.

Resumen Ejecutivo

Para entornos empresariales —desde amplios recintos de Hostelería hasta densos espacios de Venta minorista —, un WiFi fiable ya no es un extra; es una infraestructura crítica. La interferencia sigue siendo la principal culpable de las conexiones caídas, la alta latencia y el bajo rendimiento, lo que afecta directamente tanto a la eficiencia operativa como a la experiencia del WiFi de invitados . Esta guía proporciona a los arquitectos de red y gerentes de TI un enfoque definitivo y paso a paso para identificar las fuentes de interferencia y cambiar estratégicamente los canales WiFi para mitigarlas.

Al implementar las mejores prácticas de gestión del espectro, neutrales al proveedor, las organizaciones pueden maximizar el ROI de su infraestructura, asegurar una itinerancia de clientes sin interrupciones y soportar la creciente densidad de dispositivos IoT y de usuario sin comprometer los estándares de seguridad o cumplimiento, incluyendo PCI DSS y GDPR. El principio fundamental es sencillo: la interferencia es un problema de gestión del espectro, no un problema de hardware. La configuración correcta de la infraestructura existente, en la mayoría de los casos, resolverá los problemas de rendimiento que las organizaciones atribuyen erróneamente a una densidad de AP insuficiente o a equipos obsoletos.

Análisis Técnico Detallado

Comprender la capa física de las redes IEEE 802.11 es esencial antes de realizar cualquier cambio de configuración. El espectro de radiofrecuencia (RF) es un medio compartido gobernado por el protocolo CSMA/CA (Carrier Sense Multiple Access with Collision Avoidance), y la interferencia generalmente se divide en dos categorías distintas: Interferencia Co-Canal (CCI) e Interferencia de Canal Adyacente (ACI).

La Interferencia Co-Canal (CCI) ocurre cuando múltiples puntos de acceso o clientes transmiten exactamente en el mismo canal. Si bien los protocolos 802.11 utilizan CSMA/CA para gestionar esto —los dispositivos escuchan antes de transmitir—, una CCI excesiva obliga a los dispositivos a esperar un tiempo de aire libre, reduciendo drásticamente el rendimiento y aumentando la latencia. Es fundamentalmente un problema de congestión más que un verdadero ruido de RF, y el mecanismo CSMA/CA puede manejarlo hasta cierto punto con elegancia.

La Interferencia de Canal Adyacente (ACI) es mucho más destructiva. Ocurre cuando los AP operan en frecuencias superpuestas —por ejemplo, los canales 2 y 4 en la banda de 2.4 GHz—. Debido a que las transmisiones se superponen pero no pueden ser decodificadas por CSMA/CA, se tratan como ruido puro, elevando el nivel de ruido y causando pérdida de paquetes y retransmisiones. En un recinto concurrido, la ACI puede reducir el rendimiento efectivo entre un 60 y un 70% y es el error de configuración más común encontrado en implementaciones empresariales.

El dilema de los 2.4 GHz

La banda de 2.4 GHz ofrece un mejor alcance y penetración de paredes, pero está severamente limitada por un espectro reducido —aproximadamente 83.5 MHz en total—. Aunque hay entre 11 y 14 canales dependiendo del dominio regulatorio, solo tres son verdaderamente no superpuestos: Canales 1, 6 y 11. Usar cualquier otro canal en una implementación con múltiples AP garantiza ACI. Además, esta banda está saturada de interferencias no WiFi, incluyendo dispositivos Bluetooth, hornos microondas y teléfonos inalámbricos DECT que operan en el mismo espectro. Para un análisis detallado de cómo Bluetooth Low Energy coexiste con la infraestructura WiFi, consulte nuestra guía sobre BLE Low Energy Explained for Enterprise . Para un tratamiento más amplio de la selección de bandas de frecuencia, consulte Wi Fi Frequencies: A Guide to Wi-Fi Frequencies in 2026 .

La ventaja de los 5 GHz

La banda de 5 GHz ofrece significativamente más espectro, proporcionando numerosos canales de 20 MHz no superpuestos a través de las sub-bandas UNII-1, UNII-2, UNII-2e y UNII-3. Esta banda es la opción predeterminada correcta para el tráfico de clientes empresariales. Sin embargo, introduce dos complejidades clave: las compensaciones de la agregación de canales (channel bonding) y la Selección Dinámica de Frecuencia (DFS).

La agregación de canales (channel bonding) —que combina canales de 20 MHz en anchos de 40, 80 o 160 MHz— aumenta el rendimiento máximo de un solo cliente, pero reduce el número total de canales independientes disponibles. En entornos de alta densidad, esto causa una CCI severa. Los canales DFS (principalmente UNII-2 y UNII-2e) requieren que los AP monitoreen las señales de radar y desocupen inmediatamente el canal si se detectan, lo que provoca desconexiones de clientes. Esta es una consideración crítica para recintos cercanos a aeropuertos, estaciones meteorológicas o instalaciones militares.

Guía de Implementación

Cambiar los canales WiFi nunca debe basarse en conjeturas. Requiere un enfoque sistemático y basado en datos.

Paso 1: Realizar un análisis de espectro

Antes de realizar cualquier cambio de configuración, establezca una línea base empírica. Despliegue un analizador de espectro —ya sea hardware dedicado o las herramientas integradas en su controlador WLAN empresarial— para inspeccionar el entorno de RF en ambas bandas. Documente lo siguiente: APs no autorizados o vecinos y sus asignaciones de canal, el nivel de ruido en cada canal, la presencia de fuentes de interferencia no WiFi y los niveles de potencia de transmisión actuales de los AP. Esta línea base es su punto de referencia para medir el impacto de los cambios posteriores.

Paso 2: Formular un plan de canales

Para la banda de 2.4 GHz: Restrinja el conjunto de canales estrictamente a los canales 1, 6 y 11. Establezca todos los anchos de canal en 20 MHz —esto no es negociable—. Si la densidad de AP es lo suficientemente alta como para causar una CCI significativa incluso con el esquema 1-6-11, considere deshabilitar la radio de 2.4 GHz en APs alternos en un patrón de tablero de ajedrez, reduciendo efectivamente a la mitad la densidad de AP de 2.4 GHz mientras se mantiene la cobertura a través de los AP restantes.

Para la banda de 5 GHz: Maximice el uso de los canales no superpuestos disponibles. En implementaciones de alta densidad —centros de conferencias, estadios, centros de Transporte — imponga anchos de canal de 20 MHz para maximizar el número de canales independientes. Aumente a 40 MHz solo en áreas de baja densidad donde la CCI no sea una preocupación. Evalúe cuidadosamente la inclusión de canales DFS basándose en su ubicación específica y la proximidad a fuentes de radar. Consulte la lista de disponibilidad de canales de su autoridad reguladora nacional para su región específica.

Paso 3: Configurar puntos de acceso

Acceda a su controlador de red de área local inalámbrica (WLC) o al panel de control de gestión en la nube para aplicar el plan de canales. La mayoría de las plataformas empresariales ofrecen funciones de Gestión de Recursos de Radio (RRM) o Auto-RF que asignan dinámicamente canales y niveles de potencia.

Enfoque	Ideal para	Riesgo
Plan estático manual	Lugares complejos, de alta densidad o adyacentes a radares	Requiere una nueva inspección periódica a medida que cambia el entorno
Auto-RF / RRM	Implementaciones más sencillas y de menor densidad	Puede causar inestabilidad de canales en entornos RF volátiles
Híbrido	La mayoría de las implementaciones empresariales	Requiere una configuración cuidadosa de las restricciones

En entornos altamente complejos, un plan de canales estático manual basado en un estudio predictivo suele ofrecer una mayor estabilidad que depender únicamente de Auto-RF. La potencia de transmisión debe ajustarse en paralelo: reduzca la potencia de transmisión del AP a 10-14 dBm en 5 GHz en implementaciones densas para reducir el tamaño de las celdas y la interferencia entre APs.

Paso 4: Validar y monitorizar

Después de aplicar los cambios, realice un estudio de validación posterior a la implementación para verificar el nuevo plan de canales. Monitorice los indicadores clave de rendimiento (KPIs) a través de su plataforma de WiFi Analytics , centrándose en las tasas de reintento, la utilización del tiempo de aire por AP, el número de asociaciones de clientes y el comportamiento de roaming. Un entorno RF bien ajustado debería mostrar tasas de reintento inferiores al 10% y una utilización del tiempo de aire inferior al 70% durante los períodos pico.

Mejores prácticas

Imponga anchos de 20 MHz en alta densidad. En entornos como centros de conferencias o estadios, priorice la capacidad —más canales no superpuestos— sobre el rendimiento máximo de un solo cliente de canales más anchos. El rendimiento agregado de la red será significativamente mayor.

Implemente la dirección de banda de forma agresiva. Configure la dirección de banda para alejar a los clientes compatibles con 5 GHz de la banda congestionada de 2.4 GHz. La mayoría de los controladores empresariales modernos lo admiten de forma nativa. Reserve 2.4 GHz para dispositivos IoT y hardware heredado que no pueda operar en 5 GHz.

Deshabilite las tasas de datos heredadas. Deshabilite las tasas de datos 802.11b (1, 2, 5.5, 11 Mbps) en todos los SSIDs. Estas tasas heredadas consumen un tiempo de aire desproporcionado y ralentizan toda la red. Establecer una tasa de datos mínima de 12 o 24 Mbps obliga a los clientes a realizar el roaming antes y reduce la sobrecarga de los marcos de gestión.

Programe auditorías de RF periódicas. El entorno RF es dinámico. Nuevas redes vecinas, modificaciones de edificios y nuevos equipos cambian el panorama de interferencias. Programe auditorías de RF trimestrales para mantener su plan de canales actualizado.

Integre la seguridad y la gestión de red. Asegúrese de que la detección y mitigación de APs no autorizados estén habilitadas para evitar que dispositivos no autorizados causen interferencias o brechas de seguridad. Para un contexto de seguridad de red más amplio, incluido el filtrado de contenido en redes de invitados, revise ¿Qué es el filtrado DNS? Cómo bloquear contenido dañino en el WiFi de invitados . Para estrategias de optimización específicas de oficinas, consulte WiFi de oficina: optimice su red WiFi de oficina moderna .

Solución de problemas y mitigación de riesgos

Síntoma: Señal fuerte, bajo rendimiento. Esta es la característica distintiva de la interferencia cocanal. El nivel de ruido es bajo, pero el tiempo de aire está saturado. Audite las asignaciones de canales y la potencia de transmisión del AP. Reduzca la potencia de transmisión y aplique anchos de canal de 20 MHz para liberar tiempo de aire y mejorar la reutilización espacial.

Síntoma: Desconexiones aleatorias de clientes en zonas específicas. Revise los registros de eventos DFS inmediatamente. Si los APs en esa zona están en canales UNII-2 o UNII-2e y están cerca de una fuente de radar, se les exigirá legalmente que desocupen el canal, desconectando a los clientes. Excluya esos canales DFS específicos del plan de canales para las zonas afectadas.

Síntoma: El plan de canales cambia automáticamente. Esto es una inestabilidad de canales causada por un algoritmo Auto-RF demasiado sensible que reacciona a interferencias transitorias. Restrinja la configuración de sensibilidad de RRM, aumente el temporizador de retención o migre a un plan de canales estático basado en datos de estudio.

Síntoma: Bajo rendimiento en áreas específicas a pesar de una buena señal. La interferencia no-WiFi de hornos microondas, teléfonos DECT o equipos industriales puede estar elevando el nivel de ruido. Un analizador de espectro identificará estas fuentes. La solución es eliminar la fuente o migrar los APs afectados a la banda de 5 GHz o 6 GHz, que es inmune a la mayoría de los interferentes no-WiFi de 2.4 GHz.

ROI e impacto empresarial

Optimizar los canales WiFi es una mejora de infraestructura de coste cero que produce retornos inmediatos y medibles. Las organizaciones que implementan una planificación adecuada de canales RF suelen reportar una reducción del 30-40% en los tickets de soporte relacionados con WiFi durante el primer trimestre. En entornos de Salud , un entorno RF correctamente ajustado garantiza un flujo ininterrumpido de datos de telemetría críticos y apoya el cumplimiento de los requisitos de comunicación de dispositivos clínicos. En Minorista , garantiza el funcionamiento sin problemas de los sistemas de punto de venta móviles, análisis de ubicación precisos y aplicaciones fiables de gestión de inventario.

Desde una perspectiva de gasto de capital, una planificación de canales correcta elimina con frecuencia la necesidad percibida de hardware AP adicional. Muchas organizaciones que creen tener una densidad de APproblema de conectividad en realidad tienen un problema de planificación de canales. Resolver la configuración de RF primero —antes de adquirir hardware adicional— es una práctica estándar en cualquier evaluación de red rigurosa. Un entorno de RF correctamente ajustado también extiende el ciclo de vida operativo de la infraestructura existente, aplazando costosos ciclos de actualización de hardware y proporcionando un retorno directo y cuantificable de la inversión de capital existente.

Definiciones clave

Co-Channel Interference (CCI)

Interference that occurs when multiple access points or client devices transmit on the exact same frequency channel simultaneously.

Managed by CSMA/CA, but causes congestion and reduced throughput when excessive. The primary symptom is high airtime utilisation with low throughput.

Adjacent-Channel Interference (ACI)

Interference caused by devices transmitting on overlapping but non-identical frequency channels, creating RF noise that CSMA/CA cannot decode or manage.

More destructive than CCI. Raises the noise floor, causes packet loss, and forces retransmissions. Caused by using channels other than 1, 6, and 11 on 2.4 GHz.

Dynamic Frequency Selection (DFS)

An IEEE 802.11h mechanism that requires WiFi access points to monitor for radar signals on certain 5 GHz channels and immediately vacate the channel if radar is detected.

Affects UNII-2 and UNII-2e channels. Critical consideration for venues near airports, weather stations, or military sites, where frequent radar detection causes client disconnections.

Radio Resource Management (RRM)

Automated algorithms within enterprise WLAN controllers that dynamically adjust channel assignments and transmit power levels based on real-time RF conditions.

Useful for adapting to changing RF environments, but can cause 'channel churn' — frequent channel changes — in volatile environments, disrupting client connectivity.

Channel Bonding

The process of combining multiple adjacent 20 MHz channels into wider 40, 80, or 160 MHz channels to increase peak single-client throughput.

Reduces the total number of available non-overlapping channels, increasing CCI risk in dense deployments. Should be avoided in high-density enterprise environments.

Band Steering

A WLAN controller feature that encourages dual-band capable client devices to associate with the 5 GHz band rather than the congested 2.4 GHz band.

Essential for load balancing in enterprise deployments. Preserves the limited 2.4 GHz spectrum for IoT devices and legacy hardware that cannot operate on 5 GHz.

CSMA/CA

Carrier Sense Multiple Access with Collision Avoidance. The medium access control protocol used by IEEE 802.11 WiFi, requiring devices to listen for clear airtime before transmitting.

The mechanism that governs how WiFi devices share the RF medium. High CCI forces devices to wait longer for clear airtime, directly reducing throughput and increasing latency.

Noise Floor

The aggregate level of background RF energy present in a given frequency band, measured in dBm. A higher noise floor reduces the effective Signal-to-Noise Ratio (SNR) for WiFi transmissions.

Raised by ACI, non-WiFi interference, and poor channel planning. A high noise floor forces devices to use lower modulation schemes and data rates, reducing throughput.

Spatial Reuse

The ability of multiple access points to simultaneously transmit on the same channel without interfering with each other, enabled by physical separation and appropriate transmit power levels.

The fundamental mechanism that allows high-density WiFi networks to scale. Maximised by reducing AP transmit power and using the minimum necessary channel widths.

Ejemplos prácticos

A 200-room hotel is experiencing widespread complaints of slow WiFi during the evening peak. The current deployment uses 40 MHz channels on the 2.4 GHz band across 80 APs, and Auto-RF is enabled. The WLAN controller logs show frequent channel changes throughout the evening.

Phase 1 — Immediate remediation: Reconfigure all 2.4 GHz radios to 20 MHz channel widths immediately. Restrict the 2.4 GHz channel pool to channels 1, 6, and 11 only within the controller. This alone will eliminate ACI across the deployment.

Phase 2 — Stabilise Auto-RF: Review the Auto-RF event logs. If APs are changing channels more than once per hour, the algorithm is reacting to transient interference. Increase the RRM hold-down timer and reduce the sensitivity threshold. If churn persists, migrate to a static channel plan.

Phase 3 — Band steering: Enable aggressive band steering to push dual-band devices to 5 GHz. This reduces 2.4 GHz load significantly during peak periods.

Phase 4 — Validation: Deploy a spectrum analyser post-change and monitor retry rates and airtime utilisation via the WiFi analytics dashboard for 48 hours to confirm improvement.

Comentario del examinador: Using 40 MHz widths on 2.4 GHz is a critical configuration error in any multi-AP enterprise deployment. It consumes two-thirds of the available spectrum, guaranteeing severe Adjacent-Channel Interference across the entire venue. Restricting widths to 20 MHz and enforcing the 1-6-11 rule immediately reduces the noise floor and improves airtime availability. The channel churn from Auto-RF is a secondary issue — the algorithm is reacting to the ACI it is itself causing. Fixing the channel width resolves both problems simultaneously.

A large retail chain has deployed APs every 12 metres across a 4,000 sq metre distribution centre. Even on the 5 GHz band using 20 MHz channels, CCI is high, throughput is poor, and mobile scanning devices are experiencing frequent disconnections during peak shift hours.

Step 1 — Audit transmit power: The APs are almost certainly configured at maximum TX power (typically 20–23 dBm). At 12-metre spacing, this creates massive cell overlap. Reduce TX power to 10–12 dBm on 5 GHz to shrink cell sizes and reduce inter-AP interference.

Step 2 — Disable legacy data rates: Disable all 802.11b/g data rates below 12 Mbps. This forces scanning devices to roam to the nearest AP rather than staying associated with a distant AP at a low data rate, which consumes disproportionate airtime.

Step 3 — Review channel plan: Ensure the 5 GHz channel plan uses the maximum number of non-overlapping channels available. With high AP density, every unique channel matters.

Step 4 — Validate with post-change survey: Conduct a walkthrough survey with a spectrum analyser to confirm reduced inter-AP overlap and improved SNR across the floor.

Comentario del examinador: In high-density deployments, excessive transmit power is the most common cause of CCI even when the channel plan is technically correct. When APs can hear each other clearly, CSMA/CA forces them to take turns, saturating airtime. Reducing TX power is the correct architectural response — it improves spatial reuse, which is the fundamental mechanism that allows high-density WiFi to scale. Disabling legacy data rates is a complementary measure that reduces airtime waste from slow management frames and sticky client associations.

Preguntas de práctica

Q1. You are deploying a new wireless network in a multi-tenant office building. Your spectrum scan shows heavy utilisation on channels 1, 6, and 11 from neighbouring tenants. A junior engineer suggests using channels 3, 8, and 13 to 'avoid the congestion'. How do you respond, and what is the correct configuration?

Sugerencia: Consider the difference between Co-Channel Interference (CCI) and Adjacent-Channel Interference (ACI), and which is more harmful to network performance.

Ver respuesta modelo

The junior engineer's suggestion is incorrect and would cause severe performance degradation. Channels 3, 8, and 13 overlap with channels 1, 6, and 11 respectively, which would introduce Adjacent-Channel Interference — the most destructive form of WiFi interference. ACI manifests as pure RF noise that CSMA/CA cannot manage, causing packet loss and retransmissions. The correct configuration is to deploy on channels 1, 6, and 11. While this will cause Co-Channel Interference with the neighbouring tenants, CSMA/CA can handle CCI gracefully by having devices take turns. The aggregate performance will be significantly better than with ACI.

Q2. A stadium deployment is using 80 MHz channels on the 5 GHz band to advertise 'Gigabit WiFi' speeds during events. Users report slow loading times, frequent disconnections, and poor video streaming quality during peak occupancy. The AP hardware is modern WiFi 6 equipment. What is the architectural flaw, and what is the remediation?

Sugerencia: Evaluate the trade-off between peak single-client throughput and overall network capacity in a high-density environment.

Ver respuesta modelo

The architectural flaw is the use of 80 MHz channel widths in a high-density environment. Each 80 MHz channel bonds four 20 MHz channels together, drastically reducing the total number of non-overlapping channels available across the deployment. With many APs forced to reuse the same wide channels, Co-Channel Interference becomes severe. The solution is to reduce channel widths to 20 MHz across all APs. This increases the number of independent channels available, reduces CCI, and significantly improves aggregate network capacity. The peak throughput per client will decrease, but the number of clients that can be served simultaneously — and the quality of their experience — will increase substantially.

Q3. Your hospital network experiences intermittent client disconnections affecting medical devices in wards near the hospital's rooftop helipad. The affected APs are configured to use channels 52, 56, 60, and 64. What is the most likely cause, and what is the correct remediation?

Sugerencia: Consider the regulatory requirements for the specific 5 GHz channels in use and what systems operate near a helipad.

Ver respuesta modelo

Channels 52, 56, 60, and 64 are UNII-2 DFS channels. The helicopters using the helipad, or associated aviation radar systems, are likely triggering DFS radar detection events on the APs in that zone. When radar is detected, the APs are legally required to immediately vacate those channels, causing client disconnections. The correct remediation is to exclude all DFS channels from the channel plan for APs in the zones near the helipad. Reconfigure those APs to use UNII-1 channels (36, 40, 44, 48) or UNII-3 channels (149, 153, 157, 161, 165), which are not subject to DFS requirements.