-
Notifications
You must be signed in to change notification settings - Fork 271
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
[202205] FDB learning caused orchagent exited when reboot #1267
Comments
@stephenxs Do you have any idea about this issue? Why 202205 and master branch delete the fix...? |
fdb learning is disabled before reboot, so there should be no learning message, unless this was race condition, do you have syslog and sairedis.rec from that timestamp ? |
When system boot up, the default behavior of fdb learning depends on vendor SAI/SDK.
|
OA explicitly turns off FDB learning before reboot so this situation not happen, maybe this is some other scenario rather than reboot ? maybe this is unexpected reboot ? please attach full syslog and sairedis log from that day/event take a look from your paste:
@prsunny maybe we need a special case scenario here for this kind of behavior in swss |
Hi @kcudnik , Appreciated for your comments. Thanks |
if it's cold boot, then all ports should be down by default, and from sairedis recordings seems like you get port up notification, so ports were administrative UP, which should not be the case in cold boot scenario. Again, please attach syslog aroutd this boot +/- extra few minutes so we could analyze what happened |
Agree with Kamil. Also orchagent removes all port from Bridge and default Vlan member association. MAC learning is not expected to happen in normal cold boot. |
SONiC 202205, the orchagent (portsorch) crashed when init occasionally.
The reason is that FDB learned when reboot and it add reference count for default port bridge id.
Then portsorch tried to removeDefaultBridgePorts but failed because of reference count.
SONiC 201911 fixed this issue before:
#572
But this fix was removed in 202205 and master.
The text was updated successfully, but these errors were encountered: