C9120AXE-D Cisco Catalyst 9120 Dual-band WiFi 6 External Antenna AP

C9120AXE-D exact order identity

C9120AXE-D is a Cisco Catalyst 9120AX Series indoor Wi-Fi 6 access point for challenging environments with external antennas. The exact PID combines the E antenna form, a controller-based access-point order and regulatory-domain token D.

Antenna and installation boundary

Cisco specifies four external dual-band RP-TNC connectors, a four-port Smart Antenna DART connector and support for a Self-Identifying Antenna on one RP-TNC port. Antennas are sold separately. Cisco certifies the 9120AXE for gains up to 6 dBi on 2.4 and 5 GHz; preserve antenna PID, gain, pattern, cable loss and controller configuration before powering the AP. Cisco requires external antennas to be connected before power is applied; an outdoor antenna installation also requires grounding before power.

Controller-image boundary

Cisco lists this PID without the EWC infix, so the order is the controller-based access-point form rather than an EWC software-image order. Record the target controller model and release. Cisco's getting-started guide requires AireOS 8.9.111.0 or later, or IOS XE 16.11.1b or later, for the 9120AX family.

D regulatory-domain evidence

Cisco uses the final PID letter as a regulatory-domain identifier and requires customers to verify approval for the country of use. The letter is not a country name. For a D-domain spare, record the approved protected sites so it cannot be moved to a destination with a different domain requirement.

Treat this D-domain unit as location-controlled inventory. Name the destination or protected spare population, record who may reassign it and require a new Cisco lookup before any transfer. Commissioning should retain the controller country and enabled-channel outputs. This prevents an unused spare from appearing technically interchangeable after organizational or geographic changes.

Power and wired-uplink boundary

The family has one 100/1000/2500 Multigigabit Ethernet uplink. Cisco lists full 4x4 radio operation, 2.5-Gigabit Ethernet and USB with 802.3at; under 802.3af both radios reduce to 1x1, Ethernet reduces to 1 GbE and USB is disabled.

External controller decision

This PID does not carry the EWC software-image infix. Record the production controller and supported software release, and verify the live compatibility matrix before an upgrade or substitution.

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. The full 4x4 radios and 2.5-Gigabit link require 802.3at; Cisco states that 802.3af reduces both radios to 1x1, limits Ethernet to 1 GbE and disables USB.

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. Relate the installed radio mode to the survey because the flexible radio can serve 2.4/5 GHz or participate in a dual-5-GHz design.

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. Asset identity must preserve AXI, AXE or AXP, the EWC state and the final domain token because each field changes the procurement boundary.

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. A different antenna form, EWC state or regulatory token is a different 9120AX order and requires a new technical acceptance decision.

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. Record the controller release and the 9120AX compatibility source before upgrade, expansion or emergency replacement.

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. A stored 9120AX spare should be periodically tested for controller join, negotiated PoE state and the antenna or mounting dependencies it protects.

Security baseline

Retain the approved controller policy, management authorization, certificate or trust workflow, client authentication test and logging destination. Confirm behavior on the deployed controller software instead of promising a protocol from the hardware family name. Remove temporary onboarding access and verify administrative reachability after handover. This keeps product identity separate from software-dependent security claims. The 9120AX data sheet describes platform capabilities; record which security features are actually enabled and validated on the deployed controller release.

Capacity observation

Define the expected concurrent clients, application mix, airtime utilization and channel-width assumptions for this location. After commissioning, capture radio utilization, retry behavior and representative throughput during a meaningful load period. Compare the observation with the survey design and state any shortfall. A peak link rate from a data sheet is not a site capacity result and should not replace measured operating evidence. Capacity acceptance should use observed clients, channel width, airtime and retries rather than the family's maximum over-the-air rate.

Related Catalyst 9120 order records

• C9120AXP-EWC-D - compare antenna form and domain evidence.
• C9120AXI-EWC-D - compare antenna form and domain evidence.
• C9120AXI-D - compare antenna form and domain evidence.

Official evidence: Cisco Catalyst 9120AX data sheet; Cisco Catalyst 9120AX getting-started guide; Cisco wireless compliance tool.