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

[vlanmgrd]: Do not bring up VLAN members by default #667

Merged
merged 1 commit into from
Nov 1, 2018

Conversation

stcheng
Copy link
Contributor

@stcheng stcheng commented Nov 1, 2018

VLAN members' admin status and MTU are controlled by portmdrd.
vlanmgrd shall not bring up and set MTU automatically by default.

Signed-off-by: Shu0T1an ChenG shuche@microsoft.com

VLAN members' admin status and MTU are controlled by portmdrd.
vlanmgrd shall not bring up and set MTU automatically by default.

Signed-off-by: Shu0T1an ChenG <shuche@microsoft.com>
@stcheng
Copy link
Contributor Author

stcheng commented Nov 1, 2018

@jipanyang please check

Copy link
Contributor

@jipanyang jipanyang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This the behavior was inherited from the days of Linux network interface file config control. I guess we don't need it any more.
The legacy configuration might miss the explicit vlan member port admin and mtu setting, that should be taken care of by operator though.

@stcheng
Copy link
Contributor Author

stcheng commented Nov 1, 2018

yes, the pull request sonic-net/sonic-buildimage#2209 ensures that all VLAN members will have admin status set as up by default

@stcheng stcheng merged commit 15a2299 into sonic-net:master Nov 1, 2018
@stcheng stcheng deleted the vlanmgrd branch November 1, 2018 22:03
oleksandrivantsiv pushed a commit to oleksandrivantsiv/sonic-swss that referenced this pull request Mar 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants