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

Link Aggregation Issue on Virtual Chassis #6209

New Issue
Closed
opened 2025-12-29 19:38:03 +01:00 by adam · 4 comments
adam commented 2025-12-29 19:38:03 +01:00
Owner
Copy Link

Originally created by @cobusv on GitHub (Mar 14, 2022).

NetBox version

v3.1.8

Python version

3.8

Steps to Reproduce

We are making use of virtual chassis in the scenarios where we have two or more physical switches stacked to one another. This works well in general as we can keep track of all physically installed equipment on our network. The issue we have is that Link Aggregation interfaces created on one physical member of the Virtual Chassis is not seen across all the members, this limits our ability to add all member interfaces of the Link Aggregation to the LAG that may exist across all member switches of the virtual chassis.

Expected Behavior

Must be able to add all member interfaces of the Link Aggregation to the LAG that may exist across all member switches of the virtual chassis.

Observed Behavior

no error just cannot do it

Originally created by @cobusv on GitHub (Mar 14, 2022). ### NetBox version v3.1.8 ### Python version 3.8 ### Steps to Reproduce We are making use of virtual chassis in the scenarios where we have two or more physical switches stacked to one another. This works well in general as we can keep track of all physically installed equipment on our network. The issue we have is that Link Aggregation interfaces created on one physical member of the Virtual Chassis is not seen across all the members, this limits our ability to add all member interfaces of the Link Aggregation to the LAG that may exist across all member switches of the virtual chassis. ### Expected Behavior Must be able to add all member interfaces of the Link Aggregation to the LAG that may exist across all member switches of the virtual chassis. ### Observed Behavior no error just cannot do it
adam added the type: bugstatus: revisions needed labels 2025-12-29 19:38:03 +01:00
adam closed this issue 2025-12-29 19:38:03 +01:00
adam commented 2025-12-29 19:38:04 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 14, 2022):

Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.

@jeremystretch commented on GitHub (Mar 14, 2022): Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.
adam commented 2025-12-29 19:38:04 +01:00
Author
Owner
Copy Link

@cobusv commented on GitHub (Mar 16, 2022):

Hi Jeremy,

As requested herewith some more info;

We are making use of virtual chassis in the scenarios where we have two or more physical switches stacked to one another. This works well in general as we can keep track of all physically installed equipment on our network. The issue we have is that Link Aggregation interfaces created on one physical member of the Virtual Chassis is not seen across all the members, this limits our ability to add all member interfaces of the Link Aggregation to the LAG that may exist across all member switches of the virtual chassis.

Import the following to Organization Sites:
name,slug,status
Site-A,site-a,active

Import the following to Device Roles:
name,slug,color
Switch,switch,00ff00

Import the following to Manufacturers:
name,slug
ManufacturerA,manufacturera

Add the following Device Type:
Manufacturer: ManufacturerA
Model: ModelA
Slug: modela
Height (U): 1
Import the following to Devices:
name,device_role,manufacturer,device_type,status,site
Device-A1,Switch,ManufacturerA,ModelA,active,Site-A
Device-A2,Switch,ManufacturerA,ModelA,active,Site-A

Add the following to Virtual Chassis:
Name: Device-A
Member Devices: Device-A1, Device-A2
Initial position: 1

Import the following Interfaces:
device,name,type,enabled
Device-A1,10GE1/0/1,10gbase-x-sfpp,true
Device-A1,LAG1,lag,true
Device-A2,10GE2/0/1,10gbase-x-sfpp,true

Interfaces seen on Device-A1

@.***
cid:4289548986*image001.png@01D83913.EA0F9040

Able to add interface 10GE1/0/1 on Device-A1 to LAG1

@.***

cid:4289548986*image002.png@01D83913.EA0F9040

Interfaces seen on Device-A2 (LAG1 is not seen on Device-A2 so we cannot add interface 10GE2/0/1 to LAG1)

@.***

cid:4289548986*image003.png@01D83913.EA0F9040

With the above setup we can add interface 10GE1/0/1 on Device-A1 to LAG1 however we cannot add interface 10GE2/0/1 to LAG1 as Netbox does not see Link Aggregations created on one member device of a virtual chassis accross all member devices. In practice a Link Aggregation created on a virtual chassis is seen on all member devices. The same is the case for Virtual Interfaces as well which would in practice be seen across all member devices of a Virtual Chassis.

@cobusv commented on GitHub (Mar 16, 2022): Hi Jeremy, As requested herewith some more info; We are making use of virtual chassis in the scenarios where we have two or more physical switches stacked to one another. This works well in general as we can keep track of all physically installed equipment on our network. The issue we have is that Link Aggregation interfaces created on one physical member of the Virtual Chassis is not seen across all the members, this limits our ability to add all member interfaces of the Link Aggregation to the LAG that may exist across all member switches of the virtual chassis. Import the following to Organization Sites: name,slug,status Site-A,site-a,active Import the following to Device Roles: name,slug,color Switch,switch,00ff00 Import the following to Manufacturers: name,slug ManufacturerA,manufacturera Add the following Device Type: Manufacturer: ManufacturerA Model: ModelA Slug: modela Height (U): 1 Import the following to Devices: name,device_role,manufacturer,device_type,status,site Device-A1,Switch,ManufacturerA,ModelA,active,Site-A Device-A2,Switch,ManufacturerA,ModelA,active,Site-A Add the following to Virtual Chassis: Name: Device-A Member Devices: Device-A1, Device-A2 Initial position: 1 Import the following Interfaces: device,name,type,enabled Device-A1,10GE1/0/1,10gbase-x-sfpp,true Device-A1,LAG1,lag,true Device-A2,10GE2/0/1,10gbase-x-sfpp,true Interfaces seen on Device-A1 ***@***.*** cid:4289548986*image001.png@01D83913.EA0F9040 Able to add interface 10GE1/0/1 on Device-A1 to LAG1 ***@***.*** cid:4289548986*image002.png@01D83913.EA0F9040 Interfaces seen on Device-A2 (LAG1 is not seen on Device-A2 so we cannot add interface 10GE2/0/1 to LAG1) ***@***.*** cid:4289548986*image003.png@01D83913.EA0F9040 With the above setup we can add interface 10GE1/0/1 on Device-A1 to LAG1 however we cannot add interface 10GE2/0/1 to LAG1 as Netbox does not see Link Aggregations created on one member device of a virtual chassis accross all member devices. In practice a Link Aggregation created on a virtual chassis is seen on all member devices. The same is the case for Virtual Interfaces as well which would in practice be seen across all member devices of a Virtual Chassis.
adam commented 2025-12-29 19:38:04 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Mar 18, 2022):

You need to set your master and then create the lag on the master.

@DanSheps commented on GitHub (Mar 18, 2022): You need to set your master and then create the lag on the master.
adam commented 2025-12-29 19:38:04 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 22, 2022):

I'm going to close this under the assumption that Dan's pointer above has resolved this issue for you. If you would like further assistance, please open a discussion.

@jeremystretch commented on GitHub (Mar 22, 2022): I'm going to close this under the assumption that Dan's pointer above has resolved this issue for you. If you would like further assistance, please open a [discussion](https://github.com/netbox-community/netbox/discussions/new).
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: revisions needed type: bug
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#6209
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?