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

Allow to add child module interface to parent device LAG #974

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

Originally created by @zhaknafein on GitHub (May 19, 2017).

Issue Type: Feature Request

Scenario: Cisco Catalyst 6500 with chassis as parent device, 2 x 24 ports SFP interface modules as children devices. There is a PortChannel configured with one port on each SFP module (say Gig1/1 and Gig2/1).

If i create a LAG interface on one module, i can only add its interfaces in it, the other module doesn't see the LAG.

It would be nice if i could create the LAG interface on the parent device (the chassis) and be able to add the children modules' interfaces to it.

This would also probably work for stacking devices where i can create the stack as a "virtual" device, with the physical units as children devices (let's say 2 Catalyst 3750).

Originally created by @zhaknafein on GitHub (May 19, 2017). ### Issue Type: Feature Request _Scenario:_ Cisco Catalyst 6500 with chassis as parent device, 2 x 24 ports SFP interface modules as children devices. There is a PortChannel configured with one port on each SFP module (say Gig1/1 and Gig2/1). If i create a LAG interface on one module, i can only add its interfaces in it, the other module doesn't see the LAG. It would be nice if i could create the LAG interface on the parent device (the chassis) and be able to add the children modules' interfaces to it. This would also probably work for stacking devices where i can create the stack as a "virtual" device, with the physical units as children devices (let's say 2 Catalyst 3750).
adam closed this issue 2025-12-29 16:27:31 +01:00
adam commented 2025-12-29 16:27:31 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 19, 2017):

It sounds like you're using device bays to represent line cards. Device bays only hold child devices, which have their own control planes and thus cannot share interfaces among them (like blade servers within a chassis).

#824 has been opened to add the concept of a modular line card within a chassis, to which interfaces can be attached, but for now just create the interfaces on the chassis device. (Line cards can still be tracked for inventory purposes as InventoryItems.)

@jeremystretch commented on GitHub (May 19, 2017): It sounds like you're using device bays to represent line cards. Device bays only hold child devices, which have their own control planes and thus cannot share interfaces among them (like blade servers within a chassis). #824 has been opened to add the concept of a modular line card within a chassis, to which interfaces can be attached, but for now just create the interfaces on the chassis device. (Line cards can still be tracked for inventory purposes as InventoryItems.)
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#974
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?