Cisco AIR-AP3802I-G-K9 802.11ac Wave 2 Internal Antenna Access Point

AIR-AP3802I-G-K9 exact order identity

AIR-AP3802I-G-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 G.

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.

G regulatory evidence

The domain token is not a country name. Reconcile the G-domain PID at receiving and prevent a nearby domain SKU from being accepted as a cosmetic substitution.

Use substitution handling as the G-domain control. Receiving must compare every character of the ordered and delivered PID, quarantine a different token and preserve the disposition decision. After acceptance, link the correct label to the controller object and site. This keeps a nearby Catalyst 9120 SKU from entering service solely because its family and antenna enclosure look identical.

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

Country approval retention

Save the Cisco compliance lookup result, lookup date, deployment country, approved regulatory token and reviewer. If the destination changes, stop and repeat the approval rather than moving the unit on the strength of an earlier purchase. Compare the controller country setting and available channels with the retained evidence. Regulatory eligibility is a deployment condition and cannot be inferred from connector fit, stock location or a similar-looking part number. Save the Cisco country lookup and controller country setting with the exact regulatory token.

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 3800 generation must leave service and which surrounding dependencies need migration. Apply the 2027 support limit to software, spares, entitlement and replacement planning.

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.

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.

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.

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.

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 include PID, all serials, compliance result, controller, antenna record and lifecycle owner.

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.