C9115AXI-E1 Cisco Catalyst 9115 4x4 MIMO Bluetooth 5 Access Point

C9115AXI-E1 exact order identity

C9115AXI-E1 is a Cisco Catalyst 9115 Series indoor 802.11ax access point. The complete PID selects the I antenna form, controller-based access-point order and regulatory-domain token E1.

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

The exact PID has no EWC infix, so it does not establish an AP-hosted Embedded Wireless Controller image. Record the target wireless LAN controller, supported release, licensing, CAPWAP join and recovery result.

E1 regulatory evidence

Cisco treats the final token as a regulatory-domain identifier and makes the customer responsible for verifying country approval. Associate the E-domain compliance result with the installed controller object and repeat the check after any country-setting migration.

Use controller migration as the E-domain evidence scenario. Export the existing country and radio configuration before the move, then compare the post-migration state with the dated Cisco compliance result. Keep both observations beside the exact PID and serial. Unchanged client connectivity is not enough because it does not show that the intended regulatory configuration survived.

Complete E1 suffix boundary

Cisco's lifecycle publication lists C9115AXI-E1 as an exact orderable PID. The cited source does not expand the meaning of the trailing 1, so procurement must preserve the complete E1 token and must not silently normalize it to E.

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

Cisco's current hardware bulletin sets 2026-12-31 as the last order date and 2031-12-31 as the last support date for affected Catalyst 9115 orders, with Cisco Wireless 9174I Access Point as the migration form for this antenna architecture.

Deployment evidence worksheet

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.

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.

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.

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.

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

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