AIR-AP3802I-NK910C - Cisco Aironet 3800i Configurable Eco-pack 10 APs

AIR-AP3802I-NK910C exact order identity

AIR-AP3802I-NK910C is a controller-based Cisco Aironet 3800 Series 802.11ac Wave 2 access-point order. The PID selects the 3802I access point with integrated antennas, configurable ten-unit K910C eco-pack and regulatory token N.

Antenna architecture

Cisco integrates the antennas into the 3802I enclosure, so no external antenna is selected by this PID. Retain enclosure orientation, bracket, mounting height and measured coverage against the approved RF survey.

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.

N regulatory evidence

The domain token is not a country name. For the N-domain order, retain both destination approval and controller evidence before moving the unit from staging to production.

Use the staging-to-production handoff as the N-domain checkpoint. The staging record should contain destination approval, complete PID, serial and controller country; the production owner must accept those same fields. If the AP is moved between managed sites, close the first assignment and create a new reviewed destination record instead of merely changing the location field.

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.

Software lifecycle file

Record the controller release approved for this unit, the source used to verify support, the last tested date and the owner for software advisories. Available hardware does not prove compatibility with a current or future controller train. Review Cisco support information before every expansion or replacement. The lifecycle file should also state when this Aironet 3800 generation must leave service and which surrounding dependencies need migration. Apply the 2027 support limit to software, spares, entitlement and replacement planning.

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.

Fault-domain separation

Build the acceptance record so power, wired link, controller join, radio state, authentication and application reachability can be reviewed independently. Preserve timestamps and device identifiers across switch and controller logs. When a test fails, identify the failing boundary before replacing hardware. This avoids classifying a cable, policy or controller problem as an access-point defect and creates evidence that can be reused during support escalation. Use synchronized switch, AP and controller timestamps to isolate power, CAPWAP, RF and authentication faults.

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-AP3802E-NK910C - compare antenna, quantity, configuration and domain evidence.
• AIR-AP3802E-B-K9 - compare antenna, quantity, configuration and domain evidence.
• AIR-AP3802E-AK910 - 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.