RF is the part of a wireless deployment that punishes shortcuts. You can mis-tag APs and fix it in an hour. You can pick the wrong HA model and swap it in a maintenance window. But an RF design built on the wrong AP count, the wrong channel plan, or the wrong power envelope will haunt you for years — and every "fix" on top of a bad design just makes the next troubleshoot harder. This guide walks through the RF design decisions you need to make on a Cisco Catalyst 9800 deployment, in the order they matter: site survey, AP placement, channel planning, power tuning, and the band-specific decisions for 2.4 GHz, 5 GHz, and 6 GHz.
Start with a Survey, Not a Floor Plan
The most common RF design mistake is deriving AP count from a floor plan and a rule of thumb ("one AP per 2,500 sq ft"). Rules of thumb are fine for back-of-napkin sizing; they are not a design. A real RF design starts with a predictive survey (Ekahau, iBwave, Hamina) followed by a validation survey (AP-on-a-stick or post-install). You need both, and you need to act on what they tell you.
The survey produces four things that every downstream decision depends on:
| Output | What it tells you | Design target |
|---|---|---|
| Primary coverage (RSSI) | Signal strength at the edge of each cell | −67 dBm for voice, −65 dBm for high-density data, −70 dBm for basic coverage |
| Secondary coverage | Whether a client can hear a second AP at an acceptable level for roaming | ≥ −75 dBm from at least one additional AP everywhere |
| SNR | Signal-to-noise ratio, i.e., usable signal above the noise floor | ≥ 25 dB for voice, ≥ 20 dB for general use |
| Co-channel overlap | How many APs are fighting on the same channel at any point in space | ≤ 2 APs above −85 dBm on the same channel |
If any of those targets can't be met with the AP count you planned, you need more APs, different placement, or different antennas — not a clever configuration. The C9800 cannot make up for APs that aren't there.
Use the survey to decide AP density, not AP spacing. In a warehouse with 20-metre ceilings, two APs 40 metres apart can give you a legitimate −65 dBm floor. In a hospital with dense walls and glass, two APs 10 metres apart might not. Density is a function of materials, ceiling height, client expectations, and band — never square footage alone.
AP Placement: Ceiling, Not Wall, Almost Always
Unless your site survey tells you otherwise, mount APs on the ceiling, horizontally, with the antennas pointed down. Wall-mounted APs (other than purpose-built directional models like the C9124 or C9166D1) produce cigar-shaped radiation patterns that create roaming cliffs and null zones. The internal omni antennas in most enterprise APs are designed for ceiling mount; mounting them on a wall breaks their assumed pattern.
Exceptions that are legitimate:
- Warehouses and large open spaces with very high ceilings — use the C9130AXI with directional antennas, or the C9124 outdoor AP with patch antennas. A standard omni AP 12 metres up pushes almost all its energy past the client height.
- Outdoor coverage — the C9124 family with sector antennas, aimed deliberately.
- High-density stadia and auditoriums — under-seat or narrow-beam overhead, designed by someone who has done it before.
For everything else — offices, classrooms, hotel corridors, hospital wards — ceiling mount with the native omni antennas. The survey will tell you whether you also need to down-tilt, use external antennas, or shift to a different model.
Channel Planning: Let DCA Work, Within a Tight Fence
Manual channel planning on a modern C9800 is almost always the wrong answer. Radio Resource Management's Dynamic Channel Assignment (DCA) is good at what it does — provided you give it a sane channel list to choose from and don't fight it.
Your job is not to pick channels. Your job is to prune the channel list DCA is allowed to use, and to pick the channel width. Those two decisions matter more than any manual assignment you could make.
| Band | Usable channels (US, indicative) | Recommended width | Notes |
|---|---|---|---|
| 2.4 GHz | 1, 6, 11 | 20 MHz only | Never use 40 MHz in 2.4 GHz. Ever. |
| 5 GHz UNII-1 | 36, 40, 44, 48 | 20 or 40 MHz | Non-DFS. Safe but limited. |
| 5 GHz UNII-2 | 52–64 | 20 or 40 MHz | DFS. Exclude if radar events are frequent. |
| 5 GHz UNII-2e | 100–144 | 20 or 40 MHz | DFS. Largest contiguous block; high-value if usable. |
| 5 GHz UNII-3 | 149–165 | 20 or 40 MHz | Non-DFS. Heavily contended in dense environments. |
| 6 GHz (Wi-Fi 6E/7) | Huge — plan on 20/40/80 MHz | 40 or 80 MHz for typical office | Tight power limits in LPI mode; plan for lower range. |
The channel-width question is the single biggest lever you have in 5 GHz. Wider channels give you more throughput per BSS but fewer non-overlapping channels, which drives co-channel interference up fast. The answer is almost always 20 MHz for dense office, 40 MHz for moderate density, and 80 MHz only for isolated high-throughput use cases (executive offices, media labs, auditoriums).
Configure your DCA channel list explicitly rather than relying on the default:
C9800(config)#ap dot11 5ghz rrm channel dca channel 36
C9800(config)#ap dot11 5ghz rrm channel dca channel 40
C9800(config)#ap dot11 5ghz rrm channel dca channel 44
C9800(config)#ap dot11 5ghz rrm channel dca channel 48
C9800(config)#ap dot11 5ghz rrm channel dca channel 149
C9800(config)#ap dot11 5ghz rrm channel dca channel 153
C9800(config)#ap dot11 5ghz rrm channel dca channel 157
C9800(config)#ap dot11 5ghz rrm channel dca channel 161
C9800#show ap dot11 5ghz channel
Leader Automatic Channel Assignment
Channel Assignment Mode : AUTO
Channel Update Interval : 600 seconds
Anchor time (Hour of the day) : 3
DCA Sensitivity Level : MEDIUM : 15 dB
Channel Width : 40 MHz
DCA Allowed Channel List : 36,40,44,48,149,153,157,161That configuration says: "Use UNII-1 and UNII-3, skip DFS, run at 40 MHz." If your environment can tolerate DFS (no nearby weather or military radar), add the UNII-2 and UNII-2e blocks and your capacity goes up dramatically.
Power Tuning: Tight Fence, Let TPC Do the Rest
Transmit Power Control (TPC) is DCA's sibling, and it fails in the same way for the same reason: the defaults are too loose, and people either leave them alone or turn TPC off entirely.
The default TPC range on a C9800 is −10 to 30 dBm. That range is technically correct and practically useless — no realistic deployment has cells where −10 dBm is appropriate, and allowing 30 dBm pushes every AP to maximum EIRP, which blows up co-channel interference.
A sensible starting point for 5 GHz in an office:
| Environment | TPC min | TPC max | Rationale |
|---|---|---|---|
| Dense office (≈ 1 AP per 200 m²) | 8 dBm | 14 dBm | Prevents cells from growing past their survey footprint |
| Standard office | 11 dBm | 17 dBm | Balances edge coverage and overlap |
| Large open / warehouse | 14 dBm | 20 dBm | Cells need to reach farther; survey-driven |
| High-density (auditorium) | 5 dBm | 11 dBm | Small cells by design |
C9800(config)#ap dot11 5ghz rrm txpower max 17
C9800(config)#ap dot11 5ghz rrm txpower min 11
C9800#show ap dot11 5ghz summary
AP Name Radio Mac Oper State Channel Width TxPwr
-------------------------------------------------------------------
AP-HQ-001 aaaa.bbbb.0010 Up 44* 40 3/8 (14 dBm)
AP-HQ-002 aaaa.bbbb.0020 Up 149* 40 4/8 (13 dBm)
AP-HQ-003 aaaa.bbbb.0030 Up 36* 40 3/8 (14 dBm)The TxPwr column tells you where in the TPC range TPC has settled. If every AP is at 1/8 (maximum power), the TPC range is too wide or your AP density is too low. If every AP is at 8/8 (minimum power), the TPC range is too high and cells are collapsing.
2.4 GHz: Use Less of It
2.4 GHz is unsalvageable in most dense deployments. There are only three non-overlapping 20 MHz channels, Bluetooth and microwaves share the band, and most client devices now have 5 GHz (and often 6 GHz) radios. The correct design move in a dense office is not to tune 2.4 GHz — it is to use less of it.
Two techniques:
Flexible Radio Assignment (FRA) lets the C9800 decide which 2.4 GHz radios to keep enabled and which to repurpose as monitor radios or (on dual-5 GHz-capable APs) as a second 5 GHz radio. The algorithm aims for a minimum 2.4 GHz coverage footprint and reclaims the rest. On a dense AP mesh, FRA will disable roughly half the 2.4 GHz radios automatically.
C9800(config)#ap dot11 24ghz rrm channel fra
C9800(config)#ap fra interval 1
C9800(config)#ap fra sensitivity high
C9800#show ap fra
FRA State : Enabled
FRA Sensitivity : higher (95%)
FRA Interval : 1 Hour(s)
Last Run : 600 seconds ago
Last Run time : 12 seconds
AP Name MAC Address Slot Radio Role COF%
-----------------------------------------------------------------
AP-HQ-005 aaaa.bbbb.0050 0 Client-Serving 32
AP-HQ-006 aaaa.bbbb.0060 0 Monitor N/AManual disable of every other 2.4 GHz radio via an RF Profile is the blunt-force alternative if FRA doesn't fit your environment. It works but it's static — FRA is better if you trust it.
5 GHz: The Main Event
5 GHz is where most of your capacity lives, and therefore where most of your design effort should go. A few specific things to get right:
- Disable legacy data rates. Leaving 1, 2, 5.5, and 11 Mbps enabled in 5 GHz is impossible (they don't exist in 5 GHz), but the equivalent in 5 GHz is leaving 6 and 9 Mbps enabled. Disable 6, 9, and 12 Mbps as basic rates and raise your minimum supported rate to 12 or 18 Mbps. This shrinks cells to match your survey and forces clients to roam rather than hanging on at the edge.
- Enable 802.11k and 802.11v. They're free, every modern client supports them, and they give the WLC and client a way to negotiate better roams. 802.11r (FT) for SSIDs that need fast roaming (voice, scanners), WPA2/WPA3 PSK, or 802.1X.
- Turn on Coverage Hole Detection with tuned thresholds. Default thresholds flag a lot of false positives; tune to your environment and act on the reports.
- Enable CleanAir on CleanAir-capable APs. Spectrum analysis inside the AP catches interference (microwaves, video bridges, jammers) that packet-layer telemetry can't see.
C9800(config)#ap dot11 5ghz rate RATE_6M disable
C9800(config)#ap dot11 5ghz rate RATE_9M disable
C9800(config)#ap dot11 5ghz rate RATE_12M mandatory
C9800(config)#ap dot11 5ghz rate RATE_24M supported
C9800#show ap dot11 5ghz network
802.11a Network : Enabled
11nSupport : Enabled
802.11a Low Band : Enabled
802.11a Mid Band : Enabled
802.11a High Band : Enabled
Mandatory Rates: 12.0 24.0
Supported Rates: 18.0 36.0 48.0 54.06 GHz: Plan for Density and Range
6 GHz changes the assumptions. The band gives you huge contiguous spectrum — enough for many non-overlapping 80 MHz channels or even 160 MHz in some regulatory domains — but it comes with a catch: power limits are much tighter than 5 GHz in Low Power Indoor (LPI) mode, which is the default for most enterprise deployments. A 6 GHz AP at LPI power does not cover the same footprint as the 5 GHz radio in the same chassis.
Design implications:
- Do not assume one-to-one coverage parity with 5 GHz. A 5 GHz survey that gives you −65 dBm edge will give you −72 or −74 dBm at 6 GHz at the same spot.
- Use 40 MHz channels as the default starting point in office environments. 80 MHz is tempting but reduces reuse, and in 6 GHz you need reuse for density.
- Enable WPA3-SAE or WPA3-Enterprise only. 6 GHz SSIDs legally cannot run WPA2 in most regions — this is a protocol requirement, not a design preference.
- If your regulatory region allows Standard Power (SP) with AFC, and you need the range, plan the AFC integration as a project of its own. It's not a checkbox.
Validate with Real Data, Not Just the GUI
A design that looks good in Ekahau can still fail in production. Validate with the data the C9800 actually collects:
C9800#show ap auto-rf dot11 5ghz ap AP-HQ-001
Number Of Slots : 2
AP Name : AP-HQ-001
MAC Address : aaaa.bbbb.0001
Radio Type : RADIO_TYPE_80211a
Noise Information
Noise Profile : PASSED
Channel 36 : -92 dBm
Channel 40 : -91 dBm
Channel 44 : -92 dBm
...
Interference Information
Interference Profile : PASSED
Channel 36 : -75 dBm @ 3% busy
...
Neighbor Information
Neighbor Name : AP-HQ-002
RSSI : -67 dBm
Channel : 149
C9800#show wireless stats client summary
Total Number of Clients : 1247
Clients In Run State : 1231
Clients In IP Learn State : 8
Clients in Excluded State : 2
C9800#show ap dot11 5ghz cleanair air-quality summary
AP Name Slot Channel AQ
-----------------------------------
AP-HQ-001 1 44 94
AP-HQ-002 1 149 91Noise floors that creep above −85 dBm, neighbours at better than −65 dBm (too many, too close), or an air quality score below 80 — any of those is telling you that the RF design is drifting, and no amount of controller tuning will fix the underlying problem.
Key Takeaways
RF design starts with a survey and ends with validation against real telemetry. AP count and placement come from measured data, not floor-plan arithmetic. Channel width is the biggest lever in 5 GHz — pick 20 or 40 MHz for most deployments, not 80. Prune the DCA channel list explicitly and let DCA work inside that fence. Tighten the TPC range to match your survey and expect most APs to land in the middle of it. Shrink the 2.4 GHz footprint with FRA rather than trying to tune three overlapping channels. In 6 GHz, assume smaller cells than 5 GHz and plan density accordingly. And validate everything with show ap auto-rf, CleanAir air quality, and client-state counts — the controller will tell you whether the design is working, if you ask it.