AIR-AP2802I-Z-K9 Cisco Aironet 2800i WPA2 Security Access Point

AIR-AP2802I-Z-K9 exact order identity

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

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

Z regulatory-domain channel evidence

Cisco's 2800 Series data sheet lists the Z profile as 2.4 GHz channels 1-11; 5 GHz blocks at 5.180-5.320, 5.500-5.700 excluding 5.600-5.640, and 5.745-5.825 GHz. The Z profile spans lower, middle and upper 5 GHz groups while retaining a documented gap in the middle group. That exclusion must survive controller template changes.

Compare the live channel list with the Z-domain evidence after every initial join or controller migration. Treat an enabled channel inside the excluded range as a release blocker. 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: lower, middle and upper groups provide broad planning options, but the documented middle gap remains a hard evidence point. Create a channel-list comparison that highlights the excluded range and retain it with the country lookup. After automatic channel changes or controller migration, repeat that comparison. Stable client service alone does not prove that the Z-domain constraints are still being enforced.

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.

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.

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.

Monitoring handover

Assign owners for AP reachability, controller join failures, radio utilization, client health and switch-port errors. Confirm that the exact serial appears in inventory and monitoring, then test the alert path. Record dashboard object, notification route and escalation owner. Telemetry that is not tied to an owned asset does not provide a reliable service baseline and will not support later comparison after channel or software changes.

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.

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-ZK910C - compare antenna architecture and regulatory-domain evidence.
• AIR-AP2802E-ZK910 - compare antenna architecture and regulatory-domain evidence.
• AIR-AP2802E-Z-K9C - 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.