-
Notifications
You must be signed in to change notification settings - Fork 730
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
[Dual-ToR][active-active] After 'config reload' it takes a lot of time to set up mux ports #15644
Comments
Hi @ayurkiv-nvda, can you please share syslog when running into this issue? |
Hello @bingwang-ms |
Hi @ayurkiv-nvda - Based on the log you shared. But the interfaces didn't get up till
SONiC has an assumption that link should go operationally up within 5min after
Though we might need to adjust the timeout for this test anyway. |
Hello @zjswhhh |
Hi @ayurkiv-nvda - Checked our nightly test data, this case passed consistently on 202405 and 202311. Since the delay still matches our expectation, I feel it's unlikely an image issue. The current wait time in this test is 60s+30s after |
Hello @zjswhhh |
@zjswhhh @bingwang-ms can you confirm who is working on increasing the timeout? |
Description
It is a degradation comparing to 202311
(Did not reproduce on 202311.689016-bba184c4d)
Steps to reproduce the issue:
Problem was found during running community test test_active_link_admin_down_config_reload_downstream[active-active] on 202405
Original scenario:
Simplified scenario:
Describe the results you received:
redis-dump -d 0 -k "HW_MUX_CABLE_TABLE:*
return empty lines,show mux status
is emptyon 202405 it takes approximately 2 minutes 15 seconds beetween
config reload
and non-empty data inredis-dump -d 0 -k "HW_MUX_CABLE_TABLE:*
on 202311 it takes ~2 minutes beetween
config reload
and non-empty data inredis-dump -d 0 -k "HW_MUX_CABLE_TABLE:*
Describe the results you expected:
show mux status
shows valid info afrer 2minutes after config reloadOutput 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: