Skip to content
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

Switch startup failure after upgrading to SAIv1.13 #1435

Open
Yukissss opened this issue Oct 18, 2024 · 3 comments
Open

Switch startup failure after upgrading to SAIv1.13 #1435

Yukissss opened this issue Oct 18, 2024 · 3 comments

Comments

@Yukissss
Copy link

Yukissss commented Oct 18, 2024

Description
I have recently upgraded our Broadcom switch to support SAIv1.3, and after the upgrade, the switch is failing to start the switch state service as indicated in the sairedis.rec and systemd logs. The current versions in use are LIBSAIBCM_XGS_VERSION = 10.1.7.0 and BRCM_OPENNSL_KERNEL_VERSION = 8.4.0.2. The logging output includes the following information: sai_api_initialize:451 BRCM SAI ver: [10.1.7.0], OCP SAI ver: [1.13.2], SDK ver: [sdk-6.5.29]
I am unsure if the issue is due to an inappropriate SDK version or another factor(I did not update the linux kernel version, could it be the reason?). Could this be the cause, or is there another reason for the switch failing to start the switch state service?
Attachments
img_v3_02fp_1837229c-ea06-4048-ba3c-91dafa46492g
image

@Yukissss Yukissss changed the title Switch startup failure after upgrading to SAIv1.3 Switch startup failure after upgrading to SAIv1.13 Oct 18, 2024
@kcudnik
Copy link
Collaborator

kcudnik commented Oct 18, 2024

is that all syslog ? there are no warning or errors ?

@Yukissss
Copy link
Author

There are some NOTICE: initialize fafiled, sai_api_query failed for 11apis. It seems ok, syncd doesn't exit here.
I did not find more obvious warnings or errors.

@kcudnik
Copy link
Collaborator

kcudnik commented Oct 21, 2024

yes, there are no erorr messages from syncd directly, just from supervisor, maybe it's crashing and doing core dump
last message is at 1:59:49.035 and then at 1:59:52 it's exiting, not sure what happens there, can you run syncd in debulg level? it should debug all in/out from any function, we would see then at which point it's exiting

since it's brcm, im going to bet that it probably vendor issue and crash dump

please also check if there is a coredump in syncd docker

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants