C9115AXE-N - Cisco Catalyst 9115 WiFi 6 Enterprise Access Point

C9115AXE-N exact order identity

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

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

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.

N regulatory evidence

Cisco treats the final token as a regulatory-domain identifier and makes the customer responsible for verifying country approval. For the N-domain order, retain both destination approval and controller evidence before moving the unit from staging to production.

Use the staging-to-production handoff as the N-domain checkpoint. The staging record should contain destination approval, complete PID, serial and controller country; the production owner must accept those same fields. If the AP is moved between managed sites, close the first assignment and create a new reviewed destination record instead of merely changing the location field.

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

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 9174E Access Point as the migration form for this antenna architecture.

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.

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.

Monitoring handover

Assign owners for AP reachability, controller join failures, radio utilization, client health and switch-port errors. Confirm that the exact serial appears in inventory and monitoring, then test the alert path. Record dashboard object, notification route and escalation owner. Telemetry that is not tied to an owned asset does not provide a reliable service baseline and will not support later comparison after channel or software changes. Correlate AP serial, CAPWAP state, radio health, Ethernet errors, PoE negotiation and client experience.

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.

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.

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.

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