AIR-AP1832I-T-K9C Cisco 1832i Bluetooth 4 WiFi 5 Mobility Express AP

AIR-AP1832I-T-K9C exact order identity

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

T 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. Document the T-domain destination and controller country setting before installation, then keep the evidence through software upgrades.

Use software-upgrade governance for the T-domain record. Before an upgrade, preserve the controller country, enabled channels, AP serial and dated compliance lookup; after the change, capture the same fields for comparison. Investigate a changed radio state before production acceptance. This ties the domain decision to an observable configuration history instead of a one-time purchasing note.

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

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 1832i, retain the controller or Mobility Express role, software release, regulatory token and first successful join.

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. The 1832i draws up to 15.4 W and supports 802.3af or 802.3at; Cisco states that 802.3af disables the USB port.

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.

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.

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.

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-TK910C - compare software and procurement form.
• AIR-AP1832I-T-K9 - compare software and procurement form.
• AIRAP1832I-ZK910C - 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.