No, you will create a port group for each VLAN. You can create a third VDS (or use a VSS) for MGMT if you really want, but you are also fine to continue making a port group for each VLAN on the e...
See more...
No, you will create a port group for each VLAN. You can create a third VDS (or use a VSS) for MGMT if you really want, but you are also fine to continue making a port group for each VLAN on the existing switch. You will want to manipulate the active / standby / unused for your port groups to separate vMotion traffic from guest and management traffic. The main drawback to how it is configured now is that you are sending your traffic untagged, you will need to have the upstream ports configured as trunks and then add VLAN tags to your port groups. Your network team should be able to configure a "native VLAN" on the trunk for the same VLAN that is currently assigned. This will allow you to continue sending untagged traffic while you work to migrate your port groups to VLANs. With 8 uplinks per host you could do - MGMT - VLAN XXX - Active Uplink 1 , Standby Uplink 2, Unused all others vMotion - VLAN YYY - Active Uplink 2, Standby Uplink 1, Unused all others Desktops - VLAN DDD - Active Uplinks 3 - 8, unused 1,2 This would provide separation of traffic without needing to create another VDS. You have enough NICs that you have flexibility to do anything you want, so you definitely have the option of just creating a VDS MGMT and vMotion and moving these guys over. You do want to make sure that MGMT and vMotion are on separate subnets and VLANs. Edit - There are a lot of options for network configurations, and with 10G and the number of gig interfaces you have you could do any. You may want to read Chris Wahls networking for VMware book so you know all of your options and the trade offs.