-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Interface Bridges in Device Type #8272
Comments
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. Please see our contributing guide. |
Just wanted to add that it would be nice to be able to do the same for Parent interface and LAG interface. I've run into both situations recently. On our aggregation switches, we create a LAG for the uplink and it would certainly save a step to have that already set up in the device template. The bigger issue I had recently was with the parent/child relationship, as we have some devices with bulk connectors that we currently model as a physical connector with virtual child interfaces under it and it's cumbersome having to remember to create those relationships each time a new device is added. Please let me know if I need to open a separate FR or if it's sufficient to update this one to include all the interface relationship types. I assume the implementation for one should be almost identical for the others, but maybe I'm missing something. |
NetBox version
v3.1.4
Feature type
Change to existing functionality
Proposed functionality
Currently you can only bridge interfaces if the device already exists. It would be nice to "pre-bridge" interfaces in the device Type.
Use case
When you have devices like mediaconverter, currently you have to manually bridge the 2 interfaces after creating the device for every single device. It would be a lot easier to bridge the interfaces in the device type.
Database changes
No response
External dependencies
No response
The text was updated successfully, but these errors were encountered: