AIR-AP1852E-K-K9 Cisco Aironet Enterprise-class 1852e WiFi 5 AP

AIR-AP1852E-K-K9 exact order identity

AIR-AP1852E-K-K9 is a 1852e indoor access point for separately purchased external antennas in the Cisco Aironet 1850 Series. This exact SKU combines regulatory-domain token K with a single-unit fixed-domain K9 order. The platform is a dual-band 802.11ac Wave 2 access point with four 5 GHz spatial streams in single-user operation and three in multiuser operation.

Antenna and environmental boundary

Cisco states that external antennas are sold separately and certifies the platform for antenna gains up to 6 dBi at both 2.4 and 5 GHz. Record the approved Cisco antenna part numbers, four radio paths, gain, pattern, cable loss, connectors and mounting orientation. A compatible connector alone is not regulatory or RF-design evidence.

Order and controller boundary

Cisco lists K9 as a controller-based dual-band 802.11ac Wave 2 order. Match the complete fixed-domain PID at receiving. Create one serial-level asset record and stage CAPWAP join, controller software, country setting and radio operation before production release.

K regulatory-domain evidence

Cisco lists this profile as 2.4 GHz channels 1-13; 5 GHz blocks at 5.180-5.320, 5.500-5.620, and 5.745-5.805 GHz. The K profile has three separated 5 GHz groups, with narrower middle and upper limits than several neighboring profiles. Those boundaries must be reflected in controller and survey records. Verify all three channel groups and their upper limits after the AP joins the controller. Retain the output with the K-domain purchase line so a broader template cannot be mistaken for compliance.

Procurement inference: three separated groups with distinct upper limits make boundary verification more important than a simple channel count. The acceptance package should list each enabled group and compare it with the K-domain survey. If the controller aggregates the output into one display, export a detailed channel list for evidence. Recheck those boundaries after controller migration or country-setting changes.

Power and interface boundary

The 1852 provides a PoE Gigabit uplink and a Gigabit AUX port for link aggregation. Cisco states that 802.3af disables AUX and USB on both antenna forms and reduces the 1852e 2.4 GHz radio from 3x4 to 2x3. Record negotiated power before promising the complete interface and radio state.

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. For this 1852 order, include the AireOS or Catalyst 9800 release actually used and note whether the unit is controller-managed or operating in an approved Mobility Express role.

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. The 1852 draws up to 20.9 W; 802.3af also disables AUX Ethernet and USB, while the external-antenna 1852e reduces its 2.4 GHz radio from 3x4 to 2x3.

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. The 1852i and 1852e have different operating-temperature ranges, and an external-antenna deployment also requires a complete cable and mounting bill of materials.

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. If the product came from a ten-unit pack, the 1852 carton identity must be expanded into ten individual records before support, return or replacement handling.

Security baseline

Retain the approved controller policy, management authorization, certificate or trust workflow, client authentication test and logging destination. Confirm behavior on the deployed controller software instead of promising a protocol from the hardware family name. Remove temporary onboarding access and verify administrative reachability after handover. This keeps product identity separate from software-dependent security claims. Record the security behavior verified on the deployed controller release; do not turn a family data-sheet capability into an unconditional software claim.

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. Capacity acceptance should show actual client mix, airtime and retries under the available regulatory-domain channels, not only a maximum PHY figure.

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. The 1852 domain table varies materially by token, so preserve interference observations against the exact enabled-channel list rather than a generic country template.

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. Cisco names the Catalyst 9115AX family as the migration option in the lifecycle bulletin; map controller, power, cabling, mount and antenna changes before replacement.

Lifecycle decision

Cisco ended sale of the Aironet 1850 Series on 1 May 2022, ended software maintenance on 1 May 2023 and lists 30 April 2027 as the last support date. Cisco identifies Catalyst 9115AX as the migration family. Available inventory does not extend those milestones.

Related Aironet 1852 order records

• AIR-AP1852I-KK910C - compare antenna form and domain evidence.
• AIR-AP1852I-K-K9C - compare antenna form and domain evidence.
• AIR-AP1852I-K-K9 - compare antenna form and domain evidence.

Official evidence: Cisco Aironet 1850 Series data sheet; Cisco Aironet 1850 hardware guide; Cisco Aironet 1850 lifecycle bulletin; and Cisco wireless compliance tool.