Open williambargent opened 2 days ago
Hi @williambargent
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
v4_acl_entries:
'100': { action: permit, protocol: tcp, src_ip: any, dst_ip: any, tcp_flags: [ established ], comment: "PERMIT ESTABLISHED" }
'200': { action: deny, protocol: any, src_ip: any, dst_ip: any, count: true, log: true, comment: "DEFAULT DENY" }
protocol: tcp by protocol: 6 ? (from ansible aos cx doc it is int not a string...) and on the output, talk about protocol any
for the error "Parameters not supported: ", it is coming from pyaoscx module about some capabilities not supported
Thanks, I have tested with protocol: 6
and protocol: any
however I get the same error.
The documentation that I have been referring to mentions that protocol
is a str
value.
https://github.com/aruba/aoscx-ansible-collection/blob/master/docs/aoscx_acl.md
Thanks, I have tested with
protocol: 6
andprotocol: any
however I get the same error.The documentation that I have been referring to mentions that
protocol
is astr
value. https://github.com/aruba/aoscx-ansible-collection/blob/master/docs/aoscx_acl.md
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: