AIR-AP2802I-BK910C Cisco Aironet 2800i WiFi 5 Eco-pack 10 APs

AIR-AP2802I-BK910C exact order identity

AIR-AP2802I-BK910C is a Cisco Aironet 2800 Series controller-based 802.11ac Wave 2 access point order. The exact line combines a 2802I indoor access point with integrated antennas, regulatory-domain token B, and a configurable ten-unit eco-pack.

Antenna boundary

Cisco documents twelve cross-polarized internal antennas in the 2802I enclosure. No external antenna is selected by this access-point SKU. The RF result therefore depends on enclosure orientation, mounting height, obstructions and the surveyed placement. Receiving should confirm the mounting kit, while commissioning should retain photographs of the final orientation and compare measured coverage with the approved survey.

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.

B regulatory-domain channel evidence

Cisco's 2800 Series data sheet lists the B profile as 2.4 GHz channels 1-11; 5 GHz blocks at 5.180-5.320, 5.500-5.720, and 5.745-5.825 GHz. The B plan contains a broad middle 5 GHz range followed by a separate upper block. Capacity planning should identify which radios use each block and should not copy a narrower domain's channel template.

Retain a controller export showing the enabled lower, middle and upper channel sets. Compare the installed country setting, dynamic channel assignment and survey plan before accepting the site. 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 comparatively broad middle range and separate upper range can influence how capacity is distributed across radios. Preserve the survey's planned channel groups and compare them with the controller's dynamic assignment after a representative operating period. If the destination authorization narrows the available set, update the capacity calculation and acceptance record rather than leaving a B-profile assumption in the design.

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.

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.

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.

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.

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.

Controlled spare policy

If purchased as a spare, name the protected site population, compatible controller image, storage location, storage conditions and periodic power-on test. Confirm that regulatory token, antenna architecture and mounting parts match the population it protects. Set a final-use review date. A stored unit can become unsuitable while untouched because controller software, country approval, certificates or network architecture may change.

Receiving inspection

At receipt, compare model label, regulatory token, antenna form, quantity, serials and visible condition with the authorized order. Photograph labels before cartons are separated. Quarantine shortages, mixed units, damaged connectors or unapproved substitutions. Do not rely on a distributor description as evidence that the exact Cisco order arrived. Close the inspection only when every physical unit is accounted for.

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.

Related Aironet 2802 order records

• AIR-AP2802E-BK910 - compare antenna architecture and regulatory-domain evidence.
• AIR-AP2802E-B-K9C - compare antenna architecture and regulatory-domain evidence.
• AIR-AP2802E-B-K9 - 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.