Wi-Fi 7: why the cabling infrastructure matters more than the access points

What Wi-Fi 7 actually needs from the infrastructure behind it

Wi-Fi 7 (802.11be) introduces multi-link operation, 320 MHz channel widths and theoretical throughput figures that make its predecessors look pedestrian. In practice, what matters for a business deployment isn't the radio spec – it's whether the three infrastructure layers beneath the AP can actually support it.

Those three layers are: the cabling from the AP location back to the switch, the switch's PoE capability, and the switch's uplink capacity to the rest of the network. Each one can independently cap performance. Most businesses evaluate none of them before approving a Wi-Fi 7 upgrade.

The result is predictable: new access points, same connectivity complaints. The conversation then circles back to the AP vendor, firmware gets updated, channels get adjusted – and the actual bottleneck (a Cat5e cable or a 30W PoE port) goes unfixed for months.

The cabling question: Cat5e, Cat6 and Cat6A explained

Copper cable categories define the maximum data rate a cable can sustain over a given distance. Cat5e, the standard for most commercial installations during the 2000s and early 2010s, supports Gigabit Ethernet (1Gbps) at up to 100 metres. Cat6 supports 1Gbps reliably at 100 metres and can support 10Gbps at shorter runs – typically up to about 55 metres – though this is rarely relied upon in practice. Cat6A supports 10Gbps at the full 100-metre horizontal cable distance.

Wi-Fi 7 access points from Cisco, HPE Aruba, Ubiquiti UniFi and others are shipping with multi-gigabit uplink ports – 2.5Gbps is common, 5Gbps ports appear on higher-end models. A Cat5e or standard-length Cat6 cable feeding that AP limits the backhaul to 1Gbps. The AP's radio can aggregate far more than that from the wireless clients connected to it; the cable becomes the pinch point.

The practical implication: if your building has Cat5e or Cat6 cabling and you're planning a Wi-Fi 7 deployment, you have a decision to make. Either recable to Cat6A – which is the correct long-term answer – or accept that you're constraining a premium AP to legacy backhaul speeds. A Wi-Fi 7 AP running on Cat5e cabling isn't delivering Wi-Fi 7 performance; it's delivering Wi-Fi 7 radio capability with a 1Gbps ceiling on what it can actually move.

For any new commercial fit-out or significant refurbishment, Cat6A should be the default specification. The material cost difference between Cat6 and Cat6A at installation is modest. The cost of recabling after the fact is not.

PoE++: why your existing switches may not support Wi-Fi 7 APs

Most enterprise Wi-Fi 7 access points require IEEE 802.3bt – PoE++ or PoE 4.0 – to operate at full capability. PoE++ delivers up to 90W per port. Compare this with the earlier standards: 802.3af (the original PoE spec) delivers 15.4W; 802.3at (PoE+) delivers 30W.

Connect a Wi-Fi 7 AP that wants 802.3bt to a switch that only provides 802.3at, and one of two things happens: the AP doesn't power on at all, or it negotiates down to the available wattage and operates in reduced power mode. In reduced power mode, the AP typically disables one or more of its radios. A tri-band Wi-Fi 7 AP running on insufficient PoE may operate as a dual-band Wi-Fi 6 equivalent. You've paid for Wi-Fi 7 and you're running Wi-Fi 5 performance from a Wi-Fi 6 radio count.

This is a straightforward problem with a straightforward solution: check the AP's PoE requirement in the datasheet before purchasing, then check what standard your existing switches support. The issue is that many businesses don't do this until after the equipment arrives. PoE++ switches are more expensive than PoE+ switches – upgrading the switch estate is frequently a larger project cost than the APs themselves.

The switch upgrade is a legitimate and often necessary part of a Wi-Fi 7 deployment. Plan for it as a line item, not an afterthought.

Switch uplink capacity: the bottleneck nobody mentions

Even with Cat6A cabling and PoE++ switches, there's a third constraint that receives almost no attention in the access-point-focused conversation: the uplink from the floor switch to the core network.

A typical floor switch in an older commercial building has a 1Gbps uplink to the network core. If you install eight Wi-Fi 7 APs on that switch, each capable of 2.5Gbps backhaul, you have 20Gbps of potential AP-to-switch capacity feeding into a 1Gbps pipe to the rest of the network. In a high-density environment – a conference venue, an open-plan office, a hospitality space – that uplink becomes the bottleneck the moment traffic loads increase.

The correct specification for a Wi-Fi 7 deployment is a 10Gbps uplink from the access layer switch to the core. This requires either a switch with a 10Gbps SFP+ uplink port or aggregated uplinks – and a core switch or router capable of terminating 10Gbps connections. In buildings where the core infrastructure hasn't been touched since a Cat6 installation in 2012, this is a meaningful upgrade.

It's also worth auditing the density of APs per switch. Eight APs at 2.5Gbps is a different planning problem from three APs at 2.5Gbps. The access layer design needs to reflect the AP count and the expected traffic load per AP.

Refurbishment vs new build: different approaches

The right answer depends heavily on the building's existing infrastructure.

In a refurbishment scenario, the first step is a structured cabling survey: what cable category is installed, what is the run length and condition of terminations, and what PoE standard are the existing switches? If the building has Cat5e and 802.3at switches, deploying Wi-Fi 7 properly requires both a recabling programme and switch replacement – a significant project that should be costed and scoped before the AP hardware is even selected.

If a full recabling isn't in budget, the honest recommendation is often Wi-Fi 6 rather than Wi-Fi 7. Wi-Fi 6 can saturate a 1Gbps Cat5e backhaul and doesn't require PoE++. The performance gap between Wi-Fi 6 and Wi-Fi 7 is most pronounced in very high-density environments with many concurrent users; in a standard office or SME setting with existing Cat5e cabling, Wi-Fi 6 on correctly powered infrastructure will outperform Wi-Fi 7 on infrastructure it can't actually use.

In a new build or full fit-out, the answer is straightforward: specify Cat6A throughout, PoE++ switches, and 10Gbps core uplinks. The marginal cost of doing this correctly at installation is a fraction of the cost of returning to the building two years later to recable and replace switches.

How to specify a Wi-Fi 7 deployment that performs as expected

Before a Wi-Fi 7 project is scoped – certainly before access points are selected – three questions need answers.

What cable category is installed, and what are the run lengths? If it's Cat5e or short-run Cat6 with no documentation, commission a cabling survey. Don't assume. The FLUKE test reports from the original installation will tell you what you have; if they don't exist, a survey will.

What PoE standard do the existing switches support? Check the switch model against the manufacturer's datasheet. 802.3af and 802.3at are common; 802.3bt is less so in switches installed before 2020. If the switches don't support PoE++, budget for their replacement as part of the Wi-Fi 7 project.

What is the uplink capacity from the access layer to the core? If floor switches have 1Gbps uplinks, plan for 10Gbps upgrades alongside the AP deployment. The uplink is the infrastructure element most likely to be overlooked and most likely to cause performance complaints after the project completes.

A Wi-Fi 7 deployment designed around these three answers will perform as expected. One that ignores them will generate a support call six months after commissioning, when someone points out that the new Wi-Fi is no faster than the old Wi-Fi – and they'll be right.