C9120AXI-EWC-D Cisco 9120AX Embedded Wireless Controller AP

C9120AXI-EWC-D exact order identity

C9120AXI-EWC-D is a Cisco Catalyst 9120AX Series indoor Wi-Fi 6 access point with integrated antennas. The exact PID combines the I antenna form, a access-point order carrying the Embedded Wireless Controller software image and regulatory-domain token D.

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

D 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. For a D-domain spare, record the approved protected sites so it cannot be moved to a destination with a different domain requirement.

Treat this D-domain unit as location-controlled inventory. Name the destination or protected spare population, record who may reassign it and require a new Cisco lookup before any transfer. Commissioning should retain the controller country and enabled-channel outputs. This prevents an unused spare from appearing technically interchangeable after organizational or geographic changes.

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

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.

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.

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.

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.

Operational log retention

Store the initial controller events, switch-port state, radio assignment, channel list and client test results with a consistent asset identifier. Define how long commissioning evidence is retained and who can retrieve it. A later firmware, controller or RF change should add a new dated observation rather than overwrite the original. The resulting history supports lifecycle decisions and distinguishes a new regression from the accepted baseline. The accepted baseline should include controller join, power mode, Ethernet rate, radio mode, domain evidence and representative client tests.

Related Catalyst 9120 order records

• C9120AXE-D - compare antenna form and domain evidence.
• C9120AXP-EWC-D - compare antenna form and domain evidence.
• C9120AXI-D - compare controller-image state 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.