the customer deployment has v1/v2 mixed PTP environment from two clocking sys (Danta and Q-sys). The AVD has the PTP fabric/endpoint cfg generated and applied. PTPv2 so far looks good, but there's no PTPv1's multicast forwarding. We have to hardcore the command under the "eos_cli".
Which component of AVD is impacted
eos_designs
Use case example
the customer deployment has v1/v2 mixed PTP environment from two clocking sys (Danta and Q-sys). The AVD has the PTP fabric/endpoint cfg generated and applied. PTPv2 so far looks good, but there's no PTPv1's multicast forwarding.
Describe the solution you would like
give option to enable ptpv1 forward with boolean value setting.
Describe alternatives you have considered
hardcoded in the "eos_cli" structure
Additional context
No response
Contributing Guide
[X] I agree to follow this project's Code of Conduct
Enhancement summary
the customer deployment has v1/v2 mixed PTP environment from two clocking sys (Danta and Q-sys). The AVD has the PTP fabric/endpoint cfg generated and applied. PTPv2 so far looks good, but there's no PTPv1's multicast forwarding. We have to hardcore the command under the "eos_cli".
Which component of AVD is impacted
eos_designs
Use case example
the customer deployment has v1/v2 mixed PTP environment from two clocking sys (Danta and Q-sys). The AVD has the PTP fabric/endpoint cfg generated and applied. PTPv2 so far looks good, but there's no PTPv1's multicast forwarding.
Describe the solution you would like
give option to enable ptpv1 forward with boolean value setting.
Describe alternatives you have considered
hardcoded in the "eos_cli" structure
Additional context
No response
Contributing Guide