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

AIR-AP3802I-N-K9 exact order identity

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

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.

N regulatory evidence

The domain token is not a country name. For the N-domain order, retain both destination approval and controller evidence before moving the unit from staging to production.

Use the staging-to-production handoff as the N-domain checkpoint. The staging record should contain destination approval, complete PID, serial and controller country; the production owner must accept those same fields. If the AP is moved between managed sites, close the first assignment and create a new reviewed destination record instead of merely changing the location field.

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

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 this 3802 order, retain controller discovery, image transfer and final CAPWAP join by serial.

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.

Mechanical installation record

List the bracket, ceiling or wall interface, enclosure requirement, safety restraint, service clearance and cable-entry plan before scheduling installation. Receiving should identify missing mechanical items before the access point reaches site. Photograph the mounted label and final cable entry, then record how the unit can be reached for replacement. A complete electronic order can still be an unusable deployment kit when mechanical dependencies are omitted. Reconcile bracket, enclosure, restraint, cable entry and every external-antenna component before site work.

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.

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.

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.

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.

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-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.