You have been asked to troubleshoot the initial configuration of a virtual network connecting two
local zones with the outside world.
View the exhibit.
The command
dladm create-vnic -1 vswitch192.168.1 vnic1
fails with the error
dladm: invalid link name ‘vswitch192.168.1’
What is the reason for this error?
A.
The name vswitch192.168.1 is not legal.
B.
The zone must be specified with
dladm create-vnic -z zone3 vnic1.
C.
The virtual interface must be specified with
dladm create-vnic -z zone3 vnic1.
D.
The virtual interface must be created with
ipadm create-vnic -1 switch192.168.1.
E.
The virtual switch must be created first with
dladm create -etherstub vswitch192.168.1.
Explanation:
There is no data-link named vswitch192.168.
We need to create an etherstub first.
See Note and example below for details.
Note: Create a VNIC in the system’s global zone.
# dladm create-vnic -l data-link vnic-name
data-link is the name of the interface where the VNIC is to be configured.
-l link, –link=linklink can be a physical link or an etherstub.
vnic-name is the name that you want to give the VNIC.
For example, to create a VNIC named vnic0 on interface e1000g0, you would type the following:
# dladm create-vnic -l e1000g0 vnic0
Example: Creating a Virtual Network Without a Physical NIC
First, create an etherstub with name stub1:
# dladm create-etherstub stub1
Create two VNICs with names hello0 and test1 on the etherstub. This
operation implicitly creates a virtual switch connecting hello0 and
test1.
# dladm create-vnic -l stub1 hello0
# dladm create-vnic -l stub1 test1
Reference: man dladm
E
E
root@s11:~# dladm create-vnic -l vswitch192.168.1 vnic1
dladm: invalid lower link name ‘vswitch192.168.1’
root@s11:~# dladm create-etherstub vswitch192.168.1
root@s11:~# dladm create-vnic -l vswitch192.168.1 vnic1
root@s11:~# dladm
LINK CLASS MTU STATE OVER
net1 phys 1500 up —
net0 phys 1500 up —
dbzone/net0 vnic 1500 up net0
vswitch192.168.1 etherstub 9000 unknown —
vnic1 vnic 9000 unknown vswitch192.168.1