We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We would like to be able to configure private vlan feature within eos_design Network Services L2.
eos_designs
For segmentation purposes, we use pvlan so Virtual Machines can only access a backup master server without allowing VM to access each other.
I imagine two possible solutions.
first is to add direct private vlan configuration under l2vlans
<network_services_keys.name>: - name: <str; required; unique> l2vlans: - id: <int; 1-4094; required> private_vlan: type: <str; "community" | "isolated"> primary_vlan: <int>
second is to add a structured_config field :
<network_services_keys.name>: - name: <str; required; unique> l2vlans: - id: <int; 1-4094; required> structured_config: private_vlan: type: <str; "community" | "isolated"> primary_vlan: <int>
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Enhancement summary
We would like to be able to configure private vlan feature within eos_design Network Services L2.
Which component of AVD is impacted
eos_designs
Use case example
For segmentation purposes, we use pvlan so Virtual Machines can only access a backup master server without allowing VM to access each other.
Describe the solution you would like
I imagine two possible solutions.
first is to add direct private vlan configuration under l2vlans
second is to add a structured_config field :
Describe alternatives you have considered
No response
Additional context
No response
Contributing Guide
The text was updated successfully, but these errors were encountered: