AIR-AP3802E-ZK910C Cisco Aironet 3800e WIFi 5 AP 10-Pack

AIR-AP3802E-ZK910C exact order identity

AIR-AP3802E-ZK910C 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 Z.

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.

Z regulatory evidence

The domain token is not a country name. Attach the Z-domain compliance lookup to the commissioning package and flag any later country-setting change for reapproval.

Build the Z-domain package as a commissioning baseline. Combine the exact PID, destination lookup, controller country, enabled-channel output, antenna or mounting evidence and representative client test under one review date. Later automatic radio changes may be operationally valid, but country-setting or hardware reassignment changes require explicit reapproval and a new baseline entry.

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.

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.

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.

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.

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.

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.