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

LAG ports can’t span multiple stack members #3041

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

Originally created by @millijuna on GitHub (Dec 4, 2019).

Environment

  • Python version: 3.7.3
  • NetBox version: 2.6.7

I have a 3 switch Cisco 3750 stack which is connected to another switch via a two port LAG. Each of the LAG members is on a different stack member.

In netbox, the LAG is (for some reason) attached to member :1 of the stack. when I try to add the member interfaces (from stack members 2 and 3), the interface editing interface can’t find the LAG on stack member 1.

Edit: this happens when the LAG wasn’t created on the stack master.

Steps to Reproduce

  1. Create a 3 member stack
  2. Create a LAG interface on one stack member
  3. Try to add an interface from another stack member to that LAG. Can’t be done.

I expect that I would be able to add any interface from any stack member to the LAG.

Observed Behavior

Originally created by @millijuna on GitHub (Dec 4, 2019). <!-- NOTE: This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.7.3 * NetBox version: 2.6.7 I have a 3 switch Cisco 3750 stack which is connected to another switch via a two port LAG. Each of the LAG members is on a different stack member. In netbox, the LAG is (for some reason) attached to member :1 of the stack. when I try to add the member interfaces (from stack members 2 and 3), the interface editing interface can’t find the LAG on stack member 1. Edit: this happens when the LAG wasn’t created on the stack master. ### Steps to Reproduce 1. Create a 3 member stack 2. Create a LAG interface on one stack member 3. Try to add an interface from another stack member to that LAG. Can’t be done. <!-- What did you expect to happen? --> I expect that I would be able to add any interface from any stack member to the LAG. <!-- What happened instead? --> ### Observed Behavior
adam closed this issue 2025-12-29 18:25:04 +01:00
adam commented 2025-12-29 18:25:04 +01:00
Author
Owner
Copy Link

@hSaria commented on GitHub (Dec 4, 2019):

I believe this is due to how the list of vc_interfaces is acquired, namely the condition below. Only the master of a virtual chassis is allowed to see the interfaces of other members in the same virtual chassis.
1048d3909b/netbox/dcim/models.py (L1820-L1821)

@hSaria commented on GitHub (Dec 4, 2019): I believe this is due to how the list of `vc_interfaces` is acquired, namely the condition below. Only the master of a virtual chassis is allowed to see the interfaces of other members in the same virtual chassis. https://github.com/netbox-community/netbox/blob/1048d3909b9e5fe96acc793c35bbbe9820dacefb/netbox/dcim/models.py#L1820-L1821
adam commented 2025-12-29 18:25:05 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 5, 2019):

@hSaria is correct: The LAG interface must be created on the stack master. Non-master members can only see their own interfaces.

@jeremystretch commented on GitHub (Dec 5, 2019): @hSaria is correct: The LAG interface must be created on the stack master. Non-master members can only see their own interfaces.
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#3041
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?