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

Patch panel #724

New Issue
Closed
opened 2025-12-29 16:25:08 +01:00 by adam · 8 comments
adam commented 2025-12-29 16:25:08 +01:00
Owner
Copy Link

Originally created by @VictorJ76 on GitHub (Feb 23, 2017).

I just want to know if there is or there will be a patch panel device in netbox ?
It will be very usefull for me. This will be to store information in patch panel in racks.

Best regards.

Victor

Originally created by @VictorJ76 on GitHub (Feb 23, 2017). I just want to know if there is or there will be a patch panel device in netbox ? It will be very usefull for me. This will be to store information in patch panel in racks. Best regards. Victor
adam added the status: duplicate label 2025-12-29 16:25:08 +01:00
adam closed this issue 2025-12-29 16:25:09 +01:00
adam commented 2025-12-29 16:25:09 +01:00
Author
Owner
Copy Link

@rlaneyjr commented on GitHub (Feb 23, 2017):

I agree with Victor in the sense where you could have a placeholder for a device in the rack. This would prevent other devices from being added when there is already something there. Use case would be the Network Team and the Server Team shares the rack. These placeholders would be arbitrarily named and sized.

@rlaneyjr commented on GitHub (Feb 23, 2017): I agree with Victor in the sense where you could have a placeholder for a device in the rack. This would prevent other devices from being added when there is already something there. Use case would be the Network Team and the Server Team shares the rack. These placeholders would be arbitrarily named and sized.
adam commented 2025-12-29 16:25:09 +01:00
Author
Owner
Copy Link

@therealjoshuad commented on GitHub (Feb 23, 2017):

I created a device role for it. Even added ports so I can label what's what.

@therealjoshuad commented on GitHub (Feb 23, 2017): I created a device role for it. Even added ports so I can label what's what.
adam commented 2025-12-29 16:25:09 +01:00
Author
Owner
Copy Link

@rlaneyjr commented on GitHub (Feb 23, 2017):

Good idea however, you also have to create a manufacturer, device-type, tenant, platform. I was wanting to stay away from cluttering my NetBox with stuff I do not manage.

@rlaneyjr commented on GitHub (Feb 23, 2017): Good idea however, you also have to create a manufacturer, device-type, tenant, platform. I was wanting to stay away from cluttering my NetBox with stuff I do not manage.
adam commented 2025-12-29 16:25:10 +01:00
Author
Owner
Copy Link

@therealjoshuad commented on GitHub (Feb 23, 2017):

I just use the following

Manufacturer: Generic
Device Type: Patch Panel
Tenant is optional
Platform is optional

I believe there's. even discussion about patch panels in other issue, there might be more suggestions there too

@therealjoshuad commented on GitHub (Feb 23, 2017): I just use the following Manufacturer: Generic Device Type: Patch Panel Tenant is optional Platform is optional I believe there's. even discussion about patch panels in other issue, there might be more suggestions there too
adam commented 2025-12-29 16:25:10 +01:00
Author
Owner
Copy Link

@VictorJ76 commented on GitHub (Feb 23, 2017):

@therealjoshuad when you says, you labels what's what, you mean you write in description's interface ? because the description isn't directly visible. I can't display what I want in name's interface but it's too long for me.

@VictorJ76 commented on GitHub (Feb 23, 2017): @therealjoshuad when you says, you labels what's what, you mean you write in description's interface ? because the description isn't directly visible. I can't display what I want in name's interface but it's too long for me.
adam commented 2025-12-29 16:25:10 +01:00
Author
Owner
Copy Link

@rlaneyjr commented on GitHub (Feb 23, 2017):

@therealjoshuad Thanks! I have created my 1U, 2U, 3U, 4U placeholders. I feel so dumb...lol.

@rlaneyjr commented on GitHub (Feb 23, 2017): @therealjoshuad Thanks! I have created my 1U, 2U, 3U, 4U placeholders. I feel so dumb...lol.
adam commented 2025-12-29 16:25:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 23, 2017):

Patch panels will be included in #20. I strongly advise against trying to represent patch panels in NetBox until explicit support has been added.

@jeremystretch commented on GitHub (Feb 23, 2017): Patch panels will be included in #20. I strongly advise against trying to represent patch panels in NetBox until explicit support has been added.
adam commented 2025-12-29 16:25:10 +01:00
Author
Owner
Copy Link

@therealjoshuad commented on GitHub (Feb 23, 2017):

@v5ctor It's not visible, but if you hover over the comment bubble, it shows it.

It's definitely not ideal, but we have a Visio diagram with the patch panel port numbers layer over the floor plan. In netbox, I have a patch panel with an interface with the corresponding patch panel number. I then connect the patch panel interface to the appropriate switch interface. So it's represented as two devices connecting to each other, and once #20 is implemented, I'll just re-add the patch panels. It'll be a little extra work, but we're a small company, so we don't have a crazy amount of IDFs

@therealjoshuad commented on GitHub (Feb 23, 2017): @v5ctor It's not visible, but if you hover over the comment bubble, it shows it. It's definitely not ideal, but we have a Visio diagram with the patch panel port numbers layer over the floor plan. In netbox, I have a patch panel with an interface with the corresponding patch panel number. I then connect the patch panel interface to the appropriate switch interface. So it's represented as two devices connecting to each other, and once #20 is implemented, I'll just re-add the patch panels. It'll be a little extra work, but we're a small company, so we don't have a crazy amount of IDFs
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#724
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?