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

Addition of Logical Interface Type #3107

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

Originally created by @nathbooth on GitHub (Jan 2, 2020).

Environment

  • Python version: 3.7
  • NetBox version: v2.6.9

Addition of sub-interface in dcim/interfaces as an interface type

Proposed Functionality

Addition of type: 'logical' to interface types under 'Virtual Interfaces' with no restriction on parent LAGs, the current type of virtual is restricted to not allow that parent to be a LAG.

Use Case

When using Link Aggregation on layer-3 capable devices it is common to have layer 3 sub-interfaces on devices. At present this is possible, but the type can only be defined at 'Other'

Database Changes

None

External Dependencies

None

Originally created by @nathbooth on GitHub (Jan 2, 2020). ### Environment * Python version: 3.7 * NetBox version: v2.6.9 Addition of sub-interface in dcim/interfaces as an interface type ### Proposed Functionality Addition of type: 'logical' to interface types under 'Virtual Interfaces' with no restriction on parent LAGs, the current type of virtual is restricted to not allow that parent to be a LAG. ### Use Case When using Link Aggregation on layer-3 capable devices it is common to have layer 3 sub-interfaces on devices. At present this is possible, but the type can only be defined at 'Other' ### Database Changes None ### External Dependencies None
adam closed this issue 2025-12-29 18:25:41 +01:00
adam commented 2025-12-29 18:25:42 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jan 2, 2020):

Hello nathbooth,

For a layer3 sub-interface on a LAG, you would still use Virtual. Parent LAG's associate Physical ports as members of that port channel. A logical interface that is set with a parent lag would be considered part of that port channel (member interface).

You would have them setup in the following manner:

Port-Channel1 - LAG
Port-Channel1.23 - Virtual (This is one of your L3 Po's)
Port-Channel1.45 - Virtual (This is one of your L3 Po's)

If you have further questions regarding this, please head on over to the netbox discussion group at https://groups.google.com/forum/#!forum/netbox-discuss and feel free to ask some more questions there.

I am going to close this out for now.

@DanSheps commented on GitHub (Jan 2, 2020): Hello nathbooth, For a layer3 sub-interface on a LAG, you would still use Virtual. Parent LAG's associate Physical ports as members of that port channel. A logical interface that is set with a parent lag would be considered part of that port channel (member interface). You would have them setup in the following manner: Port-Channel1 - LAG Port-Channel1.23 - Virtual (This is one of your L3 Po's) Port-Channel1.45 - Virtual (This is one of your L3 Po's) If you have further questions regarding this, please head on over to the netbox discussion group at https://groups.google.com/forum/#!forum/netbox-discuss and feel free to ask some more questions there. I am going to close this out for now.
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#3107
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?