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

AIR-AP4800-Z-K9C Order Identity

AIR-AP4800-Z-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 Z, 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 Z. Treat that token as an identifier, not a country name. Complete order-country consistency and local spectrum validation 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 Z.

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.

Software lifecycle

Check the target controller release against Cisco support documentation and the approved migration architecture before buying additional 3800 Series capacity. The lifecycle note should name the approved controller release, last tested release, security-maintenance owner and migration review date. Review Cisco notices before each expansion because available inventory does not extend software compatibility. A replacement design should cover controller, licensing, power, cabling and mounting rather than only the radio unit.

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.

Site acceptance

Commission association, authentication, roaming, uplink negotiation and monitoring at the intended location. Preserve results that can be compared after later changes. The handover record should contain client authentication, DHCP and DNS checks, roaming evidence, controller alarms, switch-port counters and a monitoring owner. Test from representative client types in the intended coverage area. Acceptance is incomplete when the AP merely joins the controller but user and operational paths remain unverified.

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.

Migration dependency

Inventory controller, licensing, switch power, cabling and mounting dependencies that must change when the 3802 is replaced by a newer platform. Map the existing AP to its controller, licenses, authentication services, switch port, power budget, cable, bracket and monitoring objects. The successor plan should state which dependencies can be reused and which require change. This prevents a nominal AP replacement from failing because the surrounding platform was never inventoried.

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-S-K9C
• AIR-AP4800-Q-K9C
• AIR-AP4800-K-K9C

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