The next group of tasks involves creating an EVS switch that you use to deploy the cloud workload. Some configuration tasks are performed on the Oracle VM Server for SPARC service domain, while others are performed on the guest domains.
The following EVS setup is used:
Two compute nodes that correspond to two guest domains. Each guest domain has a net0 interface for its vnet datalink, which are then used as uplink-ports by the elastic virtual switch.
One node that acts as the EVS controller.
One node that acts as the EVS client.
Set of four zones: Zone-A1 and Zone-B1, which are configured on the first guest domain, and Zone-B2 and Zone-C2, which are configured on second guest domain.
The four zones are configured with a VNIC (anet) resource on each zone, which are then connected to the EVS switches.
Before You Begin
Perform all of the necessary planning and prerequisite tasks, which include installing the EVS packages and configuring the appropriate authorizations.
For planning instructions, see Perform Preliminary Tasks Prior to Creating an EVS Virtual Tenant Network.
For security requirements, see Security Requirements for Using EVS in Managing Network Virtualization and Network Resources in Oracle Solaris 11.3.
# evsadm set-prop -p controller=CONTROLLER
You can deploy the EVS controller on any node, as long as it can reach the Oracle VM Server for SPARC guest domains through the vnet interfaces.
For example, you can deploy the EVS controller in any of the following ways:
In the service domain's global zone
In a non-global zone of the service domain
In its own guest domain
On a separate physical machine
For more information about configuring an EVS controller, see Configuring an EVS Controller in Managing Network Virtualization and Network Resources in Oracle Solaris 11.3.
# evsadm set-controlprop -p l2-type=vxlan
# evsadm set-controlprop -p vxlan-range=200-300 # evsadm set-controlprop -p vxlan-addr=192.0.2.0/27
Note that you determine the VXLAN range during the planning phase, prior to setting up the EVS switch. For more information about configuring EVS controller properties, see Example 11, Configuring and Setting Properties for the EVS Controller.
# evsadm set-controlprop -p uplink-port=net0
# evsadm show-controlprop -p l2-type,vxlan-range,vxlan-addr NAME VALUE DEFAULT HOST l2-type vxlan vxlan -- vxlan-range 200-300 -- -- vxlan-addr 192.0.2.0/27 0.0.0.0 -- uplink-port net0 -- --
The controller must be assigned an IP address that is reachable from each of the guest domains. For this example, that IP address is 192.0.2.10/27.
# evsadm create-evs vswitch_a
Repeat this step to create the two other EVS switches that are used in the configuration (vswitch_b and vswitch_c).
# evsadm add-ipnet -p subnet=192.0.2.32/27 vswitch_a/ipnet # evsadm show-ipnet NAME TENANT SUBNET DEFROUTER AVAILRANGE vswitch_a/ipnet sys-global 192.0.2.32/27 192.0.2.33 192.0.2.34-192.0.2.63
Repeat this step for the two other EVS switches that are used in the configuration (vswitch_b and vswitch_c).
# evsadm NAME TENANT STATUS VNIC IP HOST vswitch_a sys-global -- -- vswitch_a/ipnet --
# evsadm show-evs -L EVS TENANT VID VNI vswitch_a sys-global -- 200 vswitch_b sys-global -- 201 vswitch_c sys-global -- 202