AIR-AP1852I-Z-K9 Cisco Aironet 1852i Beamforming Access Point

AIR-AP1852I-Z-K9 exact order identity

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

Z regulatory-domain evidence

Cisco lists this profile as 2.4 GHz channels 1-11; 5 GHz blocks at 5.180-5.320, 5.500-5.700 excluding 5.600-5.640, and 5.745-5.825 GHz. The Z profile spans lower, middle and upper 5 GHz groups while retaining a documented gap in the middle group. That exclusion must survive controller template changes. Compare the live channel list with the Z-domain evidence after every initial join or controller migration. Treat an enabled channel inside the excluded range as a release blocker.

Procurement inference: lower, middle and upper groups provide broad planning options, but the documented middle gap remains a hard evidence point. Create a channel-list comparison that highlights the excluded range and retain it with the country lookup. After automatic channel changes or controller migration, repeat that comparison. Stable client service alone does not prove that the Z-domain constraints are still being enforced.

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

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 nearby Aironet 2802 line 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.

Software lifecycle file

Record the controller release approved for this unit, the source used to verify support, the last tested date and the owner for software advisories. Available hardware does not prove compatibility with a current or future controller train. Review Cisco support information before every expansion or replacement. The lifecycle file should also state when this Aironet generation must leave service and which surrounding dependencies need migration. Cisco ended 1850 Series software maintenance in 2023, so controller compatibility evidence is especially important for inventory purchased late in the lifecycle.

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.

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.

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.

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-Z-K9C - compare antenna form and domain evidence.
• AIR-AP1852E-EK910C - compare antenna form and domain evidence.
• AIR-AP1852E-BK910C - 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.