-
Notifications
You must be signed in to change notification settings - Fork 557
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
create, key: SAI_OBJECT_TYPE_LAG_MEMBER:oid:0x1a0000000005b7, status: SAI_STATUS_FAILURE #199
Labels
Comments
|
|
This was referenced Apr 28, 2017
Issue caused by recent update of Mellanox SAI. We temporary moving back to previous version. Fix for the issue will be provided on Wednesday. |
oleksandrivantsiv
added a commit
to sonic-net/sonic-buildimage
that referenced
this issue
Apr 28, 2017
This reverts commit ce663ba. Revert due to issue in MLNX SAI: sonic-net/sonic-swss#199
Fixed in sonic-net/sonic-buildimage#593 |
Issue still not fixed |
@marian-pritsak is this fixed? |
Issue was resolved. Closing... |
EdenGri
pushed a commit
to EdenGri/sonic-swss
that referenced
this issue
Feb 28, 2022
oleksandrivantsiv
pushed a commit
to oleksandrivantsiv/sonic-swss
that referenced
this issue
Mar 1, 2023
* Added SAI dump support to syncd * Refactored sai_sdk_dump tool to use SAI directly
lukasstockner
pushed a commit
to genesiscloud/sonic-swss
that referenced
this issue
Apr 2, 2023
#### Description Following error is seen while parsing EEPROM fields for few transceivers. 'utf-8' codec can't decode byte 0xff in position 6: invalid start byte #### Motivation and Context EEPROM fields will not be displayed if unicode characters are not properly. E.g. Vendor Date: 20'u-tf--8'
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
The text was updated successfully, but these errors were encountered: