AIR-AP3802I-H-K9 Cisco Aironet 3800i Access Point

AIR-AP3802I-H-K9 exact order identity

AIR-AP3802I-H-K9 is a controller-based Cisco Aironet 3800 Series 802.11ac Wave 2 access-point order. The PID selects the 3802I access point with integrated antennas, single-unit fixed-domain K9 order and regulatory token H.

Antenna architecture

Cisco integrates the antennas into the 3802I enclosure, so no external antenna is selected by this PID. Retain enclosure orientation, bracket, mounting height and measured coverage against the approved RF survey.

Quantity and configuration boundary

This K9 line is a single access-point order. Antenna, mounting, power and controller dependencies remain separate bill-of-material decisions.

H regulatory evidence

The domain token is not a country name. Capture the H-domain lookup date, reviewer and destination; a successful controller join does not replace this evidence.

Build the H-domain evidence around staged controller join. Capture the lookup, destination, controller country, software release and first successful join without treating the join itself as regulatory proof. Before production release, a reviewer should reconcile all five fields. A later controller reset or country change should create a new dated result while retaining the accepted baseline.

Controller, PoE and uplink boundary

Validate the exact controller release and CAPWAP join before deployment. Preserve negotiated PoE, multigigabit Ethernet rate, cable certification and error counters; family capability does not prove the installed switch and cable path achieve that rate.

Lifecycle and migration decision

Cisco lists 2022-10-31 as end of sale and 2027-10-31 as last support for the Aironet 3800 Series, with Catalyst 9130AX as the replacement direction. Available inventory does not extend those dates.

Deployment evidence worksheet

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. Commission association, authentication, addressing, DNS and application reachability on representative clients.

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. Document roaming path, neighboring cells, client type and controller events at each cell boundary.

Monitoring handover

Assign owners for AP reachability, controller join failures, radio utilization, client health and switch-port errors. Confirm that the exact serial appears in inventory and monitoring, then test the alert path. Record dashboard object, notification route and escalation owner. Telemetry that is not tied to an owned asset does not provide a reliable service baseline and will not support later comparison after channel or software changes. Monitor serial, CAPWAP state, radio health, Ethernet errors, PoE and client experience under one owner.

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

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 only security capabilities proven on the deployed controller and software release.

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 and client performance instead of maximum family PHY rates.

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 enabled-channel export after initial join and every controller migration.

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. Compare Catalyst 9130AX controller, power, cabling, antenna, mounting and coverage dependencies.

Related Aironet 3802 orders

• AIR-AP3802E-ZK910 - compare antenna, quantity, configuration and domain evidence.
• AIR-AP3802E-E-K9 - compare antenna, quantity, configuration and domain evidence.
• AIR-AP3802E-T-K9 - compare antenna, quantity, configuration and domain evidence.

Official evidence: Cisco Aironet 3800 data sheet; Cisco getting-started guide; Cisco 3800 lifecycle bulletin; Cisco support page; and Cisco compliance lookup.