AIR-AP1852E-F-K9 Cisco Aironet 1852e Indoor WiFi 5 Access Points

AIR-AP1852E-F-K9 exact order identity

AIR-AP1852E-F-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 F 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.

F regulatory-domain evidence

Cisco lists this profile as 2.4 GHz channels 1-13; 5 GHz blocks at 5.250-5.350 and 5.725-5.825 GHz. The F profile is split between a compact mid-lower block and a high block. It does not match the common 5.180 GHz starting point, so imported controller templates require deliberate review. Validate both separated channel groups on the target controller and confirm that the RF survey used the same boundaries. Record any disabled channel and its local regulatory reason.

Procurement inference: the two separated 5 GHz ranges call for a survey that distinguishes the mid-lower group from the high group. Confirm that expected clients, neighboring radios and controller policy can use the approved choices at the destination. When replacing a unit from a different domain, do not preserve old channel assignments blindly; generate a new assignment and compare measured interference in both F-profile groups.

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

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.

Ethernet and cabling proof

Preserve the permanent-link test, patch-lead identities, switch port, negotiated Ethernet rate and error counters. Investigate pair faults, excessive length or rate fallback before wireless acceptance begins. A link light only proves connectivity at some rate; it does not demonstrate the intended uplink performance. Tie the cable result to the AP serial so a later throughput problem can be separated from radio, controller and wired-path causes. The platform has one PoE Gigabit interface and one Gigabit AUX interface used for link aggregation, so preserve both link states and the power condition under which AUX is available.

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.

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.

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