C9115AXE-EWC-S - Cisco Catalyst 9115 WiFi 6 APs - External Antennas

C9115AXE-EWC-S exact order identity

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

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.

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

Power-state acceptance

Measure power after the access point has joined its controller and the planned radios and services are active. Record switch model, port, negotiated power level, LLDP result and any reduced-capability warning. An idle boot result is not sufficient evidence for the deployed power budget. If an injector is proposed, verify its supported use and include its exact identity in the maintained bill of materials rather than treating it as an unspecified accessory. Record the negotiated 802.3at or 802.3af state because a successful boot does not prove full radio capacity.

Survey-to-install reconciliation

Attach the approved RF survey location, mounting height, orientation, expected client density, channel width and neighboring-radio assumptions to the order. After installation, compare measured coverage and interference with that design. If ceiling construction, antenna placement or obstructions changed, document the deviation and repeat the affected measurements. This provides a site-specific acceptance reason for the exact unit instead of relying on a family data sheet alone. Tie the accepted RF survey to the exact integrated or external antenna form shown by the PID.

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.

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 Catalyst 9115 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. Treat a changed antenna letter, EWC infix or regulatory token as a new procurement identity.

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.

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.

Related Catalyst 9115 order records

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