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

Generic, non-unique Device for passive rack unit usage. #817

New Issue
Closed
opened 2025-12-29 16:26:04 +01:00 by adam · 4 comments
adam commented 2025-12-29 16:26:04 +01:00
Owner
Copy Link

Originally created by @ghost on GitHub (Mar 30, 2017).

Issue type: Feature Request

Python version:
NetBox version:

It would be helpful when using Netbox to track rack usage to be able to use a 'generic' object in a rack unit. Currently when assigning RUs to things like Cable Management or Patch Panels one must create a unique name per cable management rack unit. This leads to "site-row-rack-rack unit-Cable MGMT" or "site-row-rack-rack unit-SMF to Row 3 Rack 2A" naming which is mildly onerous.

Having a 'generic' object would be hepful for this - being able to drop a 'passive physical' device into the rack that removes the requirement to uniquely name physical items.

Originally created by @ghost on GitHub (Mar 30, 2017). <!-- Please note: GitHub issues are to be used only for feature requests and bug reports. For installation assistance or general discussion, please join us on the mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please indicate "bug report" or "feature request" below. Be sure to search the existing set of issues (both open and closed) to see if a similar issue has already been raised. --> ### Issue type: Feature Request <!-- If filing a bug, please indicate the version of Python and NetBox you are running. (This is not necessary for feature requests.) --> **Python version:** **NetBox version:** <!-- If filing a bug, please record the exact steps taken to reproduce the bug and any errors messages that are generated. If filing a feature request, please precisely describe the data model or workflow you would like to see implemented, and provide a use case. --> It would be helpful when using Netbox to track rack usage to be able to use a 'generic' object in a rack unit. Currently when assigning RUs to things like Cable Management or Patch Panels one must create a unique name per cable management rack unit. This leads to "site-row-rack-rack unit-Cable MGMT" or "site-row-rack-rack unit-SMF to Row 3 Rack 2A" naming which is mildly onerous. Having a 'generic' object would be hepful for this - being able to drop a 'passive physical' device into the rack that removes the requirement to uniquely name physical items.
adam added the status: duplicate label 2025-12-29 16:26:04 +01:00
adam closed this issue 2025-12-29 16:26:04 +01:00
adam commented 2025-12-29 16:26:04 +01:00
Author
Owner
Copy Link

@dav3860 commented on GitHub (Mar 30, 2017):

Yes, I agree, it would be useful.

@dav3860 commented on GitHub (Mar 30, 2017): Yes, I agree, it would be useful.
adam commented 2025-12-29 16:26:04 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Mar 30, 2017):

Why would you want to obscure documentation like this? I mean, isn't
defining what the device does a great thing?

On Thu, Mar 30, 2017, 03:15 dav3860, notifications@github.com wrote:

Yes, I agree, it would be useful.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/digitalocean/netbox/issues/1018#issuecomment-290323320,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABfg5rtrOOL4y2v5Jm_PpCStRbYIWusLks5rq1aHgaJpZM4Mtz0x
.

@jsenecal commented on GitHub (Mar 30, 2017): Why would you want to obscure documentation like this? I mean, isn't defining what the device does a great thing? On Thu, Mar 30, 2017, 03:15 dav3860, <notifications@github.com> wrote: > Yes, I agree, it would be useful. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/digitalocean/netbox/issues/1018#issuecomment-290323320>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ABfg5rtrOOL4y2v5Jm_PpCStRbYIWusLks5rq1aHgaJpZM4Mtz0x> > . >
adam commented 2025-12-29 16:26:05 +01:00
Author
Owner
Copy Link

@therealjoshuad commented on GitHub (Mar 30, 2017):

I think he's talking about devices that don't need to be defined, for example if there is wire management in a few Us, all I need to know is that those Us aren't available, with a simple indicator as "wire menagament", each wire management doesn't need to be tracked.

But to OP, I think this is what unnamed devices are for, have you tried that yet?

@therealjoshuad commented on GitHub (Mar 30, 2017): I think he's talking about devices that don't need to be defined, for example if there is wire management in a few Us, all I need to know is that those Us aren't available, with a simple indicator as "wire menagament", each wire management doesn't need to be tracked. But to OP, I think this is what unnamed devices are for, have you tried that yet?
adam commented 2025-12-29 16:26:05 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 30, 2017):

Currently when assigning RUs to things like Cable Management or Patch Panels one must create a unique name per cable management rack unit.

Like @therealjoshuad said, you have the option of leaving the device unnamed. The device's make and model will be displayed in the rack elevation.

Seems like this is covered by #417 so I'm going to close it as a duplicate.

@jeremystretch commented on GitHub (Mar 30, 2017): > Currently when assigning RUs to things like Cable Management or Patch Panels one must create a unique name per cable management rack unit. Like @therealjoshuad said, you have the option of leaving the device unnamed. The device's make and model will be displayed in the rack elevation. Seems like this is covered by #417 so I'm going to close it as a duplicate.
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#817
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?