Cisco AIR-AP3802E-A-K9 - 802.11ac Wave 2 Access Point

AIR-AP3802E-A-K9 exact order identity

AIR-AP3802E-A-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 A.

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.

A regulatory evidence

The domain token is not a country name. Retain the destination-country result, the exact A-domain PID and the controller country setting in one approval record.

Use receiving as the A-domain control point: photograph the carton PID, reconcile it with the purchase order and attach the Cisco lookup before the serial is released. At commissioning, compare the controller country setting with that same record. A return replacement must repeat both checks because matching enclosure and antenna form do not establish matching regulatory identity.

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.

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. Prove the permanent link, patch leads, multigigabit switch port, negotiated rate and error counters.

Survey-to-install reconciliation

Attach the approved RF survey location, mounting height, orientation, expected client density, channel width and neighboring-radio assumptions to the order. After installation, compare measured coverage and interference with that design. If ceiling construction, antenna placement or obstructions changed, document the deviation and repeat the affected measurements. This provides a site-specific acceptance reason for the exact unit instead of relying on a family data sheet alone. Tie the post-install RF result to the exact integrated or external antenna architecture.

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.

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.

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.

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.