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

Allow maximum power draw for PDU like devices #5844

New Issue
Closed
opened 2025-12-29 19:33:25 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:33:25 +01:00
Owner
Copy Link

Originally created by @Computroniks on GitHub (Dec 28, 2021).

NetBox version

v3.1.2

Feature type

Change to existing functionality

Proposed functionality

Currently, if a value for maximum draw on a power port is specified, the utilization of that power port is no longer calculated. For example:
I create a PDU with 1 power port and 8 power outlets. Each of these 8 power outlets is connected to a device drawing 100VA. If I do not specify the maximum draw for the power port, the power utilization is calculated correctly (at 800VA). If I then set the maximum draw to 2500VA, the power utilization is no longer calculated and is displayed as 0VA.

Currently the power available is calculated from the values of the feed, which may be able to supply more power than the PDU is rated for, thus making the maximum power available misleading. In the UK for example, an average socket is rated to provide 13A at 240V. This is higher than the maximum current for an IEC C13 cable at 10A and consequently the PDU connected to said IEC C13 cable is only rated for 10A. This would mean that the displayed maximum would be 3120VA (assume 100% max utilization) where as the actual maximum the equipment is rated for would be 2808VA.

Use case

All PDUs have a maximum rated power output. If this power output is exceeded, at the very minimum a fuse may blow but there is the risk of damage to equipment. For this reason it would be useful to state in the management system the maximum power draw allowed for the PDU. It could be the case that the maximum output of the PDU is less than the maximum output of the feed and as such the maximum output of the PDU should be used in all calculations.

Database changes

I don't belive that this change will need any database changes.

External dependencies

I don't think that any external dependencies will be required.

Originally created by @Computroniks on GitHub (Dec 28, 2021). ### NetBox version v3.1.2 ### Feature type Change to existing functionality ### Proposed functionality Currently, if a value for maximum draw on a power port is specified, the utilization of that power port is no longer calculated. For example: I create a PDU with 1 power port and 8 power outlets. Each of these 8 power outlets is connected to a device drawing 100VA. If I do not specify the maximum draw for the power port, the power utilization is calculated correctly (at 800VA). If I then set the maximum draw to 2500VA, the power utilization is no longer calculated and is displayed as 0VA. Currently the power available is calculated from the values of the feed, which may be able to supply more power than the PDU is rated for, thus making the maximum power available misleading. In the UK for example, an average socket is rated to provide 13A at 240V. This is higher than the maximum current for an IEC C13 cable at 10A and consequently the PDU connected to said IEC C13 cable is only rated for 10A. This would mean that the displayed maximum would be 3120VA (assume 100% max utilization) where as the actual maximum the equipment is rated for would be 2808VA. ### Use case All PDUs have a maximum rated power output. If this power output is exceeded, at the very minimum a fuse may blow but there is the risk of damage to equipment. For this reason it would be useful to state in the management system the maximum power draw allowed for the PDU. It could be the case that the maximum output of the PDU is less than the maximum output of the feed and as such the maximum output of the PDU should be used in all calculations. ### Database changes I don't belive that this change will need any database changes. ### External dependencies I don't think that any external dependencies will be required.
adam added the type: featurepending closure labels 2025-12-29 19:33:25 +01:00
adam closed this issue 2025-12-29 19:33:25 +01:00
adam commented 2025-12-29 19:33:26 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 27, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Feb 27, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:33:26 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 31, 2022):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Mar 31, 2022): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure type: feature
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#5844
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?