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

Assign Circuits to Virtual Interfaces or Multiple Circuits to single Interface #1827

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

Originally created by @jvanderaa on GitHub (Jul 3, 2018).

Issue type

[x] Feature request
[ ] Bug report
[ ] Documentation
[ ] Housekeeping

Environment

  • Python version: 3.6.5
  • NetBox version: 2.3.4

Description

Trying to model out provider ports, where there are effectively sub circuits within the single parent circuit. Ideally this could get tied as a child to a parent of the larger provider port. The A-side would be the parent, and the z-side would be a device. In order to do this today we would create a virtual interface tied to the primary interface. This however won't accept a circuit. So then we would have to create it as type physical interface, even though it would be a virtual.

Originally created by @jvanderaa on GitHub (Jul 3, 2018). <!-- Before opening a new issue, please search through the existing issues to see if your topic has already been addressed. Note that you may need to remove the "is:open" filter from the search bar to include closed issues. Check the appropriate type for your issue below by placing an x between the brackets. For assistance with installation issues, or for any other issues other than those listed below, please raise your topic for discussion on our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please note that issues which do not fall under any of the below categories will be closed. Due to an excessive backlog of feature requests, we are not currently accepting any proposals which extend NetBox's feature scope. Do not prepend any sort of tag to your issue's title. An administrator will review your issue and assign labels as appropriate. ---> ### Issue type [x] Feature request <!-- An enhancement of existing functionality --> [ ] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> [ ] Housekeeping <!-- Changes pertaining to the codebase itself --> ### Environment * Python version: 3.6.5 * NetBox version: 2.3.4 ### Description Trying to model out provider ports, where there are effectively sub circuits within the single parent circuit. Ideally this could get tied as a child to a parent of the larger provider port. The A-side would be the parent, and the z-side would be a device. In order to do this today we would create a virtual interface tied to the primary interface. This however won't accept a circuit. So then we would have to create it as type physical interface, even though it would be a virtual.
adam closed this issue 2025-12-29 17:19:33 +01:00
adam commented 2025-12-29 17:19:33 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 3, 2018):

NetBox does not support modeling virtual circuits. Circuits in NetBox are physical link, and as such can only terminate to physical interfaces. Please see the discussion in #790 for more detail.

@jeremystretch commented on GitHub (Jul 3, 2018): NetBox does not support modeling virtual circuits. Circuits in NetBox are physical link, and as such can only terminate to physical interfaces. Please see the discussion in #790 for more detail.
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
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#1827
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?