Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
zhaknafein opened this issue May 19, 2017 · 1 comment
Closed

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

zhaknafein opened this issue May 19, 2017 · 1 comment

Comments

@zhaknafein
Copy link

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).

@jeremystretch
Copy link
Member

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.)

@lock lock bot locked as resolved and limited conversation to collaborators Jan 18, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants