AIR-AP2802E-AK910 Cisco Aironet 2800e Eco-pack 4x4:3 MU-MIMO 10 APs

AIR-AP2802E-AK910 exact order identity

AIR-AP2802E-AK910 is a Cisco Aironet 2800 Series controller-based 802.11ac Wave 2 access point order. The exact line combines a 2802E indoor access point for external antennas, regulatory-domain token A, and a fixed-domain ten-unit eco-pack.

Antenna boundary

Cisco documents four RP-TNC antenna connectors plus a Smart Antenna connector on the 2802E. Antennas are a separate engineered part of the deployment bill of materials. Before release, record each Cisco-supported antenna part number, connector use, gain, pattern, cable type, cable loss, mounting orientation and local approval. A connector fit alone does not establish RF performance or regulatory suitability.

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

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.

Serial-level asset control

Capture chassis serial, base MAC address, carton reference, deployment site, controller assignment and asset owner. Reconcile the identifiers against the purchase line before activation. Multi-unit cartons require an entry for every physical access point; a carton SKU alone cannot show which unit was installed, held as a spare or returned. This record is also needed to trace support entitlement, replacement history and monitoring ownership.

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.

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.

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.

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.

Related Aironet 2802 order records

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