AIR-AP2802E-EK910 Cisco Aironet 2800e Dual-band 802.11a/g/n/ac 10 APs

AIR-AP2802E-EK910 exact order identity

AIR-AP2802E-EK910 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 E, 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.

E regulatory-domain channel evidence

Cisco's 2800 Series data sheet lists the E profile as 2.4 GHz channels 1-13; 5 GHz blocks at 5.180-5.320 and 5.500-5.700 GHz, excluding 5.600-5.640 GHz. The E profile combines lower and middle 5 GHz operation but documents an internal exclusion in the middle block. Survey and controller evidence must show that the gap was understood.

Compare the enabled channel export with the E-domain profile, paying particular attention to the excluded sub-block. Preserve the lookup date, country selection and controller result in the asset file. 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's excluded middle sub-block creates a specific migration check. Preserve the prior controller channel template, then prove that the new or restored template does not reintroduce the excluded range. If channel capacity was calculated from a continuous middle block, correct the design assumptions and record the narrower usable plan before installation approval.

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.

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.

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.

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.

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.

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-AP2802I-E-K9C - compare antenna architecture and regulatory-domain evidence.
• AIR-AP2802I-EK910 - compare antenna architecture and regulatory-domain evidence.
• AIR-AP2802E-EK910C - compare order quantity or configuration 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.