AIR-AP2802I-B-K9 Cisco Aironet 2800i Advanced RF Management AP

AIR-AP2802I-B-K9 exact order identity

AIR-AP2802I-B-K9 is a Cisco Aironet 2800 Series controller-based 802.11ac Wave 2 access point order. The exact line combines a 2802I indoor access point with integrated antennas, regulatory-domain token B, and a single-unit, fixed regulatory-domain order.

Antenna boundary

Cisco documents twelve cross-polarized internal antennas in the 2802I enclosure. No external antenna is selected by this access-point SKU. The RF result therefore depends on enclosure orientation, mounting height, obstructions and the surveyed placement. Receiving should confirm the mounting kit, while commissioning should retain photographs of the final orientation and compare measured coverage with the approved survey.

Order-form boundary

Cisco's ordering convention uses K9 for one access point. This line already carries a regulatory-domain token, so receiving must match the complete part number rather than accepting another domain as an equivalent. Create one asset record for the chassis serial and MAC address. Link that record to the approved destination, controller, switch port, mounting position and compliance lookup before the unit joins production. Because this is a fixed-domain line, a quotation or received label carrying another domain is a different order and requires a fresh approval. The single unit needs one serial-level record, while accessories, controller readiness and destination approval remain separate acceptance items.

B regulatory-domain channel evidence

Cisco's 2800 Series data sheet lists the B profile as 2.4 GHz channels 1-11; 5 GHz blocks at 5.180-5.320, 5.500-5.720, and 5.745-5.825 GHz. The B plan contains a broad middle 5 GHz range followed by a separate upper block. Capacity planning should identify which radios use each block and should not copy a narrower domain's channel template.

Retain a controller export showing the enabled lower, middle and upper channel sets. Compare the installed country setting, dynamic channel assignment and survey plan before accepting the site. Regulatory-domain letters are identifiers, not country names; use Cisco's compliance tool for the actual deployment country and retain the lookup date.

Procurement inference: the comparatively broad middle range and separate upper range can influence how capacity is distributed across radios. Preserve the survey's planned channel groups and compare them with the controller's dynamic assignment after a representative operating period. If the destination authorization narrows the available set, update the capacity calculation and acceptance record rather than leaving a B-profile assumption in the design.

Deployment evidence worksheet

Authentication path test

Commission representative clients through association, authentication, address assignment, DNS and application reachability. Preserve the identity policy used, test client type, result and relevant controller logs. An access point that joins its controller has not yet demonstrated the user path. Repeat the test after any controller, certificate or authentication-service change and retain failures separately from RF or switch-port evidence.

Roaming acceptance

Define the neighboring access points and client types used for roaming validation. Record handoff behavior, interruption observed, authentication result and controller events along the intended movement path. Compare the outcome with the site's design target rather than declaring success from static association. Where this unit replaces an older AP, test both entry and exit from its cell so a local improvement does not hide a boundary problem.

Monitoring handover

Assign owners for AP reachability, controller join failures, radio utilization, client health and switch-port errors. Confirm that the exact serial appears in inventory and monitoring, then test the alert path. Record dashboard object, notification route and escalation owner. Telemetry that is not tied to an owned asset does not provide a reliable service baseline and will not support later comparison after channel or software changes.

Change-window controls

Document staging evidence, production window, installer, rollback owner and measurable success criteria. Preserve the prior controller or AP state needed for recovery. After the change, close temporary credentials, compare authentication, monitoring and RF results with the approved baseline, and record the final decision. The work is not complete merely because the unit powers on or appears in a controller list.

Security baseline

Retain the approved controller policy, management authorization, certificate or trust workflow, client authentication test and logging destination. Confirm behavior on the deployed controller software instead of promising a protocol from the hardware family name. Remove temporary onboarding access and verify administrative reachability after handover. This keeps product identity separate from software-dependent security claims.

Capacity observation

Define the expected concurrent clients, application mix, airtime utilization and channel-width assumptions for this location. After commissioning, capture radio utilization, retry behavior and representative throughput during a meaningful load period. Compare the observation with the survey design and state any shortfall. A peak link rate from a data sheet is not a site capacity result and should not replace measured operating evidence.

Interference baseline

Preserve the pre-install and post-install noise, neighboring-radio and channel-occupancy observations for the selected location. Record any controller-driven channel change during acceptance. If the regulatory profile limits the channel choices, state how that constraint affected reuse and mitigation. This baseline gives future troubleshooting a reference point and prevents an unrelated interference change from being attributed to the hardware order.

Replacement dependency map

Map this unit to controller, licenses, authentication services, switch power, cable, bracket, antenna design and monitoring objects. For an end-of-sale platform, state which dependencies can be reused by the planned Catalyst migration and which require change. A nominal access-point replacement can fail when the surrounding platform was never inventoried. Keep the map with the asset rather than only in a one-time project file.

Related Aironet 2802 order records

• AIR-AP2802E-BK910C - compare antenna architecture and regulatory-domain evidence.
• AIR-AP2802E-BK910 - compare antenna architecture and regulatory-domain evidence.
• AIR-AP2802E-B-K9C - compare antenna architecture and regulatory-domain evidence.

Official evidence: Cisco Aironet 2800 Series data sheet; Cisco 2800 Series getting started guide; Cisco 2800 Series support and lifecycle page; and Cisco wireless compliance tool.