AIRAP1832I-FK910C Cisco 1832i Controller-based Mobility Express AP

AIRAP1832I-FK910C exact order identity

AIRAP1832I-FK910C is a Cisco Aironet 1832i indoor access point with integrated antennas. This exact PID combines regulatory-domain token F 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.

F 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. Keep the F-domain approval beside the RF survey and antenna record so a later antenna change triggers a regulatory review.

Make antenna-change control the focus for this F-domain order. Record the approved antenna PID, gain, cable and mounting plan with the country lookup, then require review whenever any RF component changes. The controller configuration and final installation photographs should refer to the same asset. A mechanically compatible replacement antenna is not automatically an approved regulatory substitute.

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

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. Record the single 10/100/1000 Ethernet uplink rate, cable test and switch-port counters before evaluating wireless performance.

Survey-to-install reconciliation

Attach the approved RF survey location, mounting height, orientation, expected client density, channel width and neighboring-radio assumptions to the order. After installation, compare measured coverage and interference with that design. If ceiling construction, antenna placement or obstructions changed, document the deviation and repeat the affected measurements. This provides a site-specific acceptance reason for the exact unit instead of relying on a family data sheet alone. Compare the installed integrated-antenna orientation and measured coverage with the approved survey instead of relying on the family data sheet.

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.

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.

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 which security functions are actually configured on the deployed controller release; do not present optional family capabilities as enabled facts.

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.

Related Aironet 1832 order records

• AIR-AP1832I-F-K9C - compare software and procurement form.
• AIR-AP1832I-F-K9 - compare software and procurement form.
• AIR-AP1832I-Z-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.