starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Calculation of Power Utilization not Working (not cascaded) #3827

New Issue
Closed
opened 2025-12-29 18:31:23 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:31:23 +01:00
Owner
Copy Link

Originally created by @RHuehne on GitHub (Jul 2, 2020).

Environment

  • Python version: ?? (using netbox-docker 0.24.1)
  • NetBox version: 2.8.6

According to several posts here, the functionality of calculating the power Utilization should work now. In my case it does not. If I create a PDU Device (1 PowerPort <=> 8 OutletPorts) and connect a Server with 750W PSU to one of the outletPorts, I can see this on the connection, but there is no calculation done in "Power Utilization". It looks like the consumed watt values comming from the PowerOutlets are not linked to the PowerPort.

In our case, we need to have two PDU Devices: One in the rack, and one towards the UPS as the middle PDU splits up the 3 Legs from the UPS to single ones for the racks.

Steps to Reproduce

  1. Create a Uplink Device with PowerOutletPorts.
  2. Create new Device (PDU) with 1 PowerPort (Connected to the Uplink Devices OutletPort1) associated (input/leg) with 8 PowerOutlets
  3. Attach Device (e.g. a Server) with a PowerPort (Max 750W, allocated 500W) to PowerOutlet#1 on PDU Device

Expected Behavior

On the PDU-Device, under Power Utilization, "Allocated", "Available" and "Utilization" have the cumulated values from each of its OutletPorts.

Observed Behavior

"Allocated" is 0VA"
"Available" is "--"
"Utilization" is "--"

OutletPort Watts are not cumulated and pushed up to the PowerPort.

02-07-_2020_15-12-21

Originally created by @RHuehne on GitHub (Jul 2, 2020). <!-- --> ### Environment * Python version: ?? (using netbox-docker 0.24.1) * NetBox version: 2.8.6 According to several posts here, the functionality of calculating the power Utilization should work now. In my case it does not. If I create a PDU Device (1 PowerPort <=> 8 OutletPorts) and connect a Server with 750W PSU to one of the outletPorts, I can see this on the connection, but there is no calculation done in "Power Utilization". It looks like the consumed watt values comming from the PowerOutlets are not linked to the PowerPort. In our case, we need to have two PDU Devices: One in the rack, and one towards the UPS as the middle PDU splits up the 3 Legs from the UPS to single ones for the racks. ### Steps to Reproduce 1. Create a Uplink Device with PowerOutletPorts. 2. Create new Device (PDU) with 1 PowerPort (Connected to the Uplink Devices OutletPort1) associated (input/leg) with 8 PowerOutlets 3. Attach Device (e.g. a Server) with a PowerPort (Max 750W, allocated 500W) to PowerOutlet#1 on PDU Device ### Expected Behavior On the PDU-Device, under Power Utilization, "Allocated", "Available" and "Utilization" have the cumulated values from each of its OutletPorts. ### Observed Behavior "Allocated" is 0VA" "Available" is "--" "Utilization" is "--" OutletPort Watts are not cumulated and pushed up to the PowerPort. ![02-07-_2020_15-12-21](https://user-images.githubusercontent.com/13745200/86364212-28831c80-bc78-11ea-93a7-31b06f321a7f.png)
adam added the status: duplicate label 2025-12-29 18:31:23 +01:00
adam closed this issue 2025-12-29 18:31:23 +01:00
adam commented 2025-12-29 18:31:24 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jul 2, 2020):

Duplicate of #3377

@DanSheps commented on GitHub (Jul 2, 2020): Duplicate of #3377
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#3827
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?