AIR-AP1852I-Q-K9C Cisco Aironet 1852i Beamforming Access Point

AIR-AP1852I-Q-K9C exact order identity

AIR-AP1852I-Q-K9C is a 1852i indoor access point with integrated omnidirectional antennas in the Cisco Aironet 1850 Series. This exact SKU combines regulatory-domain token Q with a single-unit configurable K9C 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 K9C as a configurable controller-based order, and its lifecycle table describes affected K9C lines as Mobility Express products. Retain the final domain and software role on the quotation and received unit. Prove the intended controller or Mobility Express state instead of inferring it from the suffix alone.

Q regulatory-domain evidence

Cisco lists this profile as 2.4 GHz channels 1-13; 5 GHz blocks at 5.180-5.320 and 5.500-5.700 GHz. The Q profile provides lower and continuous middle 5 GHz blocks without the upper block listed for some domains. Capacity and interference planning should use those two groups only. Export the lower and middle channel sets from the target controller and compare them with the Q-domain survey. Escalate an upper-band dependency before the purchase is released.

Procurement inference: the absence of a listed upper block means that lower and middle spectrum must carry the intended design. Before purchase, confirm that survey capacity and neighboring deployments do not depend on upper-band separation. During acceptance, record utilization in both available groups and document any controller policy that further narrows them. A different domain's three-group template is not suitable substitution evidence.

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

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.

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.

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.

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.

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.

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