C9115AXI-EWC-Q - Cisco 9115AXI Series WiFi 6 AP with Internal Antennas

C9115AXI-EWC-Q exact order identity

C9115AXI-EWC-Q 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 Q.

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.

Q regulatory evidence

Cisco treats the final token as a regulatory-domain identifier and makes the customer responsible for verifying country approval. Store the Q-domain compliance result with serial, site and antenna form so return or replacement activity remains traceable.

Organize the Q-domain evidence for return and replacement traceability. Preserve the original unit's PID, approval and site, then require the replacement label and controller country to be checked independently. Link both serials to the same service case without copying the old approval blindly. This makes regulatory identity visible during an RMA rather than only during initial purchase.

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

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. Reconcile mounting hardware, enclosure condition and every separately ordered external-antenna component.

Serial-level asset control

Capture chassis serial, base MAC address, carton reference, deployment site, controller assignment and asset owner. Reconcile the identifiers against the purchase line before activation. Multi-unit cartons require an entry for every physical access point; a carton SKU alone cannot show which unit was installed, held as a spare or returned. This record is also needed to trace support entitlement, replacement history and monitoring ownership. Link serial, base MAC, installed site, controller object and regulatory evidence before activation.

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 Catalyst 9115 generation must leave service and which surrounding dependencies need migration. Apply the published hardware or EWC lifecycle to support and migration planning instead of inventory age.

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. Prove a stored spare against the protected controller release, PoE state, antenna design and domain approval.

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.

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 synchronized switch, AP and controller timestamps to separate power, CAPWAP, RF and authentication faults.

Operational log retention

Store the initial controller events, switch-port state, radio assignment, channel list and client test results with a consistent asset identifier. Define how long commissioning evidence is retained and who can retrieve it. A later firmware, controller or RF change should add a new dated observation rather than overwrite the original. The resulting history supports lifecycle decisions and distinguishes a new regression from the accepted baseline. Keep the first accepted power, wired, radio and client results as the baseline for later troubleshooting.

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. Handover should include exact PID, serial, compliance result, software role, antenna record and lifecycle owner.

Related Catalyst 9115 order records

• C9115AXE-Q - compare antenna form, controller-image state and regulatory evidence.
• C9115AXE-N - compare antenna form, controller-image state and regulatory evidence.
• C9115AXE-F - 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.