-
Notifications
You must be signed in to change notification settings - Fork 23
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
module: aoscx_acl - tcp_flags - BUG #119
Comments
What switch model and firmware ? |
Good evening @alagoutte, I have tested with multiple 8360's, the firmware is 10.13.1040, it also occurred on 10.13.1031. |
Can you try to replace
protocol: tcp by protocol: 6 ? (from ansible aos cx doc it is int not a string...) for the error "Parameters not supported: ", it is coming from pyaoscx module about some capabilities not supported |
Thanks, I have tested with The documentation that I have been referring to mentions that |
but the code say "int" https://github.com/aruba/aoscx-ansible-collection/blob/master/plugins/modules/aoscx_acl.py#L265 :) (i think the doc is regenerated... @tchiapuziowong you have always "protocol": "any", on verbose ? |
Hello CX Ansible Team,
I'm having trouble using the
tcp_flags
parameter now that thetcp_established
bool has been depreciated.I have the following in my playbook:
This
v4_acl_entries
variable is stored in a separate file in the following format:This seems to occur for any list item: ack, cwr, ece, established, fin, psh, rst, syn, urg. I have been following the documentation page: https://github.com/aruba/aoscx-ansible-collection/blob/master/docs/aoscx_acl.md
The error I receive:
My versions:
The text was updated successfully, but these errors were encountered: