AIR-AP2802I-T-K9C Cisco Aironet 2800i WiFi 5 4x4 MU-MIMO Access Point

AIR-AP2802I-T-K9C exact order identity

AIR-AP2802I-T-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 T, 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.

T regulatory-domain channel evidence

Cisco's 2800 Series data sheet lists the T profile as 2.4 GHz channels 1-11; 5 GHz blocks at 5.280-5.320, 5.500-5.700 excluding 5.600-5.640, and 5.745-5.825 GHz. The T profile has a short lower block, a middle block with an internal exclusion, and a separate upper block. A generic three-band summary would hide two important boundaries.

Inspect the short lower range and excluded middle sub-block in the controller export. Attach the result to the T-domain destination approval before enabling production radios. 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: this profile combines a short lower group with a middle exclusion and an upper group, so two separate checks can be missed by a generic template. Require the controller export to demonstrate both the lower boundary and the middle gap. If either differs, stop activation and review destination settings. Keep the result with the exact T-domain asset through controller upgrades.

Deployment evidence worksheet

Mechanical installation record

List the bracket, ceiling or wall interface, enclosure requirement, safety restraint, service clearance and cable-entry plan before scheduling installation. Receiving should identify missing mechanical items before the access point reaches site. Photograph the mounted label and final cable entry, then record how the unit can be reached for replacement. A complete electronic order can still be an unusable deployment kit when mechanical dependencies are omitted.

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.

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.

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.

Receiving inspection

At receipt, compare model label, regulatory token, antenna form, quantity, serials and visible condition with the authorized order. Photograph labels before cartons are separated. Quarantine shortages, mixed units, damaged connectors or unapproved substitutions. Do not rely on a distributor description as evidence that the exact Cisco order arrived. Close the inspection only when every physical unit is accounted for.

Fault-domain separation

Build the acceptance record so power, wired link, controller join, radio state, authentication and application reachability can be reviewed independently. Preserve timestamps and device identifiers across switch and controller logs. When a test fails, identify the failing boundary before replacing hardware. This avoids classifying a cable, policy or controller problem as an access-point defect and creates evidence that can be reused during support escalation.

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-TK910C - compare antenna architecture and regulatory-domain evidence.
• AIR-AP2802E-TK910 - compare antenna architecture and regulatory-domain evidence.
• AIR-AP2802E-T-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.