Importing Interfaces with assigned LAG from different Virtual Chassis Member #7122

Closed
opened 2025-12-29 20:19:27 +01:00 by adam · 2 comments
Owner

Originally created by @willflo on GitHub (Oct 19, 2022).

NetBox version

v3.3.1

Feature type

New functionality

Proposed functionality

Hey,
we are currently working on importing switches. Since we are using a lot of Stacks (collection of multiple switches working as one virtual) we are creating virtual chassis to showcase switch stacks. In the moment we are trying to import interfaces via the form we can't assign an Interface from Member 5 for example in a LAG which is configured on Member 1. Manually after the creation of the interface its working but not for an import of multiple interfaces.

Use case

Gives the opportunity to import switch stacks with all the proper interface to LAG assignments.

Database changes

No response

External dependencies

No response

Originally created by @willflo on GitHub (Oct 19, 2022). ### NetBox version v3.3.1 ### Feature type New functionality ### Proposed functionality Hey, we are currently working on importing switches. Since we are using a lot of Stacks (collection of multiple switches working as one virtual) we are creating virtual chassis to showcase switch stacks. In the moment we are trying to import interfaces via the form we can't assign an Interface from Member 5 for example in a LAG which is configured on Member 1. Manually after the creation of the interface its working but not for an import of multiple interfaces. ### Use case Gives the opportunity to import switch stacks with all the proper interface to LAG assignments. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closure labels 2025-12-29 20:19:27 +01:00
adam closed this issue 2025-12-29 20:19:27 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Dec 19, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Dec 19, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@github-actions[bot] commented on GitHub (Jan 18, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jan 18, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7122