EVS hosts that connect to the EVS switch are also called compute nodes. The connection is established through the host's VNIC. The host itself can contain virtual machines which connect to the switch through VNIC anets. Thus, zones can become EVS nodes as well.
This procedure describes steps to configure a node to become part of the EVS topology. It contains steps that also involve non-global zone configuration. The information related to non-global zone is limited to what is relevant to EVS setups. For complete details about how to create, install, and configure zones, see Creating and Using Oracle Solaris Zones.
Before You Begin
The following must be completed:
Required EVS packages are installed. See Installing the Required Packages.
SSH authentication for evsuser is completed. See About SSH Authentication and the evsuser.
The controller node is configured. See Configuring the EVS Controller.
The elastic virtual switch is configured. See How to Configure an Elastic Virtual Switch.
The host itself can already contain existing zones. Or, you can simultaneously create the zone and configure it to connect to the switch.
evsnode$ dladm create-vnic -t -c EVS-switch-name[/VPort-name] [-T tenant-name] VNIC-name
Specifies that the VNIC is temporary, which is required for VNICs created for EVS.
Name of the elastic virtual switch to which the VNIC will connect. If you do not specify the VPort name, the system automatically generates a VPort and assigns the VPort to the VNIC. After the VNIC is connected to an elastic virtual switch, the VNIC either inherits the properties from the specified elastic virtual switch or VPort.
Name of the tenant that owns the EVS. If the tenant is not specified, then the system assumes the owner is the default sys-global tenant.
The name of the VNIC.
evsnode$ dladm show-vnic -c
The –c option displays the information specifically about VNICs connected to an elastic virtual switch.
You use the zonecfg command to perform this step. Refer to the example for the command usage.
The anet resource has the following properties to set for a zone:
Specifies the name of the tenant. If a value is not specified when configuring a zone, the system assigns the default value, sys-global tenant.
Specifies the name of the virtual port. If a value is not specified when configuring a zone, a system VPort is automatically generated for the elastic virtual switch and the port inherits the elastic virtual switch properties.
Specifies the name of an elastic virtual switch to which you must connect the anet resource.
This example shows how to create a zone with a VNIC anet resource to connect to the switch and has the following details:
Zone: evszone
Tenant: tenantA
Elastic Virtual Switch: ORA
Host's datalink: net1
VNIC anet for the zone: evszone/net1
evsnode$ zonecfg -z evszone Use 'create' to begin configuring a new zone zonecfg:evszone> create create: Using system default template 'SYSdefault' zonecfg:evszone> set zonepath=/export/zones/evszone zonecfg:evszone> set tenant=tenantA zonecfg:evszone> add anet zonecfg:evszone:net> set evs=ORA zonecfg:evszone:net> set vport=vport0 zonecfg:evszone:net> end zonecfg:evszone> exit evsnode$ zoneadm -z evszone install evsnode$ zoneadm -z evszone boot evsnode$ zlogin -C evszone evsnode$ dladm show-vnic -c LINK TENANT EVS VPORT OVER MACADDRESS IDS evszone/net1 tenantA ORA vport0 net2 2:8:20:89:a1:97 VID:200
When evszone boots, the VNIC anet evszone/net1 is associated with the MAC address, IP address, and SLA properties of the VPort ORA/vport0. For more information about configuring a zone's VNIC anet resources for an elastic virtual switch, see Use Case: Configuring an EVS Network Topology.