AIR-AP2802E-E-K9 Cisco Aironet 2800e Enterprise 802.11ac Wave 2 AP

AIR-AP2802E-E-K9 exact order identity

AIR-AP2802E-E-K9 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 single-unit, fixed regulatory-domain order.

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 K9 for one access point. This line already carries a regulatory-domain token, so receiving must match the complete part number rather than accepting another domain as an equivalent. Create one asset record for the chassis serial and MAC address. Link that record to the approved destination, controller, switch port, mounting position and compliance lookup before the unit joins production. 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 single unit needs one serial-level record, while accessories, controller readiness and destination approval remain separate acceptance items.

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

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.

Software lifecycle file

Record the controller release approved for this unit, the source used to verify support, the last tested date and the owner for software advisories. Available hardware does not prove compatibility with a current or future controller train. Review Cisco support information before every expansion or replacement. The lifecycle file should also state when this Aironet generation must leave service and which surrounding dependencies need migration.

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.

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.

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.

Related Aironet 2802 order records

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