AIR-AP2802E-EK910C Cisco Aironet 2800e Indoor WiFi 5 10 APs

AIR-AP2802E-EK910C exact order identity

AIR-AP2802E-EK910C 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 E, 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.

E regulatory-domain channel evidence

Cisco's 2800 Series data sheet lists the E profile as 2.4 GHz channels 1-13; 5 GHz blocks at 5.180-5.320 and 5.500-5.700 GHz, excluding 5.600-5.640 GHz. The E profile combines lower and middle 5 GHz operation but documents an internal exclusion in the middle block. Survey and controller evidence must show that the gap was understood.

Compare the enabled channel export with the E-domain profile, paying particular attention to the excluded sub-block. Preserve the lookup date, country selection and controller result in the asset file. 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: this profile's excluded middle sub-block creates a specific migration check. Preserve the prior controller channel template, then prove that the new or restored template does not reintroduce the excluded range. If channel capacity was calculated from a continuous middle block, correct the design assumptions and record the narrower usable plan before installation approval.

Deployment evidence worksheet

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.

Mechanical installation record

List the bracket, ceiling or wall interface, enclosure requirement, safety restraint, service clearance and cable-entry plan before scheduling installation. Receiving should identify missing mechanical items before the access point reaches site. Photograph the mounted label and final cable entry, then record how the unit can be reached for replacement. A complete electronic order can still be an unusable deployment kit when mechanical dependencies are omitted.

Country approval retention

Save the Cisco compliance lookup result, lookup date, deployment country, approved regulatory token and reviewer. If the destination changes, stop and repeat the approval rather than moving the unit on the strength of an earlier purchase. Compare the controller country setting and available channels with the retained evidence. Regulatory eligibility is a deployment condition and cannot be inferred from connector fit, stock location or a similar-looking part number.

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 2802 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.

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 generation must leave service and which surrounding dependencies need migration.

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.

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-EK910 - compare antenna architecture and regulatory-domain evidence.
• AIR-AP2802I-E-K9C - compare antenna architecture and regulatory-domain evidence.
• AIR-AP2802E-EK910 - compare order quantity or configuration 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.