AIRAP1832I-SK910C Cisco 1832i Bluetooth 4 3x3 MIMO Mobility Express AP

AIRAP1832I-SK910C exact order identity

AIRAP1832I-SK910C is a Cisco Aironet 1832i indoor access point with integrated antennas. This exact PID combines regulatory-domain token S with a legacy K910C Mobility Express procurement line. 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's Aironet 1830 lifecycle bulletin lists each AIRAP1832I-xK910C PID as Cisco Aironet Mobility Express 1830 Series. The bulletin does not state the physical carton quantity for these K910C lines. Verify quantity, serial count and software role from the authorized quotation and received carton rather than expanding the suffix into an unsupported claim.

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

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

Mechanical installation record

List the bracket, ceiling or wall interface, enclosure requirement, safety restraint, service clearance and cable-entry plan before scheduling installation. Receiving should identify missing mechanical items before the access point reaches site. Photograph the mounted label and final cable entry, then record how the unit can be reached for replacement. A complete electronic order can still be an unusable deployment kit when mechanical dependencies are omitted. The 1832i supports common Cisco Aironet mounting brackets; preserve the exact bracket and ceiling or wall interface used at the site.

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. For a K910C line, reconcile every received serial against the authorized carton quantity because Cisco's lifecycle description does not state that quantity.

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 generation must leave service and which surrounding dependencies need migration. Cisco ended 1830 Series software maintenance on 1 May 2023, so the retained controller compatibility result is a lifecycle control.

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.

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 live controller country and enabled-channel state beside the exact domain token and deployment approval.

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 controller, switch and client timestamps to separate power, CAPWAP, RF and authentication faults before declaring hardware failure.

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 join, power, wired, radio and client test results so later software or RF changes have a 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 contain exact PID, serials, quantity evidence, compliance lookup, software role, mounting record and lifecycle owner.

Related Aironet 1832 order records

• AIR-AP1832I-Z-K9C - compare regulatory-domain evidence.
• AIR-AP1832I-Z-K9 - compare regulatory-domain evidence.
• AIR-AP1832I-T-K9C - 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.