AIR-AP1852I-K-K9C Cisco Aironet 1852i Controller-based Access Point

AIR-AP1852I-K-K9C exact order identity

AIR-AP1852I-K-K9C is a 1852i indoor access point with integrated omnidirectional antennas in the Cisco Aironet 1850 Series. This exact SKU combines regulatory-domain token K 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 rates the internal antenna system at 3 dBi for 2.4 GHz and 5 dBi for 5 GHz, with 360-degree horizontal beamwidth. No external antenna is selected by this SKU. Preserve enclosure orientation, bracket, mounting height and post-install coverage because placement determines how the integrated pattern is used.

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.

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.

Survey-to-install reconciliation

Attach the approved RF survey location, mounting height, orientation, expected client density, channel width and neighboring-radio assumptions to the order. After installation, compare measured coverage and interference with that design. If ceiling construction, antenna placement or obstructions changed, document the deviation and repeat the affected measurements. This provides a site-specific acceptance reason for the exact unit instead of relying on a family data sheet alone. Relate the survey result to the 1852's 4x4:4 single-user and 4x4:3 multiuser 5 GHz design rather than treating the published 1.7 Gbps PHY rate as measured site throughput.

Quotation substitution gate

Compare antenna form, regulatory token, configuration suffix, pack quantity and complete Cisco part number on the authorized quotation. Treat any changed token as a substitution that requires a new technical and regulatory review. Procurement should not accept a different access-point order merely because the family name matches. Preserve the approved line, received label and exception decision so the final asset can be traced to the exact order reviewed here. A K9, K9C, K910, K910C, antenna-form or regulatory-token change is a different 1852 procurement line and must not be accepted as a cosmetic substitution.

Roaming acceptance

Define the neighboring access points and client types used for roaming validation. Record handoff behavior, interruption observed, authentication result and controller events along the intended movement path. Compare the outcome with the site's design target rather than declaring success from static association. Where this unit replaces an older AP, test both entry and exit from its cell so a local improvement does not hide a boundary problem. When replacing a neighboring legacy AP, preserve roaming evidence in both directions and compare it with the 1852's installed radio and channel state.

Monitoring handover

Assign owners for AP reachability, controller join failures, radio utilization, client health and switch-port errors. Confirm that the exact serial appears in inventory and monitoring, then test the alert path. Record dashboard object, notification route and escalation owner. Telemetry that is not tied to an owned asset does not provide a reliable service baseline and will not support later comparison after channel or software changes. Monitoring should identify the 1852 serial, controller object, both Ethernet interfaces, radio health and the team responsible for end-of-support migration.

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.

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