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

Incorrect Port Delimiter in Arista Traffic Policy #360

Open
vsrx6 opened this issue Oct 16, 2024 · 0 comments
Open

Incorrect Port Delimiter in Arista Traffic Policy #360

vsrx6 opened this issue Oct 16, 2024 · 0 comments

Comments

@vsrx6
Copy link

vsrx6 commented Oct 16, 2024

Arista traffic policy currently generates space-separated ports in match conditions, causing commit failures. This should be comma-separated.

Current (incorrect) policy:

"protocol tcp source port 1024-65535 destination port 49 2824 3502 3524 2800-2801"

Required (correct) policy:

"protocol tcp source port 1024-65535 destination port 49, 2824, 3502, 3524, 2800-2801"

Lab test:

lab-device(config-traffic-policy-match-test-test-ipv4)#protocol tcp source port 50 ?
  destination  Destination
  ,            extend list
  -            specify range
  <cr>

lab-device(config-traffic-policy-match-test-test-ipv4)#protocol tcp source port 50 100 200
% Invalid input
lab-device(config-traffic-policy-match-test-test-ipv4)#protocol tcp source port 50, 100, 200
lab-device(config-traffic-policy-match-test-test-ipv4)#

Reference: https://www.arista.com/en/support/toi/eos-4-24-2f/14550-support-for-traffic-policy-on-interfaces

@vsrx6 vsrx6 changed the title Incorrect Port Delimiters in Arista Traffic Policy Incorrect Port Delimiter in Arista Traffic Policy Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant