AIR-AP4800-H-K9C - Cisco Aironet 4800 Access Point

AIR-AP4800-H-K9C Order Identity

AIR-AP4800-H-K9C is a Cisco Aironet 4800 Series, controller-based 802.11ac Wave 2 access point order. This exact SKU is a 4800 internal-antenna access point, carries regulatory-domain token H, and uses a configurable single-unit order.

Antenna and quantity boundary

Integrated multiradio antenna system; no external Wi-Fi antenna is selected as part of this SKU. Confirm mounting orientation, ceiling structure, Hyperlocation requirements and RF survey assumptions because the antenna system is integral to the platform.

This K9 order form represents one access point; antennas, mounting choices, power source and controller dependencies remain separate unless the authorized bill of materials states otherwise.

The C suffix marks a configurable order form. The final Cisco quotation must preserve the selected regulatory domain and any configuration choices; the suffix does not make the unit globally deployable.

Regulatory-domain control

The order carries regulatory-domain token H. Treat that token as an identifier, not a country name. Complete import destination check and approved channel-plan evidence against Cisco's current compliance resources before shipment or activation.

Cisco uses the variable regulatory-domain position in its ordering structure. Deployment eligibility must be checked for the destination country; this page does not infer a country mapping from token H.

Controller readiness

Record the intended Cisco wireless controller, supported software train and join method. Validate the AP on a staging network before changing the production RF plan. The acceptance file should identify the controller address, discovery path, AP authorization method and the release evidence used for approval. Capture the first successful join, configuration download and radio state, then remove any temporary staging authorization. This makes a later controller migration traceable without claiming that every software release supports the hardware.

Replacement planning

Cisco lists the 3800 Series in its end-of-life notices. Record the permitted service horizon, replacement trigger and successor design with this purchase. Document the event that ends further 3802 deployment, the approved successor family and any controller coexistence constraint. Include funding, survey impact and installation sequencing. If the item is purchased as a spare, set a final-use date so old inventory does not silently outlive the network's supported architecture.

Spare policy

State whether the unit is production capacity, a cold spare or a replacement. Define firmware, storage, periodic test and ownership requirements for unused stock. A spare should have a named site scope, compatible controller image, storage condition and periodic power-on test. Record whether its regulatory domain, antenna form and mounting kit match the protected population. Before use, repeat compliance and software checks because suitability can change while the unit is held in stock.

Antenna governance

Keep antenna identity and approved installation conditions with the AP record. A matching connector alone is not evidence of regulatory or RF suitability. For external-antenna models, preserve manufacturer part numbers, connector arrangement, gain, pattern, cable type, loss and mounting orientation. For internal-antenna models, preserve enclosure orientation and placement constraints. In both cases, compare the installed design with country approval and the RF survey before service acceptance.

Monitoring ownership

Assign owners for controller alarms, switch-port health, radio utilization and software advisories so the installed AP remains observable after handover. Monitoring handover should name the team that owns AP reachability, controller join failures, radio utilization, client health and switch-port errors. Define alert thresholds and an escalation path, then verify that the exact serial appears in the operational inventory. Unowned telemetry does not provide a reliable service baseline.

Security baseline

Record the approved controller policy, management access, certificate handling and authentication test. Do not infer current security support from the hardware name alone. Retain the controller policy name, management authorization, certificate or trust workflow, authentication test and logging destination used at commissioning. Confirm the supported security behavior on the deployed software release. The hardware family alone must not be used to promise a feature or protocol that has not been validated.

Lifecycle and migration evidence

Cisco's support site lists an end-of-life announcement for the Cisco Aironet 4800 Series. Confirm current support dates, controller compatibility and the approved replacement path before treating available stock as suitable for a new deployment.

Related 4800 internal-antenna access point records

• AIR-AP4800-R-K9
• AIR-AP4800-E1-K9C
• AIR-AP4800-B1-K9C

Official evidence: Cisco Aironet 4800 Series data sheet, Cisco Aironet 4800 Series getting started guide, and Cisco end-of-life notices.