starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Full Layer 1 path maps and internal circuit id's #260

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

Originally created by @jtdub on GitHub (Jul 20, 2016).

For the purpose of having complete visibility of a cable path, I propose that we treat all cross-connects as circuits, assigning them with internal circuit ID's and identifying the connection from each source port on a patch panel to each destination port on a patch panel.

For example:

pp1_port1 <-> pp2_port2

Then when you establish a cross-connect between two devices, you can map out the complete path of the cable and assign the 'circuit' with a circuit ID.

CID: INT000001

spine1_port1 <-> pp1_port1 <-> pp2_port1 <-> leaf1_port1

You could also define the cross-connect role, which would also serve in assisting in deploying device configs, using netbox as a source of truth, an external system to pull the variables, compile templated configs, and push configs to a device.

Originally created by @jtdub on GitHub (Jul 20, 2016). For the purpose of having complete visibility of a cable path, I propose that we treat all cross-connects as circuits, assigning them with internal circuit ID's and identifying the connection from each source port on a patch panel to each destination port on a patch panel. For example: ``` pp1_port1 <-> pp2_port2 ``` Then when you establish a cross-connect between two devices, you can map out the complete path of the cable and assign the 'circuit' with a circuit ID. ``` CID: INT000001 spine1_port1 <-> pp1_port1 <-> pp2_port1 <-> leaf1_port1 ``` You could also define the cross-connect role, which would also serve in assisting in deploying device configs, using netbox as a source of truth, an external system to pull the variables, compile templated configs, and push configs to a device.
adam added the status: duplicate label 2025-12-29 16:20:16 +01:00
adam closed this issue 2025-12-29 16:20:16 +01:00
adam commented 2025-12-29 16:20:16 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 20, 2016):

Seems like this is covered by #20 and/or #49.

@jeremystretch commented on GitHub (Jul 20, 2016): Seems like this is covered by #20 and/or #49.
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#260
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?