AIR-AP1815I-B-K9 Cisco Aironet 1815I 2x2:2 MU-MIMO WiFi 5 AP

AIR-AP1815I-B-K9 exact order identity

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

B regulatory-domain evidence

The domain letter is an ordering identifier, not a country name. Match the B-domain carton label to the purchase line before serial assignment, then archive the dated compliance lookup.

Build the B-domain record around quotation-to-asset traceability. Preserve the authorized line, received label, chassis serial, assigned site and reviewer as one chain. If the controller later moves to another country configuration, open a new approval event rather than overwriting the original evidence; the history should explain both the purchased identity and every deployment decision.

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.

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.

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. A spare must be proven against the protected controller image, regulatory identity, bracket and PoE environment.

Authentication path test

Commission representative clients through association, authentication, address assignment, DNS and application reachability. Preserve the identity policy used, test client type, result and relevant controller logs. An access point that joins its controller has not yet demonstrated the user path. Repeat the test after any controller, certificate or authentication-service change and retain failures separately from RF or switch-port evidence. Test association, authentication, address assignment, DNS and application reachability after the AP is operational.

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.

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.

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-B-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.