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

Support LAG interfaces in Device type definition #8505

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

Originally created by @oneone84 on GitHub (Aug 24, 2023).

NetBox version

v.3.6 beta2

Feature type

Data model extension

Proposed functionality

When defining a device type I want to be able to set a parent LAG interface in the interface template. As of now, It seems like I can only connect them to a bridge interface.
bild

Also, when cloning a device I would like the clone to retain child interface to LAG relationship on the cloned device (to the new interface of course).

Use case

We always connect our servers using one or more LAG interfaces with 2 physical child interfaces and as of now we have to click alot to relate the physical interfaces to the LAG interface.

I would wish to create this from template, or as a workaround at least be able to clone a server with this already setup.

Database changes

don't think so.

External dependencies

don't think so.

Originally created by @oneone84 on GitHub (Aug 24, 2023). ### NetBox version v.3.6 beta2 ### Feature type Data model extension ### Proposed functionality When defining a device type I want to be able to set a parent LAG interface in the interface template. As of now, It seems like I can only connect them to a bridge interface. ![bild](https://github.com/netbox-community/netbox/assets/44062096/d3647a64-88de-4d60-a183-810fd28c744d) Also, when cloning a device I would like the clone to retain child interface to LAG relationship on the cloned device (to the new interface of course). ### Use case We always connect our servers using one or more LAG interfaces with 2 physical child interfaces and as of now we have to click alot to relate the physical interfaces to the LAG interface. I would wish to create this from template, or as a workaround at least be able to clone a server with this already setup. ### Database changes don't think so. ### External dependencies don't think so.
adam added the type: feature label 2025-12-29 20:37:32 +01:00
adam closed this issue 2025-12-29 20:37:33 +01:00
adam commented 2025-12-29 20:37:33 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 24, 2023):

The device type is a hardware definition, and has only attributes which are consistent among all its instances. A LAG is a software configuration that varies among instances, so it would not be appropriate to add to the interface template model.

You might consider using custom scripts to automate the creation of LAG interfaces and other configuration items when instantiating devices.

@jeremystretch commented on GitHub (Aug 24, 2023): The device type is a hardware definition, and has only attributes which are consistent among all its instances. A LAG is a software configuration that varies among instances, so it would not be appropriate to add to the interface template model. You might consider using custom scripts to automate the creation of LAG interfaces and other configuration items when instantiating devices.
adam commented 2025-12-29 20:37:33 +01:00
Author
Owner
Copy Link

@oneone84 commented on GitHub (Aug 24, 2023):

The device type is a hardware definition, and has only attributes which are consistent among all its instances. A LAG is a software configuration that varies among instances, so it would not be appropriate to add to the interface template model.

You might consider using custom scripts to automate the creation of LAG interfaces and other configuration items when instantiating devices.

Hi Jeremy, can you direct me to some instructions on how to create such a script? Creating the physical ports and lags are not a problem, but linking them together will be alot of manual work, if I can't automate it.

@oneone84 commented on GitHub (Aug 24, 2023): > The device type is a hardware definition, and has only attributes which are consistent among all its instances. A LAG is a software configuration that varies among instances, so it would not be appropriate to add to the interface template model. > > You might consider using custom scripts to automate the creation of LAG interfaces and other configuration items when instantiating devices. Hi Jeremy, can you direct me to some instructions on how to create such a script? Creating the physical ports and lags are not a problem, but linking them together will be alot of manual work, if I can't automate it.
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#8505
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?