An EVS controller provides functionality for the configuration and administration of an elastic virtual switch and all the resources associated with it. You must set properties for an EVS controller, which captures information necessary for implementing Layer 2 segments across physical machines. For more information, see EVS Controller.
Planning for an EVS controller includes the following considerations:
Determine whether you are implementing the elastic virtual switch by using a VLAN, VXLAN, or both.
If you use a VLAN to implement the elastic virtual switch, you need to set the properties uplink-port and vlan-range.
If you use a VXLAN to implement the elastic virtual switch, you need to set the properties vxlan-range and uplink-port or vxlan-addr. Optionally, you can also set the properties vxlan-mgroup and vxlan-ipvers.
If the compute nodes do not have the same datalink, then for every compute node, you need to specify the datalink for the uplink-port property.
For example, consider two compute nodes, host1 with the datalink net2 and host2 with the datalink net3. You need to specify the datalinks of both the hosts when you set the uplink-port property as follows:
# evsadm set-controlprop -h host1 -p uplink-port=net2 # evsadm set-controlprop -h host2 -p uplink-port=net3