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

PowerPort maximum_draw and allocated_draw is limited to about 32KW. #3686

New Issue
Closed
opened 2025-12-29 18:30:37 +01:00 by adam · 6 comments
adam commented 2025-12-29 18:30:37 +01:00
Owner
Copy Link

Originally created by @ThomasADavis on GitHub (May 13, 2020).

Environment

  • Python version: 3.6.8
  • NetBox version: 2.8.2

Steps to Reproduce

  1. Disable any installed plugins by commenting out the PLUGINS setting in
    configuration.py.
  2. Create a PowerPort.
  3. Set maximum draw/allocated draw to a value greater than 32kw (ie, 33kw)

We have systems with power ports in the 400kw/300kw range coming in..

Expected Behavior

setting maximum_draw/allocated_draw to a value higher than 32kw

Observed Behavior

Maximum power draw (watts)
Ensure this value is less than or equal to 32767.

Allocated power draw (watts)
Ensure this value is less than or equal to 32767.

please change maximum_draw and allocated_draw from PositiveSmallIntegerField to PositiveIntegerField in dcim/models/device_components.py

Originally created by @ThomasADavis on GitHub (May 13, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report, and that any plugins have been disabled. --> ### Environment * Python version: 3.6.8 * NetBox version: 2.8.2 <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox. Begin with the creation of any necessary database objects and call out every operation being performed explicitly. If reporting a bug in the REST API, be sure to reconstruct the raw HTTP request(s) being made: Don't rely on a client library such as pynetbox. --> ### Steps to Reproduce 1. Disable any installed plugins by commenting out the `PLUGINS` setting in `configuration.py`. 2. Create a PowerPort. 3. Set maximum draw/allocated draw to a value greater than 32kw (ie, 33kw) We have systems with power ports in the 400kw/300kw range coming in.. <!-- What did you expect to happen? --> ### Expected Behavior setting maximum_draw/allocated_draw to a value higher than 32kw <!-- What happened instead? --> ### Observed Behavior Maximum power draw (watts) Ensure this value is less than or equal to 32767. Allocated power draw (watts) Ensure this value is less than or equal to 32767. please change maximum_draw and allocated_draw from PositiveSmallIntegerField to PositiveIntegerField in dcim/models/device_components.py
adam closed this issue 2025-12-29 18:30:37 +01:00
adam commented 2025-12-29 18:30:37 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 13, 2020):

Please specify your Python version as indicated by the template.

@jeremystretch commented on GitHub (May 13, 2020): Please specify your Python version as indicated by the template.
adam commented 2025-12-29 18:30:37 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 26, 2020):

Can you cite a real-world example of a piece of equipment that would be in-scope for modeling within NetBox that draws 32KW of power from a single power port?

@jeremystretch commented on GitHub (May 26, 2020): Can you cite a real-world example of a piece of equipment that would be in-scope for modeling within NetBox that draws 32KW of power from a single power port?
adam commented 2025-12-29 18:30:37 +01:00
Author
Owner
Copy Link

@ThomasADavis commented on GitHub (May 26, 2020):

Cray Shasta Cabinets have 3ea, 150amp, 480v feeds into them, feeding into 6 chassis's.

We have on scheduled delivery of cabinets that will use 300KW or 400KW (GPU based system). They are water cooled, not air cooled.

We also have dual 550KVA/1.1KVA UPS's feeding the floor.

So, the goal is get a complete Cray Shasta system into netbox.

@ThomasADavis commented on GitHub (May 26, 2020): Cray Shasta Cabinets have 3ea, 150amp, 480v feeds into them, feeding into 6 chassis's. We have on scheduled delivery of cabinets that will use 300KW or 400KW (GPU based system). They are water cooled, not air cooled. We also have dual 550KVA/1.1KVA UPS's feeding the floor. So, the goal is get a complete Cray Shasta system into netbox.
adam commented 2025-12-29 18:30:37 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 26, 2020):

That's a feed though, not an individual power port, correct? Power ports are assigned to discrete devices within a rack.

@jeremystretch commented on GitHub (May 26, 2020): That's a feed though, not an individual power port, correct? Power ports are assigned to discrete devices within a rack.
adam commented 2025-12-29 18:30:37 +01:00
Author
Owner
Copy Link

@ThomasADavis commented on GitHub (May 26, 2020):

We use feeds for the substations, so we can model the panels and cabinets as devices. Our panels are smart devices, not dumb. Look at them as very expensive pdu strips mounted on the wall, with very expensive power connectors, at very high power (1600amps @ 480v)

I know power cascading calculations are not working.

It also allows us to also draw a power topology, and know what gets turned off when a panel/ups/pdu is shutdown.

@ThomasADavis commented on GitHub (May 26, 2020): We use feeds for the substations, so we can model the panels and cabinets as devices. Our panels are smart devices, not dumb. Look at them as very expensive pdu strips mounted on the wall, with very expensive power connectors, at very high power (1600amps @ 480v) I know power cascading calculations are not working. It also allows us to also draw a power topology, and know what gets turned off when a panel/ups/pdu is shutdown.
adam commented 2025-12-29 18:30:38 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 27, 2020):

That explains it then. Power ports are intended to model individual power supplies within a device, hence the limitation. You can associate power feeds with racks though, which sounds like it should work for your use case.

@jeremystretch commented on GitHub (May 27, 2020): That explains it then. Power ports are intended to model individual power supplies within a device, hence the limitation. You can associate power feeds with racks though, which sounds like it should work for your use case.
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
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#3686
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?