-
Notifications
You must be signed in to change notification settings - Fork 15
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
All ACL rules deletion, ACL table deletion and single ACL rule deletion not working #57
Comments
Here are delete logs for single acl-set:
|
Here are delete logs for whole acl table:
|
This is same issue of CVL as reported earlier. Please confirm, if it is merged to master branch. If so then please close this. |
I am still having some problem deleting either individual or all ACLs via gnmi. It is complaining about MyACL1 constraints, but I am trying to delete MyACL3... This is the result of trying to delete a single acl-set with gnmi command:
|
@maheshwari-mayank ^ see above |
This changes have been merged to 'master' branch recently. Please check it again. |
All 3 deletes working fine, closing this issue. |
CLI handler for 'ip access-list XYZ' was not sednding RESTCONF compliant payload earlier. New ygot code does not accept it. Modified the actioner to use 'PATCH /restconf/data/openconfig-acl:acl/acl-sets/acl-set' request with correct payload.
…-path-list (#57) * check if deleting as-path-list rules means deleting the as-path-list * snc-17101: deleting as-path rule needs to match the action first * pass cliclient as an input parameter
gnmi commands used:
To delete all rules: ./gnmi_set -delete /openconfig-acl:acl -target_addr 127.0.0.1:8080 -alsologtostderr -insecure true -pretty
To delete an ACL table: ./gnmi_set -delete /openconfig-acl:acl/acl-sets/acl-set[name=MyACL1][type=ACL_IPV4] -target_addr 127.0.0.1:8080 -alsologtostderr -insecure true -pretty
To delete a single rule: ./gnmi_set -delete /openconfig-acl:acl/acl-sets/acl-set[name=MyACL1][type=ACL_IPV4]/acl-entries/acl-entry[sequence-id=1] -target_addr 127.0.0.1:8080 -alsologtostderr -insecure true -pretty
The text was updated successfully, but these errors were encountered: