C9120AXP-EWC-K Cisco Catalyst 9120 Indoor Professionally Installed AP

C9120AXP-EWC-K exact order identity

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

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.

K 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. Tie the K-domain purchase line to the controller country configuration and the post-join enabled-channel export.

Center the K-domain package on channel-state evidence. Retain the Cisco country lookup and controller country configuration, then export the enabled-channel state after the AP joins. Store the output with exact PID, serial and survey reference. Repeat the comparison after controller upgrades so a software change cannot silently separate the live radio state from the approved order.

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

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.

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.

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.

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