AIR-AP1832I-Z-K9C Cisco 1832i 802.11ac Wave 2 Mobility Express AP

AIR-AP1832I-Z-K9C exact order identity

AIR-AP1832I-Z-K9C is a Cisco Aironet 1832i indoor access point with integrated antennas. This exact PID combines regulatory-domain token Z 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.

Z 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. Attach the Z-domain compliance lookup to the commissioning package and flag any later country-setting change for reapproval.

Build the Z-domain package as a commissioning baseline. Combine the exact PID, destination lookup, controller country, enabled-channel output, antenna or mounting evidence and representative client test under one review date. Later automatic radio changes may be operationally valid, but country-setting or hardware reassignment changes require explicit reapproval and a new baseline entry.

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

Quotation substitution gate

Compare antenna form, regulatory token, configuration suffix, pack quantity and complete Cisco part number on the authorized quotation. Treat any changed token as a substitution that requires a new technical and regulatory review. Procurement should not accept a nearby Aironet 2802 line merely because the family name matches. Preserve the approved line, received label and exception decision so the final asset can be traced to the exact order reviewed here. A K9, K9C, K910C or regulatory-token change is a different 1832i procurement line and requires a new review.

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.

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.

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. Preserve the live controller country and enabled-channel state beside the exact domain token and deployment approval.

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 Catalyst 9115AX as the migration family; map controller, power, mounting and coverage 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 power, CAPWAP, RF and authentication faults before declaring hardware failure.

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. Keep the first accepted join, power, wired, radio and client test results so later software or RF changes have a baseline.

Related Aironet 1832 order records

• AIRAP1832I-ZK910C - compare software and procurement form.
• AIR-AP1832I-Z-K9 - compare software and procurement form.
• AIRAP1832I-TK910C - 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.