C9115AXE-EWC-Z - Cisco Catalyst 9115 Series WiFi 6 Access Point

C9115AXE-EWC-Z exact order identity

C9115AXE-EWC-Z 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 Z.

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.

Z regulatory evidence

Cisco treats the final token as a regulatory-domain identifier and makes the customer responsible for verifying country approval. Attach the Z-domain compliance lookup to the commissioning package and flag any later country-setting change for reapproval.

Build the Z-domain package as a commissioning baseline. Combine the exact PID, destination lookup, controller country, enabled-channel output, antenna or mounting evidence and representative client test under one review date. Later automatic radio changes may be operationally valid, but country-setting or hardware reassignment changes require explicit reapproval and a new baseline entry.

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

Country approval retention

Save the Cisco compliance lookup result, lookup date, deployment country, approved regulatory token and reviewer. If the destination changes, stop and repeat the approval rather than moving the unit on the strength of an earlier purchase. Compare the controller country setting and available channels with the retained evidence. Regulatory eligibility is a deployment condition and cannot be inferred from connector fit, stock location or a similar-looking part number. Save a dated Cisco compliance lookup; controller join is not proof that the destination country is approved.

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.

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.

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.

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.

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 AXI from AXE and EWC from non-EWC before the chassis is powered.

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

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