Endpoint for LAG interface #8767

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

Originally created by @PieterL75 on GitHub (Oct 23, 2023).

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

Originally created by @PieterL75 on GitHub (Oct 23, 2023). ### 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_
adam added the type: featurepending closure labels 2025-12-29 20:40:59 +01:00
adam closed this issue 2025-12-29 20:40:59 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 22, 2024):

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 (Jan 22, 2024): 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 (Feb 22, 2024):

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 (Feb 22, 2024): 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#8767