Indoor AIR-AP3802E-I-K9 Cisco Aironet 3800e Access Point

AIR-AP3802E-I-K9 exact order identity

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

Antenna architecture

The 3802E requires separately selected compatible external antennas; connector fit alone is not an approved RF design. Record antenna PID, connector use, gain, pattern, cable loss, mounting, grounding and country approval.

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.

I regulatory evidence

The domain token is not a country name. Preserve the I-domain label in the asset record and verify that replacement stock carries the same approved regulatory identity.

Use replacement-stock readiness for the I-domain workflow. List the deployed population this unit may protect, confirm those assets use the same approved token and retain the mounting or antenna dependencies. During periodic spare testing, verify controller join and country configuration without reassigning the unit. Any cross-site use requires a fresh destination approval before installation.

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

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. Record negotiated PoE state after radios and production features are active, not only at idle boot.

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. A ten-unit order still requires ten serial, MAC, site and controller asset records.

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. Test stored spares against controller release, PoE, domain, antenna and mounting dependencies.

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.

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.

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 must distinguish 3802E from 3802I and single-unit from ten-unit order before release.

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 synchronized switch, AP and controller timestamps to isolate power, CAPWAP, RF and authentication faults.

Related Aironet 3802 orders

• AIR-AP3802I-Z-K9 - compare antenna, quantity, configuration and domain evidence.
• AIR-AP3802I-E-K9 - compare antenna, quantity, configuration and domain evidence.
• AIR-AP3802I-H-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.