How to Modify Ethernet SR-IOV Virtual Function Properties

Identify the physical function device.
```
primary# ldm list-io
```
Note that the name of the physical function includes the location information for the PCIe SR-IOV card or on-board device.

Modify a virtual function property.

ldm set-io name=value [name=value...] vf-name

Example 8-9 Modifying Ethernet Virtual Function Properties

These examples describe how to use the ldm set-io command to set properties on an Ethernet virtual function.

The following example modifies properties of the specified virtual function, /SYS/MB/NET0/IOVNET.PF0.VF0, to be part of VLAN IDs 2, 3, and 4.
```
primary# ldm set-io vid=2,3,4 /SYS/MB/NET0/IOVNET.PF0.VF0
```
Note that this command dynamically changes the VLAN association for a virtual function. To use these VLANs, the VLAN interfaces in the I/O domains must be configured by using the appropriate Oracle Solaris OS networking commands.
The following example sets the pvid property value to 2 for the /SYS/MB/NET0/IOVNET.PF0.VF0 virtual function, which transparently makes the virtual function part of VLAN 2. Namely, the virtual function will not view any tagged VLAN traffic.
```
primary# ldm set-io pvid=2 /SYS/MB/NET0/IOVNET.PF0.VF0
```
The following example assigns three automatically allocated alternate MAC addresses to a virtual function. The alternate addresses enable the creation of Oracle Solaris 11 virtual network interface cards (VNICs) on top of a virtual function. Note that to use VNICs, you must run the Oracle Solaris 11 OS in the domain.

Note:
Before you run this command, stop the domain that owns the virtual function.
```
primary# ldm set-io alt-mac-addrs=auto,auto,auto /SYS/MB/NET0/IOVNET.PF0.VF0
```

The following example sets the device-specific unicast-slots property to 12 for the specified virtual function. To find the device-specific properties that are valid for a physical function, use the ldm list-io -d pf-name command.

primary# ldm set-io unicast-slots=12 /SYS/MB/NET0/IOVNET.PF0.VF0

All configuration changes for other domains are disabled until the primary
domain reboots, at which time the new configuration for the primary domain
will also take effect.