C9120AXE-B - Cisco Catalyst 9120 WiFi 6 External Antenna Access Point

C9120AXE-B exact order identity

C9120AXE-B 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 B.

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.

B 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. Match the B-domain carton label to the purchase line before serial assignment, then archive the dated compliance lookup.

Build the B-domain record around quotation-to-asset traceability. Preserve the authorized line, received label, chassis serial, assigned site and reviewer as one chain. If the controller later moves to another country configuration, open a new approval event rather than overwriting the original evidence; the history should explain both the purchased identity and every deployment decision.

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.

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.

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.

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.

Receiving inspection

At receipt, compare model label, regulatory token, antenna form, quantity, serials and visible condition with the authorized order. Photograph labels before cartons are separated. Quarantine shortages, mixed units, damaged connectors or unapproved substitutions. Do not rely on a distributor description as evidence that the exact Cisco order arrived. Close the inspection only when every physical unit is accounted for. Receiving must distinguish the integrated AXI enclosure from the external-antenna AXE and professional-installation AXP order before power is applied.

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

• C9120AXP-EWC-B - compare antenna form and domain evidence.
• C9120AXI-EWC-B - compare antenna form and domain evidence.
• C9120AXP-B - compare antenna form and domain evidence.

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