AIR-AP2802E-FK910C Cisco Aironet 2800e Enterprise WiFi 5 10 APs

AIR-AP2802E-FK910C exact order identity

AIR-AP2802E-FK910C is a Cisco Aironet 2800 Series controller-based 802.11ac Wave 2 access point order. The exact line combines a 2802E indoor access point for external antennas, regulatory-domain token F, and a configurable ten-unit eco-pack.

Antenna boundary

Cisco documents four RP-TNC antenna connectors plus a Smart Antenna connector on the 2802E. Antennas are a separate engineered part of the deployment bill of materials. Before release, record each Cisco-supported antenna part number, connector use, gain, pattern, cable type, cable loss, mounting orientation and local approval. A connector fit alone does not establish RF performance or regulatory suitability.

Order-form boundary

Cisco's ordering convention uses K910C for a configurable ten-access-point eco-pack. Configuration selection and physical quantity are separate acceptance gates: the chosen domain must be approved and ten individual units must be reconciled. Retain the configured-domain evidence with the carton record, then create ten serial-level asset rows. Do not release a partial, mixed-domain or unconfigured carton to installation without a documented correction. Because this is a configurable line, purchasing must retain the finally selected domain on both the authorized quotation and received label. The carton is not the deployable asset: each of the ten access points needs its own serial, location, controller and acceptance result.

F regulatory-domain channel evidence

Cisco's 2800 Series data sheet lists the F profile as 2.4 GHz channels 1-13; 5 GHz blocks at 5.250-5.350 and 5.725-5.825 GHz. The F profile is split between a compact mid-lower block and a high block. It does not match the common 5.180 GHz starting point, so imported controller templates require deliberate review.

Validate both separated channel groups on the target controller and confirm that the RF survey used the same boundaries. Record any disabled channel and its local regulatory reason. Regulatory-domain letters are identifiers, not country names; use Cisco's compliance tool for the actual deployment country and retain the lookup date.

Procurement inference: the two separated 5 GHz ranges call for a survey that distinguishes the mid-lower group from the high group. Confirm that expected clients, neighboring radios and controller policy can use the approved choices at the destination. When replacing a unit from a different domain, do not preserve old channel assignments blindly; generate a new assignment and compare measured interference in both F-profile groups.

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.

Power-state acceptance

Measure power after the access point has joined its controller and the planned radios and services are active. Record switch model, port, negotiated power level, LLDP result and any reduced-capability warning. An idle boot result is not sufficient evidence for the deployed power budget. If an injector is proposed, verify its supported use and include its exact identity in the maintained bill of materials rather than treating it as an unspecified accessory.

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.

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.

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.

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.

Operational log retention

Store the initial controller events, switch-port state, radio assignment, channel list and client test results with a consistent asset identifier. Define how long commissioning evidence is retained and who can retrieve it. A later firmware, controller or RF change should add a new dated observation rather than overwrite the original. The resulting history supports lifecycle decisions and distinguishes a new regression from the accepted baseline.

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.

Related Aironet 2802 order records

• AIR-AP2802I-FK910 - compare antenna architecture and regulatory-domain evidence.
• AIR-AP2802I-F-K9C - compare antenna architecture and regulatory-domain evidence.
• AIR-AP2802I-FK910C - compare antenna architecture and regulatory-domain evidence.

Official evidence: Cisco Aironet 2800 Series data sheet; Cisco 2800 Series getting started guide; Cisco 2800 Series support and lifecycle page; and Cisco wireless compliance tool.