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

Idea to enhance the cables features #2762

New Issue
Closed
opened 2025-12-29 18:21:50 +01:00 by adam · 2 comments
adam commented 2025-12-29 18:21:50 +01:00
Owner
Copy Link

Originally created by @quentindavid on GitHub (Jul 26, 2019).

Environment

  • Python version: 3.6.8
  • NetBox version: 2.5.7

It could be very useful being able to connect a cable only on one side of it, even if you don't know where it's connected on the other side. In this way, we could inventory a DC and find where the cable goes.

Proposed Functionality

When you do the inventory of the DC, you can just enter the cables connected and identify them by its label. Once you find the other side of the cable, Netbox could recognize that the cable mentioned is already connected on one side, but left unconnected on the other.

Use Case

Not sure it implies a lot of modifications in the data model, but it add a lot of flexibility.
We can also think to a new view where we see the cables connected only on one side.

Database Changes

To be determined :)

External Dependencies

No dependencies

Originally created by @quentindavid on GitHub (Jul 26, 2019). ### Environment * Python version: 3.6.8 * NetBox version: 2.5.7 It could be very useful being able to connect a cable only on one side of it, even if you don't know where it's connected on the other side. In this way, we could inventory a DC and find where the cable goes. ### Proposed Functionality When you do the inventory of the DC, you can just enter the cables connected and identify them by its label. Once you find the other side of the cable, Netbox could recognize that the cable mentioned is already connected on one side, but left unconnected on the other. ### Use Case Not sure it implies a lot of modifications in the data model, but it add a lot of flexibility. We can also think to a new view where we see the cables connected only on one side. ### Database Changes To be determined :) ### External Dependencies No dependencies
adam closed this issue 2025-12-29 18:21:50 +01:00
adam commented 2025-12-29 18:21:50 +01:00
Author
Owner
Copy Link

@lukasodhner commented on GitHub (Jul 28, 2019):

I am also in need of more cable details and options. Specifically I would want additional cable status options beyond connected and planned. Ideally there would be deprecated, failed, tested, and probably a few more. Of course some of these would qualify as “connected” and some “disconnected” (planned)” state of the current Boolean cable status. I would also really love to have comments and tags on cables. Perhaps this can be addressed in Jeremys suggestion for plugins, although I think it fits into the netbox core and is a natural extension of the cables model.

For your needs Quentindavid perhaps one option is to create a device called “unknown destination” and add 100 ports or interfaces to it. When you need to show a single ended cable connect it to that device and you can add information about where you think it might go on the port/interface of the “unknown destination” device.

Regarding cable inventory you can of course have cables with duplicate labels. The process for this would be to document all the cables and then to find the duplicates connected to “unknown device” and delete both duplicates and create a new one replacing them. I do understand for this workflow why having netbox make the connection for you would be ideal.

@lukasodhner commented on GitHub (Jul 28, 2019): I am also in need of more cable details and options. Specifically I would want additional cable status options beyond connected and planned. Ideally there would be deprecated, failed, tested, and probably a few more. Of course some of these would qualify as “connected” and some “disconnected” (planned)” state of the current Boolean cable status. I would also really love to have comments and tags on cables. Perhaps this can be addressed in Jeremys suggestion for plugins, although I think it fits into the netbox core and is a natural extension of the cables model. For your needs Quentindavid perhaps one option is to create a device called “unknown destination” and add 100 ports or interfaces to it. When you need to show a single ended cable connect it to that device and you can add information about where you think it might go on the port/interface of the “unknown destination” device. Regarding cable inventory you can of course have cables with duplicate labels. The process for this would be to document all the cables and then to find the duplicates connected to “unknown device” and delete both duplicates and create a new one replacing them. I do understand for this workflow why having netbox make the connection for you would be ideal.
adam commented 2025-12-29 18:21:51 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 29, 2019):

Sorry folks, the cable model in place now is the result of lengthy discussion leading up to the v2.5 release and won't be modified any time soon. Development is focused in other areas.

@jeremystretch commented on GitHub (Jul 29, 2019): Sorry folks, the cable model in place now is the result of lengthy discussion leading up to the v2.5 release and won't be modified any time soon. Development is focused in other areas.
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#2762
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?