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 - Multipath (ex: PON tree) - Path Split - entire tree node option #7265

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

Originally created by @Djo91 on GitHub (Nov 21, 2022).

NetBox version

v3.3.4

Feature type

New functionality

Proposed functionality

In trace fonction (of the current objet), if there is one or more path split in the cable trace, it would be nice to add a node option to display full tree, including :

I think that a grafical view is not mandatory, an array (easier to implement) could be enough like :

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns="http://www.w3.org/TR/REC-html40"> <head> <style> </style> </head>
Device Interface Cable State Lenght
OLT interface PON Cable number Connected or Not connected  
▪"Device Name" - Interface / port : """Name" > Cable number Connected or Not connected  
▪▪Front port X > "Device Name" - Interface or port : "Name" Cable number Connected or Not connected  
▪▪▪Front port Y >  "Device Name" - Interface or port : "Name" Cable number Connected or Not connected  
▪▪▪Front port Y+1 > "Device Name" - Interface or port : "Name" Cable number Connected or Not connected  
▪▪▪▪Front port Z > Empty Cable number Connected or Not connected  
▪▪▪▪Front port Z+ > Empty Cable number Connected or Not connected  
▪▪Front port X+1 > "Device Name" - Interface or port : "Name" Cable number Connected or Not connected  
▪▪▪Front port P > Empty Cable number Connected or Not connected  
▪▪▪Front port P+ > Empty Cable number Connected or Not connected  
</html>

This feature will allow us to check easily all endpoints of a PON tree.

Use case

image

Is this topology if you trace from OLT pon interface 1/1/1/1, you should have :

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns="http://www.w3.org/TR/REC-html40"> <head> <style> </style> </head>
Device Interface Cable State Lenght
OLT PON port 1/1/1/1 Cable 17 Connected 50m
▪"Splitter-1 1:2" - Rear port : "Input" > Cable 17 Connected 50m
▪▪Front port 1 > "Splitter-2 1:2" - Rear port : "Input" Cable 19 Connected 2m
▪▪▪Front port 1 >  "ONT 20" - interface : "WAN" Cable 21 Connected 2m
▪▪▪Front port 2 > "Splitter-3 1:16" - Rear port : "Input" Cable 22 Connected 200m
▪▪▪▪Front port 1 > Empty   Not connected  
▪▪▪▪Front port x > Empty   Not connected  
▪▪▪▪Front port 32 > Empty   Not connected  
▪▪Front port 2 > "Splitter-4 1:32" - Rear port : "Input" Cable 20 Connected 100m
▪▪▪Front port 1 > Empty   Not connected  
▪▪▪Front port x > Empty   Not connected  
▪▪▪Front port 15 >  "ONT 19" - interface : "WAN"   Connected 5m
▪▪▪Front port x > Empty   Not connected  
▪▪▪Front port 32 > Empty   Not connected  
</html>

If necessary I can model the topology in example on : https://demo.netbox.dev/

Database changes

No response

External dependencies

No response

Originally created by @Djo91 on GitHub (Nov 21, 2022). ### NetBox version v3.3.4 ### Feature type New functionality ### Proposed functionality In trace fonction (of the current objet), if there is one or more path split in the cable trace, it would be nice to add a node option to display full tree, including : - the entire tree from the selected level of the path - cable path trace without PathEndpoint (https://github.com/netbox-community/netbox/issues/9718#issue-1304154421) I think that a grafical view is not mandatory, an array (easier to implement) could be enough like : <html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta name=ProgId content=Excel.Sheet> <meta name=Generator content="Microsoft Excel 15"> <link id=Main-File rel=Main-File href="file:///c:/Temp/msohtmlclip1/01/clip.htm"> <link rel=File-List href="file:///c:/Temp/msohtmlclip1/01/clip_filelist.xml"> <style> <!--table {mso-displayed-decimal-separator:"\,"; mso-displayed-thousand-separator:" ";} @page {margin:.75in .7in .75in .7in; mso-header-margin:.3in; mso-footer-margin:.3in;} tr {mso-height-source:auto;} col {mso-width-source:auto;} br {mso-data-placement:same-cell;} td {padding-top:1px; padding-right:1px; padding-left:1px; mso-ignore:padding; color:black; font-size:11.0pt; font-weight:400; font-style:normal; text-decoration:none; font-family:Calibri, sans-serif; mso-font-charset:0; mso-number-format:General; text-align:general; vertical-align:bottom; border:none; mso-background-source:auto; mso-pattern:auto; mso-protection:locked visible; white-space:nowrap; mso-rotate:0;} .xl65 {white-space:normal;} --> </style> </head> <body link="#0563C1" vlink="#954F72"> Device Interface | Cable | State | Lenght -- | -- | -- | -- OLT interface PON | Cable number | Connected or Not connected |   ▪"Device Name" - Interface / port : """Name" > | Cable number | Connected or Not connected |   ▪▪Front port X > "Device Name" - Interface or port : "Name" | Cable number | Connected or Not connected |   ▪▪▪Front port Y >  "Device Name" - Interface or port : "Name" | Cable number | Connected or Not connected |   ▪▪▪Front port Y+1 > "Device Name" - Interface or port : "Name" | Cable number | Connected or Not connected |   ▪▪▪▪Front port Z > Empty | Cable number | Connected or Not connected |   ▪▪▪▪Front port Z+ > Empty | Cable number | Connected or Not connected |   ▪▪Front port X+1 > "Device Name" - Interface or port : "Name" | Cable number | Connected or Not connected |   ▪▪▪Front port P > Empty | Cable number | Connected or Not connected |   ▪▪▪Front port P+ > Empty | Cable number | Connected or Not connected |   </body> </html> This feature will allow us to check easily all endpoints of a PON tree. ### Use case ![image](https://user-images.githubusercontent.com/41725967/203091137-9654e962-3c65-4da6-b606-8fc67ece7f11.png) Is this topology if you trace from OLT pon interface 1/1/1/1, you should have : <html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta name=ProgId content=Excel.Sheet> <meta name=Generator content="Microsoft Excel 15"> <link id=Main-File rel=Main-File href="file:///c:/Temp/msohtmlclip1/01/clip.htm"> <link rel=File-List href="file:///c:/Temp/msohtmlclip1/01/clip_filelist.xml"> <style> <!--table {mso-displayed-decimal-separator:"\,"; mso-displayed-thousand-separator:" ";} @page {margin:.75in .7in .75in .7in; mso-header-margin:.3in; mso-footer-margin:.3in;} tr {mso-height-source:auto;} col {mso-width-source:auto;} br {mso-data-placement:same-cell;} td {padding-top:1px; padding-right:1px; padding-left:1px; mso-ignore:padding; color:black; font-size:11.0pt; font-weight:400; font-style:normal; text-decoration:none; font-family:Calibri, sans-serif; mso-font-charset:0; mso-number-format:General; text-align:general; vertical-align:bottom; border:none; mso-background-source:auto; mso-pattern:auto; mso-protection:locked visible; white-space:nowrap; mso-rotate:0;} .xl65 {white-space:normal;} --> </style> </head> <body link="#0563C1" vlink="#954F72"> Device Interface | Cable | State | Lenght -- | -- | -- | -- OLT PON port 1/1/1/1 | Cable 17 | Connected | 50m ▪"Splitter-1 1:2" - Rear port : "Input" > | Cable 17 | Connected | 50m ▪▪Front port 1 > "Splitter-2 1:2" - Rear port : "Input" | Cable 19 | Connected | 2m ▪▪▪Front port 1 >  "ONT 20" - interface : "WAN" | Cable 21 | Connected | 2m ▪▪▪Front port 2 > "Splitter-3 1:16" - Rear port : "Input" | Cable 22 | Connected | 200m ▪▪▪▪Front port 1 > Empty |   | Not connected |   ▪▪▪▪Front port x > Empty |   | Not connected |   ▪▪▪▪Front port 32 > Empty |   | Not connected |   ▪▪Front port 2 > "Splitter-4 1:32" - Rear port : "Input" | Cable 20 | Connected | 100m ▪▪▪Front port 1 > Empty |   | Not connected |   ▪▪▪Front port x > Empty |   | Not connected |   ▪▪▪Front port 15 >  "ONT 19" - interface : "WAN" |   | Connected | 5m ▪▪▪Front port x > Empty |   | Not connected |   ▪▪▪Front port 32 > Empty |   | Not connected |   </body> </html> If necessary I can model the topology in example on : https://demo.netbox.dev/ ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closure labels 2025-12-29 20:21:00 +01:00
adam closed this issue 2025-12-29 20:21:00 +01:00
adam commented 2025-12-29 20:21:01 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 22, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jan 22, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:21:01 +01:00
Author
Owner
Copy Link

@bluecmd commented on GitHub (Jan 27, 2023):

I think this might also be a solution to was originally reported as a potential bug in https://github.com/netbox-community/netbox/issues/10355 (it was a planned omission, not a bug, as explained in the issue). I see that @CupcakeMunster haven't 👍 this issue, writing this comment to cross-link the issues for visibility in case it is still relevant for their use case.

@bluecmd commented on GitHub (Jan 27, 2023): I think this might also be a solution to was originally reported as a potential bug in https://github.com/netbox-community/netbox/issues/10355 (it was a planned omission, not a bug, as explained in the issue). I see that @CupcakeMunster haven't :+1: this issue, writing this comment to cross-link the issues for visibility in case it is still relevant for their use case.
adam commented 2025-12-29 20:21:01 +01:00
Author
Owner
Copy Link

@copyrights commented on GitHub (Jan 29, 2023):

This would also be nice for y-cables and alike.

@copyrights commented on GitHub (Jan 29, 2023): This would also be nice for y-cables and alike.
adam commented 2025-12-29 20:21:01 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 17, 2023):

Going to close this out as no one has detailed a specific implementation proposal. If anyone would like to develop and share a proof of concept, I'd be happy to revisit the idea.

@jeremystretch commented on GitHub (Feb 17, 2023): Going to close this out as no one has detailed a specific implementation proposal. If anyone would like to develop and share a proof of concept, I'd be happy to revisit the idea.
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 pending closure 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#7265
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?