C9115AXE-F - Cisco Catalyst 9115 WiFi 6 Access Point for Enterprises

C9115AXE-F exact order identity

C9115AXE-F 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 F.

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.

F regulatory evidence

Cisco treats the final token as a regulatory-domain identifier and makes the customer responsible for verifying country approval. Keep the F-domain approval beside the RF survey and antenna record so a later antenna change triggers a regulatory review.

Make antenna-change control the focus for this F-domain order. Record the approved antenna PID, gain, cable and mounting plan with the country lookup, then require review whenever any RF component changes. The controller configuration and final installation photographs should refer to the same asset. A mechanically compatible replacement antenna is not automatically an approved regulatory substitute.

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

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.

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.

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.

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.

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.

Operational log retention

Store the initial controller events, switch-port state, radio assignment, channel list and client test results with a consistent asset identifier. Define how long commissioning evidence is retained and who can retrieve it. A later firmware, controller or RF change should add a new dated observation rather than overwrite the original. The resulting history supports lifecycle decisions and distinguishes a new regression from the accepted baseline. Keep the first accepted power, wired, radio and client results as the baseline for later troubleshooting.

Related Catalyst 9115 order records

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