AIR-AP2802I-DK910C Cisco Aironet 2800i Enterprise Eco-pack 10 APs

AIR-AP2802I-DK910C exact order identity

AIR-AP2802I-DK910C 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 configurable 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 K910C for a configurable ten-access-point eco-pack. Configuration selection and physical quantity are separate acceptance gates: the chosen domain must be approved and ten individual units must be reconciled. Retain the configured-domain evidence with the carton record, then create ten serial-level asset rows. Do not release a partial, mixed-domain or unconfigured carton to installation without a documented correction. Because this is a configurable line, purchasing must retain the finally selected domain on both the authorized quotation and received label. 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.

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.

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.

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.

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.

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-DK910 - 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.