C9120AXP-EWC-T Cisco 9120 Professional Installed AP 4x4 MIMO

C9120AXP-EWC-T exact order identity

C9120AXP-EWC-T is a Cisco Catalyst 9120AX Series professional-installation indoor Wi-Fi 6 access point with external antennas. The exact PID combines the P antenna form, a access-point order carrying the Embedded Wireless Controller software image and regulatory-domain token T.

Antenna and installation boundary

Cisco specifies four external dual-band RP-TNC connectors, a four-port Smart Antenna DART connector and support for Self-Identifying Antennas. Antennas are sold separately. Cisco certifies the 9120AXP up to 13 dBi on both bands with AIR-ANT2513P4M-N=; that published combination does not authorize an arbitrary high-gain antenna. Cisco requires external antennas to be connected before power is applied; an outdoor antenna installation also requires grounding before power.

Controller-image boundary

Cisco defines the EWC PID as the same antenna-form access point with a Cisco Embedded Wireless Controller software image. Cisco ended sale of EWC-AP on 29 November 2024 and identifies IOS XE 17.15.x as the final EWC-AP train. Its bulletin permits conversion to lightweight CAPWAP mode for controller-based operation, subject to the applicable support terms.

T 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. Document the T-domain destination and controller country setting before installation, then keep the evidence through software upgrades.

Use software-upgrade governance for the T-domain record. Before an upgrade, preserve the controller country, enabled channels, AP serial and dated compliance lookup; after the change, capture the same fields for comparison. Investigate a changed radio state before production acceptance. This ties the domain decision to an observable configuration history instead of a one-time purchasing note.

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.

EWC lifecycle decision

Cisco ended sale of EWC-AP on 29 November 2024, lists IOS XE 17.15.x as the final EWC-AP software train and gives 30 November 2029 as the last support date. The lifecycle bulletin says these APs can be converted to lightweight CAPWAP mode; record that conversion and controller plan rather than treating the EWC suffix as a permanent operating requirement.

Deployment evidence worksheet

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.

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.

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.

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.

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.

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. For EWC orders, record the 17.15.x support ceiling and a CAPWAP conversion decision; for non-EWC orders, record the external controller lifecycle.

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-T - compare antenna form and domain evidence.
• C9120AXE-T - compare antenna form and domain evidence.
• C9120AXI-EWC-T - compare antenna form and domain evidence.

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