AIR-AP1815I-Q-K9 Cisco Aironet 1815I Dual-band WiFi 5 Access Point

AIR-AP1815I-Q-K9 exact order identity

AIR-AP1815I-Q-K9 is an indoor Cisco Aironet 1815i 802.11ac Wave 2 access point. It uses internal antennas only, supports concurrent 2.4-GHz and 5-GHz radios with 2x2 MIMO and two spatial streams, and provides one 10/100/1000 Ethernet uplink with 802.3af/at PoE.

Software order boundary

Cisco identifies the K9 line as a dual-band controller-based 802.11ac Wave 2 access point. Record the intended wireless LAN controller and software release, DHCP or DNS discovery path, certificate state and successful CAPWAP join.

Q regulatory-domain evidence

The domain letter is an ordering identifier, not a country name. Store the Q-domain compliance result with serial, site and antenna form so return or replacement activity remains traceable.

Organize the Q-domain evidence for return and replacement traceability. Preserve the original unit's PID, approval and site, then require the replacement label and controller country to be checked independently. Link both serials to the same service case without copying the old approval blindly. This makes regulatory identity visible during an RMA rather than only during initial purchase.

Integrated antenna and installation boundary

Cisco documents two integrated 2.4-GHz antennas and two integrated 5-GHz antennas. There is no external-antenna conversion in this PID. Reconcile AIR-AP-BRACKET-8 or other selected mounting hardware and verify the final wall or ceiling placement against the RF survey.

Lifecycle decision

Cisco lists this product family as end of sale, identifies Catalyst 9105AX as the migration direction and publishes 30 April 2027 as the last support date. Available inventory does not extend that date.

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 the 1815i, retain controller discovery, software download and final join evidence 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. Cisco documents 802.3af/at PoE on the single Ethernet uplink; record the negotiated power source and boot state.

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. The 1815i requires a Gigabit Ethernet link to avoid a wired bottleneck; retain negotiated rate and cable counters.

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. The integrated-antenna result depends on wall or ceiling position, orientation and the accepted RF survey.

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. Monitoring should join AP serial, controller state, radio health, Ethernet errors and client experience.

Change-window controls

Document staging evidence, production window, installer, rollback owner and measurable success criteria. Preserve the prior controller or AP state needed for recovery. After the change, close temporary credentials, compare authentication, monitoring and RF results with the approved baseline, and record the final decision. The work is not complete merely because the unit powers on or appears in a controller list. Rollback must restore controller assignment, country state, switch port and the previously accepted RF service.

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 settings demonstrated on the deployed controller or Mobility Express 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 behavior rather than a published PHY rate as site-capacity evidence.

Related Aironet 1815i order records

• AIR-AP1815I-Q-K9C - compare software order and regulatory-domain evidence.
• AIR-AP1815I-F-K9C - compare software order and regulatory-domain evidence.
• AIR-AP1815I-T-K9C - compare software order and regulatory-domain evidence.

Official evidence: Cisco 1815i data sheet; Cisco 1815i getting started guide; Cisco Aironet 1815 lifecycle bulletin; Cisco support page; and Cisco compliance lookup.