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

Requesting the addition of support for a platform-specific recirculation channel to mirror egress traffic to the CPU. #4495

Open
1 task done
dayrton opened this issue Sep 19, 2024 · 1 comment · May be fixed by #4554
Open
1 task done
Labels
type: enhancement New feature or request

Comments

@dayrton
Copy link

dayrton commented Sep 19, 2024

Enhancement summary

For the following platforms, Egress mirroring to Cpu requires configuring a recirculation channel. For which, we currently don't have support through AVD.
CCS-710P-12***
CCS-710P-16***
DCS-7010TX-48***
CCS-720DF***
CCS-720DP***
CCS-720DT***
CCS-720XP-24ZY4***
CCS-720XP-24Y6***
CCS-720XP-48Y6***
CCS-720XP-48ZC2***
CCS-720XP-96ZC2***

Which component of AVD is impacted

eos_designs

Use case example

We want to be able to mirror the traffic in their OT-DC campus enviornment which have CCS-720XP-48Y4 switches. We need this recirculation channel configured in order to be configure mirror sessions. Please refer to this TOI for more info. https://www.arista.com/en/support/toi/eos-4-32-0f/13722-mirror-cpu

Describe the solution you would like

We are thinking this solution should be tied to the platform type since it's only for specific platforms. Or maybe we don’t need to—regular support for this key might be sufficient, and we can control which group gets that config through AVD.

Describe alternatives you have considered

We used raw_eos_cli at the group level, but we already have eos_cli configured under global_variables. The eos_cli at the global level is being overridden by the new group-level eos_cli config. For now, we're using a custom Jinja template as a workaround.

Additional context

No response

Contributing Guide

  • I agree to follow this project's Code of Conduct
@dayrton dayrton added the type: enhancement New feature or request label Sep 19, 2024
@nathanmusser
Copy link
Contributor

I've started a PR draft to address this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants