AIR-AP1832I-A-K9C Cisco Aironet 1832i Indoor Mobility Express AP

AIR-AP1832I-A-K9C exact order identity

AIR-AP1832I-A-K9C is a Cisco Aironet 1832i indoor access point with integrated antennas. This exact PID combines regulatory-domain token A with a single configurable K9C Mobility Express order. Cisco documents 802.11ac Wave 2, 3x3 MIMO with two spatial streams and a maximum 5-GHz PHY rate of 867 Mbps.

Integrated-antenna boundary

The 1832i antenna system is internal. No external antenna is selected by this access-point PID, so mounting location, orientation, ceiling construction and the post-install survey determine how the published platform is used.

Software and order boundary

Cisco identifies AIR-AP1832I-x-K9C as configurable and supplied with the default Mobility Express software option. Preserve the intended Mobility Express or external-controller role, actual software release and conversion state instead of inferring the live role from the carton alone.

A regulatory-domain evidence

Cisco treats the letter as a regulatory-domain identifier and requires approval for the country of use; it is not a country name. Retain the destination-country result, the exact A-domain PID and the controller country setting in one approval record.

Use receiving as the A-domain control point: photograph the carton PID, reconcile it with the purchase order and attach the Cisco lookup before the serial is released. At commissioning, compare the controller country setting with that same record. A return replacement must repeat both checks because matching enclosure and antenna form do not establish matching regulatory identity.

Power and interface boundary

The AP supports 802.3af, 802.3at, Enhanced PoE, a local power supply and Cisco power injectors. Cisco lists a 15.4 W draw and states that USB is disabled when 802.3af is used. Record the negotiated power and the single Gigabit Ethernet uplink state.

Lifecycle decision

Cisco ended sale of the Aironet 1830 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 these dates.

Deployment evidence worksheet

Survey-to-install reconciliation

Attach the approved RF survey location, mounting height, orientation, expected client density, channel width and neighboring-radio assumptions to the order. After installation, compare measured coverage and interference with that design. If ceiling construction, antenna placement or obstructions changed, document the deviation and repeat the affected measurements. This provides a site-specific acceptance reason for the exact unit instead of relying on a family data sheet alone. Compare the installed integrated-antenna orientation and measured coverage with the approved survey instead of relying on the family data sheet.

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 makes the customer responsible for country approval; keep the dated compliance lookup with the 1832i serial and controller country.

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 1832i should be tested against the protected controller release, domain, mounting hardware and April 2027 support cutoff.

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. Roaming acceptance should identify neighboring cells, client type and controller events rather than treating static association as proof.

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 connect the 1832i serial with join state, radio health, Ethernet errors, client experience and lifecycle ownership.

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 which security functions are actually configured on the deployed controller release; do not present optional family capabilities as enabled facts.

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 evidence should use measured airtime, retries, client mix and channel width rather than the published 867-Mbps 5-GHz PHY rate.

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 power, CAPWAP, RF and authentication faults before declaring hardware failure.

Related Aironet 1832 order records

• AIRAP1832I-AK910C - compare software and procurement form.
• AIR-AP1832I-A-K9 - compare software and procurement form.
• AIRAP1832I-ZK910C - compare regulatory-domain evidence.

Official evidence: Cisco Aironet 1830 Series data sheet; Cisco Aironet 1830 lifecycle bulletin; Cisco Aironet 1830 support page; and Cisco wireless compliance tool.