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

Feature Request for passive network components. #10732

New Issue
Closed
opened 2025-12-29 21:35:19 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:35:19 +01:00
Owner
Copy Link

Originally created by @d3rl1nkhd on GitHub (Feb 5, 2025).

NetBox version

v4.1.6

Feature type

New functionality

Proposed functionality

In the company i work we want do document all network racks. In all of those there are passive network components like cable manage panels or airflow panels. At the moment if you have 10 cable management panels in you're rack, you would need to create different 10 devices. Therefore now you have 10 devices which have no use and just looks like a mess.

Solution:
You create a new menu field with Passive Network Components where you can create a cable management panel or an airflow panel and then assign it to multiple racks and rack heights.

For us this feature would be really essential, otherwise we can't document the network racks rigth.

Use case

This helps the overview, as you can now separate the active and passive components. And you don't have to create the same panel over and over again.

Database changes

Would probably need a new Passive Network components table.

External dependencies

No response

Originally created by @d3rl1nkhd on GitHub (Feb 5, 2025). ### NetBox version v4.1.6 ### Feature type New functionality ### Proposed functionality In the company i work we want do document all network racks. In all of those there are passive network components like cable manage panels or airflow panels. At the moment if you have 10 cable management panels in you're rack, you would need to create different 10 devices. Therefore now you have 10 devices which have no use and just looks like a mess. Solution: You create a new menu field with Passive Network Components where you can create a cable management panel or an airflow panel and then assign it to multiple racks and rack heights. For us this feature would be really essential, otherwise we can't document the network racks rigth. ### Use case This helps the overview, as you can now separate the active and passive components. And you don't have to create the same panel over and over again. ### Database changes Would probably need a new Passive Network components table. ### External dependencies _No response_
adam added the type: featurestatus: duplicate labels 2025-12-29 21:35:19 +01:00
adam closed this issue 2025-12-29 21:35:19 +01:00
adam commented 2025-12-29 21:35:20 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 5, 2025):

This has been addressed many times in past issues. Please remember to search for existing issues before opening new ones.

@jeremystretch commented on GitHub (Feb 5, 2025): This has been addressed many times in past issues. Please remember to search for existing issues before opening new ones.
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 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#10732
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?