Study guide

2.2 Power over Ethernet (PoE, PoE+, PoE++) Standards and Budgeting

HPE Aruba Networking Certified Associate - Campus Access HPE6-A85

Track your progress as you read

Finished sections get a check mark.

1 Introduction: HPE6-A85 Exam Overview

HPE6-A85 Exam Facts and Current Blueprint

2 Chapter 1: Network Stack Fundamentals

1.1 OSI Reference Model and Encapsulation 1.2 TCP/IP Protocol Suite and IP Headers 1.3 Layer 2 Operation, ARP, and 802.1Q Tagging

3 Chapter 2: Physical Connectivity and Host Addressing

2.1 Ethernet Media and Transceiver Standards 2.2 Power over Ethernet (PoE, PoE+, PoE++) Standards and Budgeting 2.3 LLDP, LLDP-MED, and Voice VLAN Configuration 2.4 Host IP Addressing and DHCP Relay Operations

4 Chapter 3: Network Resiliency and Virtualization

3.1 Virtual Switching Framework (VSF) Architecture and Topologies 3.2 VSF Split Detection, Failover, and Auto-Stacking 3.3 Virtual Switching Extension (VSX) Architecture and Operations 3.4 High-Availability Gateways: VRRP and VSX Active-Gateway

5 Chapter 4: AOS-CX Architecture and Switch Operation

4.1 AOS-CX Hardware Portfolio and State Database Architecture 4.2 Network Analytics Engine (NAE) and Automated Telemetry 4.3 AOS-CX Interface Configuration and Port Control 4.4 Link Aggregation (LAG) and LACP Configuration

6 Chapter 5: Layer 2 Protocols and Spanning Tree

5.1 AOS-CX VLAN Configuration and Native VLAN Handling 5.2 Spanning Tree Protocols: STP, RSTP, and MSTP 5.3 Spanning Tree Protections and Loop Prevention 5.4 MAC Address Table Learning, Aging, and Forwarding

7 Chapter 6: Wireless Fundamentals, Standards, and RF

6.1 IEEE 802.11 Standards and Wi-Fi Generations 6.2 RF Fundamentals, Signal Propagation, and Channel Design 6.3 Aruba Access Point Hardware Portfolio and Suffix Conventions 6.4 WLAN Topologies, BSSID/ESSID, and Roaming Standards

8 Chapter 7: Aruba Wireless Architecture and Management

7.1 AOS 10 Architecture and Aruba Central Integration 7.2 Wireless Forwarding Modes: Bridge vs Tunnel Mode 7.3 Automated RF and Client Optimization: AirMatch and ClientMatch 7.4 Secure Wireless Access: WPA3, SAE, and MPSK Implementation

9 Chapter 8: IP Routing Fundamentals and OSPF

8.1 IP Routing Principles and Packet Forwarding 8.2 OSPFv2 Protocol Mechanics and Adjacency Formation 8.3 OSPF Designated Routers and Multi-Area Deployments 8.4 ECMP, Static Routing, and VRF Isolation

10 Chapter 9: Campus Network Security and Segmentation

9.1 DHCP Snooping and Dynamic ARP Inspection 9.2 Port Security and MAC Address Limiting 9.3 ClearPass Policy Management and RADIUS Change of Authorization 9.4 Dynamic Segmentation, User-Based Tunneling, and Policy Enforcement

11 Chapter 10: Authentication, Authorization, and Accounting

10.1 The AAA Framework and Architecture 10.2 802.1X Authentication and EAP Methods 10.3 MAC Authentication and Captive Portal Onboarding 10.4 Administrative Access Control: RADIUS vs TACACS+

12 Chapter 11: Network Management and Telemetry

11.1 Aruba Central Cloud Architecture and Group Configuration 11.2 Zero-Touch Provisioning (ZTP) and Aruba Activate 11.3 AI Insights and Aruba User Experience Insight (UXI) 11.4 Network Telemetry, Streaming APIs, and SNMP/Syslog

13 Chapter 12: Troubleshooting the Solution

12.1 Structured Troubleshooting Methodologies and Scope Isolation 12.2 AOS-CX Layer 2 and Interface Diagnostic Commands 12.3 Layer 3, IP Services, and End-to-End Diagnostics 12.4 Physical-Layer Troubleshooting 12.5 Troubleshooting Wireless Clients and Network Access

14 Chapter 13: Optimizing Performance: QoS, Baselines, and Comparisons

13.1 Quality of Service (QoS) Classification and Marking 13.2 Queuing Algorithms and Congestion Management 13.3 Traffic Policing, Shaping, and Broadcast Rate Limiting 13.4 Establishing a Performance Baseline 13.5 Comparing Results to the Baseline

15 Chapter 14: Plan the Solution

14.1 Analyzing the Current Environment 14.2 Interpreting an Architect's High-Level Design 14.3 Creating a Low-Level Design 14.4 Preparing for Implementation

16 Chapter 15: Validate and Operate the Solution

15.1 Validating the Solution 15.2 Performing Firmware Updates 15.3 Making Basic Ongoing Configuration Changes 15.4 Maintaining Network Documentation

2.2 Power over Ethernet (PoE, PoE+, PoE++) Standards and Budgeting

Key Takeaways Explain This Topic AI

IEEE PoE standards span 802.3af (15.4W Type 1), 802.3at (30W Type 2 PoE+), and 802.3bt (60W Type 3 and 90W Type 4 PoE++), powering access points, IP cameras, and smart building infrastructure.

PoE hardware classification uses physical-layer resistance and voltage pulses across 2 or 4 twisted pairs, while LLDP and LLDP-MED provide dynamic software-based power negotiation down to milliwatt precision.

AOS-CX allocates PoE per interface with power-over-ethernet allocate-by {usage | class} ; usage is the default, and LLDP-negotiated values replace the measured or class value when the PD negotiates.

power-over-ethernet priority {critical | high | low} (default low) decides which ports keep power during oversubscription; among equal priorities, lower-numbered ports win.

Always-on PoE (enabled by default per module) keeps power flowing through a soft reboot, while quick PoE (disabled by default) restores power quickly after a cold boot.

Last updated: October 2026

Power over Ethernet (PoE) revolutionizes campus network infrastructure by delivering low-voltage direct current (DC) electrical power simultaneously with data over standard twisted-pair Ethernet cabling. By eliminating the necessity for dedicated AC electrical outlets and external power bricks at every endpoint location, PoE dramatically lowers deployment expenses, simplifies installation logistics, and enables centralized power backup via uninterruptible power supplies (UPS) located in telecommunications rooms.

In a PoE deployment, two functional device roles exist:

Power Sourcing Equipment (PSE): The device that injects power onto the network cable, typically a PoE-capable access layer switch or midspan power injector.

Powered Device (PD): The client endpoint that draws power from the Ethernet cable, such as an IP telephone, wireless access point, pan-tilt-zoom (PTZ) IP surveillance camera, smart lighting fixture, or biometric door lock.

Evolution of IEEE Power over Ethernet Standards

The Institute of Electrical and Electronics Engineers (IEEE) has formalized four generations of PoE standards to accommodate ever-increasing power requirements of enterprise edge devices:

IEEE 802.3af (PoE / Type 1)

Ratified in 2003, IEEE 802.3af introduced the initial standardized method to deliver electrical power over twisted-pair copper. It supplies up to 15.4 Watts of DC power at the switch port (PSE), delivering a guaranteed minimum of 12.95 Watts to the powered device at the end of a 100-meter channel (accounting for line resistance and heat dissipation). Type 1 utilizes two pairs of a four-pair Category 5 cable and supports hardware Classes 0 through 3. Typical endpoints include basic single-line VoIP phones, stationary IP cameras, and early single-radio 802.11b/g APs.

IEEE 802.3at (PoE+ / Type 2)

Ratified in 2009, IEEE 802.3at nearly doubled power output to support dual-radio 802.11n/802.11ac Wi-Fi access points, video IP phones, and motorized cameras. PoE+ delivers up to 30.0 Watts at the PSE port, guaranteeing 25.5 Watts at the powered device over a 100-meter run. It operates over two pairs of Category 5e or higher cable, introduces hardware Class 4 , and is completely backward-compatible with 802.3af devices.

IEEE 802.3bt (PoE++ / 4-Pair PoE / 4PPoE)

Ratified in 2018, IEEE 802.3bt introduced the ability to deliver electrical power across all four twisted pairs simultaneously. Energizing all four pairs cuts cable heating and power transmission losses in half compared to delivering equivalent power over two pairs. The standard defines two distinct operational types:

Type 3 (High-Power PoE): Delivers up to 60 Watts at the PSE port, guaranteeing 51 Watts at the PD over Cat5e or higher cabling. It introduces Classes 5 and 6 and powers high-end tri-radio access points, video conferencing touchscreens, and building automation controllers. For example, HPE QuickSpecs list the Wi-Fi 7 AP-735 as unrestricted on 802.3bt Class 5 power and restricted (USB disabled) on 802.3at Class 4.

Type 4 (Ultra-High-Power PoE): Delivers up to 90 Watts (with theoretical maximums approaching 100W) at the PSE port, ensuring 71.3 Watts at the PD over Cat6A cabling. It introduces Classes 7 and 8 and powers motorized PTZ cameras with integrated heaters and blowers, thin client workstations, digital signage displays, and smart LED lighting grids. Campus access points normally fit within Type 3 (Class 5 or 6) budgets.

Comprehensive IEEE PoE Standards Comparison

Feature / Specification IEEE 802.3af (PoE) IEEE 802.3at (PoE+) IEEE 802.3bt (PoE++ Type 3) IEEE 802.3bt (PoE++ Type 4)

  • IEEE Type Designation Type 1 Type 2 Type 3 Type 4
  • Maximum Power at PSE 15.4 W 30.0 W 60.0 W 90.0 W
  • Minimum Power at PD 12.95 W 25.5 W 51.0 W 71.3 W
  • Nominal Voltage Range 44.0 - 57.0 V DC 50.0 - 57.0 V DC 50.0 - 57.0 V DC 52.0 - 57.0 V DC
  • Twisted Pairs Energized 2 pairs (Alt-A or Alt-B) 2 pairs (Alt-A or Alt-B) 4 pairs 4 pairs
  • Supported Cable Grade Cat3 / Cat5 Cat5e / Cat6 Cat5e / Cat6 Cat6A recommended
  • Supported Hardware Classes Classes 0, 1, 2, 3 Class 4 Classes 5, 6 Classes 7, 8

Target Campus Endpoints Basic VoIP, static cameras Dual-radio APs, video phones Tri-radio APs, PTZ cameras Heated PTZ cameras, digital signage, thin clients

PoE Hardware Detection and Classification Mechanics

To prevent damaging non-PoE network interface cards (such as standard laptop LAN ports), Power Sourcing Equipment never applies high voltage directly upon physical cable insertion. Instead, a strict, standardized four-stage handshake occurs:

Stage 1: Detection (Signature Resistance Probe)

The PSE emits a low probing voltage pulse between 2.8 Volts and 10 Volts DC onto the cable and measures the returned electrical impedance. A valid PoE-compliant Powered Device presents an active internal signature resistance of exactly 25 kΩ (23.75 kΩ to 26.25 kΩ) . If the switch detects a short circuit, an open circuit, or standard non-PoE termination (typically 75 Ω), the PSE halts power application and operates the port purely as a standard data interface.

Stage 2: Hardware Classification

Once a valid 25 kΩ signature is verified, the PSE ramps probing voltage to between 14.5 Volts and 20.5 Volts DC to determine the device's electrical class. The PD responds by drawing a specific constant current, signaling its maximum required wattage:

  • Hardware Class Classification Current PSE Output Power Guaranteed PD Power Applicable IEEE Standard
  • Class 0 0 - 4 mA 15.4 W 12.95 W 802.3af (Default unclassified)
  • Class 1 9 - 12 mA 4.0 W 3.84 W 802.3af (Low power)
  • Class 2 17 - 20 mA 7.0 W 6.49 W 802.3af (Medium power)
  • Class 3 26 - 30 mA 15.4 W 12.95 W 802.3af (Full Type 1)
  • Class 4 36 - 44 mA 30.0 W 25.5 W 802.3at (PoE+ Type 2)
  • Class 5 Multi-event pulses 45.0 W 40.0 W 802.3bt (Type 3)
  • Class 6 Multi-event pulses 60.0 W 51.0 W 802.3bt (Type 3)
  • Class 7 Multi-event pulses 75.0 W 62.0 W 802.3bt (Type 4)
  • Class 8 Multi-event pulses 90.0 W 71.3 W 802.3bt (Type 4)

Under 802.3bt, the PSE transmits multiple sequential classification pulses ("multi-event classification") to signal to the PD that the PSE is 4-pair capable and to confirm whether 60W or 90W power levels are authorized.

Stage 3: Power-Up

Upon verifying class capabilities and confirming sufficient available power in the switch power budget, the PSE smoothly ramps voltage up to the full operating level ( 48V to 54V DC ) within a few milliseconds.

Stage 4: Dynamic Software Negotiation via LLDP / LLDP-MED

Hardware classification is coarse-grained. For example, a device requesting Class 4 reserves 30W from the switch budget, even if it actually consumes only 8W under typical operation. Once the PD boots its network stack, it exchanges Link Layer Discovery Protocol (LLDP) and LLDP-MED Data Link Layer frames with the switch. Through the Power-via-MDI TLV , the PD communicates its precise power requirement down to 0.1 Watt increments , allowing the AOS-CX switch to dynamically adjust its reserved power budget.

AOS-CX Switch Power Budgeting and Allocation Policies

Access layer switches operate with finite internal power supplies. In enterprise environments populated with dozens of high-draw access points and video surveillance terminals, unmanaged power consumption can exceed available switch capacity.

Power Supply Configurations and Redundancy

AOS-CX switches feature flexible power supply architectures:

Fixed Internal PSUs: Found in entry-level access switches (such as the CX 6100 and CX 6200F), providing fixed PoE budgets (e.g., 370W or 740W).

Modular Hot-Swappable Dual PSUs: Found in modular enterprise switches (such as the CX 6300M and CX 6400). Installing dual power supply units allows administrators to configure:

Power Redundancy (N+1): If one PSU fails or an AC feed drops, the surviving PSU maintains power delivery without dropping connected devices.

Power Pooling / Aggregate Mode: Combines the output of the installed PSUs into one power pool, maximizing total available PoE wattage for high-density 802.3bt deployments. The exact budget depends on the model and PSU combination listed in the HPE PoE Planning Guide.

Power Allocation Methods: power-over-ethernet allocate-by

AOS-CX configures the allocation method per interface with power-over-ethernet allocate-by {usage | class} (AOS-CX 10.14 CLI Guide, 6300/6400):

allocate-by usage (the AOS-CX default):

Without LLDP negotiation, the allocated value tracks the port's actual instantaneous draw, and power is reserved based on actual consumption.

When the PD negotiates power through LLDP, the LLDP-negotiated value becomes the allocated power.

Advantage: Maximizes port density and avoids reserving watts that devices never use.

Disadvantage: Requires budget monitoring, because several devices can increase their draw at the same time.

allocate-by class :

Without LLDP negotiation, the switch reserves power based on the PD's requested class (for example, 30 W for a Class 4 device). With LLDP negotiation, the negotiated value is used.

Advantage: Predictable reservations for devices that do not negotiate.

Disadvantage: A switch full of Class 4 devices that actually draw 6 W can report an exhausted budget.

Capping a port: power-over-ethernet assigned-class {3 | 4 | 6} limits the maximum power a port will deliver, which is useful for non-compliant or legacy devices. (ArubaOS-Switch used poe-allocate-by value ; AOS-CX has no "value" method.)

Port Prioritization and Power Shedding

When a switch power supply suffers an AC feed drop, or total instantaneous power demand exceeds available budget, the switch initiates power shedding to prevent a catastrophic chassis brownout. Power shedding disconnects power from ports based on the level set with power-over-ethernet priority {critical | high | low} :

critical : Highest priority tier. Reserved for mission-critical infrastructure such as emergency VoIP phones, medical alert terminals, and core wireless APs. Ports assigned critical priority are the absolute last to lose power.

high : Medium priority tier. Assigned to standard enterprise wireless APs and physical access controllers.

low (Default): Lowest priority tier. Assigned to non-critical desktop peripherals, digital signage, and test devices. Ports assigned low priority are shut down first.

Tie-Breaking Rule: Within the same priority level, lower-numbered ports have higher precedence, so higher-numbered ports lose power first (for example, port 1/1/48 before port 1/1/1).

Always-On PoE and Quick PoE

Traditional switches disrupt PoE output during operating system reboots, forcing all connected APs, security cameras, and VoIP phones to cycle their power and spend several minutes rebooting. AOS-CX provides two power-continuity features (AOS-CX 10.14 CLI Guide):

Always-on PoE ( power-over-ethernet always-on <MODULE-ID> , global context): keeps delivering power across a soft reboot to ports that were already delivering power. It is enabled by default at the switch or slot level. It cannot help if the switch itself loses power.

Quick PoE ( power-over-ethernet quick-poe <MODULE-ID> ): after a cold boot , applies power to connected PDs as soon as possible instead of waiting for the full operating system boot. It is disabled by default , and all ports on the subsystem must have PoE enabled before you turn it on.

  • AOS-CX CLI Configuration and Diagnostics
  • Configuring PoE Allocation and Priority

To configure usage-based allocation globally and assign port-specific priorities, enter the following commands: switch# configure terminal

  • switch(config)# power-over-ethernet always-on 1/1
  • switch(config)# power-over-ethernet quick-poe 1/1
  • switch(config)# interface 1/1/1
  • switch(config-if)# description "Campus Security Emergency Phone"
  • switch(config-if)# power-over-ethernet priority critical
  • switch(config)# interface 1/1/2
  • switch(config-if)# description "Wi-Fi 6E Access Point"
  • switch(config-if)# power-over-ethernet allocate-by usage
  • switch(config-if)# power-over-ethernet priority high
  • Verifying Global PoE Status

To view overall power capacity, allocated wattage, and real-time power draw, execute show power-over-ethernet . The output below is abbreviated for study purposes; field names vary by release: switch# show power-over-ethernet

  • Total Available Power : 740.0 W
  • Total Allocated Power : 312.4 W
  • Total Remaining Power : 427.6 W
  • Total Real-Time Power : 186.2 W
  • Power Allocation Method : usage
  • Internal Power Supply : OK
  • Redundant Power Supply : OK
  • Inspecting Per-Port Power Parameters

To inspect detailed electrical parameters, hardware class, and LLDP-negotiated power on a specific port, execute show power-over-ethernet <PORT> : switch# show power-over-ethernet 1/1/2

  • Port : 1/1/2
  • Status : Delivering
  • Power Priority : High
  • Admin Status : Enabled
  • Assigned Class : Class 6 (Type 3 802.3bt)
  • Allocated Power : 45.0 W
  • Instantaneous Power : 22.8 W
  • Average Power : 21.4 W
  • Peak Power : 34.6 W
  • Voltage : 54.1 V
  • Current : 421 mA
  • Always-On (module) : Enabled

Maximum Power Delivered at Switch Port by IEEE Standard

Loading diagram... PoE Hardware Detection and Negotiation Lifecycle