AIR-AP1852I-N-K9 Cisco Aironet 1852i Dual-band Access Point

AIR-AP1852I-N-K9 exact order identity

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

N regulatory-domain evidence

Cisco lists this profile as 2.4 GHz channels 1-11; 5 GHz blocks at 5.180-5.320 and 5.745-5.825 GHz. The N profile pairs an eleven-channel 2.4 GHz plan with separated lower and upper 5 GHz blocks. The 2.4 GHz boundary is part of the order's deployment evidence, not merely a 5 GHz consideration. Check both radio bands against the N-domain record. Preserve the controller country setting, 2.4 GHz channel limit and the two 5 GHz groups with the site acceptance report.

Procurement inference: this profile combines an eleven-channel 2.4 GHz boundary with separated lower and upper 5 GHz choices. Validate both bands in the same commissioning record; a correct 5 GHz result does not prove that the 2.4 GHz plan is appropriate. When a design uses 2.4 GHz for legacy or operational clients, retain a specific association and interference test for that population.

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.

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.

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.

Authentication path test

Commission representative clients through association, authentication, address assignment, DNS and application reachability. Preserve the identity policy used, test client type, result and relevant controller logs. An access point that joins its controller has not yet demonstrated the user path. Repeat the test after any controller, certificate or authentication-service change and retain failures separately from RF or switch-port evidence. Test the complete user path after the 1852 joins; the controller relationship alone does not prove client authentication, DHCP, DNS or application reachability.

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.

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