| 1 | <?xml version='1.0' encoding='UTF-8'?>
|
|---|
| 2 | <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
|
|---|
| 3 | <topic xml:lang="en-us" id="vboxbowvnictemplates">
|
|---|
| 4 | <title><ph conkeyref="vbox-conkeyref-phrases/product-name"/> VNIC Templates for VLANs on Oracle Solaris 11 Hosts</title>
|
|---|
| 5 |
|
|---|
| 6 | <body>
|
|---|
| 7 | <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports Virtual Network Interface (VNIC) templates for
|
|---|
| 8 | configuring VMs over VLANs. An <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VNIC template is a VNIC whose
|
|---|
| 9 | name starts with <filepath>vboxvnic_template</filepath>. The string is case-sensitive. </p>
|
|---|
| 10 | <p>On Oracle Solaris 11 hosts, when Crossbow-based bridged networking is used, a VNIC template may be used to
|
|---|
| 11 | specify the VLAN ID to use while bridging over a network link. </p>
|
|---|
| 12 | <p>The following is an example of how to use a VNIC template to configure a VM over a VLAN. Create an <ph
|
|---|
| 13 | conkeyref="vbox-conkeyref-phrases/product-name"/> VNIC template, by executing as root: </p>
|
|---|
| 14 | <pre xml:space="preserve"># dladm create-vnic -t -l nge0 -v 23 vboxvnic_template0</pre>
|
|---|
| 15 | <p>This will create a temporary VNIC template over interface <userinput>nge0</userinput> with the VLAN ID 23. To
|
|---|
| 16 | create VNIC templates that are persistent across host reboots, skip the <codeph>-t</codeph> parameter in the above
|
|---|
| 17 | command. You may check the current state of links using the following command: </p>
|
|---|
| 18 | <pre xml:space="preserve">$ dladm show-link
|
|---|
| 19 | LINK CLASS MTU STATE BRIDGE OVER
|
|---|
| 20 | nge0 phys 1500 up -- --
|
|---|
| 21 | nge1 phys 1500 down -- --
|
|---|
| 22 | vboxvnic_template0 vnic 1500 up -- nge0
|
|---|
| 23 |
|
|---|
| 24 | $ dladm show-vnic
|
|---|
| 25 | LINK OVER SPEED MACADDRESS MACADDRTYPE VID
|
|---|
| 26 | vboxvnic_template0 nge0 1000 2:8:20:25:12:75 random 23</pre>
|
|---|
| 27 | <p>Once the VNIC template is created, any VMs that need to be on VLAN 23 over the interface
|
|---|
| 28 | <userinput>nge0</userinput> can be configured to bridge using this VNIC template. </p>
|
|---|
| 29 | <p>VNIC templates makes managing VMs on VLANs simpler and efficient. The VLAN details are not stored as part of
|
|---|
| 30 | every VM's configuration but rather inherited from the VNIC template while starting the VM. The VNIC template
|
|---|
| 31 | itself can be modified anytime using the <userinput>dladm</userinput> command. </p>
|
|---|
| 32 | <p>VNIC templates can be created with additional properties such as bandwidth limits and CPU fanout. Refer to your
|
|---|
| 33 | Oracle Solaris network documentation for details. The additional properties are also applied to VMs which bridge
|
|---|
| 34 | using the VNIC template. </p>
|
|---|
| 35 | </body>
|
|---|
| 36 |
|
|---|
| 37 | </topic>
|
|---|
