C9120AXI-F Cisco Catalyst 9120 Enterprise 802.11ax Access Point

C9120AXI-F exact order identity

C9120AXI-F 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 F.

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.

F 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. Keep the F-domain approval beside the RF survey and antenna record so a later antenna change triggers a regulatory review.

Make antenna-change control the focus for this F-domain order. Record the approved antenna PID, gain, cable and mounting plan with the country lookup, then require review whenever any RF component changes. The controller configuration and final installation photographs should refer to the same asset. A mechanically compatible replacement antenna is not automatically an approved regulatory substitute.

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

Controller join evidence

Stage the access point on the controller release intended for production. Retain the controller model, software version, discovery path, authorization method and first successful CAPWAP join. Confirm that configuration download completes and that both radios reach an expected operational state. Remove any temporary staging authorization before handover. This evidence separates an orderable access point from a unit that has actually been proven compatible with the planned controller environment. For the 9120AX, keep the controller model, release and first successful CAPWAP join with the exact regulatory-domain PID.

Power-state acceptance

Measure power after the access point has joined its controller and the planned radios and services are active. Record switch model, port, negotiated power level, LLDP result and any reduced-capability warning. An idle boot result is not sufficient evidence for the deployed power budget. If an injector is proposed, verify its supported use and include its exact identity in the maintained bill of materials rather than treating it as an unspecified accessory. The full 4x4 radios and 2.5-Gigabit link require 802.3at; Cisco states that 802.3af reduces both radios to 1x1, limits Ethernet to 1 GbE and disables USB.

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 wired acceptance result should show whether the single IEEE 802.3bz uplink negotiated at 100 Mbps, 1 Gbps or 2.5 Gbps.

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; retain the dated compliance lookup instead of inferring a country from the domain letter.

Authentication path test

Commission representative clients through association, authentication, address assignment, DNS and application reachability. Preserve the identity policy used, test client type, result and relevant controller logs. An access point that joins its controller has not yet demonstrated the user path. Repeat the test after any controller, certificate or authentication-service change and retain failures separately from RF or switch-port evidence. Test association, authentication, address assignment and application reachability after the 9120AX reaches its final controller and radio 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 connect the 9120AX serial to CAPWAP state, wired rate, radio utilization, client health and switch-port errors.

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 PoE reduction, CAPWAP discovery, RF conditions and authentication failures.

Handover completeness

The handover package should include exact order identity, destination approval, serial record, controller evidence, switch port, mounting or antenna record, user-path tests and named operational owners. Review the package with the receiving team and list unresolved exceptions. A unit is not operationally accepted when important evidence remains only in installer notes, email attachments or an unowned temporary dashboard. The handover package should contain the exact PID, serial, compliance result, controller assignment, antenna or mounting record and named owner.

Related Catalyst 9120 order records

• C9120AXE-EWC-F - compare antenna form and domain evidence.
• C9120AXE-F - compare antenna form and domain evidence.
• C9120AXI-EWC-F - compare controller-image state and domain evidence.

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