AIR-AP2802E-B-K9C Cisco Aironet 2800e WiFi5 Access Point

AIR-AP2802E-B-K9C exact order identity

AIR-AP2802E-B-K9C 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 B, and a single-unit, configurable 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 K9C for a configurable single unit. The C suffix does not make the access point globally deployable; the final configured domain and destination approval must still be present on the quotation and received label. Hold the unit at receiving if the configured domain is absent or differs from the approved order. Preserve the configuration selection, chassis serial, destination evidence and controller-domain check as one release record. Because this is a configurable line, purchasing must retain the finally selected domain on both the authorized quotation and received label. The single unit needs one serial-level record, while accessories, controller readiness and destination approval remain separate acceptance items.

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

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.

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.

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.

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.

Related Aironet 2802 order records

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