You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's an issue with the MTU documentation. As far as I know, it is incorrect to state that overlay traffic requires an MTU at 9000. It is recommended to use "1600 or greater" (one page among others: https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.0/administration/GUID-F7C976EF-2C0D-42D6-ACB5-13453BACD281.html). So the doc should say "1600", not "9000", unless there's an additional requirement for TKGI which should be explained.
Similarly, the statement that "NSX-T Edge Nodes must be connected to a port group that supports > 1600 bytes" is inaccurate, since the MTU should be greater or equals to 1600, not strictly greated to 1600. So > should be replaced by ≥.
The text was updated successfully, but these errors were encountered:
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.
The labels on this github issue will be updated when the story is started.
There's an issue with the MTU documentation. As far as I know, it is incorrect to state that overlay traffic requires an MTU at 9000. It is recommended to use "1600 or greater" (one page among others: https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.0/administration/GUID-F7C976EF-2C0D-42D6-ACB5-13453BACD281.html). So the doc should say "1600", not "9000", unless there's an additional requirement for TKGI which should be explained.
Similarly, the statement that "NSX-T Edge Nodes must be connected to a port group that supports > 1600 bytes" is inaccurate, since the MTU should be greater or equals to 1600, not strictly greated to 1600. So > should be replaced by ≥.
The text was updated successfully, but these errors were encountered: