AIR-AP2802E-D-K9C Cisco Aironet 2800e Enterprise WiFi5 Access Point

AIR-AP2802E-D-K9C exact order identity

AIR-AP2802E-D-K9C 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 D, and a single-unit, configurable 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 K9C for a configurable single unit. The C suffix does not make the access point globally deployable; the final configured domain and destination approval must still be present on the quotation and received label. Hold the unit at receiving if the configured domain is absent or differs from the approved order. Preserve the configuration selection, chassis serial, destination evidence and controller-domain check as one release record. Because this is a configurable line, purchasing must retain the finally selected domain on both the authorized quotation and received label. The single unit needs one serial-level record, while accessories, controller readiness and destination approval remain separate acceptance items.

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

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.

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.

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.

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.

Interference baseline

Preserve the pre-install and post-install noise, neighboring-radio and channel-occupancy observations for the selected location. Record any controller-driven channel change during acceptance. If the regulatory profile limits the channel choices, state how that constraint affected reuse and mitigation. This baseline gives future troubleshooting a reference point and prevents an unrelated interference change from being attributed to the hardware order.

Replacement dependency map

Map this unit to controller, licenses, authentication services, switch power, cable, bracket, antenna design and monitoring objects. For an end-of-sale platform, state which dependencies can be reused by the planned Catalyst migration and which require change. A nominal access-point replacement can fail when the surrounding platform was never inventoried. Keep the map with the asset rather than only in a one-time project file.

Related Aironet 2802 order records

• AIR-AP2802I-DK910C - compare antenna architecture and regulatory-domain evidence.
• AIR-AP2802I-DK910 - compare antenna architecture and regulatory-domain evidence.
• AIR-AP2802I-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.