-
Notifications
You must be signed in to change notification settings - Fork 539
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
port is not brought up after init #130
Comments
All ports here are set to false |
yes, i suspect there is bug in sonic-swss that did not setup them to true. @stcheng |
sonic-net/sonic-buildimage#381 with this pull request the issue is not seen for now. |
EdenGri
pushed a commit
to EdenGri/sonic-swss
that referenced
this issue
Feb 28, 2022
- Move back to one column of port state to be compatible with old parsers - The current state field has four choices: U, D, X, and N/A. U means the port is admin + oper status UP D means the port is admin UP but oper DOWN X means the port is admin DOWN and disabled N/A for the rest abnormal scenarios - Refactor the code Signed-off-by: Shu0T1an ChenG <[email protected]>
oleksandrivantsiv
pushed a commit
to oleksandrivantsiv/sonic-swss
that referenced
this issue
Mar 1, 2023
* Add primitive cli * Addressing comments
lukasstockner
pushed a commit
to genesiscloud/sonic-swss
that referenced
this issue
Apr 2, 2023
…od (sonic-net#130) ChassisBase and ModuleBase inherit from the DeviceBase class, which already provides a get_serial() method. Thus, these methods were redundant.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The port is not brought up after init. In the sai api record, it sets the port admin state to false in the end.
sairedis.2016-11-10.03_35_51.976755.txt
The text was updated successfully, but these errors were encountered: