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
As detailed under https://www.arista.com/en/support/toi/eos-4-25-1f/14628-ip-locking-release-updates IP locking has a "enforcement disabled" mode which is not covered today in AVD
eos_cli_config_gen
Allow enforcement disabled functionality in the physical/vlan interface
Expand the model:
ethernet_interfaces: - name: <str; required; unique> address_locking: ipv4: <bool> enforcement_disabled: <bool>
Which will generate the following CLI configuration:
locked-address ipv4 enforcement disabled
Ideally, also add support for vlan config-mode, which also supports the functionality
No response
Configuration to be generated:
vlan 10 address locking address-family ipv4 locked-address ipv4 enforcement disabled
interface Ethernet1 shutdown ! address locking address-family ipv4 locked-address ipv4 enforcement disabled
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Enhancement summary
As detailed under https://www.arista.com/en/support/toi/eos-4-25-1f/14628-ip-locking-release-updates IP locking has a "enforcement disabled" mode which is not covered today in AVD
Which component of AVD is impacted
eos_cli_config_gen
Use case example
Allow enforcement disabled functionality in the physical/vlan interface
Describe the solution you would like
Expand the model:
Which will generate the following CLI configuration:
Ideally, also add support for vlan config-mode, which also supports the functionality
Describe alternatives you have considered
No response
Additional context
Configuration to be generated:
Contributing Guide
The text was updated successfully, but these errors were encountered: