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

Provide information about LAG targets in LAG members section #11376

New Issue
Open
opened 2025-12-29 21:44:22 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:44:22 +01:00
Owner
Copy Link

Originally created by @vic-t on GitHub (Jul 14, 2025).

NetBox version

v4.3.3

Feature type

Data model extension

Proposed functionality

In the interface detail view for a LAG interface, there is a section called LAG Members.

In that section, the following information is provided:

  • Parent (Parent device of LAG interface)
  • Interface (Name of interface that is part of the LAG)
  • Type (Interface port type, such as SFP+)

I would request that this section provides information about the cable connections, at least in a simplified way such as this:

  • Parent device (Name of device hosting LAG interface)
  • LAG member interface (Name of physical interface that is part of the LAG)
  • Type of LAG member interface (Interface port type, such as SFP+)
  • Target device (Name of device that the physical interface connects to)
  • Connected Interface (Name of physical interface that is connected to the physical LAG interface)
  • Target LAG name (If the physical interface is part of a LAG, the name would be shown here, otherwise it would remain empty)
  • Type of connected interface (Interface port type.)

The names are just meant for clarity here - I'm certain shorter names could be used in practice.

Use case

It is currently not possible to quickly see how a LAG interface is connected to other devices. In the case of 2 LAG members, I'd have to click on each interface first in order to see their cable connections.

This extended information would be extremely helpful in quickly checking the validity of a LAG setup. For example, if my two LAG members connect to two target interfaces that are not part of a LAG themselves, usually with the same name, this would most likely be an error.

IMO, this change would also solve the request for MC-LAG documentation (#18796) - at least partially.

Database changes

I'm not familiar with the database schema of Netbox. Since the information is readily available behind each interface, I assume this should be a relatively small change.

External dependencies

None

Originally created by @vic-t on GitHub (Jul 14, 2025). ### NetBox version v4.3.3 ### Feature type Data model extension ### Proposed functionality In the interface detail view for a LAG interface, there is a section called `LAG Members`. In that section, the following information is provided: - **Parent** (Parent device of LAG interface) - **Interface** (Name of interface that is part of the LAG) - **Type** (Interface port type, such as SFP+) I would request that this section provides information about the cable connections, at least in a simplified way such as this: - **Parent device** (Name of device hosting LAG interface) - **LAG member interface** (Name of physical interface that is part of the LAG) - **Type of LAG member interface** (Interface port type, such as SFP+) - **Target device** (Name of device that the physical interface connects to) - **Connected Interface** (Name of physical interface that is connected to the physical LAG interface) - **Target LAG name** (If the physical interface is part of a LAG, the name would be shown here, otherwise it would remain empty) - **Type of connected interface** (Interface port type.) The names are just meant for clarity here - I'm certain shorter names could be used in practice. ### Use case It is currently not possible to quickly see how a LAG interface is connected to other devices. In the case of 2 LAG members, I'd have to click on each interface first in order to see their cable connections. This extended information would be extremely helpful in quickly checking the validity of a LAG setup. For example, if my two LAG members connect to two target interfaces that are not part of a LAG themselves, usually with the same name, this would most likely be an error. IMO, this change would also solve the request for MC-LAG documentation (#18796) - at least partially. ### Database changes I'm not familiar with the database schema of Netbox. Since the information is readily available behind each interface, I assume this should be a relatively small change. ### External dependencies None
adam added the type: featurestatus: needs ownernetboxcomplexity: low labels 2025-12-29 21:44:22 +01:00
adam commented 2025-12-29 21:44:22 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 17, 2025):

To accommodate additional info, it probably makes sense to move the current table to a bigger panel, or perhaps even to a separate tab.

@jeremystretch commented on GitHub (Jul 17, 2025): To accommodate additional info, it probably makes sense to move the current table to a bigger panel, or perhaps even to a separate tab.
adam commented 2025-12-29 21:44:22 +01:00
Author
Owner
Copy Link

@PieterL75 commented on GitHub (Sep 24, 2025):

I found this plugin that documents mclag
https://github.com/pv2b/netbox-plugin-mclag
Would be great if it could make it to the core of netbox..

@PieterL75 commented on GitHub (Sep 24, 2025): I found this plugin that documents mclag https://github.com/pv2b/netbox-plugin-mclag Would be great if it could make it to the core of netbox..
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 complexity: low netbox status: needs owner type: feature
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#11376
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?