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

Model Internal Circuits #6361

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

Originally created by @grbeneke on GitHub (Apr 15, 2022).

NetBox version

v3.2

Feature type

Change to existing functionality

Proposed functionality

Allow the circuit model to represent a logical or physical circuit being delivered from the infrastructure modeled within NetBox.

A circuit endpoint would exist on an interface or front port (rather then connected to).

This could be simply for tracking demarcation points for circuit based services delivered to external parties but should also support the onward connection to infrastructure of tenants who may be modeled in the NetBox instance.

Use case

Representation of L2VPN, E-LINE, OTN and other logical circuit-style services being delivered using the modeled infrastructure. These circuits typically exist between two endpoints and pass through many intermediate devices. They don't follow the physical infrastructure directly.

Associating a cable trace with a single circuit identifier based in modeled ports being the demarcation of the ends of the defined circuit. This is potentially more difficult as it complicates the cable trace logic with 2 parallel paths representing the same thing.

Database changes

Unknown

External dependencies

No response

Originally created by @grbeneke on GitHub (Apr 15, 2022). ### NetBox version v3.2 ### Feature type Change to existing functionality ### Proposed functionality Allow the circuit model to represent a logical or physical circuit being delivered from the infrastructure modeled within NetBox. A circuit endpoint would exist on an interface or front port (rather then connected to). This could be simply for tracking demarcation points for circuit based services delivered to external parties but should also support the onward connection to infrastructure of tenants who may be modeled in the NetBox instance. ### Use case Representation of L2VPN, E-LINE, OTN and other logical circuit-style services being delivered using the modeled infrastructure. These circuits typically exist between two endpoints and pass through many intermediate devices. They don't follow the physical infrastructure directly. Associating a cable trace with a single circuit identifier based in modeled ports being the demarcation of the ends of the defined circuit. This is potentially more difficult as it complicates the cable trace logic with 2 parallel paths representing the same thing. ### Database changes Unknown ### External dependencies _No response_
adam added the type: featurestatus: duplicate labels 2025-12-29 19:39:49 +01:00
adam closed this issue 2025-12-29 19:39:49 +01:00
adam commented 2025-12-29 19:39:50 +01:00
Author
Owner
Copy Link

@grbeneke commented on GitHub (Apr 15, 2022):

Seems that this has a lot in common with #8157

@grbeneke commented on GitHub (Apr 15, 2022): Seems that this has a lot in common with #8157
adam commented 2025-12-29 19:39:50 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Apr 16, 2022):

Duplicate of #8157

@DanSheps commented on GitHub (Apr 16, 2022): Duplicate of #8157
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#6361
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?