AIR-AP2802I-FK910 Cisco Aironet 2800i Indoor Eco-pack 10 Access Points

AIR-AP2802I-FK910 exact order identity

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

F regulatory-domain channel evidence

Cisco's 2800 Series data sheet lists the F profile as 2.4 GHz channels 1-13; 5 GHz blocks at 5.250-5.350 and 5.725-5.825 GHz. The F profile is split between a compact mid-lower block and a high block. It does not match the common 5.180 GHz starting point, so imported controller templates require deliberate review.

Validate both separated channel groups on the target controller and confirm that the RF survey used the same boundaries. Record any disabled channel and its local regulatory reason. 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 two separated 5 GHz ranges call for a survey that distinguishes the mid-lower group from the high group. Confirm that expected clients, neighboring radios and controller policy can use the approved choices at the destination. When replacing a unit from a different domain, do not preserve old channel assignments blindly; generate a new assignment and compare measured interference in both F-profile groups.

Deployment evidence worksheet

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.

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.

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.

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.

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.

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