5.2 Physical Infrastructure, Power over Ethernet (PoE) & Multi-Gigabit Networking

5.2 Physical Infrastructure, PoE & Multi-Gigabit Networking

Wireless performance depends on the access layer that powers each AP and carries its aggregated traffic. The exam expects engineers to translate a radio design into switch power budget, port speed, cabling, and VLAN requirements. The safest operational rule is simple: use the data sheet and power matrix for the exact AP model, regulatory domain, software release, and enabled options. Similar-looking Wi-Fi 6E and Wi-Fi 7 models do not shed the same features at the same input power.

PoE terms and budgets

The switch is the Power Sourcing Equipment (PSE); the AP is the Powered Device (PD). Power shown at the PSE is higher than guaranteed power at the PD because the cable dissipates energy.

Detection prevents a PSE from applying full power to a non-PoE device. Physical-layer classification establishes a power class, and LLDP or Cisco Discovery Protocol can refine the negotiated request after the AP boots. The switch must also have enough remaining chassis power budget. A port capable of 60 W is not useful if the active power supply cannot allocate it.

Do not assume that an 802.3af connection always causes a boot loop. Cisco’s current matrices for models such as CW9136 and CW9166 describe an 802.3af staging/configuration state in which radios are disabled. That is different from normal client service and different from a repeated boot failure.

Model-specific constrained-power behavior

Examples illustrate why model names matter:

Those are representative current Cisco power profiles, not a promise that every option or future software release behaves identically. Higher 802.3bt power is still required for the unrestricted feature set documented for the model. The key correction is that “PoE+ always shuts off 6 GHz” is false.

When an AP reports reduced power, inspect both ends. On the switch, verify inline-power detection, allocated/requested power, LLDP/CDP exchange, total available budget, and any port policing. On the controller/AP, inspect the actual power mode and disabled capabilities. Do not infer a specific LED pattern or radio state without model evidence.

Multi-gigabit Ethernet

A tri-band AP can aggregate more than 1 Gbps, so 2.5GBASE-T and 5GBASE-T are common access uplinks. IEEE 802.3bz was designed to reuse installed twisted pair at intermediate rates. Cisco commonly supports 2.5 and 5 Gbps over qualifying Category 5e channels, but qualification is the important word. Length, connectors, patch cords, bundle size, temperature, and alien crosstalk affect the achievable rate. Some newer platform guidance warns that speeds above 2.5 Gbps may not reach the full 100-meter objective on traditional Category 5e in adverse installations.

For a 90-meter Category 5e run, a design may target 5GBASE-T when both endpoints support it and cable testing confirms the channel. The engineer should not call 2.5 Gbps the standards-defined maximum, nor promise 5 Gbps unconditionally. Check switch port capability, AP port capability, negotiated speed, error counters, and a certified cable test. If the link downshifts, investigate the channel rather than forcing a speed that produces errors.

Power and data also interact thermally. Four-pair PoE in large bundles raises conductor temperature, while higher Ethernet signaling is sensitive to insertion loss and crosstalk. Follow the cabling vendor’s bundling and temperature guidance, especially for high-power APs.

Switchport mode follows forwarding mode

A local-mode AP normally sends its management and client traffic through CAPWAP. Its access-switch port therefore commonly carries only the AP management network, either as an access VLAN or as an intentionally designed trunk/native VLAN.

A FlexConnect AP using local switching must place client frames directly on local VLANs. Its port is an 802.1Q trunk. The native/untagged VLAN must match the AP-management design, and the allowed list must include all locally switched client VLANs. A missing management VLAN can let the AP receive power yet prevent DHCP or controller reachability.

Fabric wireless also needs the port and fabric-edge configuration prescribed by the SD-Access design; it should not be reduced to a generic “all fabric APs use this trunk template” rule.

Troubleshooting sequence

1. Identify AP model, power matrix, enabled radios/peripherals, and required switch capability.
2. Verify PSE class, allocated power, global power budget, and LLDP/CDP negotiation.
3. Verify AP-reported power mode and actual radio/uplink/peripheral restrictions.
4. Verify negotiated Ethernet speed, duplex, errors, cable category, length, and channel test.
5. Verify switchport VLAN mode against local, FlexConnect, or fabric forwarding.
6. Validate end-to-end throughput only after the physical and VLAN layers are correct.

This evidence-first sequence prevents a common exam trap: selecting a universal symptom when Cisco publishes different constrained-power profiles for different APs.