AIR-AP1815I-T-K9 Cisco Aironet 1815I Controller-based Wifi 5 Wave 2 AP

AIR-AP1815I-T-K9 exact order identity

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

T regulatory-domain evidence

The domain letter is an ordering identifier, not a country name. Document the T-domain destination and controller country setting before installation, then keep the evidence through software upgrades.

Use software-upgrade governance for the T-domain record. Before an upgrade, preserve the controller country, enabled channels, AP serial and dated compliance lookup; after the change, capture the same fields for comparison. Investigate a changed radio state before production acceptance. This ties the domain decision to an observable configuration history instead of a one-time purchasing note.

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

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.

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.

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 location and controller or Mobility Express ownership before activation.

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.

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.

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 verify the integrated-antenna 1815i identity and distinguish K9 from K9C software ordering.

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-T-K9C - compare software order and regulatory-domain evidence.
• AIR-AP1815I-F-K9C - compare software order and regulatory-domain evidence.
• AIR-AP1815I-Q-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.