C9120AXE-EWC-Q Cisco 9120 WiFi 6 AP Ideal for Harsh Settings with EWC

C9120AXE-EWC-Q exact order identity

C9120AXE-EWC-Q 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 access-point order carrying the Embedded Wireless Controller software image and regulatory-domain token Q.

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

Q 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. Store the Q-domain compliance result with serial, site and antenna form so return or replacement activity remains traceable.

Organize the Q-domain evidence for return and replacement traceability. Preserve the original unit's PID, approval and site, then require the replacement label and controller country to be checked independently. Link both serials to the same service case without copying the old approval blindly. This makes regulatory identity visible during an RMA rather than only during initial purchase.

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

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.

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.

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.

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.

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.

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.

Related Catalyst 9120 order records

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