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

Cable Trace for a complete Switch #10711

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

Originally created by @NotHBlocks on GitHub (Jan 29, 2025).

NetBox version

v4.2.1

Feature type

Change to existing functionality

Proposed functionality

It would be nice if we have a feature like cable trace for a whole Switch. With this feature you can see the cable trace of all connected cables from one Switch.
See example picture below.

For one cable now:

Image

My expectedfunction:

Image

To be clear. The other red cable show the connection to the other switch.

Use case

You can print those sites and put it analogue into the serverroom. Espacilly helpfull for Core devices. If you have an connectivity lost you have some data to check. For Example if Netbox isn´t available.

Database changes

No response

External dependencies

No response

Originally created by @NotHBlocks on GitHub (Jan 29, 2025). ### NetBox version v4.2.1 ### Feature type Change to existing functionality ### Proposed functionality It would be nice if we have a feature like cable trace for a whole Switch. With this feature you can see the cable trace of all connected cables from one Switch. See example picture below. For one cable now: ![Image](https://github.com/user-attachments/assets/ad4a00b9-9b00-4548-bbe2-39fb6b8206fb) My expectedfunction: ![Image](https://github.com/user-attachments/assets/2bd607ac-6e36-4376-b67e-089ff3ec9e57) To be clear. The other red cable show the connection to the other switch. ### Use case You can print those sites and put it analogue into the serverroom. Espacilly helpfull for Core devices. If you have an connectivity lost you have some data to check. For Example if Netbox isn´t available. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featureplugin candidate labels 2025-12-29 21:35:07 +01:00
adam closed this issue 2025-12-29 21:35:07 +01:00
adam commented 2025-12-29 21:35:07 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 29, 2025):

This is far too complex a topic to be captured in such a vague feature request. Why don't you implement your idea in a plugin first, then present it to the community for consideration as a potential core feature?

@jeremystretch commented on GitHub (Jan 29, 2025): This is far too complex a topic to be captured in such a vague feature request. Why don't you implement your idea in a plugin first, then present it to the community for consideration as a potential core feature?
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 plugin candidate 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#10711
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?