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

Allow termination of circuits with another circuit #3538

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

Originally created by @lucasalvatore on GitHub (Apr 3, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.7
  • NetBox version: 2.6.11

Proposed Functionality

Allow termination of circuits with another circuit

Use Case

The use case is for when we connect to an ISP via a 3rd party wavelength / metro connect. It would be great if netbox could show something like:

my_router xe-0/0/0 > wavelength > ISP circuit

Database Changes

Unknown

External Dependencies

None

Originally created by @lucasalvatore on GitHub (Apr 3, 2020). Originally assigned to: @jeremystretch on GitHub. ### Environment * Python version: 3.7 * NetBox version: 2.6.11 ### Proposed Functionality Allow termination of circuits with another circuit ### Use Case The use case is for when we connect to an ISP via a 3rd party wavelength / metro connect. It would be great if netbox could show something like: ``` my_router xe-0/0/0 > wavelength > ISP circuit ``` ### Database Changes Unknown ### External Dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 18:29:46 +01:00
adam closed this issue 2025-12-29 18:29:46 +01:00
adam commented 2025-12-29 18:29:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 3, 2020):

You'd still need a cable to connect the two circuit terminations. It would look like this:

[ device ] [ interface ] ---- [ termination ] [ circuit ] [ termination ] ---- [ termination ] [ circuit ] [ termination ] ---- [ interface ] [ device ]

Validation doesn't currently allow one termination to attach to another directly, but I don't think this is a limitation of the model itself.

@jeremystretch commented on GitHub (Apr 3, 2020): You'd still need a cable to connect the two circuit terminations. It would look like this: ``` [ device ] [ interface ] ---- [ termination ] [ circuit ] [ termination ] ---- [ termination ] [ circuit ] [ termination ] ---- [ interface ] [ device ] ``` Validation doesn't currently allow one termination to attach to another directly, but I don't think this is a limitation of the model itself.
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: accepted 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#3538
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?