AIR-AP1832I-D-K9C Cisco Aironet 1832i Dual-band Mobility Express AP

AIR-AP1832I-D-K9C exact order identity

AIR-AP1832I-D-K9C is a Cisco Aironet 1832i indoor access point with integrated antennas. This exact PID combines regulatory-domain token D with a single configurable K9C Mobility Express order. Cisco documents 802.11ac Wave 2, 3x3 MIMO with two spatial streams and a maximum 5-GHz PHY rate of 867 Mbps.

Integrated-antenna boundary

The 1832i antenna system is internal. No external antenna is selected by this access-point PID, so mounting location, orientation, ceiling construction and the post-install survey determine how the published platform is used.

Software and order boundary

Cisco identifies AIR-AP1832I-x-K9C as configurable and supplied with the default Mobility Express software option. Preserve the intended Mobility Express or external-controller role, actual software release and conversion state instead of inferring the live role from the carton alone.

D regulatory-domain evidence

Cisco treats the letter as a regulatory-domain identifier and requires approval for the country of use; it is not a country name. For a D-domain spare, record the approved protected sites so it cannot be moved to a destination with a different domain requirement.

Treat this D-domain unit as location-controlled inventory. Name the destination or protected spare population, record who may reassign it and require a new Cisco lookup before any transfer. Commissioning should retain the controller country and enabled-channel outputs. This prevents an unused spare from appearing technically interchangeable after organizational or geographic changes.

Power and interface boundary

The AP supports 802.3af, 802.3at, Enhanced PoE, a local power supply and Cisco power injectors. Cisco lists a 15.4 W draw and states that USB is disabled when 802.3af is used. Record the negotiated power and the single Gigabit Ethernet uplink state.

Lifecycle decision

Cisco ended sale of the Aironet 1830 Series on 1 May 2022, ended software maintenance on 1 May 2023 and lists 30 April 2027 as the last support date. Cisco identifies Catalyst 9115AX as the migration family; available inventory does not extend these dates.

Deployment evidence worksheet

Country approval retention

Save the Cisco compliance lookup result, lookup date, deployment country, approved regulatory token and reviewer. If the destination changes, stop and repeat the approval rather than moving the unit on the strength of an earlier purchase. Compare the controller country setting and available channels with the retained evidence. Regulatory eligibility is a deployment condition and cannot be inferred from connector fit, stock location or a similar-looking part number. Cisco makes the customer responsible for country approval; keep the dated compliance lookup with the 1832i serial and controller country.

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 1832i should be tested against the protected controller release, domain, mounting hardware and April 2027 support cutoff.

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, DHCP, DNS and application reachability after the AP reaches its final controller or Mobility Express role.

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. Roaming acceptance should identify neighboring cells, client type and controller events rather than treating static association as proof.

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 the former controller or Mobility Express role, country setting, switch port and accepted RF state.

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. Cisco names Catalyst 9115AX as the migration family; map controller, power, mounting and coverage changes before replacement.

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 should verify the integrated-antenna 1832i identity and distinguish K9, K9C and K910C software or procurement forms.

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 contain exact PID, serials, quantity evidence, compliance lookup, software role, mounting record and lifecycle owner.

Related Aironet 1832 order records

• AIRAP1832I-DK910C - compare software and procurement form.
• AIRAP1832I-ZK910C - compare regulatory-domain evidence.
• AIRAP1832I-TK910C - compare regulatory-domain evidence.

Official evidence: Cisco Aironet 1830 Series data sheet; Cisco Aironet 1830 lifecycle bulletin; Cisco Aironet 1830 support page; and Cisco wireless compliance tool.