Closed PieterL75 closed 8 months ago
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.
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.
NetBox version
v3.6.4
Feature type
Data model extension
Proposed functionality
a 'LAG' interface is a virtual interface, and not linkable to another interface, and cannot be traced The child interfaces are physical interfaces and link to another device's interfaces, and can be traced.
I would like to see what 'LAG' interface is of the remote device(s) it connects to. This will require a LAG interface to be 'traced', and show the multiple paths the LAG takes. As LAG can be a MLAG, the trace could go between different devices.
Use case
When creating deviceconfigs, it is partical to see what the remote MLAG name/id is, so that interface descriptions can be created. It also provides a physical topology of the LAG connections
Database changes
No response
External dependencies
No response