Changing the Default EVB Configuration

Language:

Typically, you do not need to change a default EVB configuration, which is generally sufficient as an operational EVB in a majority of cases. In the default configuration, the Oracle Solaris VSI Manager ID, ORACLE_VSIMGR_V1 automatically generates the VSI Type ID for the VNICs that you create. You do not need to set EVB-related datalink properties.

If you want to control and manage EVB configuration, then you must configure the following datalink properties that are related to EVB:

vsi-manager-id – Specifies the VSI Manager ID that is set for a physical link or a VNIC. If this property is not set for a VNIC, the default value, ORACLE_VSIMGR_V1, of the underlying physical link is used.

If you explicitly set the vsi-manager-id property, then you also need to explicitly set the VSI Type ID and VSI Version. In addition, you also need to explicitly configure these properties on the datalinks.

Note - In Oracle Solaris, when you manually configure the VSI Manager ID, VSI Type ID, and VSI Version, the corresponding VNIC properties are not automatically configured.
vsi-manager-id-encoding – Indicates the encoding that is associated with the VSI Manager ID. By default, this property is set to oracle_v1. If you do not want to associate oracle_v1 with the VSI Manager ID, set this property value to none. When you set the value none, also make sure that you configure the VSI Manager ID, VSI Type ID, and VSI Version manually because they will not be automatically generated.
vsi-type-id – Specifies a VSI Type ID. A VSI Type ID pairs with a VSI Version to be associated with a VSI profile. This 3-byte value is automatically generated if you use the default values for vsi-manager-id and vsi-manager-id-encoding. Otherwise, you must explicitly specify a value for this property.
vsi-version – Specifies a VSI Version. The VSI Version pairs with a VSI Type ID to be associated with a VSI profile. This 1-byte value is automatically generated if you use the default values for vsi-manager-id and vsi-manager-id-encoding. Otherwise, you must explicitly specify a value for this property.

You can display EVB-related properties by using the dladm show-linkprop command. You can obtain the effective values of the VNIC-related link properties from their respective EFFECTIVE field values of the properties. For more information, see Example 48, Displaying EVB-Related Datalink Properties on a Physical Link.

For more information about the EVB components, see Exchanging VNIC Information by Using VDP. For more information about EVB, see the evb(4P) man page.

How to Change the Default EVB Configuration

You must configure the vsi-manager-id and vsi-manager-id-encoding properties only on the physical link. The other EVB-related properties, such as vsi-type-id and vsi-version, must be configured on a VNIC.

Before You Begin

Ensure that your role has the appropriate rights profile to perform this procedure. See Using Rights Profiles to Perform Network Configuration.

Create a VNIC by using the datalink properties mentioned in the profile database.

$ dladm create-vnic -l datalink -p max-bw=max-bw-value,priority=priority-value VNIC

Set the encoding that is associated with the VSI Manager ID to none on the physical link because you are not using the default Oracle VSI Manager ID.
```
$ dladm set-linkprop -p vsi-manager-id-encoding=none datalink
```
Set the VSI Manager ID on the physical link with an IPv6 address.
```
$ dladm set-linkprop -p vsi-manager-id=IPv6-address datalink
```

Set the VSI Type ID and VSI Version for the VNIC that you have created.

$ dladm set-linkprop -p vsi-type-id=VSI-Type-ID,vsi-version=vsi-version VNIC

Verify the properties that are set for the VNIC.
```
$ dladm show-linkprop VNIC
```

Example 47 Setting EVB-Related Datalink Properties

The following example shows how to set datalink properties that are related to EVB. This example uses a system with a profile that you can access by using an IPv6 address, IP1.

Assume that the VSI Manager ID, IP1 has the following profiles defined:

VSI Type ID: 2
VSI Version: 1
Datalink properties: max-bw=20, priority=5

The VDP ASSOC TLV unit for vnic1 contains the following information:

VSI Manager ID = IP1
VSI Type ID = 2
VSI Version = 1

$ dladm create-vnic -l net0 -p max-bw=20,priority=5 vnic1

$ dladm set-linkprop -p vsi-manager-id-encoding=none net0
$ dladm set-linkprop -p vsi-manager-id=IP1 net0
$ dladm set-linkprop -p vsi-type-id=2,vsi-version=1 vnic1

$ dladm show-linkprop vnic1
LINK     PROPERTY                PERM VALUE      EFFECTIVE  DEFAULT    POSSIBLE
...
vnic1    vsi-type-id             rw   2          2           --         --
vnic1    vsi-version             rw   1          1           --         --
vnic1    vsi-manager-id          rw   IP1        IP1         --         --
vnic1    vsi-manager-id-encoding rw   --         none        oracle_v1  none,oracle_v1
...

Example 48 Displaying EVB-Related Datalink Properties on a Physical Link

The following example displays EVB-related properties on the physical link.

$ dladm show-linkprop -p vsi-manager-id,vsi-manager-id-encoding net4
LINK     PROPERTY                 PERM VALUE        EFFECTIVE    DEFAULT      POSSIBLE
net4     vsi-manager-id           rw   --           --           ::           --
net4     vsi-manager-id-encoding  rw   --           --           oracle_v1    none,oracle_v1

The output displays the default configuration of EVB in Oracle Solaris. By using the oracle_v1 encoding, the VSI Type ID and VSI version are automatically generated from the properties that are configured on the VNICs.

Example 49 Displaying EVB-Related Properties on a VNIC

The following example displays EVB-related properties on a VNIC.

$ dladm show-linkprop vnic0
LINK     PROPERTY                 PERM VALUE      EFFECTIVE  DEFAULT    POSSIBLE
...
vnic0    vsi-type-id              rw   --         94         --         --
vnic0    vsi-version              rw   --         0          --         --
vnic0    vsi-manager-id           rw   --         ::         --         --
vnic0    vsi-manager-id-encoding  rw   --         oracle_v1  oracle_v1  none,oracle_v1
...

The output displays the effective encoding for vnic0 as oracle_v1. In turn, the EFFECTIVE value for vsi-type-id 94 is automatically generated and effective for vnic0.