-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[Nokia-BRCM-DNX]: CLI show dropcounter counts - retains the stats after clearing #19861
Comments
@saksarav-nokia - can you please triage internally first? Thanks! |
It is the same root cause as #19779 This seems to be very fundamental issue when the user issues sonic-clear and then show for the commands in multi-asic switch. If you issue sonic-clear for asic0, then asic1 and then do show for asic0 OR son-clear for asic1, sonic-clear for asic0 and then do show for asic1, you will see this issue. The reason is that the soni-clear command creates the files in /tmp/cache/dropstat each time you run clear command and overwrites the asic 0's, when you clear for asic 0 first and then asic 0 (or asic1 file depending on the order you issue sonic-clear). Then when you do show for asic0, it reads this file created for asic 1 and it does look up for asic 0's port counter( which does n't exist) and subtract this from counter vlaue from COUNTERS_DB. So it prints the value from COUNTER_DB. |
If we add the multi-asic support to sonic-clear command for pg drop counter, then the cache file can be created with prefixing ns and show command can read the corresponding history from cache. |
@kenneth-arista can you/team please check this ? This is related to multi asic support for Qos commands. |
Copying my comments issue 19779: The solution is to not use ip netns exec before running CLI command related to "priority-group drop counters" because native multi-ASIC support has been added recently to these family of commands. Instead use the built-in -n argument. See sonic-net/sonic-utilities#3058 for further details. The reason is that ip netns exec ... limits the Linux network namespace, which conflicts with the default use of the multi_asic decorator for adding multi-asic support to existing commands. I believe historically folks have been using ip netns exec as a hack to get around old commands that haven't been taught about multi-asic. But we are putting effort into enhancing all Qos commands to natively support multi-asic. Tracking issue: #15148. |
Does the drop-counter CLI support namespace tag or not? I went ahead and tried to check if drop counter have namespace tag. I did not find it. Checked with 2205 build.
Please let me know. Thanks, |
The changes to support multi-asics merged to |
Please close this issue as I don't have permission to do so. |
@kenneth-arista , Did Arista add namespace support for sonic-clear commands also. How do you clear the counters?. I don't see -n support in 202405 |
Description
Although the device says that drop counter IS NOT supported on this device, I see that drop counters do increment.
After clearing the drop counter stats for a given ASIC, if the stats of other ASIC is cleared, the stats for the first ASIC are brought back.
Steps to reproduce the issue:
Describe the results you received:
On clearing the stats for ASIC0, and checking the stats, the stats reset. However, if we clear the stats for other ASIC, the stats on first ASIC come back again.
Describe the results you expected:
Clearing of the stats on one ASIC, should not have any impact on the stats on different ASIC.
Output of
show version
:Output of
show techsupport
:Additional information you deem important (e.g. issue happens only occasionally):
The text was updated successfully, but these errors were encountered: