3/26/2020 Drivers Nebula 150
This guide describes how to enable Network isolation provided through the VXLAN encapsulation protocol. This driver will create a bridge for each OpenNebula Virtual Network and attach a VXLAN tagged network interface to the bridge.
![]()
The VLAN id will be the same for every interface in a given network, calculated automatically by OpenNebula. It may also be forced by specifying an VLAN_ID parameter in the Virtual Network template.
NW230NXT45 ION 150 Drivers and setup for Windows 7 and previous versions Size: 22.2 MB English, Spanish Download Ion 300 updated Software Size: 28.6 MB English, Spanish. Download drivers, software, firmware and manuals for your Canon product and get access to online technical support resources and troubleshooting. We use cookies to provide you with the best possible experience in your interactions with Canon and on our website – find out more about our use of Cookies and change your cookie settings here.
Additionally each VLAN has associated a multicast address to encapsulate L2 broadcast and multicast traffic. This address is assigned by default to the 239.0.0.0/8 range as defined by RFC 2365 (Administratively Scoped IP Multicast). In particular the multicast address is obtained by adding the VLAN_ID to the 239.0.0.0/8 base address.
Considerations & Limitations¶
This driver works with the default UDP server port 8472.
VXLAN traffic is forwarded to a physical device, this device can be set (optionally) to be a VLAN tagged interface, but in that case you must make sure that the tagged interface is manually created first in all the hosts.
The physical device that will act as the physical device must have an IP.
Concurrent VXLANs host limit¶
Each VXLAN is associated with one multicast group. There is a limit on how many multicast groups can be a physical host member of at the same time. That also means, how many different VXLANs can be used on a physical host concurrently. The default value is 20 and can be changed via
sysctl through kernel runtime parameter net.ipv4.igmp_max_memberships .
For permanent change to e.g. 150, place following settings inside the
/etc/sysctl.conf :
and reload the configuration
OpenNebula Configuration¶
It is possible specify the start VLAN ID by configuring
/etc/one/oned.conf :
The following configuration attributes can be adjusted in
/var/lib/one/remotes/etc/vnm/OpenNebulaNetwork.conf :
Example:
Defining a VXLAN Network¶
To create a VXLAN network include the following information:
The following example defines a VXLAN network
In this scenario, the driver will check for the existence of the
vxlan50 bridge. If it doesn’t exist it will be created. eth0 will be tagged (eth0.50 ) and attached to vxlan50 (unless it’s already attached). Note that eth0 can be a 802.1Q tagged interface if you want to isolate the OpenNebula VXLAN traffic.
Using VXLAN with BGP EVPN¶![]()
By default VXLAN relies on multicast to discover tunnel endpoints, alternatively you can use MP-BGP EVPN for the control plane and hence increase the scalability of your network. This section describes the main configuration steps to deploy such setup.
Configuring the Hypervisors¶
The hypervisor needs to run a BGP EVPN capable routing software like FFRouting (FRR). Its main purpose is to send BGP updates with the MAC address and IP (optional) for each VXLAN tunnel endpoint (i.e. the VM interfaces in the VXLAN network) running in the host. The updates needs to be distributed to all other hypervisors in the cloud to achieve full route reachability. This second step is usually performed by one or more BGP route reflectors.
As an example, consider two hypervisors 10.4.4.11 and 10.4.4.12, and a route reflector at 10.4.4.13. The FRR configuration file for the hypervisors could be (to announce all VXLAN networks):
And the reflector for our AS 7675, and hypervisors in 10.4.4.0/24:
Note that this a simple scenario using the same configuration for all the VNIs. Once the routing software is configure you should see the updates in each hypervisor for the VMs running in it, for example:
Configuring OpenNebula¶
You need to update
/var/lib/one/remotes/vnm/OpenNebulaNetwork.conf file to:
After updating the configuration file do not forget to run onehost sync -f to distribute the changes.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |