AIR-AP2802I-DK910 Cisco Aironet 2800i Enterprise WiFi 5 Access Point

AIR-AP2802I-DK910 exact order identity

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

D regulatory-domain channel evidence

Cisco's 2800 Series data sheet lists the D profile as 2.4 GHz channels 1-11; 5 GHz blocks at 5.180-5.320 and 5.745-5.825 GHz. The D profile uses separated lower and upper 5 GHz blocks with no documented middle block. A channel plan that assumes a continuous 5 GHz range is therefore not suitable evidence for this order.

Verify that the controller presents the two expected 5 GHz groups and excludes an unapproved middle range. Store the result with the deployment country lookup and the exact D-domain quotation. 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 separation between lower and upper 5 GHz groups should be represented as two planning pools. During acceptance, compare utilization and interference in each pool rather than averaging all 5 GHz observations together. If a replacement AP was previously using a middle-range channel under another profile, document the revised reuse plan before treating the D-domain unit as a direct substitution.

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.

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.

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.

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.

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.

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.

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