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

LAG interfaces can be connected via CSV import #1757

New Issue
Closed
opened 2025-12-29 16:35:02 +01:00 by adam · 1 comment
adam commented 2025-12-29 16:35:02 +01:00
Owner
Copy Link

Originally created by @mandarg on GitHub (May 29, 2018).

An example scenario:

  • There are two devices, test1 and test2.
  • test1 has a LAG bundle po1 consisting of intf0/1 and intf0/2
  • test2 has a LAG bundle po2 consisting of intf0/1 and intf0/2
  • test1:intf0/1 is connected to test2:intf0/1
  • test1:intf0/2 is connected to test2:intf0/2

In order to represent that their LAG bundles are also "connected", I connected up test1:po1 to test2:po2 as well (connections displayed as below):

interface-connections-view

Fig 1: Devices > Interface connections view

Note that this is not possible to easily do using the standard UI controls (there is no connection button on a LAG interface). However, it works as expected through "Import Connections" or the API.

At this point, I can view test1:po1 and test2:po2 as connected in the Interface Connections view, but if I go to the test1 interface view or the test2 interface view (both shown below), I cannot see the connection.

test1-interfaces

Fig 2: test1 Interfaces section

test2-interfaces

Fig 3: test2 Interfaces section

Should this be rectified? For example, I would expect a connection to test2:po1 to be shown against po1 in the interfaces view of test1 above (Fig 2.)

Originally created by @mandarg on GitHub (May 29, 2018). An example scenario: - There are two devices, `test1` and `test2`. - `test1` has a LAG bundle `po1` consisting of `intf0/1` and `intf0/2` - `test2` has a LAG bundle `po2` consisting of `intf0/1` and `intf0/2` - `test1:intf0/1` is connected to `test2:intf0/1` - `test1:intf0/2` is connected to `test2:intf0/2` In order to represent that their LAG bundles are also "connected", I connected up `test1:po1` to `test2:po2` as well (connections displayed as below): <img width="799" alt="interface-connections-view" src="https://user-images.githubusercontent.com/160992/40686809-914ed640-6366-11e8-8b4b-1ee61ed99f89.png"> Fig 1: **Devices > Interface connections** view ------------------------ _Note that this is not possible to easily do using the standard UI controls (there is no connection button on a LAG interface). However, it works as expected through "Import Connections" or the API._ At this point, I can view `test1:po1` and `test2:po2` as connected in the Interface Connections view, but if I go to the `test1` interface view or the `test2` interface view (both shown below), I cannot see the connection. <img width="1056" alt="test1-interfaces" src="https://user-images.githubusercontent.com/160992/40686836-a5a2ff04-6366-11e8-8443-e91195229eef.png"> Fig 2: `test1` Interfaces section ------------------------ <img width="1059" alt="test2-interfaces" src="https://user-images.githubusercontent.com/160992/40686842-a7b6541c-6366-11e8-8e17-1f0b3f7ba2a3.png"> Fig 3: `test2` Interfaces section ------------------------ Should this be rectified? For example, I would expect a connection to `test2:po1` to be shown against `po1` in the interfaces view of `test1` above (Fig 2.)
adam added the type: bugstatus: accepted labels 2025-12-29 16:35:02 +01:00
adam closed this issue 2025-12-29 16:35:02 +01:00
adam commented 2025-12-29 16:35:03 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 6, 2018):

This is a bug: it should not be possible to connect LAG interfaces, as they are virtual. It seems the validation is not being enforced during import.

@jeremystretch commented on GitHub (Jun 6, 2018): This is a bug: it should not be possible to connect LAG interfaces, as they are virtual. It seems the validation is not being enforced during import.
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 status: accepted type: bug
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#1757
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?