| 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>
|
|---|
| 8 | <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports Virtual Network Interface (VNIC) templates
|
|---|
| 9 | for configuring VMs over VLANs. An <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VNIC template is
|
|---|
| 10 | a VNIC whose name starts with
|
|---|
| 11 | <filepath>vboxvnic_template</filepath>. The string is
|
|---|
| 12 | case-sensitive.
|
|---|
| 13 | </p>
|
|---|
| 14 | <p>
|
|---|
| 15 | On Oracle Solaris 11 hosts, when Crossbow-based bridged networking
|
|---|
| 16 | is used, a VNIC template may be used to specify the VLAN ID to use
|
|---|
| 17 | while bridging over a network link.
|
|---|
| 18 | </p>
|
|---|
| 19 | <p>
|
|---|
| 20 | The following is an example of how to use a VNIC template to
|
|---|
| 21 | configure a VM over a VLAN. Create an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VNIC
|
|---|
| 22 | template, by executing as root:
|
|---|
| 23 | </p>
|
|---|
| 24 | <pre xml:space="preserve"># dladm create-vnic -t -l nge0 -v 23 vboxvnic_template0</pre>
|
|---|
| 25 | <p>
|
|---|
| 26 | This will create a temporary VNIC template over interface
|
|---|
| 27 | <userinput>nge0</userinput> with the VLAN ID 23. To create VNIC
|
|---|
| 28 | templates that are persistent across host reboots, skip the
|
|---|
| 29 | <codeph>-t</codeph> parameter in the above command. You may check
|
|---|
| 30 | the current state of links using the following command:
|
|---|
| 31 | </p>
|
|---|
| 32 | <pre xml:space="preserve">$ dladm show-link
|
|---|
| 33 | LINK CLASS MTU STATE BRIDGE OVER
|
|---|
| 34 | nge0 phys 1500 up -- --
|
|---|
| 35 | nge1 phys 1500 down -- --
|
|---|
| 36 | vboxvnic_template0 vnic 1500 up -- nge0
|
|---|
| 37 |
|
|---|
| 38 | $ dladm show-vnic
|
|---|
| 39 | LINK OVER SPEED MACADDRESS MACADDRTYPE VID
|
|---|
| 40 | vboxvnic_template0 nge0 1000 2:8:20:25:12:75 random 23</pre>
|
|---|
| 41 | <p>
|
|---|
| 42 | Once the VNIC template is created, any VMs that need to be on VLAN
|
|---|
| 43 | 23 over the interface <userinput>nge0</userinput> can be configured to
|
|---|
| 44 | bridge using this VNIC template.
|
|---|
| 45 | </p>
|
|---|
| 46 | <p>
|
|---|
| 47 | VNIC templates makes managing VMs on VLANs simpler and efficient.
|
|---|
| 48 | The VLAN details are not stored as part of every VM's
|
|---|
| 49 | configuration but rather inherited from the VNIC template while
|
|---|
| 50 | starting the VM. The VNIC template itself can be modified anytime
|
|---|
| 51 | using the <userinput>dladm</userinput> command.
|
|---|
| 52 | </p>
|
|---|
| 53 | <p>
|
|---|
| 54 | VNIC templates can be created with additional properties such as
|
|---|
| 55 | bandwidth limits and CPU fanout. Refer to your Oracle Solaris
|
|---|
| 56 | network documentation for details. The additional properties are
|
|---|
| 57 | also applied to VMs which bridge using the VNIC template.
|
|---|
| 58 | </p>
|
|---|
| 59 | </body>
|
|---|
| 60 |
|
|---|
| 61 | </topic>
|
|---|
