AIR-AP1815I-D-K9 Cisco Aironet 1815I Bluetooth 4.1 2x2:2 MU-MIMO AP

AIR-AP1815I-D-K9 exact order identity

AIR-AP1815I-D-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.

D regulatory-domain evidence

The domain letter is an ordering identifier, not a country name. For a D-domain spare, record the approved protected sites so it cannot be moved to a destination with a different domain requirement.

Treat this D-domain unit as location-controlled inventory. Name the destination or protected spare population, record who may reassign it and require a new Cisco lookup before any transfer. Commissioning should retain the controller country and enabled-channel outputs. This prevents an unused spare from appearing technically interchangeable after organizational or geographic changes.

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

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.

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. Cisco makes the customer responsible for country approval; save the compliance lookup and controller country.

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 Aironet generation must leave service and which surrounding dependencies need migration. The Aironet 1815 lifecycle record governs software and replacement planning even when hardware remains available.

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. Roaming acceptance must identify neighboring cells, client type and controller events along the movement path.

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.

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.

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. Cisco names Catalyst 9105AX as the migration family; validate controller, power, mounting 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 events to separate power, CAPWAP, RF and authentication faults.

Related Aironet 1815i order records

• AIR-AP1815I-D-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.