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 circuit termination to provider networks of 3rd party providers #5202

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

Originally created by @ktims on GitHub (Aug 18, 2021).

NetBox version

v2.11.11

Feature type

Change to existing functionality

Proposed functionality

Allow Circuits to terminate onto Provider Networks of 3rd parties (ie. Provider Network not matching the Circuit Provider).

Use case

Circuits often terminate into networks that are not controlled by the provider delivering them. For example an AWS DirectConnect / Azure ExpressRoute circuit, a connection to an IXP fabric, even a Transit circuit could be considered this way (terminating to the 'Internet').

Presently, circuits can only terminate to Provider Networks that match the Circuit provider, so the only way to model this is to make the 3rd party network 'owned' by the provider providing connectivity to it. If multiple providers are providing circuits to the same Provider Network (e.g. for HA), it is not possible to model the situation sensibly.

Database changes

No model changes would be required. I am not sure if this constraint is enforced in the database (probably not...?).

External dependencies

No response

Originally created by @ktims on GitHub (Aug 18, 2021). ### NetBox version v2.11.11 ### Feature type Change to existing functionality ### Proposed functionality Allow Circuits to terminate onto Provider Networks of 3rd parties (ie. Provider Network not matching the Circuit Provider). ### Use case Circuits often terminate into networks that are not controlled by the provider delivering them. For example an AWS DirectConnect / Azure ExpressRoute circuit, a connection to an IXP fabric, even a Transit circuit could be considered this way (terminating to the 'Internet'). Presently, circuits can only terminate to Provider Networks that match the Circuit provider, so the only way to model this is to make the 3rd party network 'owned' by the provider providing connectivity to it. If multiple providers are providing circuits to the same Provider Network (e.g. for HA), it is not possible to model the situation sensibly. ### Database changes No model changes would be required. I am not sure if this constraint is enforced in the database (probably not...?). ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:25:23 +01:00
adam closed this issue 2025-12-29 19:25:23 +01:00
adam commented 2025-12-29 19:25:23 +01:00
Author
Owner
Copy Link

@sdktr commented on GitHub (Aug 19, 2021):

You can chain up several circuits to model what you want?

Circuit 1 (provider: Megaport) -A/Z-termination into: - Circuit 2 (provider: Azure, termination: Azure Provider Network)

@sdktr commented on GitHub (Aug 19, 2021): You can chain up several circuits to model what you want? Circuit 1 (provider: Megaport) -A/Z-termination into: - Circuit 2 (provider: Azure, termination: Azure Provider Network)
adam commented 2025-12-29 19:25:24 +01:00
Author
Owner
Copy Link

@ktims commented on GitHub (Aug 19, 2021):

@sdktr Oooh clever, I didn't realize circuits could be connected to each other. I will give that a try, should work.

@ktims commented on GitHub (Aug 19, 2021): @sdktr Oooh clever, I didn't realize circuits could be connected to each other. I will give that a try, should work.
adam commented 2025-12-29 19:25:24 +01:00
Author
Owner
Copy Link

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

Looks like you found a solution.

@jeremystretch commented on GitHub (Oct 5, 2021): Looks like you found a solution.
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 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#5202
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?