AIR-AP2802E-S-K9 Cisco Aironet 2800e 4x4 MU-MIMO 802.11ac Wave 2 AP

AIR-AP2802E-S-K9 exact order identity

AIR-AP2802E-S-K9 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 S, and a single-unit, fixed regulatory-domain order.

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 K9 for one access point. This line already carries a regulatory-domain token, so receiving must match the complete part number rather than accepting another domain as an equivalent. Create one asset record for the chassis serial and MAC address. Link that record to the approved destination, controller, switch port, mounting position and compliance lookup before the unit joins production. Because this is a fixed-domain line, a quotation or received label carrying another domain is a different order and requires a fresh approval. The single unit needs one serial-level record, while accessories, controller readiness and destination approval remain separate acceptance items.

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

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.

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.

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.

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.

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