Question about the MTU of vxlan about HCI

gmailTommy Lv1Posted Nov-27-2025 17:52

as I knew, the Vxlan need Jumbo frame MTU, if the 2 physical interface(eg. eth0, eth1) form as aggregation port, and 3 sub-interfaces are create for VLAN 10 – Management, VLAN 0 – Edge Network, VLAN 100 – Overlay (VXLAN). I want to know whether the MTU of 2 x pyhiscal interface(eg. eht0), aggregation port and the sub-interface of vxlan need to set 1600 ?

Imthy has solved this question and earned 10 coins.

Posting a reply earns you 2 coins. An accepted reply earns you 20 coins and another 10 coins for replying within 10 minutes. (Expired) What is Coin?

Enter your mobile phone number and company name for better service. Go

Last edited by Imthy Nov-27-2025 18:50.

For your scenario where two physical interfaces (e.g., eth0, eth1) form an aggregation port and three VLAN sub-interfaces are created for VLAN 10 (Management), VLAN 0 (Edge Network), and VLAN 100 (Overlay VXLAN), here is the recommended MTU configuration:

For VLAN sub-interfaces with VXLAN on HCI, it is sufficient to enable jumbo frames in the VXLAN configuration; there is no need to change the MTU to 1600 on the physical interface itself.

The VXLAN interface in high-performance mode sets the MTU of the HCI host's interface to 1600 bytes to avoid fragmentation of VXLAN encapsulated data, which significantly improves forwarding performance. Jumbo Frame support must be enabled on the physical switch connected to the server.

When the VXLAN port reuses the physical interface (such as in aggregation), the MTU setting on the opposite switch should be 1600 or higher to support jumbo frames properly.

The physical interfaces forming the aggregation port should have their MTU set to 1600 or above to support jumbo frames for VXLAN traffic.

In summary, the VXLAN sub-interface should have jumbo frames enabled with MTU 1600, and the physical interfaces and aggregation port should also be set to MTU 1600 or higher to ensure proper jumbo frame transmission and avoid fragmentation

Source : Solvia
Is this answer helpful?
Imthy Lv1Posted Nov-27-2025 18:41
  
Last edited by Imthy Nov-27-2025 18:50.

For your scenario where two physical interfaces (e.g., eth0, eth1) form an aggregation port and three VLAN sub-interfaces are created for VLAN 10 (Management), VLAN 0 (Edge Network), and VLAN 100 (Overlay VXLAN), here is the recommended MTU configuration:

For VLAN sub-interfaces with VXLAN on HCI, it is sufficient to enable jumbo frames in the VXLAN configuration; there is no need to change the MTU to 1600 on the physical interface itself.

The VXLAN interface in high-performance mode sets the MTU of the HCI host's interface to 1600 bytes to avoid fragmentation of VXLAN encapsulated data, which significantly improves forwarding performance. Jumbo Frame support must be enabled on the physical switch connected to the server.

When the VXLAN port reuses the physical interface (such as in aggregation), the MTU setting on the opposite switch should be 1600 or higher to support jumbo frames properly.

The physical interfaces forming the aggregation port should have their MTU set to 1600 or above to support jumbo frames for VXLAN traffic.

In summary, the VXLAN sub-interface should have jumbo frames enabled with MTU 1600, and the physical interfaces and aggregation port should also be set to MTU 1600 or higher to ensure proper jumbo frame transmission and avoid fragmentation

Source : Solvia
AimanHakim Lv2Posted Nov-30-2025 22:29
  
Hi there, it depends. If your production require large packets yes enabled it to benefit it. Just that for VXLAN is only recommended using jumbo frame if ur fully utilize micro-segmentations such as virtual routers/switch or virtual appliance as vFW etc that requires high transmission rate between the nodes.

If ur just using for VM connection to network's production, the jumbo frame is not needed.

I Can Help:

Change

Moderator on This Board

135
80
24

Started Topics

Followers

Follow

Board Leaders

NyxZale...

Weekly Sharers

Newbie5...

Weekly Questioners