AIR-AP1815I-I-K9C Cisco Aironet 1815I 802.11ac Wave 2 Access Point

AIR-AP1815I-I-K9C exact order identity

AIR-AP1815I-I-K9C 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 K9C as the configurable order whose default software option is Mobility Express. Used stock may have been converted or reimaged, so retain the running image, current role, configured country, management backup and recovery result.

I regulatory-domain evidence

The domain letter is an ordering identifier, not a country name. Preserve the I-domain label in the asset record and verify that replacement stock carries the same approved regulatory identity.

Use replacement-stock readiness for the I-domain workflow. List the deployed population this unit may protect, confirm those assets use the same approved token and retain the mounting or antenna dependencies. During periodic spare testing, verify controller join and country configuration without reassigning the unit. Any cross-site use requires a fresh destination approval before installation.

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.

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. AIR-AP-BRACKET-8 is included only when selected with the order and can be ordered separately; reconcile mounting parts.

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.

Quotation substitution gate

Compare antenna form, regulatory token, configuration suffix, pack quantity and complete Cisco part number on the authorized quotation. Treat any changed token as a substitution that requires a new technical and regulatory review. Procurement should not accept a different access-point order merely because the family name matches. Preserve the approved line, received label and exception decision so the final asset can be traced to the exact order reviewed here. A changed regulatory token or K9/K9C suffix is a different procurement identity requiring a fresh review.

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.

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 a baseline for future changes.

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 lookup, software role, mounting record and lifecycle owner.

Related Aironet 1815i order records

• AIR-AP1815I-I-K9 - compare software order and regulatory-domain evidence.
• AIR-AP1815I-Q-K9 - compare software order and regulatory-domain evidence.
• AIR-AP1815I-K-K9 - 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.