AIR-AP1852E-B-K9 Cisco Aironet 1852e 802.11a/g/n/ac Access Point

AIR-AP1852E-B-K9 exact order identity

AIR-AP1852E-B-K9 is a 1852e indoor access point for separately purchased external antennas in the Cisco Aironet 1850 Series. This exact SKU combines regulatory-domain token B 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 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 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.

B 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.720, and 5.745-5.825 GHz. The B plan contains a broad middle 5 GHz range followed by a separate upper block. Capacity planning should identify which radios use each block and should not copy a narrower domain's channel template. Retain a controller export showing the enabled lower, middle and upper channel sets. Compare the installed country setting, dynamic channel assignment and survey plan before accepting the site.

Procurement inference: the comparatively broad middle range and separate upper range can influence how capacity is distributed across radios. Preserve the survey's planned channel groups and compare them with the controller's dynamic assignment after a representative operating period. If the destination authorization narrows the available set, update the capacity calculation and acceptance record rather than leaving a B-profile assumption in the design.

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

Country approval retention

Save the Cisco compliance lookup result, lookup date, deployment country, approved regulatory token and reviewer. If the destination changes, stop and repeat the approval rather than moving the unit on the strength of an earlier purchase. Compare the controller country setting and available channels with the retained evidence. Regulatory eligibility is a deployment condition and cannot be inferred from connector fit, stock location or a similar-looking part number. Cisco explicitly makes the customer responsible for country approval; retain the lookup alongside the 1852's controller country and enabled-channel evidence.

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.

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.

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.

Replacement dependency map

Map this unit to controller, licenses, authentication services, switch power, cable, bracket, antenna design and monitoring objects. For an end-of-sale platform, state which dependencies can be reused by the planned Catalyst migration and which require change. A nominal access-point replacement can fail when the surrounding platform was never inventoried. Keep the map with the asset rather than only in a one-time project file. Cisco names the Catalyst 9115AX family as the migration option in the lifecycle bulletin; map controller, power, cabling, mount and antenna changes before replacement.

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.

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