C9115AXE-EWC-T - Cisco Catalyst 9115 Enterprise 802.11ax Access Point

C9115AXE-EWC-T exact order identity

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

Antenna and installation boundary

Cisco documents external antennas as separately ordered and certifies the 9115AXE for antenna gains up to 6 dBi at both 2.4 GHz and 5 GHz. The acceptance record must identify antenna PID, gain, pattern, connector, cable loss, mounting and country approval; an AXI antenna statement cannot be reused.

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.

T regulatory evidence

Cisco treats the final token as a regulatory-domain identifier and makes the customer responsible for verifying country approval. Document the T-domain destination and controller country setting before installation, then keep the evidence through software upgrades.

Use software-upgrade governance for the T-domain record. Before an upgrade, preserve the controller country, enabled channels, AP serial and dated compliance lookup; after the change, capture the same fields for comparison. Investigate a changed radio state before production acceptance. This ties the domain decision to an observable configuration history instead of a one-time purchasing note.

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 21.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

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 this 9115 order, retain controller discovery, image transfer and final join beside the exact serial.

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. Confirm 2.5-Gigabit negotiation under full power and retain switch-port counters with the acceptance result.

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.

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.

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.

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.

Related Catalyst 9115 order records

• C9115AXI-E1 - compare antenna form, controller-image state and regulatory evidence.
• C9115AXI-B1 - compare antenna form, controller-image state and regulatory evidence.
• C9115AXI-K - 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.