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 11:07] – walkeradmin | interfaces_vswitches_and_port_groups [2017/07/18 11:18] – walkeradmin | ||
|---|---|---|---|
| Line 29: | Line 29: | ||
| \\ | \\ | ||
| 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. | 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. | ||
| + | \\ | ||
| \\ | \\ | ||
| + | \\ | ||
interfaces_vswitches_and_port_groups.txt · Last modified: 2023/03/09 22:35 by 127.0.0.1