Create an EVS Switch to Deploy the Cloud Workload

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.

  ---

  Note -  The EVS controller and the EVS client can be located on the same host.

  ---

• 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.

How to Configure an EVS Virtual Switch to Deploy a Cloud Workload

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.2 .

1. Configure each compute node to point to the EVS controller.

   # 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 follow 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.2 .

2. On the controller, configure the required EVS properties for the compute nodes.
   1. Set the L2 topology.

      # evsadm set-controlprop -p l2-type=vxlan 

   2. Set the VXLAN range and IP address.

      # evsadm set-controlprop -p vxlan-range=200-300
      # evsadm set-controlprop -p vxlan-addr=192.168.70.0/24

      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 2–11.

   3. Specify the uplink-port (datalinks) that are used for the VXLAN.

      # evsadm set-controlprop -p uplink-port=net0

   4. Verify the configuration.

      # 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.168.70.0/24     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.168.70.10.

3. Create and verify the EVS virtual switch, which is named vswitch_a in this example.
   1. Create the EVS switch.

      # 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).

   2. Add the IPnet information to the EVS switch and verify the configuration.

      # evsadm add-ipnet -p subnet=192.168.80.0/24 vswitch_a/ipnet
      # evsadm show-ipnet
      
      NAME             TENANT     SUBNET          DEFROUTER    AVAILRANGE
      vswitch_a/ipnet  sys-global 192.168.80.0/24 192.168.80.1 192.168.80.2-192.168.80.254
        

      Repeat this step for the two other EVS switches that are used in the configuration (vswitch_b and vswitch_c).

   3. Verify that the virtual switch was successfully created.

      # evsadm
      NAME         TENANT       STATUS     VNIC      IP               HOST
      vswitch_a    sys-global    --         --      vswitch_a/ipnet    --

   4. Check the VLAN ID that is associated with the virtual switch.

      # evsadm show-evs -L
      EVS       TENANT        VID      VNI
      vswitch_a   sys-global  --       200
      vswitch_b   sys-global  --       201
      vswitch_c   sys-global  --       202