Modular Layer 2 (ml2) configuration options

Liberty - Liberty - Liberty - Liberty - Liberty - Liberty - Liberty - Liberty -

Modular Layer 2 (ml2) Flat Type configuration options
Modular Layer 2 (ml2) GRE Type configuration options
Modular Layer 2 (ml2) VLAN Type configuration options
Modular Layer 2 (ml2) VXLAN Type configuration options
Modular Layer 2 (ml2) Arista Mechanism configuration options
Modular Layer 2 (ml2) BaGpipe Mechanism configuration options
Modular Layer 2 (ml2) BigSwitch Mechanism configuration options
Modular Layer 2 (ml2) Brocade Mechanism configuration options
Modular Layer 3 (ml2) Brocade MLX ICX Mechanism configuration options
Modular Layer 2 (ml2) Cisco Mechanism configuration options
Modular Layer 2 (ml2) Freescale SDN Mechanism configuration options
Modular Layer 2 (ml2) Geneve Mechanism configuration options
Modular Layer 2 (ml2) OpenDaylight Mechanism configuration options
Modular Layer 2 (ml2) OpenFlow Agent (ofagent) Mechanism configuration options
Modular Layer 2 (ml2) L2 Population Mechanism configuration options
Modular Layer 2 (ml2) Tail-f NCS Mechanism configuration options
Modular Layer 2 (ml2) SR-IOV Mechanism configuration options

The Modular Layer 2 (ml2) plug-in has two components: network types and mechanisms. You can configure these components separately. This section describes these configuration options.

Configure MTU for VXLAN tunnelling

	Configure MTU for VXLAN tunnelling
Specific MTU configuration is necessary for VXLAN to function as expected: One option is to increase the MTU value of the physical interface and physical switch fabric by at least 50 bytes. For example, increase the MTU value to 1550. This value enables an automatic 50-byte MTU difference between the physical interface (1500) and the VXLAN interface (automatically 1500-50 = 1450). An MTU value of 1450 causes issues when virtual machine taps are configured at an MTU value of 1500. Another option is to decrease the virtual Ethernet devices' MTU. Set the `network_device_mtu` option to 1450 in the `neutron.conf` file, and set all guest virtual machines' MTU to the same value by using a DHCP option. For information about how to use this option, see Configure OVS plug-in.

Specific MTU configuration is necessary for VXLAN to function as expected:

One option is to increase the MTU value of the physical interface and physical switch fabric by at least 50 bytes. For example, increase the MTU value to 1550. This value enables an automatic 50-byte MTU difference between the physical interface (1500) and the VXLAN interface (automatically 1500-50 = 1450). An MTU value of 1450 causes issues when virtual machine taps are configured at an MTU value of 1500.
Another option is to decrease the virtual Ethernet devices' MTU. Set the network_device_mtu option to 1450 in the neutron.conf file, and set all guest virtual machines' MTU to the same value by using a DHCP option. For information about how to use this option, see Configure OVS plug-in.

Table 10.16. Description of ML2 configuration options
Configuration option = Default value	Description
[ml2]
`extension_drivers` =	(ListOpt) An ordered list of extension driver entrypoints to be loaded from the neutron.ml2.extension_drivers namespace.
`external_network_type` = `None`	(StrOpt) Default network type for external networks when no provider attributes are specified. By default it is None, which means that if provider attributes are not specified while creating external networks then they will have the same type as tenant networks. Allowed values for external_network_type config option depend on the network type values configured in type_drivers config option.
`mechanism_drivers` =	(ListOpt) An ordered list of networking mechanism driver entrypoints to be loaded from the neutron.ml2.mechanism_drivers namespace.
`path_mtu` = `0`	(IntOpt) The maximum permissible size of an unfragmented packet travelling from and to addresses where encapsulated Neutron traffic is sent. If <= 0, the path MTU is indeterminate.
`physical_network_mtus` =	(ListOpt) A list of mappings of physical networks to MTU values. The format of the mapping is <physnet>:<mtu val>. This mapping allows specifying a physical network MTU value that differs from the default segment_mtu value.
`segment_mtu` = `0`	(IntOpt) The maximum permissible size of an unfragmented packet travelling a L2 network segment. If <= 0, the segment MTU is indeterminate.
`tenant_network_types` = `local`	(ListOpt) Ordered list of network_types to allocate as tenant networks.
`type_drivers` = `local, flat, vlan, gre, vxlan, geneve`	(ListOpt) List of network type driver entrypoints to be loaded from the neutron.ml2.type_drivers namespace.

Questions? Discuss on ask.openstack.org
Found an error? Report a bug against this page

Legal notices