To create VNICs, use the dladm create-vnic command.
# dladm create-vnic -l link [-v vid] VNIC
The name of the link over which the VNIC is configured.
The VLAN ID of the VNIC if you want to create the VNIC as a VLAN. To configure a VNIC with a VLAN ID, see How to Configure VNICs With VLAN IDs. For more information about VLANs, see Chapter 3, Configuring Virtual Networks by Using Virtual Local Area Networks, in Managing Network Datalinks in Oracle Solaris 11.2 .
The name of the VNIC. For the guidelines about how to create customized names, see Rules for Valid Link Names in Configuring and Administering Network Components in Oracle Solaris 11.2 .
You can configure other properties for a VNIC, such as MAC addresses and CPUs to be associated with the VNIC. For a list of these properties, see the dladm (1M) man page. Certain property modifications work only with VNICs. For example, with the dladm create-vnic command, you can configure a MAC address as well as assign a VLAN ID to create a VNIC as a VLAN. However, you cannot configure a MAC address directly for a VLAN by using the dladm create-vlan command.
You can create only one VNIC at a time over a datalink. Like datalinks, VNICs have link properties that you can further configure as needed. For information about the different types of link properties, see Network Resource Management by Using Datalink Properties.
In addition to the VNICs that you can create by using the dladm create-vnic command, the system also creates VNICs known as system-created VNICs that help in virtual network I/O for Oracle VM Server for SPARC vnet. The system-created VNICs follow the naming convention <entity>-<name>, where entity refers to the system entity that created the VNIC and name refers to the VNIC name within the system entity. The user-created VNIC name cannot contain a hyphen (-). Only a system-created VNIC contains a hyphen (-), which helps you to differentiate between a system-created VNIC and a user-created VNIC. You cannot modify, rename, plumb, or delete system-created VNICs. For more information, see Oracle VM Server for SPARC 3.1 Administration Guide.
You can use the dlstat and snoop commands to monitor network traffic on system-created VNICs. You can also create flows over system-created VNICs by using the flowadm command. Flows help you not only manage network resources but also to monitor network traffic statistics. You can monitor network traffic statistics on flows by using the flowstat command. For more information about flows, see Configuring Flows.
To create etherstubs, use the dladm create-etherstub command.
# dladm create-etherstub etherstub
where etherstub is the name of the etherstub that you want to create.