You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"show acl table" which uses acl-loader gets data from host config db alone for multi-asic devices. The ACL entries in host need not have all the interfaces which is valid in the namespaces.
Instead we need to connect to each namespace and get the ACLs
Steps to reproduce the issue:
show acl table DATAACL
Describe the results you received:
admin@str2--lc1-1:~$ show acl table DATAACL
Name Type Binding Description Stage Status
------- ------ -------------- ------------- ------- --------------------------------------
DATAACL L3 PortChannel102 DATAACL ingress {'asic0': 'Active', 'asic1': 'Active'}
PortChannel106
Describe the results you expected:
admin@str2--lc1-1:~$ show acl table DATAACL
Name Type Binding Description Stage Status
------- ------ -------------- ------------- ------- --------------------------------------
DATAACL L3 Ethernet128 DATAACL ingress {'asic0': 'Active', 'asic1': 'Active'}
Ethernet184
PortChannel102
PortChannel106
Output of show version:
admin@str2--lc1-1:~$ show version
SONiC Software Version: SONiC.20220530.38
SONiC OS Version: 11
Distribution: Debian 11.7
Kernel: 5.10.0-18-2-amd64
Build commit: 4115919589
Build date: Fri Jul 28 01:24:14 UTC 2023
Built by: cloudtest@8ec96c8ac000000```
#### Output of `show techsupport`:
(paste your output here or download and attach the file here )
#### Additional information you deem important (e.g. issue happens only occasionally):
<!--
Also attach debug file produced by `sudo generate_dump`
-->
The text was updated successfully, but these errors were encountered:
judyjoseph
changed the title
[multi-asic] show acl table reading from host config db alone
[multi-asic] show acl table command gets data from host config db and not from asic namespace db
Aug 2, 2023
What I did
Fixessonic-net/sonic-buildimage#16012
The show acl table command currently get the ports from host config_db on multi asic platforms.
This host config_db will not the phyiscal ports in the binding ports because the host doesnt have any front panel ports on the host. This causes the show acl table not to display the phyiscal ports in the output on multi asic devices/linecards.
The test iface_namingmode/test_iface_namingmode.py::test_show_acl_table fails because of this issue.
yxieca
pushed a commit
to sonic-net/sonic-utilities
that referenced
this issue
Sep 6, 2023
What I did
Fixessonic-net/sonic-buildimage#16012
The show acl table command currently get the ports from host config_db on multi asic platforms.
This host config_db will not the phyiscal ports in the binding ports because the host doesnt have any front panel ports on the host. This causes the show acl table not to display the phyiscal ports in the output on multi asic devices/linecards.
The test iface_namingmode/test_iface_namingmode.py::test_show_acl_table fails because of this issue.
StormLiangMS
pushed a commit
to sonic-net/sonic-utilities
that referenced
this issue
Sep 21, 2023
What I did
Fixessonic-net/sonic-buildimage#16012
The show acl table command currently get the ports from host config_db on multi asic platforms.
This host config_db will not the phyiscal ports in the binding ports because the host doesnt have any front panel ports on the host. This causes the show acl table not to display the phyiscal ports in the output on multi asic devices/linecards.
The test iface_namingmode/test_iface_namingmode.py::test_show_acl_table fails because of this issue.
Description
"show acl table" which uses acl-loader gets data from host config db alone for multi-asic devices. The ACL entries in host need not have all the interfaces which is valid in the namespaces.
Instead we need to connect to each namespace and get the ACLs
Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
Output of
show version
:(paste your output here or download and attach the file here )
The text was updated successfully, but these errors were encountered: