interfaces_vswitches_and_port_groups
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
interfaces_vswitches_and_port_groups [2017/07/18 10:31] – walkeradmin | interfaces_vswitches_and_port_groups [2017/07/18 11:18] – 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. | 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, | ||
+ | \\ | ||
+ | \\ | ||
+ | <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | |||
+ | ---- | ||
+ | ==== 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. | ||
+ | \\ | ||
+ | \\ | ||
+ | {{ : | ||
+ | \\ | ||
+ | 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. | ||
+ | \\ | ||
+ | \\ | ||
+ | |||
+ | \\ | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | \\ | ||
+ | \\ | ||
+ | \\ | ||
+ | \\ | ||
+ | \\ | ||
+ | \\ | ||
+ | |||
+ | |||
+ | |||
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. | 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. | ||
\\ | \\ | ||
Line 72: | Line 116: | ||
\\ | \\ | ||
\\ | \\ | ||
- | + | Below is a visualisation of the relationship between Physical Interfaces, vSwitches, Port Groups and Virtual Machines. | |
+ | \\ | ||
+ | \\ | ||
+ | {{ : | ||
interfaces_vswitches_and_port_groups.txt · Last modified: 2023/03/09 22:35 by 127.0.0.1