AIR-AP1852I-R-K9C Cisco Aironet 1852i 1.733Gbps Thoughput Access Point

AIR-AP1852I-R-K9C exact order identity

AIR-AP1852I-R-K9C is a 1852i indoor access point with integrated omnidirectional antennas in the Cisco Aironet 1850 Series. This exact SKU combines regulatory-domain token R 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.

R regulatory-domain evidence

Cisco lists this profile as 2.4 GHz channels 1-13; 5 GHz blocks at 5.180-5.320 and 5.660-5.805 GHz. The R profile uses a lower 5 GHz block and a distinct high block beginning at 5.660 GHz. That second boundary is different from the broader middle ranges used by other domains. Confirm the exact start and end of the high block in the controller output. Preserve that evidence with the R-domain destination check and post-install RF measurements.

Procurement inference: the high group begins at a distinctive boundary and should be treated separately from broad middle-band plans. Preserve the exact high-group channel output and test representative clients there. If the site migrates from a profile whose second group starts lower, revise the interference map and channel-reuse assumptions before installation. Similar overall channel counts do not make the profiles operationally equivalent.

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.

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.

Controlled spare policy

If purchased as a spare, name the protected site population, compatible controller image, storage location, storage conditions and periodic power-on test. Confirm that regulatory token, antenna architecture and mounting parts match the population it protects. Set a final-use review date. A stored unit can become unsuitable while untouched because controller software, country approval, certificates or network architecture may change. A spare 1852 must be checked against the protected controller release, certificate behavior, regulatory domain, antenna form and 2027 support cutoff before assignment.

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.

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.

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.

Receiving inspection

At receipt, compare model label, regulatory token, antenna form, quantity, serials and visible condition with the authorized order. Photograph labels before cartons are separated. Quarantine shortages, mixed units, damaged connectors or unapproved substitutions. Do not rely on a distributor description as evidence that the exact Cisco order arrived. Close the inspection only when every physical unit is accounted for. Receiving inspection should distinguish the internal-antenna 1852i from the external-antenna 1852e and should verify all carton quantities before labels are separated.

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