
A Cisco Catalyst 9200 can power Wi-Fi 6E access points, but the number of APs you can support is determined by watts as well as ports. The exact Catalyst 9200 PoE budget depends on the switch model, installed power supplies, AP power requirement, other powered devices and the amount of capacity you want to keep in reserve.
This matters more with newer wireless infrastructure because some Wi-Fi 6E access points require substantially more power than basic phones or earlier-generation APs.
A 24-port PoE+ switch may physically have enough interfaces for 20 APs but still lack enough available PoE power to run those APs at their intended operating level.
The correct design process is:
AP power requirement → device quantity → total PoE demand → reserve and redundancy → switch/PSU selection
What Is the Catalyst 9200 PoE Budget?
The Catalyst 9200 PoE budget is the total electrical power that the switch can allocate through its Ethernet ports to powered devices such as access points, IP phones and cameras.
Three separate specifications matter.
Number of PoE-Capable Ports
This tells you how many Ethernet interfaces can potentially provide power.
A 48-port Catalyst 9200 PoE model, for example, provides significantly more physical connectivity than a 24-port model.
But 48 PoE-capable ports do not automatically mean the switch has enough electrical capacity to operate 48 high-power access points simultaneously.
Maximum Power Per Port
The PoE standard supported by the switch determines how much power an individual port can provide.
Standard C9200 and C9200L PoE+ models support IEEE 802.3at PoE+, which allows the Power Sourcing Equipment to deliver up to 30W per compatible port.
Total Available PoE Budget
This is the amount of power that can actually be distributed across all powered ports.
For example, a 24-port C9200-24P with one 600W AC PSU provides approximately 370W of available PoE, while a relevant 48-port C9200-48P with one 1000W PSU provides approximately 740W.
The PSU’s wattage is therefore not the same as the switch’s usable PoE capacity.
That distinction is central to accurate PoE planning.
PoE, PoE+ and Higher-Power PoE Explained
PoE standards define the amount of power a switch can provide and the amount a connected device can receive.
| PoE Type | IEEE Standard | Maximum PSE Output | Approx. Maximum at Powered Device | Typical Use |
|---|---|---|---|---|
| PoE | 802.3af | 15.4W | 12.95W | Phones, low-power devices |
| PoE+ | 802.3at | 30W | 25.5W | Enterprise APs, cameras |
| PoE++ Type 3 | 802.3bt | 60W | Up to 51W | Higher-power APs/devices |
| PoE++ Type 4 | 802.3bt | 90W | Around 71W | Very high-power endpoints |
Two terms are useful here:
PSE — Power Sourcing Equipment: the switch supplying power.
PD — Powered Device: the AP, phone, camera or other endpoint receiving power.
A PoE+ switch port can source up to 30W, while up to approximately 25.5W is available to the powered device after accounting for the standard’s cabling allowance.
This is why a switch specification that says “30W per port” should not be compared blindly with an AP’s input requirement.
How Much Power Do Wi-Fi 6E Access Points Need?
There is no single power requirement for every Wi-Fi 6E access point.
Power demand varies according to:
- Radio configuration
- 2.4 GHz, 5 GHz and 6 GHz operation
- Number of spatial streams
- Ethernet speed
- USB functionality
- IoT/BLE radios
- Processing workload
- AP model
Cisco Catalyst 9160-series APs illustrate the differences clearly.
Cisco Catalyst 9162
The Catalyst 9162 can operate its 2.4 GHz, 5 GHz and 6 GHz radios in its normal 2×2 configuration with 802.3at PoE+.
Maximum PoE consumption is approximately 25.5W.
The AP can operate from 802.3af power, but its wireless configuration is reduced. In that lower-power mode, radio capability and wired link speed are restricted.
For a normal full-feature deployment, 25.5W is therefore a more appropriate planning figure than the reduced 802.3af figure.
Cisco Catalyst 9164
The Catalyst 9164 uses approximately 25W maximum on PoE+ for its primary radio configuration.
With higher-power 802.3bt/UPOE input, maximum consumption can reach approximately 30W, with additional functionality such as USB power becoming available.
802.3af operation is primarily intended for staging rather than normal production wireless use.
Cisco Catalyst 9166
The Catalyst 9166 can consume approximately 25.5W on PoE+.
With 802.3bt/UPOE power, maximum consumption increases to approximately 30.5W, including support for USB power.
Under 802.3af, the normal radio configuration is not available.
This means the same AP can have different power requirements depending on how you intend to operate it.
Cisco Wi-Fi 6E AP Power Requirements
| Cisco AP | Normal PoE+ Planning Level | Higher-Power Mode | Lower-Power Behaviour |
|---|---|---|---|
| Catalyst 9162 | Up to 25.5W | 25.5W | 802.3af reduces radio capability |
| Catalyst 9163E | Up to 25.5W | Model/feature dependent | Reduced radios and link speed on 802.3af |
| Catalyst 9164 | Up to 25W | Up to 30W | 802.3af mainly for staging |
| Catalyst 9166 | Up to 25.5W | Up to 30.5W | 802.3af mainly for staging |
The important procurement lesson is simple:
Do not ask how much power a “Wi-Fi 6E AP” needs. Ask how much power the exact AP model needs for the features you intend to use.
How to Calculate Catalyst 9200 PoE Requirements
The simplest calculation is:
Required AP PoE Budget = Number of APs × Planning Wattage per AP
Suppose a business plans to install 20 Catalyst 9166 APs using PoE+.
Planning power per AP:
25.5W
Number of APs:
20
Calculation:
20 × 25.5W = 510W
The APs alone therefore require approximately 510W of planned PoE allocation.
But that is not necessarily the final answer.
The same switch may also power:
- IP phones
- Security cameras
- Door controllers
- IoT gateways
- Video endpoints
Those loads must be added.
A more realistic formula is:
Total Required PoE = AP Load + Other PoE Devices + Planning Reserve
How Much Spare PoE Capacity Should You Leave?
There is no universal Cisco rule requiring every switch to retain a specific percentage of unused PoE power.
A practical engineering reserve can still be useful.
For many installations, 10–20% spare capacity can provide a reasonable starting point for:
- Small expansions
- Device replacement
- Changes in AP configuration
- Additional powered endpoints
- Power-demand variation
This percentage is an engineering planning recommendation, not a Cisco requirement.
Where future growth is known, calculate it directly.
If the business plans to add six APs within 18 months, include those six APs in the design rather than assuming a generic reserve will cover them.
Catalyst 9200 PoE Budget Calculation Example
Consider a hypothetical corporate office with:
- 16 Wi-Fi 6E APs
- 8 IP phones
- 4 cameras
Assume:
- AP planning power = 25.5W
- Phone planning power = 7W
- Camera planning power = 15W
Step 1: Calculate AP Power
16 × 25.5W = 408W
Step 2: Calculate Phone Power
8 × 7W = 56W
Step 3: Calculate Camera Power
4 × 15W = 60W
Step 4: Calculate Total Device Demand
408W + 56W + 60W = 524W
Step 5: Add a 15% Example Reserve
524W × 0.15 = 78.6W
Total planned capacity:
524W + 78.6W = 602.6W
The switch configuration should therefore provide at least approximately 603W of usable PoE capacity under these planning assumptions.
A configuration providing only 370W would be insufficient.
A configuration providing 740W could support the calculated normal load.
But the redundancy design still needs to answer:
What happens if one PSU fails?
How Many Wi-Fi 6E APs Can a Catalyst 9200 Power?
There is no single AP number for every Catalyst 9200.
The theoretical AP count can be calculated as:
Available PoE Budget ÷ AP Planning Wattage
Assume an AP requires 25.5W.
370W Available PoE
370 ÷ 25.5 = 14.5
The theoretical limit is therefore 14 APs, before accounting for reserve or other powered devices.
With a 15% example reserve:
370 × 0.85 = 314.5W
314.5 ÷ 25.5 = 12.3
A more conservative planning count would be approximately 12 APs if no other PoE devices use the switch.
740W Available PoE
740 ÷ 25.5 = 29.0
Power theoretically supports approximately 29 AP allocations.
However, a 24-port switch cannot directly connect 29 APs.
Here, physical port count becomes the limiting resource before watts do.
1,440W Available PoE
1,440 ÷ 25.5 = 56.4
Again, a 48-port switch has only 48 access interfaces.
Even though the electrical budget theoretically supports more than 48 AP allocations, the port count becomes the practical ceiling.
This leads to one of the most useful rules in PoE design:
Your AP capacity is limited by whichever resource is exhausted first: ports or watts.
Theoretical vs Practical AP Capacity
Using a 25.5W planning value:
| Available PoE Budget | Theoretical AP Count | Approx. Count With 15% Reserve* |
|---|---|---|
| 240W | 9 | 8 |
| 370W | 14 | 12 |
| 740W | 29 | 24 |
| 1,440W | 56 | 48 or fewer depending on ports |
*Before accounting for other powered devices. The 15% reserve is a planning example, not a fixed Cisco requirement.
Catalyst 9200 PoE Budget by Model
The available PoE capacity varies with switch model and PSU configuration.
| Catalyst Model | Ports | Default/Primary AC PSU | PoE With Primary PSU | Maximum With Supported Additional PSU |
|---|---|---|---|---|
| C9200-24P | 24 PoE+ | 600W | 370W | 740W |
| C9200-48P | 48 PoE+ | 1000W | 740W | 1,440W |
| C9200-48PL | 48 Partial PoE+ | 600W | 370W | 740W |
| C9200-24PXG | 24 mixed 1G/mGig | 600W | 370W | 740W |
| C9200-48PXG | 48 mixed 1G/mGig | 1000W | 740W | 1,440W |
| C9200L-24P | 24 PoE+ | 600W | 370W | 740W |
| C9200L-48P | 48 PoE+ | 1000W | 740W | 1,440W |
| C9200L-48PL | 48 Partial PoE+ | 600W | 370W | 740W |
| C9200L-24PXG | 24 mixed 1G/mGig | 600W | 370W | 740W |
| C9200L-48PXG | 48 mixed 1G/mGig | 1000W | 740W | 1,440W |
| C9200CX-12P | 12 PoE+ | 315W | 240W | Model-specific |
| C9200CX-8P | 8 PoE+ | 315W | 240W | Model-specific |
| C9200CX-8UXG | 8 UPOE/mGig | 315W | 240W | Model-specific |
The maximum number in a data sheet still does not mean every deployment can safely operate at that load under every failure scenario.
Why a 600W PSU Does Not Mean 600W of PoE
The switch itself consumes power.
Therefore:
PSU rating ≠ available PoE budget
A C9200-24P with a 600W power supply does not provide 600W to endpoints.
The switch’s documented available PoE is approximately 370W with that primary AC configuration.
Likewise, a C9200-48P with a 1000W PSU provides approximately 740W of available PoE, not 1000W.
Always use the switch’s published available PoE value when calculating endpoint capacity.
Do not use the number printed on the PSU.
C9200 vs C9200L for Wi-Fi 6E PoE Deployments
From a PoE-planning perspective, C9200 and C9200L share similar full-PoE budget patterns in comparable 24- and 48-port configurations.
The bigger differences for Wi-Fi 6E can be elsewhere.
Multigigabit Connectivity
Many newer APs provide Ethernet interfaces above 1Gbps.
Examples include:
- 2.5G AP connectivity
- 5G AP connectivity
A standard 1G access port can provide enough PoE but still constrain wired throughput.
For higher-performance Wi-Fi 6E designs, PXG multigigabit Catalyst 9200 models may therefore be more appropriate.
The switch must satisfy both:
Electrical requirement
and
Ethernet bandwidth requirement
Uplink Capacity
A high-density wireless deployment can aggregate substantial traffic.
If 20 multigigabit APs connect to one access switch, the uplink architecture deserves the same attention as PoE.
A switch with enough electrical capacity but insufficient upstream bandwidth is still the wrong design.
Hardware Flexibility
C9200 provides modular uplink architecture on applicable models.
C9200L uses fixed uplinks.
This may matter where future distribution-layer upgrades or higher uplink speeds are expected.
For readers comparing appropriate hardware, the logical next step is reviewing Catalyst 9200 PoE+ models
24-Port vs 48-Port Catalyst 9200 for AP Deployments
A 48-port switch is not automatically better for Wi-Fi 6E.
Consider two examples.
Scenario A: 10 APs
10 × 25.5W = 255W
A suitable 24-port switch with 370W available PoE can accommodate the raw AP requirement.
It also leaves 14 physical ports for other endpoints.
Scenario B: 20 APs
20 × 25.5W = 510W
A 370W configuration cannot meet the planned AP demand.
A higher-power configuration is required before phones or cameras are even included.
The correct decision should consider:
- AP count
- Total PoE load
- Spare ports
- Other powered endpoints
- Multigigabit requirements
- Rack topology
- Cable distribution
- Uplink capacity
- Failure domains
- Expansion
There is also a resiliency argument against concentrating every AP on one switch.
If one switch failure disconnects an entire floor’s wireless infrastructure, distributing APs across multiple access switches may provide better operational resilience even where one large switch has enough ports and watts.
What Happens If the Catalyst 9200 Runs Out of PoE Budget?
A Catalyst 9200 cannot allocate more PoE power than its available capacity.
If a newly connected powered device requests power and the remaining budget is insufficient, that port may be denied power.
The access point, phone or camera would then fail to power normally from that interface.
Cisco IOS XE also supports power-management behaviour such as port priority and power policing.
This allows network administrators to decide which powered devices deserve priority where power becomes constrained.
For example, a network might prioritize:
- Wireless access points
- Emergency phones
- Security systems
above lower-priority devices.
But priority mechanisms should not be used as a substitute for adequate design.
A production switch should normally have enough capacity to support its intended load under the required operating conditions.
Can Wi-Fi 6E APs Run on Lower PoE Power?
Some Cisco Wi-Fi 6E APs can power on using lower PoE levels, but the feature set may be restricted.
The behaviour is AP-specific.
Catalyst 9162
With 802.3af power, the AP operates with reduced radio capability and reduced wired link speed compared with its PoE+ configuration.
Catalyst 9163E
Lower 802.3af power can reduce radio configuration and Ethernet capability.
Catalyst 9164
802.3af is intended primarily for configuration staging, with normal radio functionality unavailable.
Catalyst 9166
The same general limitation applies: 802.3af can be used for staging, but not normal full-radio operation.
This creates a key planning rule:
An AP powering on does not prove that the switch is providing enough power for the intended wireless service.
Always verify the AP’s operating mode.
Should You Design Around Maximum or Typical AP Power?
For switch-capacity planning, it is usually safer to work with a defensible maximum or negotiated planning figure for the required AP operating mode.
Typical power draw may be lower.
That is useful for:
- Electricity-cost modelling
- UPS runtime estimation
- Energy-efficiency analysis
But designing purely around typical consumption can create problems if AP demand later increases.
Power consumption may vary with:
- Client load
- Radio utilisation
- USB peripherals
- Enabled features
- Firmware
- Operating mode
Use typical figures for energy modelling.
Use appropriate worst-case or negotiated figures for ensuring that the switch can provide enough power.
Planning APs Plus Phones, Cameras and Other Devices
The switch PoE budget belongs to the entire switch, not only the wireless APs.
Consider this example:
| Powered Device | Quantity | Planning Wattage | Total |
|---|---|---|---|
| Wi-Fi 6E APs | 12 | 25.5W | 306W |
| IP phones | 10 | 7W | 70W |
| Cameras | 6 | 15W | 90W |
| Access-control devices | 2 | 10W | 20W |
| Total | 486W |
The APs alone require only 306W.
A 370W configuration might initially appear sufficient.
Once the other devices are included, demand rises to 486W.
That configuration is now undersized.
This is why the correct question is:
“How much PoE does every connected powered device require?”
not simply:
“How many APs do we have?”
Does Stacking Increase the Catalyst 9200 PoE Budget?
Normal StackWise stacking should not be treated as one unlimited shared PoE pool.
Stacking combines supported switches into a logical system for networking and management, but each chassis still has its own power supplies and connected powered devices.
A practical design should therefore calculate PoE member by member.
For example:
Switch 1
- Available PoE: 740W
- Connected load: 520W
Switch 2
- Available PoE: 740W
- Connected load: 300W
Total stack load is 820W, but that does not mean the spare capacity on Switch 2 automatically supplies APs physically connected to Switch 1.
This matters when distributing high-power access points across stack members.
Avoid placing almost every AP on one member while another member carries very little PoE load.
Planning for Power-Supply Redundancy
There are two different questions:
Do I have enough PoE power during normal operation?
and
Do I still have enough PoE power after a PSU failure?
They are not the same.
Suppose a 48-port C9200 configuration provides up to 1,440W with two supported power supplies.
The planned endpoint load is:
1,000W
Normal operation:
1,440W available
1,000W required
The design appears sufficient.
Now assume one PSU fails and available PoE capacity drops to approximately the single-PSU level:
740W
Failure state:
740W available
1,000W required
The system is now oversubscribed.
This is not full PoE redundancy.
If every AP must remain operational after a PSU failure, the normal production load should be designed around the capacity available in the required failure state.
For this example, that would mean targeting 740W or less if the design expects one PSU to fail without sacrificing any planned PoE load.
Wi-Fi 6E Deployment Planning Scenarios
Small Office
Assume:
- 6 Wi-Fi 6E APs
- 10 IP phones
- Limited growth
AP load:
6 × 25.5W = 153W
If phones average 7W planning allocation:
10 × 7W = 70W
Total:
223W
A 370W PoE budget could provide reasonable headroom under these assumptions.
The next decision is whether the APs require multigigabit access.
Medium Office
Assume:
- 18 APs
- 12 phones
- 6 cameras
AP load alone:
18 × 25.5W = 459W
The deployment has already exceeded a 370W budget before phones and cameras are counted.
A higher-PoE configuration is required.
Hotel or Hospitality Environment
Hotels often have relatively dense AP placement across:
- Guest rooms
- Corridors
- Meeting rooms
- Restaurants
- Public areas
Rather than putting every AP on one large access switch, distribute wireless infrastructure according to floor layout, cabling paths and failure domains.
A switch outage should not unnecessarily remove wireless service from a large part of the property.
School or University
Wireless demand can be high in:
- Classrooms
- Lecture halls
- Libraries
- Laboratories
- Shared spaces
Calculate both power and bandwidth.
A high-density Wi-Fi 6E deployment may justify multigigabit access even if standard PoE+ provides sufficient power.
Large Enterprise Campus
PoE planning should happen at the access-closet level.
For each closet, determine:
- Number of APs
- AP model
- AP power mode
- Phones and cameras
- Switch distribution
- PSU redundancy
- Multigigabit ports
- Uplink requirements
- Future expansion
This produces a much more resilient design than trying to maximize the number of APs on every switch.
Catalyst 9200 PoE Planning Decision Matrix
| Requirement | What to Check | Why It Matters |
|---|---|---|
| 4–8 APs | AP wattage + other devices | Usually modest power requirement |
| 12–14 APs | 370W budget threshold | Power can become limiting |
| 15–24 APs | Higher PoE capacity | 370W may be insufficient |
| Wi-Fi 6E APs | Exact AP power mode | Lower power may restrict features |
| Multigigabit APs | PXG access ports | Sufficient power does not guarantee enough bandwidth |
| APs + phones | Combined PoE load | Both draw from same switch budget |
| APs + cameras | Combined watts | Video endpoints can add substantial load |
| Two PSUs | Failure-state capacity | Additional PSU may increase capacity but not full redundancy at peak load |
| Future AP expansion | Spare ports + spare watts | Both resources are needed |
| 24 vs 48 ports | Watts + topology | Port count alone should not drive selection |
| Stacked deployment | Load per member | PoE should be balanced across chassis |
| Critical wireless | PSU/switch failure plan | Wireless availability matters during failures |
Common Catalyst 9200 PoE Planning Mistakes
Counting Ports Instead of Watts
A 48-port PoE switch does not mean that 48 maximum-power devices can always operate simultaneously.
Calculate the wattage.
Using Typical AP Power Instead of Planning Power
Typical draw may underestimate what the switch must be able to allocate.
Use an appropriate planning figure.
Ignoring Other PoE Devices
Phones, cameras and access-control systems use the same switch PoE budget.
Ignoring PSU Configuration
The exact power supply changes available PoE capacity.
Do not compare switches solely by chassis model.
Forgetting Redundancy Requirements
A switch may have enough power with both PSUs running but become undersized after one supply fails.
Buying Based Only on “PoE+”
PoE+ describes the port-level standard.
It does not describe the total PoE budget.
Not Planning for Expansion
Future APs require both:
- Spare Ethernet ports
- Spare electrical power
Assuming Every Wi-Fi 6E AP Uses 25.5W
AP models differ.
Some require more power for additional functionality.
Ignoring Multigigabit Requirements
A 1G port might deliver sufficient PoE while limiting the AP’s wired throughput.
Using Third-Party PoE Tables Without Verifying the Exact Hardware
Switch revisions, PSU combinations and AP specifications matter.
Use the exact switch and AP models when planning.
Catalyst 9200 Wi-Fi 6E PoE Planning Checklist
Before purchasing, confirm:
- Exact C9200/C9200L/C9200CX SKU
- Number of Ethernet ports
- Number of PoE-capable ports
- Supported PoE standard
- Maximum per-port output
- Published available PoE budget
- Primary PSU model
- Secondary PSU requirement
- Number of APs
- Exact AP model
- AP planning wattage
- AP PoE standard
- AP reduced-power behaviour
- Number of IP phones
- Number of cameras
- Number of access-control devices
- Other PoE endpoints
- Total calculated power load
- Planning reserve
- Future AP additions
- Required PSU-failure capacity
- Stack design
- AP distribution across stack members
- Multigigabit access requirement
- Uplink bandwidth
- Optics/transceivers
- Network licensing
- Support requirements
This list can be given directly to engineering and procurement teams before requesting pricing.
Choosing Catalyst 9200 PoE+ Models in UAE & Saudi Arabia
A request such as:
“Please quote a 48-port Cisco Catalyst 9200 PoE switch.”
is not detailed enough for a Wi-Fi 6E project.
For UAE, Saudi Arabia and wider GCC deployments, provide the supplier with:
- Exact switch family
- 24 or 48 ports
- Number of APs
- Exact AP model
- Required AP operating mode
- Total AP power
- Number of phones/cameras
- Total calculated PoE demand
- Required reserve
- Primary PSU
- Secondary PSU
- Redundancy requirement
- 1G or multigigabit access
- Uplink speed
- Stacking
- Network modules
- Optics
- License requirements
- Quantity
- Support needs
Buyers comparing Catalyst 9200 PoE+ models can review the relevant hardware on:
NETSEG can then help match the switch SKU, PSU arrangement, PoE capacity, mGig access requirements, uplinks and accessories to the actual wireless design.
A configuration-specific quotation is more useful than purchasing by port count because a Wi-Fi 6E deployment needs both sufficient electrical capacity and sufficient network bandwidth.
Frequently Asked Questions
What is the PoE budget of a Cisco Catalyst 9200?
The PoE budget varies by exact Catalyst 9200 model and installed power supplies. Relevant 24-port full-PoE C9200/C9200L models provide approximately 370W with one 600W AC PSU, while relevant 48-port models provide approximately 740W with one 1000W PSU. Supported second PSUs can increase available capacity.
How many access points can a Catalyst 9200 power?
Divide the documented available PoE budget by the planning wattage of each AP, then check ports, other PoE devices and reserve capacity. With 25.5W APs, 370W theoretically supports 14 AP allocations before reserve. A production design may support fewer after other loads and spare capacity are included.
Can Catalyst 9200 power Wi-Fi 6E access points?
Yes. PoE+ Catalyst 9200 models can power compatible Wi-Fi 6E access points such as Cisco Catalyst 9160-series APs. The switch must have enough total PoE capacity, and the access port should also support the Ethernet speed required by the AP.
Is PoE+ enough for Wi-Fi 6E?
PoE+ is sufficient for normal radio operation on several Cisco Wi-Fi 6E APs, but not necessarily every optional feature. Some models require higher-power input for functions such as USB, while 802.3af may force restricted or staging-only operation.
What happens if a Catalyst 9200 exceeds its PoE budget?
A port can be denied power when there is insufficient remaining PoE capacity. Cisco IOS XE also supports power-management and port-priority mechanisms. A production deployment should be designed so normal operation does not depend on devices competing for insufficient power.
Does a 48-port Catalyst 9200 have more PoE than a 24-port model?
Comparable full-PoE 48-port models generally have a larger default PoE budget than comparable 24-port models. Relevant 48-port configurations provide about 740W with one 1000W PSU, while relevant 24-port models provide about 370W with one 600W PSU.
Does adding a second PSU increase the Catalyst 9200 PoE budget?
Yes, on supported models a second compatible PSU can increase the available PoE budget. However, if the deployment uses all of that additional capacity, one PSU failure may leave insufficient power for the full endpoint load. Redundancy must therefore be calculated separately.
Can Wi-Fi 6E APs run with lower PoE power?
Some can, but the feature impact is model-specific. Catalyst 9162 and 9163E can operate with reduced capability on 802.3af, while Catalyst 9164 and 9166 use 802.3af primarily for staging with radios unavailable.
How do I calculate the required PoE budget?
Multiply each powered-device quantity by its planning wattage, total all device categories, then add an appropriate reserve. Compare that result with the switch’s documented available PoE capacity and repeat the calculation for any required PSU-failure condition.
Does StackWise combine PoE budgets?
Do not treat normal StackWise operation as one unrestricted shared PoE pool. Calculate the available PoE and connected load for each physical stack member. Distribute high-power APs sensibly across switches so one member is not overloaded while another has unused capacity.
How much spare PoE capacity should I leave?
There is no universal Cisco-required percentage. A 10–20% engineering reserve can be a useful starting point for some networks, but deployments expecting significant growth or requiring high availability may need more. Known future APs should be calculated directly.
Should PoE planning use typical or maximum AP power?
Use an appropriate maximum or negotiated planning figure when determining switch capacity. Typical power is useful for energy estimates, but relying on it alone can underestimate the amount the switch must be able to allocate during higher-demand operating conditions.