Skip to main content

Power Management

Monitoring and managing power consumption for your EDC.

⏱️ Time Required: 5 minutes (setup) | 2 minutes (daily monitoring)

Overview​

The EnGenius PDU provides comprehensive power monitoring and management capabilities for your EDC. Regular monitoring helps ensure efficient operation and prevents power-related issues.

Key capabilities:

  • Real-time power consumption monitoring
  • Per-outlet power measurement
  • Remote outlet control
  • Power threshold alerts
  • Historical power usage data

Accessing PDU Management​

Via Web Interface​

To access PDU:

  1. Navigate to PDU IP address in web browser

    • IP address provided in EnGenius documentation
    • See Initial Access for login details

  2. Log in with credentials

    • Username and password from EnGenius documentation
    • Change default password if not already changed

  3. PDU dashboard loads

    • Real-time power consumption
    • Outlet status
    • System information

[IMAGE: PDU web interface dashboard showing power consumption and outlet status]

Via LCD Display​

Physical PDU display on rear panel:

The PDU has an integrated LCD display showing:

  • Input voltage (V)
  • Current draw (A)
  • Power consumption (W)
  • Active power (W)
  • Temperature

Reading the display:

  • Display cycles through metrics automatically
  • Shows real-time values
  • Useful for quick checks without network access

Monitoring Power Consumption​

Real-Time Monitoring​

Check power consumption regularly:

Via web interface:

  • Dashboard shows total power consumption
  • Per-outlet power consumption
  • Current, voltage, and wattage
  • Power factor

Via LCD display:

  • Quick check of total consumption
  • Visible without network access
  • Located on PDU at rear panel

Normal Power Consumption Ranges​

Expected power draw by edition:

📦 NUC Edition:

  • Idle: 150-250W
  • Light load: 200-350W
  • Moderate load: 300-500W
  • Heavy load: 400-600W
  • Maximum: ~600W

🔶 HR01-2 Edition:

  • Idle: 250-400W
  • Light load: 350-550W
  • Moderate load: 500-700W
  • Heavy load: 600-800W
  • Maximum: ~800W

🔷 HR01-4 Edition:

  • Idle: 400-600W
  • Light load: 600-800W
  • Moderate load: 800-1000W
  • Heavy load: 1000-1200W
  • Maximum: ~1200W (estimated)

Note: Actual consumption depends on:

  • Number of running VMs
  • VM workload intensity
  • Connected PoE devices
  • Optional accessories
  • Ambient temperature (affects cooling load)

Per-Outlet Monitoring​

Viewing Outlet Power Consumption​

Individual outlet power tracking:

  1. Access PDU web interface
  2. Navigate to outlet management section
  3. View per-outlet consumption
    • Each outlet shows power draw
    • Identify high-consumption devices
    • Monitor trends over time

Typical outlet assignments:

  • Outlets 1-3: Compute nodes (primary consumers)
  • Outlet 4: Switch
  • Outlet 5: Additional compute or accessories
  • Outlet 6: Reserve or accessories

Use outlet monitoring to:

  • Identify power-hungry devices
  • Balance load across outlets
  • Detect anomalies (unexpected high draw)
  • Plan capacity for additional devices

Power Threshold Alerts​

Setting Up Alerts​

Configure alerts for power thresholds:

  1. Access PDU settings

    • Navigate to alert configuration
    • Set threshold values

  2. Configure warning threshold

    • Recommended: 80% of rated capacity
    • Example: 960W for 1200W PDU (12A × 120V)
    • Gives warning before critical

  3. Configure critical threshold

    • Recommended: 90% of rated capacity
    • Example: 1080W for 1200W PDU
    • Immediate attention required

  4. Set notification method

    • Email alerts (if PDU has network connectivity)
    • SNMP traps (for monitoring systems)
    • LCD display warning

[IMAGE: PDU alert configuration screen]

Responding to Power Alerts​

If you receive a power alert:

Warning threshold (80%):

  1. Check which devices are drawing excessive power
  2. Review VM workloads (reduce if possible)
  3. Disconnect non-essential accessories
  4. Monitor temperature (high temps increase fan power)
  5. Consider load balancing or capacity upgrade

Critical threshold (90%):

  1. Immediately identify high-power devices
  2. Shut down non-critical VMs
  3. Disconnect optional accessories
  4. Verify PDU rating matches input power
  5. Contact support if issue persists

PDU overload protection:

  • PDU will automatically protect against overload
  • May shut down outlets to prevent damage
  • Follow troubleshooting below if this occurs

Outlet Control​

Manual Outlet Control​

Turn outlets on/off remotely:

  1. Access PDU web interface
  2. Navigate to outlet control
  3. Select outlet to control
  4. Click on/off

Use cases for outlet control:

  • Remote reboot of compute nodes
  • Power cycling stuck devices
  • Controlled shutdown sequence
  • Emergency power off

[IMAGE: PDU outlet control interface]

Outlet Groups​

Group outlets for bulk control:

Create outlet groups:

  1. Access PDU group configuration

  2. Create logical groups:

    • "Compute Nodes" (outlets for compute)
    • "Networking" (switch, optional equipment)
    • "Accessories" (optional devices)

  3. Control entire group with one action

    • Turn all compute nodes off/on together
    • Simplified management
    • Coordinated power sequencing

Scheduled Power Control​

Schedule outlet power cycles:

Use cases:

  • Automated weekly reboots
  • Scheduled maintenance windows
  • Power conservation schedules
  • Automated testing

Setup:

  1. Access PDU scheduling feature
  2. Create schedule
  3. Assign outlets to schedule
  4. Enable and monitor

Note: Use scheduled power control carefully. Improper scheduling can cause unexpected shutdowns.

Off-Grid and Battery Operation​

Monitoring Battery Runtime​

When running on battery backup or off-grid power:

Key metrics to monitor:

  • Battery state of charge (SOC)
  • Estimated runtime remaining
  • Power draw from battery
  • Battery voltage

Maximize battery runtime:

  1. Shut down non-essential VMs
  2. Reduce workload intensity
  3. Use Eco cooling profile (see Cooling Management)
  4. Disconnect optional accessories
  5. Monitor consumption closely

Calculating Runtime​

Estimated runtime calculation:

Formula:

Runtime (hours) = Battery Capacity (Wh) / Power Draw (W) × Efficiency Factor

Example with HiveRadar Delta 3 Pro (4096Wh):

  • NUC Edition at 300W: ~12 hours (accounting for 90% efficiency)
  • HR01-2 Edition at 500W: ~7 hours
  • HR01-2 Edition at 800W (heavy load): ~4 hours

Factors affecting runtime:

  • Battery age and condition
  • Ambient temperature
  • Inverter efficiency
  • Load variance over time

Battery Low Procedures​

When battery reaches low threshold:

Recommended actions:

At 30% remaining:

  1. Save all work in VMs
  2. Reduce workload if possible
  3. Prepare for shutdown if needed
  4. Alert users of low battery

At 20% remaining:

  1. Begin graceful VM shutdown
  2. Save data and close applications
  3. Notify all users immediately
  4. Prepare for system shutdown

At 10% remaining:

  1. Shut down all VMs immediately
  2. Shut down HCI cluster gracefully
  3. Shut down compute nodes
  4. Leave monitoring and networking up until last

Automated shutdown:

  • IoT device can coordinate automated shutdown
  • See IoT Monitoring
  • Configure thresholds and actions

Historical Power Data​

Use historical data to:

  • Identify consumption patterns
  • Plan capacity needs
  • Detect anomalies
  • Optimize workloads

Access historical data:

  1. PDU web interface
  2. Navigate to statistics or history section
  3. View graphs and reports
  4. Export data if needed

What to look for:

  • Gradual increase in consumption (capacity planning)
  • Sudden spikes (investigate cause)
  • Patterns by time of day (workload optimization)
  • Seasonal variations (temperature effects)

Power Efficiency Tips​

Reduce power consumption:

  1. Optimize VM allocation

    • Don't over-allocate CPU/memory
    • Shut down unused VMs
    • Consolidate workloads where possible

  2. Use appropriate cooling profiles

    • Eco mode for low temps
    • Balanced for normal operation
    • Turbo only when needed
    • See Cooling Management

  3. Monitor idle consumption

    • Identify devices drawing power when idle
    • Power off when not in use
    • Use PDU scheduling for automation

  4. Maintain good airflow

    • Clear obstructions from vents
    • Adequate clearance (6+ inches rear)
    • Cooler operation = less fan power

  5. Update firmware regularly

    • Energy efficiency improvements
    • Better power management
    • Optimized performance

Troubleshooting​

PDU showing overload alarm

Problem: PDU alarm indicating overload condition

Actions:

  1. Check total power consumption on PDU display/web interface
  2. Identify which outlets drawing excessive power
  3. Disconnect non-essential devices immediately
  4. Verify input voltage is correct (120V or 240V as rated)
  5. Check for short circuits or faulty devices
  6. Reduce load below 80% of PDU rating

Prevention:

  • Monitor power consumption regularly
  • Set up threshold alerts
  • Plan capacity before adding devices
  • Use appropriately rated PDU for your deployment
Outlet unresponsive to control

Problem: Cannot turn outlet on/off via web interface

Solutions:

  1. Refresh web interface and try again
  2. Check PDU network connectivity
  3. Try opposite action (if trying to turn on, try off first)
  4. Physical power cycle of PDU (last resort)
  5. Check firmware version (may need update)

If outlet physically stuck:

  • May be hardware issue with outlet relay
  • Contact support for service
  • Use different outlet temporarily
Power consumption higher than expected

Problem: EDC drawing more power than normal range

Check:

  1. Number of running VMs (more VMs = more power)
  2. VM workload intensity (CPU/storage activity)
  3. Cooling profile setting (Turbo uses more fan power)
  4. Ambient temperature (hot environment = more cooling needed)
  5. Additional connected devices (PoE devices, accessories)
  6. Per-outlet consumption to identify culprit

Solutions:

  • Reduce VM workloads if possible
  • Switch to Eco or Balanced cooling profile
  • Improve ventilation and airflow
  • Disconnect unnecessary devices
  • Check for runaway processes in VMs
Cannot access PDU web interface

Problem: Cannot reach PDU management interface

Solutions:

  1. Verify PDU network connection (port 7 on switch)
  2. Check switch port status for PDU port
  3. Verify correct IP address (see EnGenius documentation)
  4. Try pinging PDU IP address
  5. Check laptop network configuration
  6. Look at PDU LCD display (may show network error)
  7. Try factory reset if necessary (see EnGenius documentation)

Best Practices​

For reliable power management:

  1. Monitor regularly

    • Check consumption at least weekly
    • Set up automated alerts
    • Review trends monthly

  2. Plan capacity

    • Keep load below 80% of rated capacity
    • Plan for growth and additional devices
    • Upgrade PDU if consistently approaching limit

  3. Document configuration

    • Record outlet assignments
    • Document threshold settings
    • Note normal consumption ranges

  4. Maintain UPS/battery

    • Test battery runtime periodically
    • Replace aging batteries
    • Keep battery charged

  5. Use power data

    • Historical data informs capacity planning
    • Identify optimization opportunities
    • Support troubleshooting with data

Additional Resources​

PDU documentation:

Off-grid power: 👉 Optional Components: Off-Grid Power

IoT monitoring integration: 👉 IoT Monitoring

What's Next?​

After setting up power management:

👉 Cooling Management - Optimize cooling and fan settings

👉 Daily Operations Index - Other daily operational tasks