C9115AXI-K - Cisco Catalyst 9115 Series Access Points Wi-Fi 6

C9115AXI-K exact order identity

C9115AXI-K 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 K.

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.

K regulatory evidence

Cisco treats the final token as a regulatory-domain identifier and makes the customer responsible for verifying country approval. Tie the K-domain purchase line to the controller country configuration and the post-join enabled-channel export.

Center the K-domain package on channel-state evidence. Retain the Cisco country lookup and controller country configuration, then export the enabled-channel state after the AP joins. Store the output with exact PID, serial and survey reference. Repeat the comparison after controller upgrades so a software change cannot silently separate the live radio state from the approved order.

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

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.

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.

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.

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.

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.

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.

Related Catalyst 9115 order records

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