[202205] system neighbor was not programmed in remote ASIC #12343
Assignees
Labels
Arista
Chassis 🤖
Modular chassis support
chassis-voq
Voq chassis changes
P0
Priority of the issue
Triaged
this issue has been triaged
Comments
rlhui
added
Chassis 🤖
|
@ysmanman from Arista is working on this issue. |
6 tasks
arlakshm
added a commit
that referenced
this issue
Oct 29, 2022
Signed-off-by: Arvindsrinivasan Lakshmi Narasimhan arlakshm@microsoft.com Why I did it closes #12343 Today in SONiC the notify-keyspace-events is from DbInterface class when application try do any configdb set. In Chassis the chassis_db may not get any configdb set operations, so there is chance this configuration will never be set. So the chassis_db updates from one line card will not be propogated to other linecards, which are doing a psubscribe to get these event. How I did it update the redis.conf to set notify-keyspace-events AKE so that the notify-keyspace-events are set when the redis instance is started How to verify it Test on chassis
yxieca
pushed a commit
that referenced
this issue
Nov 10, 2022
Signed-off-by: Arvindsrinivasan Lakshmi Narasimhan arlakshm@microsoft.com Why I did it closes #12343 Today in SONiC the notify-keyspace-events is from DbInterface class when application try do any configdb set. In Chassis the chassis_db may not get any configdb set operations, so there is chance this configuration will never be set. So the chassis_db updates from one line card will not be propogated to other linecards, which are doing a psubscribe to get these event. How I did it update the redis.conf to set notify-keyspace-events AKE so that the notify-keyspace-events are set when the redis instance is started How to verify it Test on chassis
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
We noticed the issue when triaging t2 sonic-mgmt test failure with 202205 image. The issue is that some system neighbors, including inband neighbor, were added in chassis neigh table, but they were missing in kernel and also hw in some asics. We haven't figured out the exact trigger of the issue. Our experiment shows config reload may fix this issue. So this seems due to some race condition. This was seen in both single- or multi-asic LCs.
Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
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: