- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Ken,
Let say this is your ports and vmnic numbering
| Port Type and Port# | vmnic# | Physical Switch |
|---|---|---|
| Copper Port#1 | vmnic0 | Enterasys 7100 |
| Copper Port#2 | vmnic1 | Enterasys 7100 |
| Fibre Port#1 | vmnic2 | Extreme 670 |
| Fibre Port#2 | vmnic3 | Extreme 670 |
I would create 2 dvswitches one for back-end traffic vmnic0 & vmnic1 and another one for vmnic2 & vmnic3 as they are connected to different switches
If you use one dvswitch for all 4 vmnics, you would need to overrides each of the portgroup configuration.
For example, if you have a vMotion portgroup on a dvswitch that connects to all vmnics, you would need to override the portgroup to not use vmnic2 and vmnic3.
Separating them into two dvswitches will make it more easier to manage.
You mentioned about stacking and MLAG, if you are going to configure the uplinks as active-active using port-channel or LACP, the options for teaming are IP Hash and LACP Enhanced LACP Support on a vSphere 5.5 Distributed Switch (2051826)
Your understanding on route based on physical NIC load (LBT) is correct and this is normally used for VM traffic.
If you want to use LBT or route based on originating virtual port (port ID) then you should not configure port-channel or LACP down to the ESXi hosts
Author of VMware NSX Cookbook http://bit.ly/NSXCookbook
https://github.com/bayupw/PowerNSX-Scripts
https://nz.linkedin.com/in/bayupw | twitter @bayupw