AIR-AP1815W-K-K9C Cisco Aironet 1815W Dual-radio Mobility Express AP

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

AIR-AP1815W-K-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.

K regulatory evidence

The domain letter is an ordering identifier, not a country name. Tie the K-domain purchase line to the controller country configuration and the post-join enabled-channel export.

Center the K-domain package on channel-state evidence. Retain the Cisco country lookup and controller country configuration, then export the enabled-channel state after the AP joins. Store the output with exact PID, serial and survey reference. Repeat the comparison after controller upgrades so a software change cannot silently separate the live radio state from the approved order.

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

Controller join evidence

Stage the access point on the controller release intended for production. Retain the controller model, software version, discovery path, authorization method and first successful CAPWAP join. Confirm that configuration download completes and that both radios reach an expected operational state. Remove any temporary staging authorization before handover. This evidence separates an orderable access point from a unit that has actually been proven compatible with the planned controller environment. For the 1815w, retain controller discovery, software download and final join beside the exact serial.

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.

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 nearby Aironet 1815w line 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 domain letter or K9/K9C suffix is a different 1815w procurement identity.

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 wireless clients and every occupied local wired port through authentication and application access.

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.

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. Compare the Catalyst 9105AX migration with wall mounting, ports, PoE-out, software and coverage needs.

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 wireless, wired, power and client results as the operational baseline.

Related Aironet 1815w order records

• AIR-AP1815W-K-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.