AIR-AP1852E-S-K9 Cisco Aironet 1852e 4x4 MIMO WiFi 5 Access Point

AIR-AP1852E-S-K9 exact order identity

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

S regulatory-domain evidence

Cisco lists this profile as 2.4 GHz channels 1-13; 5 GHz blocks at 5.180-5.320, 5.500-5.700, and 5.745-5.825 GHz. The S profile lists lower, middle and upper 5 GHz groups. The separation between middle and upper groups should remain explicit in RF planning and acceptance records. Validate all three groups after controller provisioning and compare enabled channels with the approved survey. Keep the S-domain lookup and controller export together for future audits.

Procurement inference: three listed 5 GHz groups give several planning pools, but destination approval still controls actual use. The survey should state how radios are distributed among lower, middle and upper groups, and acceptance should compare that plan with dynamic assignment. If one group is disabled locally or by policy, recalculate capacity and retain the exception instead of presenting the full S-profile table as deployed capability.

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

Mechanical installation record

List the bracket, ceiling or wall interface, enclosure requirement, safety restraint, service clearance and cable-entry plan before scheduling installation. Receiving should identify missing mechanical items before the access point reaches site. Photograph the mounted label and final cable entry, then record how the unit can be reached for replacement. A complete electronic order can still be an unusable deployment kit when mechanical dependencies are omitted. The 1852i and 1852e have different operating-temperature ranges, and an external-antenna deployment also requires a complete cable and mounting bill of materials.

Serial-level asset control

Capture chassis serial, base MAC address, carton reference, deployment site, controller assignment and asset owner. Reconcile the identifiers against the purchase line before activation. Multi-unit cartons require an entry for every physical access point; a carton SKU alone cannot show which unit was installed, held as a spare or returned. This record is also needed to trace support entitlement, replacement history and monitoring ownership. If the product came from a ten-unit pack, the 1852 carton identity must be expanded into ten individual records before support, return or replacement handling.

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.

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.

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.

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