AIR-AP3802E-GK910C Cisco Aironet 3800e Enterprise 802.11ac Wave 2 AP

AIR-AP3802E-GK910C exact order identity

AIR-AP3802E-GK910C 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, configurable ten-unit K910C eco-pack and regulatory token G.

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

Cisco identifies K910C as a configurable ten-access-point eco-pack. Preserve the selected regulatory-domain evidence and reconcile ten physical units independently.

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

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.

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.

Related Aironet 3802 orders

• AIR-AP3802I-NK910C - compare antenna, quantity, configuration and domain evidence.
• AIR-AP3802I-TK910C - compare antenna, quantity, configuration and domain evidence.
• AIR-AP3802I-HK910C - 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.