C9120AXE-Z - Cisco Catalyst 9120 Dual-concurrent WiFi 6 Access Point

C9120AXE-Z exact order identity

C9120AXE-Z is a Cisco Catalyst 9120AX Series indoor Wi-Fi 6 access point for challenging environments with external antennas. The exact PID combines the E antenna form, a controller-based access-point order and regulatory-domain token Z.

Antenna and installation boundary

Cisco specifies four external dual-band RP-TNC connectors, a four-port Smart Antenna DART connector and support for a Self-Identifying Antenna on one RP-TNC port. Antennas are sold separately. Cisco certifies the 9120AXE for gains up to 6 dBi on 2.4 and 5 GHz; preserve antenna PID, gain, pattern, cable loss and controller configuration before powering the AP. Cisco requires external antennas to be connected before power is applied; an outdoor antenna installation also requires grounding before power.

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.

Z 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. 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 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.

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. Asset identity must preserve AXI, AXE or AXP, the EWC state and the final domain token because each field changes the procurement boundary.

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.

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.

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 evidence should identify the neighboring cells, client type and flexible-radio mode instead of relying on a static association test.

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.

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

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

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