Cisco AIR-AP3802E-ZK910 Wireless Access Point

AIR-AP3802E-ZK910 exact order identity

AIR-AP3802E-ZK910 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, fixed-domain ten-unit K910 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 K910 as a fixed-domain ten-access-point eco-pack. Reconcile all ten chassis serials and reject a mixed-domain or short carton.

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

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.

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.

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.

Receiving inspection

At receipt, compare model label, regulatory token, antenna form, quantity, serials and visible condition with the authorized order. Photograph labels before cartons are separated. Quarantine shortages, mixed units, damaged connectors or unapproved substitutions. Do not rely on a distributor description as evidence that the exact Cisco order arrived. Close the inspection only when every physical unit is accounted for. Receiving must distinguish 3802E from 3802I and single-unit from ten-unit order before release.

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-AP3802I-Z-K9 - compare antenna, quantity, configuration and domain evidence.
• AIR-AP3802E-Z-K9 - compare antenna, quantity, configuration and domain evidence.
• AIR-AP3802I-E-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.