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 circuits terminaison on LAG and virtual interfaces #5579

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

Originally created by @SteveRodrigue on GitHub (Oct 28, 2021).

NetBox version

v2.11.6

Feature type

Data model extension

Proposed functionality

Allow to attach circuits termination to LAG or virtual interfaces because a physical circuit may transport multiple services or underlying circuits.

Use case

I'll use the example of Company X buying 20Gbps Internet from ACME.

ACME provides 3 circuits ID.
10Gbps physical A = cctidA
10Gbps physical B = cctidB
20Gbps Internet service (LAG) = cctidC

In Netbox:

  1. cctidA is created and attached to an interface X.
  2. cctidB is created and attached to another interface Y.
  3. A LAG is created and interfaces X and Y are assigned to it.
  4. cctidC is created, but can't be attached or assigned to the LAG interface.

This is not uncommon for providers to give their customer more than one 1 circuit ID. Another common use case is for Public-Cloud interconnect: on a single physical circuit, multiple logical circuits are assigned to reach multiple VPCs. Typically, each of these circuit will terminate on a sub-interface or svi (vlan interface).

Database changes

LAG and virtual interfaces should be allowed when it comes to select a circuit termination (A/Z).

External dependencies

No response

Originally created by @SteveRodrigue on GitHub (Oct 28, 2021). ### NetBox version v2.11.6 ### Feature type Data model extension ### Proposed functionality Allow to attach circuits termination to LAG or virtual interfaces because a physical circuit may transport multiple services or underlying circuits. ### Use case I'll use the example of Company X buying 20Gbps Internet from ACME. ``` ACME provides 3 circuits ID. 10Gbps physical A = cctidA 10Gbps physical B = cctidB 20Gbps Internet service (LAG) = cctidC ``` In Netbox: 1. cctidA is created and attached to an interface X. 2. cctidB is created and attached to another interface Y. 3. A LAG is created and interfaces X and Y are assigned to it. 4. cctidC is created, but can't be attached or assigned to the LAG interface. This is not uncommon for providers to give their customer more than one 1 circuit ID. Another common use case is for Public-Cloud interconnect: on a single physical circuit, multiple logical circuits are assigned to reach multiple VPCs. Typically, each of these circuit will terminate on a sub-interface or svi (vlan interface). ### Database changes LAG and virtual interfaces should be allowed when it comes to select a circuit termination (A/Z). ### External dependencies _No response_
adam added the type: featurestatus: duplicate labels 2025-12-29 19:29:43 +01:00
adam closed this issue 2025-12-29 19:29:43 +01:00
adam commented 2025-12-29 19:29:44 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 28, 2021):

This has been discussed in many past issues. Please search for "virtual circuits."

@jeremystretch commented on GitHub (Oct 28, 2021): This has been discussed in many past issues. Please search for "virtual circuits."
adam commented 2025-12-29 19:29:44 +01:00
Author
Owner
Copy Link

@SteveRodrigue commented on GitHub (Oct 28, 2021):

@jeremystretch : Thanks for pointing that out. I may have missed it and the search I did, didn't seemed to match what I was looking for.

I'll look back in opened feature requets.

@SteveRodrigue commented on GitHub (Oct 28, 2021): @jeremystretch : Thanks for pointing that out. I may have missed it and the search I did, didn't seemed to match what I was looking for. I'll look back in opened feature requets.
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 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#5579
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?