-
Notifications
You must be signed in to change notification settings - Fork 529
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
add lag member failed on mellanox platform #191
Comments
Please find the attached sai record. |
it looks like we are recreating the LAG_MEMBER for the same lag_id and port_id pair.
|
The SAI function call looks fine. After the creation of all LAGs, it first removes one LAG member and then re-create it. I will double check with the latest build. |
@liatgrozovik hey Liat, could you also help to take a look at this? I notice that attaching/detaching members of a LAG will cause creation failure. |
Tried on HEAD.220-68fcc36 Commands:
syncd does not crash, LAG is still working after member is added back to LAG |
@marian-pritsak i tried also and it seems that everything is working well. I will double check nightly test to see if it is still an issue or I will close it. |
what is the root cause for this? |
Signed-off-by: Chenchen Qi <chenchen.qcc@alibaba-inc.com>
Apr 14 19:40:46 str-msn2700-04 NOTICE orchagent: :- addLagMember: Add member Ethernet120 to LAG PortChannel03 lid:20000000005a1 pid:100000000000f
Apr 14 19:40:46 str-msn2700-04 ERR syncd: :- handle_generic: failed to create -1
Apr 14 19:40:46 str-msn2700-04 ERR syncd: :- processEvent: failed to execute api: create, key: SAI_OBJECT_TYPE_LAG_MEMBER:oid:0x1a0000000005b8, status: SAI_STATUS_FAILURE
Apr 14 19:40:46 str-msn2700-04 ERR syncd: :- processEvent: field: SAI_LAG_MEMBER_ATTR_LAG_ID, value: oid:0x20000000005a1
Apr 14 19:40:46 str-msn2700-04 ERR syncd: :- processEvent: field: SAI_LAG_MEMBER_ATTR_PORT_ID, value: oid:0x100000000000f
Apr 14 19:40:46 str-msn2700-04 NOTICE syncd: :- exit_and_notify: sending switch_shutdown_request notification to OA
Apr 14 19:40:46 str-msn2700-04 NOTICE orchagent: :- handle_switch_shutdown_request: switch shutdown request
Apr 14 19:40:46 str-msn2700-04 ERR orchagent: :- on_switch_shutdown_request: Syncd stopped
Apr 14 19:40:46 str-msn2700-04 INFO swss.sh[2648]: terminate called without an active exception
The text was updated successfully, but these errors were encountered: