AIR-AP1815W-S-K9C Cisco Aironet 1815W Dual-band Mobility Express AP

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

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

S regulatory evidence

The domain letter is an ordering identifier, not a country name. Compare the complete S-domain PID on quotation, carton and asset record; family equivalence is not regulatory equivalence.

Make quotation accuracy the S-domain control. The approved quote, supplier confirmation, received carton and asset record must carry the complete same PID. A substitution request should identify antenna form, controller-image state and regulatory token separately. Only after destination approval and controller review should the replacement line be accepted, even if pricing and lead time are unchanged.

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.

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 1815w generation must leave service and which surrounding dependencies need migration. Apply the 1815 Series lifecycle to software, support and Catalyst 9105AX migration planning.

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.

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.

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 role, country setting, switch port, room cabling and prior RF service.

Capacity observation

Define the expected concurrent clients, application mix, airtime utilization and channel-width assumptions for this location. After commissioning, capture radio utilization, retry behavior and representative throughput during a meaningful load period. Compare the observation with the survey design and state any shortfall. A peak link rate from a data sheet is not a site capacity result and should not replace measured operating evidence. Use measured airtime, retries, wired load and client performance rather than headline PHY rate.

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.

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 PID, serial, room, compliance result, software role, cabling and lifecycle owner.

Related Aironet 1815w order records

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