Cisco AIR-AP3802E-HK910 Wireless Access Point

AIR-AP3802E-HK910 Order Identity

AIR-AP3802E-HK910 is a Cisco Aironet 3800 Series, controller-based 802.11ac Wave 2 access point order. This exact SKU is a 3802E external-antenna access point, carries regulatory-domain token H, and uses a fixed-domain 10-unit eco-pack.

Antenna and quantity boundary

External antennas are required and must be selected as separate, compatible order items. Build an antenna bill of materials that records connector, gain, pattern, cable loss, mounting hardware and local radio limits before release.

Cisco identifies the K910 order form as an eco-pack containing 10 access points; carton-level receiving must reconcile all ten serial numbers.

This is a non-C fixed-domain order form. Receiving must match the exact domain-bearing SKU and must not substitute a configurable or different-domain line without approval.

Regulatory-domain control

The order carries regulatory-domain token H. Treat that token as an identifier, not a country name. Complete domain-token reconciliation and RF design sign-off against Cisco's current compliance resources before shipment or activation.

Cisco uses the variable regulatory-domain position in its ordering structure. Deployment eligibility must be checked for the destination country; this page does not infer a country mapping from token H.

Controller readiness

Record the intended Cisco wireless controller, supported software train and join method. Validate the AP on a staging network before changing the production RF plan. The acceptance file should identify the controller address, discovery path, AP authorization method and the release evidence used for approval. Capture the first successful join, configuration download and radio state, then remove any temporary staging authorization. This makes a later controller migration traceable without claiming that every software release supports the hardware.

Power budget

Confirm the switch port's negotiated PoE mode, available power, cable length and LLDP behavior. Keep the measured power result with commissioning evidence. Measure the power state after both radios and production features are active, not only while the unit is idle. Record switch model, port, power class, negotiated result and any feature reduction shown by the controller. If an injector is proposed, verify its Cisco support and place it in the maintained bill of materials.

Multigigabit uplink

The 3800 Series supports multigigabit Ethernet. Verify the switch port, cabling category, negotiated rate and error counters instead of assuming a 2.5 or 5 Gbps link. Commissioning should preserve the negotiated Ethernet rate, cable-test result, packet errors and switch configuration. Where the access switch is limited to 1 Gbps, state that design choice explicitly instead of presenting multigigabit capability as achieved throughput. Recheck negotiation after patch-cord or switch changes.

Monitoring ownership

Assign owners for controller alarms, switch-port health, radio utilization and software advisories so the installed AP remains observable after handover. Monitoring handover should name the team that owns AP reachability, controller join failures, radio utilization, client health and switch-port errors. Define alert thresholds and an escalation path, then verify that the exact serial appears in the operational inventory. Unowned telemetry does not provide a reliable service baseline.

Security baseline

Record the approved controller policy, management access, certificate handling and authentication test. Do not infer current security support from the hardware name alone. Retain the controller policy name, management authorization, certificate or trust workflow, authentication test and logging destination used at commissioning. Confirm the supported security behavior on the deployed software release. The hardware family alone must not be used to promise a feature or protocol that has not been validated.

Change control

Define the staging date, installation window, rollback owner and validation threshold before the AP is joined to a production controller. The change record should list staging evidence, production window, responsible installer, rollback decision and success criteria. Preserve the previous controller or AP state needed for recovery. After the window, close temporary credentials and compare monitoring, authentication and RF results with the approved baseline before declaring completion.

Lifecycle and migration evidence

Cisco's support site lists an end-of-life announcement for the Aironet 3800 Series. Confirm current support dates, controller compatibility and the approved replacement path before treating available stock as suitable for a new deployment.

Related 3802E external-antenna access point records

• AIR-AP3802E-IK910
• AIR-AP3802E-QK910
• AIR-AP3802E-SK910

Official evidence: Cisco Aironet 3800 Series data sheet, Cisco 3800 Series getting started guide, and Cisco end-of-life notices.