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

Rack Utilization Percentage for "Racked" Devices only #275

New Issue
Closed
opened 2025-12-29 16:20:27 +01:00 by adam · 1 comment
adam commented 2025-12-29 16:20:27 +01:00
Owner
Copy Link

Originally created by @jbro209070 on GitHub (Jul 22, 2016).

Sorry for making another post about this Jeremy, but you closed out the last one before I could finish posting my question.

Say I were to take down a cisco 1921 router (1U) and put it on a shelf. Unless I were to change it to 0U in device types, it would still say that im utilizing rack space even when unracked. When I want to put it back on the rack, I would have to go into device types and change it back to 1U again. Is there a way to set utilization to only pull percentage off devices that are "racked" and ignore "unracked" device U height?

Originally created by @jbro209070 on GitHub (Jul 22, 2016). Sorry for making another post about this Jeremy, but you closed out the last one before I could finish posting my question. Say I were to take down a cisco 1921 router (1U) and put it on a shelf. Unless I were to change it to 0U in device types, it would still say that im utilizing rack space even when unracked. When I want to put it back on the rack, I would have to go into device types and change it back to 1U again. Is there a way to set utilization to only pull percentage off devices that are "racked" and ignore "unracked" device U height?
adam closed this issue 2025-12-29 16:20:27 +01:00
adam commented 2025-12-29 16:20:27 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 22, 2016):

This is intentional. Often, we know that certain devices exist within a rack, but we might not know the specific positions in which they're mounted (because we don't have immediate physical access to the rack to check). NetBox still allows us to assign a device to a rack and consider it as consuming space for inventory purposes.

If you've physically removed a device from a rack, it should be deleted from NetBox as well, as it no longer resides in that rack. As to whether NetBox can/should be used to track devices not installed in a rack, see #198.

@jeremystretch commented on GitHub (Jul 22, 2016): This is intentional. Often, we know that certain devices exist within a rack, but we might not know the specific positions in which they're mounted (because we don't have immediate physical access to the rack to check). NetBox still allows us to assign a device to a rack and consider it as consuming space for inventory purposes. If you've physically removed a device from a rack, it should be deleted from NetBox as well, as it no longer resides in that rack. As to whether NetBox can/should be used to track devices not installed in a rack, see #198.
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#275
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?