AIR-AP2802E-H-K9C Cisco Aironet 2800e 5.2 Gbps WiFi 5 Access Point

AIR-AP2802E-H-K9C exact order identity

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

H regulatory-domain channel evidence

Cisco's 2800 Series data sheet lists the H profile as 2.4 GHz channels 1-13; 5 GHz blocks at 5.150-5.350 and 5.745-5.825 GHz. The H profile starts its lower 5 GHz range at 5.150 GHz and also provides a separated upper block. That lower boundary distinguishes it from nearby domain profiles.

Capture the controller's complete lower-range and upper-range channel output. Match it to the approved H-domain destination and investigate a template that begins at a different lower boundary. 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: because the lower group begins below the more common 5.180 GHz boundary, country approval and controller output must be read together. Do not infer that every channel inside the numerical span is available at the destination. Preserve the exact enabled-channel export and associate post-install measurements with it so later troubleshooting can distinguish a regulatory change from an RF-performance change.

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.

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.

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.

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.

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.

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