AIR-AP3802I-GK910 - Cisco Aironet 3800i Access Point

AIR-AP3802I-GK910 Order Identity

AIR-AP3802I-GK910 is a Cisco Aironet 3800 Series, controller-based 802.11ac Wave 2 access point order. This exact SKU is a 3802I internal-antenna access point, carries regulatory-domain token G, and uses a fixed-domain 10-unit eco-pack.

Antenna and quantity boundary

Integrated antennas; no external antenna is included or selected as part of this SKU. Confirm the mounting position, ceiling construction and intended coverage because antenna orientation is determined by the integrated-antenna enclosure.

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 G. Treat that token as an identifier, not a country name. Complete deployment-country approval and controller domain alignment 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 G.

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.

Regulatory approval

Use Cisco's country compliance information for the deployment address and retain the result. The domain letter must not be translated into a country from memory. Keep the Cisco lookup date, destination country, approved domain and reviewer with the asset record. If the deployment country changes, stop and repeat the approval rather than assuming that a previously purchased AP can move across borders. Controller settings and antenna choices must remain consistent with that evidence.

Software lifecycle

Check the target controller release against Cisco support documentation and the approved migration architecture before buying additional 3800 Series capacity. The lifecycle note should name the approved controller release, last tested release, security-maintenance owner and migration review date. Review Cisco notices before each expansion because available inventory does not extend software compatibility. A replacement design should cover controller, licensing, power, cabling and mounting rather than only the radio unit.

Spare policy

State whether the unit is production capacity, a cold spare or a replacement. Define firmware, storage, periodic test and ownership requirements for unused stock. A spare should have a named site scope, compatible controller image, storage condition and periodic power-on test. Record whether its regulatory domain, antenna form and mounting kit match the protected population. Before use, repeat compliance and software checks because suitability can change while the unit is held in stock.

Migration dependency

Inventory controller, licensing, switch power, cabling and mounting dependencies that must change when the 3802 is replaced by a newer platform. Map the existing AP to its controller, licenses, authentication services, switch port, power budget, cable, bracket and monitoring objects. The successor plan should state which dependencies can be reused and which require change. This prevents a nominal AP replacement from failing because the surrounding platform was never inventoried.

Lifecycle and migration evidence

Cisco's support site lists an end-of-life announcement for the Cisco 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 3802I internal-antenna access point records

• AIR-AP3802I-DK910
• AIR-AP3802I-EK910
• AIR-AP3802I-HK910

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