C9115AXI-EWC-S Cisco Catalyst 9115 Series WiFi 6 Indoor Access Point

C9115AXI-EWC-S exact order identity

C9115AXI-EWC-S is a Cisco Catalyst 9115 Series indoor 802.11ax access point. The complete PID selects the I antenna form, access-point order carrying an Embedded Wireless Controller image and regulatory-domain token S.

Antenna and installation boundary

Cisco documents integrated omnidirectional antennas with peak gain of 3 dBi at 2.4 GHz and 4 dBi at 5 GHz. External antennas are not part of this AXI order. Mounting position, enclosure orientation and measured RF coverage are the installation evidence.

Controller-image boundary

Cisco defines the EWC order as a Catalyst 9115 access point supplied with the Embedded Wireless Controller software image. Cisco ended sale of EWC-AP orders on 2024-11-29, names IOS XE 17.15.x as the final EWC-AP train and permits conversion to lightweight CAPWAP mode.

S regulatory evidence

Cisco treats the final token as a regulatory-domain identifier and makes the customer responsible for verifying country approval. Compare the complete S-domain PID on quotation, carton and asset record; family equivalence is not regulatory equivalence.

Make quotation accuracy the S-domain control. The approved quote, supplier confirmation, received carton and asset record must carry the complete same PID. A substitution request should identify antenna form, controller-image state and regulatory token separately. Only after destination approval and controller review should the replacement line be accepted, even if pricing and lead time are unchanged.

PoE and environmental reduced states

With 802.3at, the 9115 operates both radios at 4x4, negotiates 2.5G and enables USB; 802.3at full-feature consumption is published as 20.4W. Under 802.3af both radios reduce to 2x2, Ethernet reduces to 1G and USB is disabled. Cisco also documents the same reduced state above 40 degrees C ambient.

Lifecycle and migration decision

The EWC order has already passed its 2024-11-29 end-of-sale date. Cisco identifies 17.15.x as the final EWC-AP train and 2029-11-30 as last support, while allowing conversion to lightweight CAPWAP mode.

Deployment evidence worksheet

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, DNS and application reachability after final staging.

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. Document roaming path, client type, neighboring cells and controller events rather than only a static join.

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. Correlate AP serial, CAPWAP state, radio health, Ethernet errors, PoE negotiation and client experience.

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. A rollback record must restore controller assignment, country setting, switch port and prior RF service.

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. Record only security features demonstrated on the deployed controller and software 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. Use measured airtime, retries and client performance rather than the family's maximum PHY rate.

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 enabled-channel export after first join and after every controller or country-setting change.

Replacement dependency map

Map this unit to controller, licenses, authentication services, switch power, cable, bracket, antenna design and monitoring objects. For an end-of-sale platform, state which dependencies can be reused by the planned Catalyst migration and which require change. A nominal access-point replacement can fail when the surrounding platform was never inventoried. Keep the map with the asset rather than only in a one-time project file. Compare the relevant 9174I or 9174E migration form, including controller, power, antenna and coverage changes.

Related Catalyst 9115 order records

• C9115AXE-S - compare antenna form, controller-image state and regulatory evidence.
• C9115AXE-EWC-S - compare antenna form, controller-image state and regulatory evidence.
• C9115AXE-N - compare antenna form, controller-image state and regulatory evidence.

Official evidence: Cisco Catalyst 9115 data sheet; Cisco deployment guide; Cisco EWC-AP lifecycle bulletin; and Cisco compliance lookup.