C9120AXI-EWC-N Cisco 9120AXI WiFi 6 Enterprise Access Point

C9120AXI-EWC-N exact order identity

C9120AXI-EWC-N 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 N.

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.

N 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 the N-domain order, retain both destination approval and controller evidence before moving the unit from staging to production.

Use the staging-to-production handoff as the N-domain checkpoint. The staging record should contain destination approval, complete PID, serial and controller country; the production owner must accept those same fields. If the AP is moved between managed sites, close the first assignment and create a new reviewed destination record instead of merely changing the location field.

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

Power-state acceptance

Measure power after the access point has joined its controller and the planned radios and services are active. Record switch model, port, negotiated power level, LLDP result and any reduced-capability warning. An idle boot result is not sufficient evidence for the deployed power budget. If an injector is proposed, verify its supported use and include its exact identity in the maintained bill of materials rather than treating it as an unspecified accessory. The full 4x4 radios and 2.5-Gigabit link require 802.3at; Cisco states that 802.3af reduces both radios to 1x1, limits Ethernet to 1 GbE and disables USB.

Ethernet and cabling proof

Preserve the permanent-link test, patch-lead identities, switch port, negotiated Ethernet rate and error counters. Investigate pair faults, excessive length or rate fallback before wireless acceptance begins. A link light only proves connectivity at some rate; it does not demonstrate the intended uplink performance. Tie the cable result to the AP serial so a later throughput problem can be separated from radio, controller and wired-path causes. The wired acceptance result should show whether the single IEEE 802.3bz uplink negotiated at 100 Mbps, 1 Gbps or 2.5 Gbps.

Mechanical installation record

List the bracket, ceiling or wall interface, enclosure requirement, safety restraint, service clearance and cable-entry plan before scheduling installation. Receiving should identify missing mechanical items before the access point reaches site. Photograph the mounted label and final cable entry, then record how the unit can be reached for replacement. A complete electronic order can still be an unusable deployment kit when mechanical dependencies are omitted. Use only Cisco-supported 9120AX mounting hardware; Cisco states that AIR-AP-BRACKET-3 is not compatible with this family.

Quotation substitution gate

Compare antenna form, regulatory token, configuration suffix, pack quantity and complete Cisco part number on the authorized quotation. Treat any changed token as a substitution that requires a new technical and regulatory review. Procurement should not accept a nearby Aironet 2802 line merely because the family name matches. Preserve the approved line, received label and exception decision so the final asset can be traced to the exact order reviewed here. A different antenna form, EWC state or regulatory token is a different 9120AX order and requires a new technical acceptance decision.

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.

Controlled spare policy

If purchased as a spare, name the protected site population, compatible controller image, storage location, storage conditions and periodic power-on test. Confirm that regulatory token, antenna architecture and mounting parts match the population it protects. Set a final-use review date. A stored unit can become unsuitable while untouched because controller software, country approval, certificates or network architecture may change. A stored 9120AX spare should be periodically tested for controller join, negotiated PoE state and the antenna or mounting dependencies it protects.

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.

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.

Related Catalyst 9120 order records

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