Differences

This shows you the differences between two versions of the page.

--- interfaces_vswitches_and_port_groups [2017/07/18 11:05] – [Terminology] walkeradmin
+++ interfaces_vswitches_and_port_groups [2017/07/18 11:28] – walkeradmin
@@ Line 19: / Line 19: @@
 \\
 \\
-vmnic - This is the name VMWare has assigned to each of your physical interfaces. So on my server I have vmnic0 to vmnic11 (vmnic0 is my connected to my management switch, vmnic7 is connected to my data switch).
+<color #22b14c>vmnic</color> - This is the name VMWare has assigned to each of your physical interfaces. So on my server I have <color #22b14c>vmnic0</color> to <color #22b14c>vmnic11</color> (<color #22b14c>vmnic0</color> is my connected to my management switch, vmnic7 is connected to my data switch).
 \\
 \\
@@ Line 26: / Line 26: @@
 ==== Graphical Overview ====
 As a picture paints a thousand words, let us look at what we are dealing with graphically.
+\\
+\\
+Imagine for simplicity, you wanted each Physical Interface to map to an interface in your VM. Lets say you have 3 Interfaces in your VM, you would have something like this.
+\\
+\\
+{{ :single_int.jpg?450 |}}
+\\
+Now while this is valid, consider that I am passing data from VM1 to VM2, I would need, with 2 data ports per VM, four data ports. What would be better is if I put the data out of VM1 and data in of VM 2 in a port group, that shared a single interface.
+\\
+\\
+In the example below we can see that the third physical interface is connected to both VMs (the yellow lines) and both of these interfaces are in the same Port Group. This means we shared data between the two VMs using only a single port.
+\\
+{{ :shared_interface.jpg?450 |}}
+\\
 \\
+\\
+\\
+\\
+\\
+\\
+\\