C9120AXI-K Cisco Catalyst 9120 Dual-band 802.11ax Access Points

C9120AXI-K exact order identity

C9120AXI-K is a Cisco Catalyst 9120AX Series indoor Wi-Fi 6 access point with integrated antennas. The exact PID combines the I antenna form, a controller-based access-point order and regulatory-domain token K.

Antenna and installation boundary

Cisco documents four integrated dual-band antennas, four additional single-band 5 GHz antennas used in dual-5-GHz mode, one 2.4 GHz IoT antenna and one dual-band auxiliary-radio antenna. No external antenna is selected by this PID. Mounting position, enclosure orientation and the post-install RF survey are therefore part of the acceptance evidence. The integrated-antenna order does not require an external antenna bill of materials.

Controller-image boundary

Cisco lists this PID without the EWC infix, so the order is the controller-based access-point form rather than an EWC software-image order. Record the target controller model and release. Cisco's getting-started guide requires AireOS 8.9.111.0 or later, or IOS XE 16.11.1b or later, for the 9120AX family.

K regulatory-domain evidence

Cisco uses the final PID letter as a regulatory-domain identifier and requires customers to verify approval for the country of use. The letter is not a country name. Tie the K-domain purchase line to the controller country configuration and the post-join enabled-channel export.

Center the K-domain package on channel-state evidence. Retain the Cisco country lookup and controller country configuration, then export the enabled-channel state after the AP joins. Store the output with exact PID, serial and survey reference. Repeat the comparison after controller upgrades so a software change cannot silently separate the live radio state from the approved order.

Power and wired-uplink boundary

The family has one 100/1000/2500 Multigigabit Ethernet uplink. Cisco lists full 4x4 radio operation, 2.5-Gigabit Ethernet and USB with 802.3at; under 802.3af both radios reduce to 1x1, Ethernet reduces to 1 GbE and USB is disabled.

External controller decision

This PID does not carry the EWC software-image infix. Record the production controller and supported software release, and verify the live compatibility matrix before an upgrade or substitution.

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. Relate the installed radio mode to the survey because the flexible radio can serve 2.4/5 GHz or participate in a dual-5-GHz design.

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. Use only Cisco-supported 9120AX mounting hardware; Cisco states that AIR-AP-BRACKET-3 is not compatible with this family.

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. Record the controller release and the 9120AX compatibility source before upgrade, expansion or emergency replacement.

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 planning must preserve controller image, domain setting, antenna configuration and the prior AP's radio and switch-port state.

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. The 9120AX data sheet describes platform capabilities; record which security features are actually enabled and validated on the deployed controller release.

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 use observed clients, channel width, airtime and retries rather than the family's maximum over-the-air 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 exact enabled-channel export because the regulatory token and destination approval control the usable spectrum.

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. The accepted baseline should include controller join, power mode, Ethernet rate, radio mode, domain evidence and representative client tests.

Related Catalyst 9120 order records

• C9120AXP-EWC-K - compare antenna form and domain evidence.
• C9120AXE-EWC-K - compare antenna form and domain evidence.
• C9120AXP-K - compare antenna form and domain evidence.

Official evidence: Cisco Catalyst 9120AX data sheet; Cisco Catalyst 9120AX getting-started guide; Cisco wireless compliance tool.