Instances and 802.3ad layer3 4 link aggregation [closed]

asked 2014-09-05 19:19:38 -0500

capsali gravatar image

updated 2014-09-05 19:21:03 -0500


This may be a stupid question but i need to know.

In my openstack setup i use eth bonding 802.3ad layer3+4 on all nodes for the management,tunnel and external network.

I chose layer3+4 for better throughoutput, as it balances load on all slaves in the bonding.

The problem with layer3+4 is that 802.3ad is not fully complient with this layer, mostly if ip fragmentation appears.

The neutron dhcp sets mtu of instances <1500, so ip fragmentation is about to happen.

Will this affect my bonding? Should i go with layer2+3?

I don't have much load now on the external network so i cannot figure out if it's hurting my network.

Does anybody know if it will be a problem?

edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by capsali
close date 2015-10-08 07:09:23.250955


Only if there is heavy UDP traffic.

yHuKyM gravatar imageyHuKyM ( 2014-09-06 16:20:09 -0500 )edit

Here from IBM, check the last section: (

yHuKyM gravatar imageyHuKyM ( 2014-09-06 16:28:34 -0500 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2014-12-02 07:15:07 -0500

gaud gravatar image

By the way, you might be able to change the "dhcp-option-force" dnsmasq option


edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools



Asked: 2014-09-05 19:19:38 -0500

Seen: 296 times

Last updated: Dec 02 '14