Closed sj-harrish closed 1 year ago
Do you see the same issue on SONiC VS? Please provide steps to reproduce with SAI Challenger (SAI-C). Please include:
@andriy-kokhan , Thanks much for your response. We are collecting the details and we will get back with the logs. Another follow-up query in this regard, Could you please let us know the reason behind the commit change - https://github.com/opencomputeproject/SAI-Challenger/commit/6799cd2f090502b2ddb1513d59efc851a0a889f4#diff-f3d97dbb02a5bd229642e8abc64ae1710723377d55e63e50faa1a6dceb0eded7 where the self.r.publish("ASIC_STATE_CHANNEL", "G") is changed to self.r.publish("ASIC_STATE_CHANNEL@1", "G") in sai.py.? Thanks in advance,
@andriy-kokhan , Thanks much for your response. We are collecting the details and we will get back with the logs. Another follow-up query in this regard, Could you please let us know the reason behind the commit change - 6799cd2#diff-f3d97dbb02a5bd229642e8abc64ae1710723377d55e63e50faa1a6dceb0eded7 where the self.r.publish("ASIC_STATE_CHANNEL", "G") is changed to self.r.publish("ASIC_STATE_CHANNEL@1", "G") in sai.py.? Thanks in advance,
As you probably noticed, the mentioned commit also updates the refpoints of SAI and sairedis/swss-common. The communication mechanism has been slightly updated in SONiC itself. So, the change that you've mentioned has been done to make SAI-C compatible with the new version of sairedis. Not a big problem taking into account that we are trying to be compatible with the latest version of SAI and latest SONiC as a primary use-case.
As a result, two things that you should keep in mind:
Also, you may want to propose a fix to SAI-C community to either somehow auto-detect whether there should be "@1" prefix or make this commit dependent.
Thanks much @andriy-kokhan for your inputs. We will get back if we have any further queries.
Hi SAI-Challenger Team,
We are observing that SAI LAG API calls are taking more than 3+ minutes to respond to the request published via ASIC_STATE_KEY_VALUE_OP_QUEUE lpush and publish method. The issue is not seen in SONiC-202111 Community but observed from SONiC-202205 branch. Could you please help us in identifying the issue here.? Thanks in advance,
Version Details:
SONiC-202205. Hash - 9a3571cec HW - NVIDIA - SN4600
Detailed Steps used to Recreate: