AIR-AP2802I-AK910 Cisco Aironet 2800i Indoor 4x4 MU-MIMO Access Point

AIR-AP2802I-AK910 exact order identity

AIR-AP2802I-AK910 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 A, and a fixed-domain ten-unit eco-pack.

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 K910 for a ten-access-point eco-pack. The carton part number does not replace serial-level control, and all ten units must retain the stated regulatory-domain identity. Reconcile ten chassis serials and MAC addresses against the carton and purchase line. Assign every unit to a destination and controller record; a quantity shortage, mixed domain or substituted antenna form is a receiving exception. 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 carton is not the deployable asset: each of the ten access points needs its own serial, location, controller and acceptance result.

A regulatory-domain channel evidence

Cisco's 2800 Series data sheet lists the A profile as 2.4 GHz channels 1-11; 5 GHz blocks at 5.180-5.320, 5.500-5.700 excluding 5.600-5.640, and 5.745-5.825 GHz. The A plan combines lower, middle and upper 5 GHz blocks, but the documented gap inside the middle block matters. The RF design and controller template must preserve that exclusion instead of treating the listed span as continuous.

Export the controller channel list after provisioning and compare it with the approved A-domain record. Investigate any channel inside the excluded middle sub-block or any missing approval evidence before service activation. 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 is useful only when the destination approval and controller expose the documented lower, split-middle and upper choices. The middle exclusion should appear explicitly in the site worksheet, because a broad frequency-range label can conceal it. When migrating controllers, compare exported enabled-channel lists before and after the move; do not use unchanged SSID service as proof that the regulatory plan remained intact.

Deployment evidence worksheet

Controller join evidence

Stage the access point on the controller release intended for production. Retain the controller model, software version, discovery path, authorization method and first successful CAPWAP join. Confirm that configuration download completes and that both radios reach an expected operational state. Remove any temporary staging authorization before handover. This evidence separates an orderable access point from a unit that has actually been proven compatible with the planned controller environment.

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.

Survey-to-install reconciliation

Attach the approved RF survey location, mounting height, orientation, expected client density, channel width and neighboring-radio assumptions to the order. After installation, compare measured coverage and interference with that design. If ceiling construction, antenna placement or obstructions changed, document the deviation and repeat the affected measurements. This provides a site-specific acceptance reason for the exact unit instead of relying on a family data sheet alone.

Country approval retention

Save the Cisco compliance lookup result, lookup date, deployment country, approved regulatory token and reviewer. If the destination changes, stop and repeat the approval rather than moving the unit on the strength of an earlier purchase. Compare the controller country setting and available channels with the retained evidence. Regulatory eligibility is a deployment condition and cannot be inferred from connector fit, stock location or a similar-looking part number.

Controlled spare policy

If purchased as a spare, name the protected site population, compatible controller image, storage location, storage conditions and periodic power-on test. Confirm that regulatory token, antenna architecture and mounting parts match the population it protects. Set a final-use review date. A stored unit can become unsuitable while untouched because controller software, country approval, certificates or network architecture may change.

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.

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.

Related Aironet 2802 order records

• AIR-AP2802E-AK910C - compare antenna architecture and regulatory-domain evidence.
• AIR-AP2802E-A-K9C - compare antenna architecture and regulatory-domain evidence.
• AIR-AP2802E-A-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.