C9120AXP-EWC-B Cisco 9120 Professionally Installed WiFi 6 AP with EWC

C9120AXP-EWC-B exact order identity

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

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.

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

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.

Survey-to-install reconciliation

Attach the approved RF survey location, mounting height, orientation, expected client density, channel width and neighboring-radio assumptions to the order. After installation, compare measured coverage and interference with that design. If ceiling construction, antenna placement or obstructions changed, document the deviation and repeat the affected measurements. This provides a site-specific acceptance reason for the exact unit instead of relying on a family data sheet alone. Relate the installed radio mode to the survey because the flexible radio can serve 2.4/5 GHz or participate in a dual-5-GHz design.

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.

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.

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.

Related Catalyst 9120 order records

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