AIR-AP2802I-I-K9C Cisco Aironet 2800i Indoor Controller-based AP

AIR-AP2802I-I-K9C exact order identity

AIR-AP2802I-I-K9C 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 I, and a single-unit, configurable 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 K9C for a configurable single unit. The C suffix does not make the access point globally deployable; the final configured domain and destination approval must still be present on the quotation and received label. Hold the unit at receiving if the configured domain is absent or differs from the approved order. Preserve the configuration selection, chassis serial, destination evidence and controller-domain check as one release record. Because this is a configurable line, purchasing must retain the finally selected domain on both the authorized quotation and received label. The single unit needs one serial-level record, while accessories, controller readiness and destination approval remain separate acceptance items.

I regulatory-domain channel evidence

Cisco's 2800 Series data sheet lists the I profile as 2.4 GHz channels 1-13 and the 5.180-5.320 GHz lower block. The I profile listed by Cisco is confined to the lower 5 GHz block. Designs that depend on middle or upper 5 GHz capacity need revision before this SKU can be approved.

Commission with a lower-block-only channel plan and preserve the controller export. Recalculate co-channel reuse if the pre-purchase survey assumed additional 5 GHz spectrum. 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 lower-block-only 5 GHz plan places a tighter ceiling on channel diversity than profiles with middle or upper groups. Capacity approval should therefore show the client load, channel width and reuse plan that fit within this listed range. If the access point is a spare, verify that the protected population uses the same I-domain constraints before assigning it to emergency replacement stock.

Deployment evidence worksheet

Power-state acceptance

Measure power after the access point has joined its controller and the planned radios and services are active. Record switch model, port, negotiated power level, LLDP result and any reduced-capability warning. An idle boot result is not sufficient evidence for the deployed power budget. If an injector is proposed, verify its supported use and include its exact identity in the maintained bill of materials rather than treating it as an unspecified accessory.

Serial-level asset control

Capture chassis serial, base MAC address, carton reference, deployment site, controller assignment and asset owner. Reconcile the identifiers against the purchase line before activation. Multi-unit cartons require an entry for every physical access point; a carton SKU alone cannot show which unit was installed, held as a spare or returned. This record is also needed to trace support entitlement, replacement history and monitoring ownership.

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.

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.

Operational log retention

Store the initial controller events, switch-port state, radio assignment, channel list and client test results with a consistent asset identifier. Define how long commissioning evidence is retained and who can retrieve it. A later firmware, controller or RF change should add a new dated observation rather than overwrite the original. The resulting history supports lifecycle decisions and distinguishes a new regression from the accepted baseline.

Handover completeness

The handover package should include exact order identity, destination approval, serial record, controller evidence, switch port, mounting or antenna record, user-path tests and named operational owners. Review the package with the receiving team and list unresolved exceptions. A unit is not operationally accepted when important evidence remains only in installer notes, email attachments or an unowned temporary dashboard.

Related Aironet 2802 order records

• AIR-AP2802E-IK910C - compare antenna architecture and regulatory-domain evidence.
• AIR-AP2802E-IK910 - compare antenna architecture and regulatory-domain evidence.
• AIR-AP2802E-I-K9 - 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.