AIR-AP1852E-S-K9C Cisco Aironet 1852e Indoor Dual-band WiFi 5 AP

AIR-AP1852E-S-K9C exact order identity

AIR-AP1852E-S-K9C is a 1852e indoor access point for separately purchased external antennas in the Cisco Aironet 1850 Series. This exact SKU combines regulatory-domain token S with a single-unit configurable K9C 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 K9C as a configurable controller-based order, and its lifecycle table describes affected K9C lines as Mobility Express products. Retain the final domain and software role on the quotation and received unit. Prove the intended controller or Mobility Express state instead of inferring it from the suffix alone.

S 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.700, and 5.745-5.825 GHz. The S profile lists lower, middle and upper 5 GHz groups. The separation between middle and upper groups should remain explicit in RF planning and acceptance records. Validate all three groups after controller provisioning and compare enabled channels with the approved survey. Keep the S-domain lookup and controller export together for future audits.

Procurement inference: three listed 5 GHz groups give several planning pools, but destination approval still controls actual use. The survey should state how radios are distributed among lower, middle and upper groups, and acceptance should compare that plan with dynamic assignment. If one group is disabled locally or by policy, recalculate capacity and retain the exception instead of presenting the full S-profile table as deployed capability.

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.

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. Rollback must account for controller image alignment, country configuration and any Mobility Express primary role, not only the physical swap.

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.

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.

Fault-domain separation

Build the acceptance record so power, wired link, controller join, radio state, authentication and application reachability can be reviewed independently. Preserve timestamps and device identifiers across switch and controller logs. When a test fails, identify the failing boundary before replacing hardware. This avoids classifying a cable, policy or controller problem as an access-point defect and creates evidence that can be reused during support escalation. Use controller, switch and client timestamps to separate a PoE/AUX limitation, CAPWAP issue, RF condition and authentication failure before declaring a hardware defect.

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. Preserve the original 1852 controller join, power mode, AUX state, channel list and client tests so later changes can be compared with an 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. The final handover should include the exact PID, regulatory approval, serial, antenna or mounting record, power mode, both Ethernet interfaces and lifecycle owner.

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-SK910C - compare antenna form and domain evidence.
• AIR-AP1852I-S-K9C - compare antenna form and domain evidence.
• AIR-AP1852E-S-K9 - compare order 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.