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

[vnet] Set MTU for the VNET bridge RIF in BITMAP implementation #1271

Merged
merged 1 commit into from
Apr 23, 2020

Conversation

volodymyrsamotiy
Copy link
Collaborator

Signed-off-by: Volodymyr Samotiy [email protected]

What I did
In BITMAP implementation, set MTU for the internal VNET bridge RIF to max value.

Why I did it
To make jumbo frames routed on BITMAP VNET interfaces. Currently if sending traffic from VNET to another VNI using a tunnel route then frames larger than 1500 are not routed and trapped to the CPU.

How I verified it
Executed vxlan_vnet ansible test with the modified MTU.

Details if related
N/A

Copy link
Collaborator

@prsunny prsunny left a comment

Choose a reason for hiding this comment

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

Based on discussion, this is a temporary fix for Bitmap implementation and is already handled in VRF implementation

@prsunny prsunny merged commit 3829053 into sonic-net:master Apr 23, 2020
abdosi pushed a commit that referenced this pull request Apr 27, 2020
EdenGri pushed a commit to EdenGri/sonic-swss that referenced this pull request Feb 28, 2022
added new value "always_enabled" for the state and auto-restart field of Feature Table

Once the field value is "always_enabled" it can be changes from config feature .. command

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

Successfully merging this pull request may close these issues.

3 participants