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 LAG to span over multple Devices (evpn multihoming) #2486

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

Originally created by @spolack on GitHub (Apr 1, 2019).

Proposed Functionality

A LAG could span over multiple devices. There should be a way to model this in Netbox. As LAG interface names could differ across devices (i.e. ae0 on Device A, ae25 on Device B) we should be able to link LAG interfaces somehow, so they could share VLANS, tags and mtu and other properties.

Use Case

In order to model "eVPN multihoming", we'd like to span a LAG over multiple devices in Netbox. This would be also useful to model MC-LAG.

Database Changes

This could be accomplished by implementing a virtual parent lag interface, which is not assigned to any device. LAG interfaces could reference to that virtual parent lag interface.

Originally created by @spolack on GitHub (Apr 1, 2019). ### Proposed Functionality A LAG could span over multiple devices. There should be a way to model this in Netbox. As LAG interface names could differ across devices (i.e. ae0 on Device A, ae25 on Device B) we should be able to link LAG interfaces somehow, so they could share VLANS, tags and mtu and other properties. ### Use Case In order to model "eVPN multihoming", we'd like to span a LAG over multiple devices in Netbox. This would be also useful to model MC-LAG. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes This could be accomplished by implementing a virtual parent lag interface, which is not assigned to any device. LAG interfaces could reference to that virtual parent lag interface.
adam added the status: duplicate label 2025-12-29 18:19:16 +01:00
adam closed this issue 2025-12-29 18:19:16 +01:00
adam commented 2025-12-29 18:19:17 +01:00
Author
Owner
Copy Link

@lampwins commented on GitHub (Apr 2, 2019):

While I know you mention EVPN, from a modeling standpoint this would be the same as MLAG which would be a duplicate of https://github.com/digitalocean/netbox/issues/2830

@lampwins commented on GitHub (Apr 2, 2019): While I know you mention EVPN, from a modeling standpoint this would be the same as MLAG which would be a duplicate of https://github.com/digitalocean/netbox/issues/2830
adam commented 2025-12-29 18:19:17 +01:00
Author
Owner
Copy Link

@spolack commented on GitHub (Apr 2, 2019):

The multichassis functionality is accomplished by proprietary hacks performed on the forwarding plane, which vary in their implementation among platforms and are out of scope for NetBox.

This is not the case with evpn - Thats non-proprietary and shouldnt be considered as a hack, although it might look like that from a tradional network engineer perspective.

Please reevalute this, as EVPN + Multihoming will definately become a topic in near future.

@spolack commented on GitHub (Apr 2, 2019): > The multichassis functionality is accomplished by proprietary hacks performed on the forwarding plane, which vary in their implementation among platforms and are out of scope for NetBox. This is not the case with evpn - Thats non-proprietary and shouldnt be considered as a hack, although it might look like that from a tradional network engineer perspective. Please reevalute this, as EVPN + Multihoming will definately become a topic in near future.
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
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#2486
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?