AIR-AP1815W-B-K9C Cisco 1815W 802.11ac, Wave 2 Mobility Express AP

AIR-AP1815W-B-K9C exact wall-plate order

AIR-AP1815W-B-K9C is a compact Cisco Aironet 1815w access point for wall or junction-box installation in hospitality, residence and multi-dwelling environments. It supports concurrent 2.4-GHz and 5-GHz 2x2 radios with two spatial streams and integrated antennas.

Software order boundary

Cisco defines AIR-AP1815W-x-K9C as the order whose default software option is Mobility Express. Used inventory may have been reimaged, so preserve running software, current role, configuration backup and recovery evidence.

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

Room-side Ethernet and PoE boundary

The 1815w provides one Gigabit uplink, three local Gigabit Ethernet ports and one passive RJ-45 pass-through path. LAN 1 can provide 802.3af Class 0 PoE-out only when the AP itself receives 802.3at; there is no PoE output when the AP receives 802.3af.

Mounting and antenna boundary

The unit uses integrated dual-band antennas with approximately 2 dBi peak gain at 2.4 GHz and 3 dBi at 5 GHz. It installs vertically with AIR-AP-BRACKET-W3; AIR-AP1815W-KIT is a separate spacer and RJ-45 jumper option when the cabling path requires it.

Lifecycle decision

Cisco lists the Aironet 1815 family as end of sale, publishes 2027-04-30 as the last support date and identifies the Catalyst 9105AX Series as the migration family. Existing stock does not extend that support date.

Room 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. Record whether the AP receives 802.3af or 802.3at and whether LAN 1 PoE-out is expected.

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. Test the uplink, three local Gigabit ports and passive pass-through path required by the room design.

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. Prove a spare against the protected controller or Mobility Express image, bracket, PoE and port design.

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. Document roaming from the room cell into neighboring coverage with client and controller events.

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. Monitor AP join, both radios, uplink errors, local-port state, PoE-out and representative clients.

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 functions demonstrated on the deployed controller or Mobility Express release.

Interference baseline

Preserve the pre-install and post-install noise, neighboring-radio and channel-occupancy observations for the selected location. Record any controller-driven channel change during acceptance. If the regulatory profile limits the channel choices, state how that constraint affected reuse and mitigation. This baseline gives future troubleshooting a reference point and prevents an unrelated interference change from being attributed to the hardware order. Preserve the controller country and enabled-channel export after join or software conversion.

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 identify the wall-plate 1815w and distinguish K9 from K9C before staging.

Related Aironet 1815w order records

• AIR-AP1815W-B-K9 - compare software order and regulatory-domain evidence.
• AIR-AP1815W-I-K9 - compare software order and regulatory-domain evidence.
• AIR-AP1815W-Z-K9 - compare software order and regulatory-domain evidence.

Official evidence: Cisco Aironet 1815w data sheet; Cisco 1815w getting-started guide; Cisco wall-plate deployment guide; Cisco 1815 lifecycle bulletin; and Cisco compliance lookup.