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 visibility between Parent and Child devices. #2265

New Issue
Closed
opened 2025-12-29 17:24:18 +01:00 by adam · 1 comment
adam commented 2025-12-29 17:24:18 +01:00
Owner
Copy Link

Originally created by @marcinkorzycki on GitHub (Jan 5, 2019).

Environment

  • Python version: 3.5.3

  • NetBox version: 2.5.2

    I would like to have visibility of LAG created in Parent Core Switch on Child Core Linecard added via Device Bay. I have Dell C9010 which is an Network Chassis with modules. Every Port-Channel is visible on whole core switch, not only on specific module.

Steps to Reproduce

screenshot_1
screenshot_2
screenshot_3

Expected Behavior

Enable LAG created in Parent Device on Child Device or additional checkbox while creating LAG interface in parent device that it can be visible on child device.

Observed Behavior

Can't choose LAG created in Parent Device on Child Device. It is visible only in Parent Device.

Originally created by @marcinkorzycki on GitHub (Jan 5, 2019). ### Environment * Python version: 3.5.3 * NetBox version: 2.5.2 I would like to have visibility of LAG created in Parent Core Switch on Child Core Linecard added via Device Bay. I have Dell C9010 which is an Network Chassis with modules. Every Port-Channel is visible on whole core switch, not only on specific module. ### Steps to Reproduce ![screenshot_1](https://user-images.githubusercontent.com/24276423/50728000-d6654780-1123-11e9-95b1-5ea7f055f2f9.png) ![screenshot_2](https://user-images.githubusercontent.com/24276423/50728002-d8c7a180-1123-11e9-9022-2968e82c3348.png) ![screenshot_3](https://user-images.githubusercontent.com/24276423/50728003-d9f8ce80-1123-11e9-916d-83f582993e99.png) ### Expected Behavior Enable LAG created in Parent Device on Child Device or additional checkbox while creating LAG interface in parent device that it can be visible on child device. ### Observed Behavior Can't choose LAG created in Parent Device on Child Device. It is visible only in Parent Device.
adam closed this issue 2025-12-29 17:24:18 +01:00
adam commented 2025-12-29 17:24:19 +01:00
Author
Owner
Copy Link

@lampwins commented on GitHub (Jan 5, 2019):

This is a misuse of Parent/Child devices. This concept in NetBox is meant for chassis-based devices in which the chassis provides nothing more than power to a child in a device bay. Think blade servers, not networking line cards. When the line card is "dumb" meaning that outside of the chassis, it serves no purpose at all, it should not be modeled as a child device, because it is not a device at all; it is just a line card that provides interfaces.

Instead, create your chassis as the normal device and add all the line card interfaces directly to it. You can then add the line cards as inventory items on the chassis if you so choose.

@lampwins commented on GitHub (Jan 5, 2019): This is a misuse of Parent/Child devices. This concept in NetBox is meant for chassis-based devices in which the chassis provides nothing more than power to a child in a device bay. Think blade servers, not networking line cards. When the line card is "dumb" meaning that outside of the chassis, it serves no purpose at all, it should not be modeled as a child device, because it is not a device at all; it is just a line card that provides interfaces. Instead, create your chassis as the normal device and add all the line card interfaces directly to it. You can then add the line cards as inventory items on the chassis if you so choose.
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
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#2265
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?