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 assigning a parent LAG interface belonging to a non-master member in the same virtual chassis #3988

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

Originally created by @jeremystretch on GitHub (Aug 14, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.6.9
  • NetBox version: 2.9-beta2

Proposed Functionality

When a device is a member of a virtual chassis, an interface on that device should be able to be assigned to any LAG interface on any member of the same virtual chassis. Currently, a VC member interface can be assigned only to a LAG on the VC master.

Use Case

Beginning with NetBox v2.9, the designation of a master device for a virtual chassis is optional. It should be possible to assign LAGs across members of the same VC regardless of master designation.

Database Changes

None

External Dependencies

None

Originally created by @jeremystretch on GitHub (Aug 14, 2020). Originally assigned to: @jeremystretch on GitHub. ### Environment * Python version: 3.6.9 * NetBox version: 2.9-beta2 ### Proposed Functionality When a device is a member of a virtual chassis, an interface on that device should be able to be assigned to any LAG interface on any member of the same virtual chassis. Currently, a VC member interface can be assigned only to a LAG on the VC master. ### Use Case Beginning with NetBox v2.9, the designation of a master device for a virtual chassis is optional. It should be possible to assign LAGs across members of the same VC regardless of master designation. ### Database Changes None ### External Dependencies None
adam added the status: acceptedtype: featurebeta labels 2025-12-29 18:32:29 +01:00
adam closed this issue 2025-12-29 18:32:29 +01:00
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 beta status: accepted 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#3988
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?