Enhancement summary
The following Campus commands are common and need to be removed to avoid unsupported command errors when configuring them in veos:
dot1x protocol bpdu bypass
address locking
locked-address ipv4 enforcement disabled
locked-address ipv6 enforcement disabled
Which component of AVD is impacted
eos_designs
Use case example
Campus deployments with IP locking and dot1x
Describe the solution you would like
Remove those commands for digital twin
Describe alternatives you have considered
Currently we need a script that disables the feature in the pipeline prior to build configs:
#### update unsupported commands for digital twin ####
yq -i '.dot1x_settings.bypass_bpdu = false' "${GLOBAL_VARS_PATH}/GLOBAL.yml"
yq -i '.address_locking_settings.locked_address.ipv4_enforcement_disabled = false' "${GLOBAL_VARS_PATH}/GLOBAL.yml"
yq -i '.address_locking_settings.locked_address.ipv6_enforcement_disabled = false' "${GLOBAL_VARS_PATH}/GLOBAL.yml"
Additional context
No response
Contributing Guide
Enhancement summary
The following Campus commands are common and need to be removed to avoid unsupported command errors when configuring them in veos:
Which component of AVD is impacted
eos_designs
Use case example
Campus deployments with IP locking and dot1x
Describe the solution you would like
Remove those commands for digital twin
Describe alternatives you have considered
Currently we need a script that disables the feature in the pipeline prior to build configs:
Additional context
No response
Contributing Guide