Differences

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

--- interfaces_vswitches_and_port_groups [2017/07/18 10:46] – walkeradmin
+++ interfaces_vswitches_and_port_groups [2017/07/18 11:04] – walkeradmin
@@ Line 5: / Line 5: @@
 ----
+==== Overview ====
 If you are like me, and used earlier versions of VMWare (ver4) then version 6 might be a little confusing when it comes to the networking architecture. When I used to use older versions of VMWare (never used vCenter) you just as signed a physical interface to a VM. While you can still do this, it's not as obvious how to do it.
 \\
 \\
+==== Terminology ====
+When considering how networking functions in VMWare (6.5.0 is what i am using) it can seem very confusing, however once you have configured it once it makes a lot of sense, it's just a little confusing at first. Before we look at configuration, lets consider some common terms that we will be using.
+\\
+vSwitch - This is a virtual switch, this just allows a user to assign virtual ports (called port groups) to a virtual switch. A vSwitch contains one or more port groups and is associated with a physical interface.
+\\
+\\
+Port Groups - Port Groups are a bit like Cisco VLANs. You create a Port Group, and in each Virtual Machine you can assign each of your VM interfaces to a Port Group.
+\\
+\\
+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).
+\\
+\\
+----
+==== Graphical Overview ====
+As a picture paints a thousand words, let us look at what we are dealing with graphically.
+\\
 Consider my example below, I three servers, all connected to a switch, and I am passing multicast traffice between them, that is being processed in a particular way at each stage. Basically I want an input, two processing stages, a storage device and an output.
 \\