C9120AXI-EWC-B Cisco Catalyst 9120 Dual band WiFi 6 EWC Access Point

C9120AXI-EWC-B exact order identity

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

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.

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.

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.

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.

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.

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.

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.

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