AIR-AP2802I-G-K9 Cisco Aironet 2800i Indoor Access Point

AIR-AP2802I-G-K9 exact order identity

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

G regulatory-domain channel evidence

Cisco's 2800 Series data sheet lists the G profile as 2.4 GHz channels 1-13 and the 5.745-5.825 GHz upper block. Cisco lists the G profile with an upper 5 GHz block and no lower or middle 5 GHz block. This changes available channel count and makes destination-specific capacity validation important.

Use an upper-band-specific commissioning checklist. Confirm controller country, available channel list and post-install utilization before accepting a design that was sized using another domain. 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 listed upper-only 5 GHz choice makes channel reuse and client compatibility central to acceptance. Record the client mix used during testing and verify association on approved upper-block channels. If the site's earlier survey relied on lower or DFS middle channels, the design requires revision rather than a simple model substitution, even when antenna architecture and controller family remain unchanged.

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.

Ethernet and cabling proof

Preserve the permanent-link test, patch-lead identities, switch port, negotiated Ethernet rate and error counters. Investigate pair faults, excessive length or rate fallback before wireless acceptance begins. A link light only proves connectivity at some rate; it does not demonstrate the intended uplink performance. Tie the cable result to the AP serial so a later throughput problem can be separated from radio, controller and wired-path causes.

Software lifecycle file

Record the controller release approved for this unit, the source used to verify support, the last tested date and the owner for software advisories. Available hardware does not prove compatibility with a current or future controller train. Review Cisco support information before every expansion or replacement. The lifecycle file should also state when this Aironet generation must leave service and which surrounding dependencies need migration.

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.

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.

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.

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.

Related Aironet 2802 order records

• AIR-AP2802E-GK910C - compare antenna architecture and regulatory-domain evidence.
• AIR-AP2802E-GK910 - compare antenna architecture and regulatory-domain evidence.
• AIR-AP2802E-G-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.