AIR-AP3802I-TK910C Cisco Aironet 3800 4x4:3 MU-MIMO 10 APs

AIR-AP3802I-TK910C exact order identity

AIR-AP3802I-TK910C 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 T.

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.

T regulatory evidence

The domain token is not a country name. Document the T-domain destination and controller country setting before installation, then keep the evidence through software upgrades.

Use software-upgrade governance for the T-domain record. Before an upgrade, preserve the controller country, enabled channels, AP serial and dated compliance lookup; after the change, capture the same fields for comparison. Investigate a changed radio state before production acceptance. This ties the domain decision to an observable configuration history instead of a one-time purchasing note.

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

Controller join evidence

Stage the access point on the controller release intended for production. Retain the controller model, software version, discovery path, authorization method and first successful CAPWAP join. Confirm that configuration download completes and that both radios reach an expected operational state. Remove any temporary staging authorization before handover. This evidence separates an orderable access point from a unit that has actually been proven compatible with the planned controller environment. For this 3802 order, retain controller discovery, image transfer and final CAPWAP join by serial.

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.

Quotation substitution gate

Compare antenna form, regulatory token, configuration suffix, pack quantity and complete Cisco part number on the authorized quotation. Treat any changed token as a substitution that requires a new technical and regulatory review. Procurement should not accept a nearby Aironet 3802 line merely because the family name matches. Preserve the approved line, received label and exception decision so the final asset can be traced to the exact order reviewed here. A changed antenna letter, domain, quantity or configurable suffix requires a new procurement review.

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.

Interference baseline

Preserve the pre-install and post-install noise, neighboring-radio and channel-occupancy observations for the selected location. Record any controller-driven channel change during acceptance. If the regulatory profile limits the channel choices, state how that constraint affected reuse and mitigation. This baseline gives future troubleshooting a reference point and prevents an unrelated interference change from being attributed to the hardware order. Preserve the enabled-channel export after initial join and every controller migration.

Replacement dependency map

Map this unit to controller, licenses, authentication services, switch power, cable, bracket, antenna design and monitoring objects. For an end-of-sale platform, state which dependencies can be reused by the planned Catalyst migration and which require change. A nominal access-point replacement can fail when the surrounding platform was never inventoried. Keep the map with the asset rather than only in a one-time project file. Compare Catalyst 9130AX controller, power, cabling, antenna, mounting and coverage dependencies.

Related Aironet 3802 orders

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