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.

Sign up for GitHub

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

Jump to bottom

Add support for Port-Channel in Network Services #3120

Open
1 task done
theotherguy2175 opened this issue Aug 31, 2023 · 5 comments · May be fixed by #5019
Open
1 task done

Add support for Port-Channel in Network Services #3120

theotherguy2175 opened this issue Aug 31, 2023 · 5 comments · May be fixed by #5019
Assignees
@bjmeuer
Labels
type: enhancement New feature or request

Comments

@theotherguy2175
Copy link

Enhancement summary

Currently in network services. For a vrf to be defined you have to either have a l3_interface or a svi, is it possible to include port-channels into this feature? It looks like it does work, but gives a notification that it's not a supported.

Which component of AVD is impacted

eos_designs, eos_cli_config_gen

Use case example

vrf to be defined you have to either have a l3_interface or a svi, is it possible to include port-channels

Describe the solution you would like

Having port-channels be added to this feature.

Describe alternatives you have considered

No response

Additional context

No response

Contributing Guide

  • I agree to follow this project's Code of Conduct
@theotherguy2175 theotherguy2175 added the type: enhancement New feature or request label Aug 31, 2023
@ClausHolbechArista
Copy link
Contributor

Since port-channels will need to have member interfaces defined as well, we cannot use the same data model as for l3_interfaces. Instead it could be added as a separate l3_port_channels key under the vrf.

@github-actions GitHub Actions
Copy link

github-actions bot commented Dec 1, 2023

This issue is stale because it has been open 90 days with no activity. The issue will be reviewed by a maintainer and may be closed

@theotherguy2175
Copy link
Author

Would it be possible to have options to have this defined in network services. Maybe port over some of the structured config?

@github-actions GitHub Actions
Copy link

This issue is stale because it has been open 90 days with no activity. The issue will be reviewed by a maintainer and may be closed

@forcecity
Copy link

This feature is also needed for us regarding we need to tweak the description and MTU for the main port-channel interfaces while we are configuring the sub-port-channel interfaces.

interface Port-Channelxxx
   description xxxxx
   no shutdown
   mtu xxxx
   no switchport
!

@bjmeuer bjmeuer self-assigned this Feb 7, 2025
@bjmeuer bjmeuer linked a pull request Feb 12, 2025 that will close this issue
Open
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bjmeuer bjmeuer

Labels
type: enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Feat(eos_designs): Add l3_port_channel support in network services bjmeuer/avd
4 participants
@theotherguy2175 @forcecity @bjmeuer @ClausHolbechArista