Cross-platform comparison and architecture guidance for all enterprise wireless technologies: Wi-Fi standards (6/6E/7), RF design, deployment architecture, site surveys, roaming, and platform selection. Use for \"wireless comparison\", \"Wi-Fi architecture\", \"Wi-Fi 6\", \"Wi-Fi 6E\", \"Wi-Fi 7\", \"WLAN design\", \"wireless migration\", \"site survey\", \"RF design\", \"wireless platform selection\". Do NOT use for cisco-wireless-, aruba-wireless-, or juniper-mist-specific configuration -- ...
Pro scans all 2 files and shows the line behind each finding
Scanned 9/24/2026
npx -y skills add chrishuffman5/domain-expert --skill wireless --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Wireless?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/chrishuffman5-wireless)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: wireless
description: "Cross-platform comparison and architecture guidance for all enterprise wireless technologies: Wi-Fi standards (6/6E/7), RF design, deployment architecture, site surveys, roaming, and platform selection. Use for \"wireless comparison\", \"Wi-Fi architecture\", \"Wi-Fi 6\", \"Wi-Fi 6E\", \"Wi-Fi 7\", \"WLAN design\", \"wireless migration\", \"site survey\", \"RF design\", \"wireless platform selection\". Do NOT use for cisco-wireless-, aruba-wireless-, or juniper-mist-specific configuration -- use that technology's own skill."
license: MIT
---
# Wireless / WLAN
This skill covers all enterprise wireless LAN technologies, providing cross-platform expertise in Wi-Fi standards (802.11ax/be), RF design, deployment architecture, site survey methodology, roaming, security, and platform selection. Sibling technology skills provide deep implementation details.
## When to Use This Skill vs. a Technology Skill
**Use this skill when the question is cross-platform or architectural:**
- "Which wireless platform should I deploy for our campus?"
- "Compare Cisco 9800 vs Aruba Central vs Juniper Mist"
- "How do I design a wireless deployment for a 5-floor office?"
- "What Wi-Fi 7 features matter for my upgrade plan?"
- "Explain BSS coloring and OFDMA"
- "Plan a wireless migration from controller-based to cloud-managed"
**Route to a technology skill when the question is platform-specific:**
- "Configure FlexConnect on C9800" --> the `cisco-wireless` skill
- "Aruba AirMatch tuning for 6 GHz" --> the `aruba-wireless` skill
- "Mist SLE threshold adjustment" --> the `juniper-mist` skill
- "IOS-XE 17.15 Wi-Fi 7 MLO config" --> the `cisco-wireless` skill's `references/versions/17.15.md`
## How to Approach Tasks
1. **Classify** the request:
- **Platform selection** -- Load `references/concepts.md` for Wi-Fi fundamentals, then compare platforms below
- **RF design / site survey** -- Apply RF planning principles and band/channel guidance
- **Migration** -- Identify source and target platforms, map feature gaps, assess AP reuse
- **Troubleshooting** -- Identify the platform, consult the technology skill
- **Standards / theory** -- Use `references/concepts.md` for 802.11ax/be, OFDMA, BSS coloring, roaming
2. **Gather context** -- Environment type (campus, branch, warehouse, outdoor), density expectations, device mix (IoT, laptops, phones), existing infrastructure, management model preference (on-prem vs cloud), security requirements (WPA3, 802.1X, NAC)
3. **Analyze** -- Apply wireless-specific reasoning. Consider RF environment, channel planning, client compatibility, roaming requirements, and deployment scale.
4. **Recommend** -- Provide platform-specific guidance with trade-offs. Wireless decisions are highly environment-dependent.
5. **Qualify** -- State assumptions about density, building materials, client capabilities, and regulatory domain.
## Wi-Fi Standards Overview
| Standard | Marketing Name | Bands | Max PHY Rate | Key Features |
|---|---|---|---|---|
| 802.11ac Wave 2 | Wi-Fi 5 | 5 GHz | 3.5 Gbps | MU-MIMO (DL only), 160 MHz channels |
| 802.11ax | Wi-Fi 6 | 2.4/5 GHz | 9.6 Gbps | OFDMA, UL MU-MIMO, BSS Coloring, TWT, 1024-QAM |
| 802.11ax | Wi-Fi 6E | 2.4/5/6 GHz | 9.6 Gbps | Same as Wi-Fi 6, extended to 6 GHz (1.2 GHz new spectrum) |
| 802.11be | Wi-Fi 7 | 2.4/5/6 GHz | 46 Gbps | MLO, 320 MHz channels, 4096-QAM, 16x16 MU-MIMO |
**Key insight:** Wi-Fi 6E and Wi-Fi 7 require 6 GHz capable clients. As of 2026, client adoption of 6 GHz is growing but not universal. Design for dual-band (5 + 6 GHz) operation; do not abandon 5 GHz yet.
**Security escalation:** 6 GHz band requires WPA3 -- no legacy WPA2 permitted. Wi-Fi 7 certified deployments also mandate WPA3. Plan WPA3 migration before deploying 6E/7 SSIDs.
## Platform Comparison
### Cisco Catalyst 9800 + Catalyst APs
**Strengths:**
- IOS-XE based WLC with full YANG/NETCONF/RESTCONF programmability
- Multiple deployment modes: centralized, FlexConnect, SD-Access fabric, embedded WLC
- Mature RRM with DCA, TPC, CHD, CleanAir, and Flexible Radio Assignment
- Radioactive tracing for deep per-client troubleshooting without broad debug impact
- Deep Cisco ecosystem integration (Catalyst Center, DNA Spaces, ISE, SD-Access)
- Rolling AP upgrades (upgrade APs without WLC downtime)
- Wi-Fi 7 support with CW9170/9178 APs on IOS-XE 17.15+
**Considerations:**
- Requires WLC hardware or VM (not fully cloud-native management plane)
- Catalyst Center (DNA Center) needed for fabric/SD-Access, adds complexity and cost
- Licensing model: DNA Essentials vs Advantage subscription per AP
- FlexConnect vs centralized mode decisions add architectural complexity
**Best for:** Organizations in the Cisco ecosystem needing on-premises control, SD-Access fabric integration, or large campus deployments with advanced RF management.
### HPE Aruba Networking (AOS 10 + Central)
**Strengths:**
- Cloud-first architecture: Aruba Central manages APs with no on-premises controller required
- AirMatch provides AI-driven global RF optimization computed in the cloud
- ClearPass NAC integration for authentication, profiling, posture, BYOD onboarding
- Dynamic segmentation enforces consistent policy across wired and wireless
- Gateway model integrates SD-WAN, ZTNA, and stateful firewall on-premises
- Wi-Fi 7 support with AP 730 series
- Micro-branch deployment: AP with embedded gateway functions for small sites
**Considerations:**
- Cloud dependency for management plane (though APs continue forwarding during cloud outage)
- AOS 10 is a departure from AOS 8 on-prem controller model; migration requires planning
- ClearPass is a separate product with its own licensing and operational overhead
- Gateway required for full security feature set (firewall, SD-WAN, ZTNA)
**Best for:** Organizations wanting cloud-managed wireless with strong NAC (ClearPass), dynamic segmentation, and converged SD-WAN/security at the edge.
### Juniper Mist (AI-Driven Cloud)
**Strengths:**
- AI-native architecture: Mist AI provides proactive anomaly detection and root-cause analysis
- Marvis conversational AI assistant for natural-language troubleshooting
- Marvis Minis virtual network sensors proactively test connectivity before users are affected
- Service Level Expectations (SLEs) provide measurable wireless KPIs with root-cause classifiers
- Unified wired (EX switch) + wireless + WAN (SSR) management in single cloud dashboard
- BLE-integrated APs for asset tracking, wayfinding, and proximity services (vBLE patented)
- Zero-touch provisioning for APs and switches
**Considerations:**
- Fully cloud-dependent management (Mist Edge available for on-premises data plane only)
- Smaller enterprise wireless market share than Cisco or Aruba
- Mist Edge required for tunnel termination, ZTNA, guest isolation in sensitive environments
- Wi-Fi 7 AP portfolio still expanding as of 2026
**Best for:** Organizations prioritizing AI-driven operations (AIOps), proactive monitoring, unified wired/wireless/WAN management, and indoor location services.
## Deployment Architecture Patterns
### Controller-Based (Centralized)
- APs tunnel all traffic to WLC via CAPWAP/GRE
- WLC handles authentication, policy enforcement, RF management centrally
- Best for: campus deployments with reliable, low-latency LAN
- Example: Cisco 9800 Local Mode, Aruba AOS 8 with Mobility Controller
### Cloud-Managed
- Management plane in cloud; APs forward data locally
- Cloud handles provisioning, monitoring, firmware, RF optimization
- Best for: distributed sites, MSPs, organizations wanting OpEx model
- Example: Aruba Central AOS 10, Juniper Mist, Cisco Meraki
### Hybrid (FlexConnect / Local Switching)
- Control tunnel to controller; data switched locally at AP
- AP caches auth state for WAN outage survivability
- Best for: branch offices with WAN constraints
- Example: Cisco FlexConnect, Aruba AP-only mode
### Fabric / SD-Access
- Wireless integrated into network fabric (VXLAN encapsulation)
- Consistent group-based policy (SGT) across wired and wireless
- Best for: large enterprises needing micro-segmentation and policy consistency
- Example: Cisco SD-Access with C9800 Embedded WLC
## Site Survey Methodology
### Pre-Deployment Survey Types
| Type | Purpose | Tools |
|---|---|---|
| Predictive | Model RF coverage using floor plans and material attenuation | Ekahau, Hamina, iBwave |
| Passive | Walk the facility measuring existing RF environment (noise, interference, neighboring APs) | Ekahau Sidekick, Wi-Fi scanner |
| Active | Connect to the network and measure throughput, roaming, DHCP, latency | Ekahau, iPerf |
### Survey Best Practices
1. Define coverage requirements first: target RSSI (typically -67 dBm for voice/video, -72 dBm for data), SNR > 25 dB
2. Measure during realistic conditions (occupancy, interference sources active)
3. Account for building materials: drywall ~3 dB loss, concrete ~12-15 dB, glass ~2-4 dB, metal ~20+ dB
4. Plan AP density for capacity, not just coverage -- high-density environments need more APs at lower power
5. Validate roaming paths between APs -- handoff zones should have -67 dB overlap
6. Document DFS channel availability (radar events may remove channels in certain locations)
7. For 6 GHz: standard power (SP) APs with AFC provide higher transmit power than low power indoor (LPI) APs
## Channel Planning Quick Reference
| Band | Usable Channels | Width | Notes |
|---|---|---|---|
| 2.4 GHz | 1, 6, 11 (Americas) | 20 MHz only | Only 3 non-overlapping; avoid 40 MHz in enterprise |
| 5 GHz (UNII-1) | 36, 40, 44, 48 | 20/40/80 MHz | No DFS; preferred for reliability |
| 5 GHz (UNII-2/2e) | 52-64, 100-144 | 20/40/80 MHz | DFS required; radar events cause channel changes |
| 5 GHz (UNII-3) | 149-165 | 20/40/80 MHz | No DFS; good outdoor channels |
| 6 GHz | 1-233 (up to 59 channels at 20 MHz) | 20/40/80/160/320 MHz | No DFS; AFC for standard power; WPA3 required |
## Common Pitfalls
1. **Designing for coverage instead of capacity** -- Modern wireless design is density-driven. More low-power APs outperform fewer high-power APs in dense environments.
2. **Using 40 MHz channels on 2.4 GHz** -- Only 3 non-overlapping 20 MHz channels exist. 40 MHz channels cause massive co-channel interference. Never use 40 MHz on 2.4 GHz in enterprise.
3. **Ignoring client capabilities** -- The AP advertises Wi-Fi 6E/7, but if clients only support Wi-Fi 5/6, those features provide no benefit. Survey your client device fleet before designing.
4. **Deploying 6 GHz without WPA3 readiness** -- 6 GHz requires WPA3. If your RADIUS/NAC infrastructure does not support WPA3-Enterprise (192-bit or SAE), 6 GHz SSIDs will not function.
5. **Over-relying on RRM/AirMatch without baseline** -- Automated RF management works best with a proper initial design. Poor AP placement cannot be fixed by software alone.
6. **Forgetting DFS impact on 5 GHz** -- In locations near airports, weather radar, or military installations, DFS channels may be frequently vacated. Design with sufficient non-DFS channels as fallback.
7. **Single-band SSID design** -- Create band-specific SSIDs or use band steering carefully. Do not force all clients to a single band unless you understand the client population.
8. **Skipping roaming validation** -- Fast roaming (802.11r/k/v) must be tested with actual client devices. Some legacy clients do not support 802.11r and will disconnect.
## Technology Routing
| Request Pattern | Route To |
|---|---|
| Cisco 9800, C9800, FlexConnect, Catalyst AP, DNA Spaces, IOS-XE wireless | the `cisco-wireless` skill (see `references/versions/17.15.md` for version specifics) |
| Aruba, AOS 10, Aruba Central, ClearPass, AirMatch, dynamic segmentation | the `aruba-wireless` skill (see `references/versions/10.7.md` for version specifics) |
| Juniper Mist, Marvis, Mist AI, SLE, Mist Edge, vBLE, Wired Assurance | the `juniper-mist` skill |
## Reference Files
- `references/concepts.md` -- Wireless fundamentals: 802.11 standards (ax/be), channel planning, MIMO/MU-MIMO/OFDMA, BSS coloring, roaming protocols (802.11r/k/v, OKC), WPA3 security (SAE, OWE, 192-bit), site survey methodology. Read for "how does X work" or cross-platform theory questions.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!