AIR-AP2802I-SK910C Cisco Aironet 2800i 5.2 Gbps PHY Rates 10-pack APs

AIR-AP2802I-SK910C exact order identity

AIR-AP2802I-SK910C 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 S, 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.

S regulatory-domain channel evidence

Cisco's 2800 Series data sheet lists the S profile as 2.4 GHz channels 1-13; 5 GHz blocks at 5.180-5.320, 5.500-5.700, and 5.745-5.825 GHz. The S profile lists lower, middle and upper 5 GHz groups. The separation between middle and upper groups should remain explicit in RF planning and acceptance records.

Validate all three groups after controller provisioning and compare enabled channels with the approved survey. Keep the S-domain lookup and controller export together for future audits. 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: three listed 5 GHz groups give several planning pools, but destination approval still controls actual use. The survey should state how radios are distributed among lower, middle and upper groups, and acceptance should compare that plan with dynamic assignment. If one group is disabled locally or by policy, recalculate capacity and retain the exception instead of presenting the full S-profile table as deployed capability.

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.

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.

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.

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.

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.

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.

Related Aironet 2802 order records

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