VMware Network Config Setup Help?

[VMware2024]

How do I properly set up the network on new ESXi 8.0.3 hosts (Dell Intel) to migrate VMs from an older HP (AMD)vCenter setup with minimal disruption?

I'm in the process of migrating from an older VMware environment to a new one and want to make sure I set up the networking properly this time. Here's what I'm working with:

Current Environment (Old Setup):

• 3x HP servers running ESXi 7.0.3 Enterprise Plus
• vCenter 8.0.3 Standard
• AMD CPUs
• Old iSCSI storage (TrueNas)
• Networking:
• Single standard vSwitch) per host
• 8 Port Groups on that vSwitch0 attached to 2 40gb links
• 2 physical NICs per host
• No vDS in use

New Environment:

• 3x Dell servers running ESXi 8.0.3 Enterprise Plus
• vCenter 8.0.3 Standard
• Intel CPUs
• New SAN (FX2141) storage/FS6400 total storage space 13GB flash
• Planning to migrate 40 VMs to the new Dell hosts

What I Want to Do:

I'd like to set up the network properly on the new Dell hosts before migrating the VMs. Here's what I understand so far:

• Create multiple vmkernel interfaces with VLAN separation, such as:
• vmk0 = Management (VLAN X)
• vmk1 = vMotion (VLAN Y)
• vmk2 = VM Network (VLAN Z)
• vmk3 = iSCSI Storage (VLAN A)

My Questions:

1. Should I recreate the current (messy) network setup on the new hosts just to migrate VMs, and then fix it afterward?
2. Or is it better to set up the proper network config now and migrate VMs into the cleaner environment?
3. How do I implement the network configs above with the old ones
4. Any tips or best practices for setting up networking on the new hosts to match port groups and avoid VM downtime during migration?

Any guidance on the best way to structure this migration from a networking standpoint would be greatly appreciated!

[ninjabrum]

You can't vMotion from AMD to Intel (and vice versa).  You can put all your vmKernels and portgroups on the same vSwitch with 40Gb links.  New hardware is a good time to review your setup.  Follow the vSphere 8 guide for best practices.

https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/esxi-installation-and-setup-8-0/about-esxi-installation-and-setup-install.html

[CSpreha]

You can migrate to this new environment, just not Hot.   I would set up the new env cleanly, make some nicely named vDS and vPGs according to the same VLANs and subnets.   Since these will be cold vMotions (going from AMD to Intel), during the vMotion wizard you'll have to specify the destination vPG anyway, so name them nicely to ease your future work.  

Hint: also take the time to bump VMX versions on Windows/Linux VMs if you can since it's a cold move, update Operating system dropdown to match if needed as well.  Use caution if it's an appliance/OVA type VM as VMX changes can break them unless approved by the Vendor.

Enjoy!

[Alexandru Capras]

You should build the new Dell network clean from the start. VLAN tagging, VM network separation, and proper iSCSI setup (with two VMkernel adapters for port binding) you're already on the right track. 

Since you're migrating from AMD to Intel, cold migration is likely your best option. HCX can help with live migration across CPU types if you have it licensed, but it might be overkill here.
An easier move would be to temporarily mount the old TrueNAS storage on the Dell hosts, power off the VMs, register them from the existing datastore, then do a Storage vMotion to the new SAN when you're ready.

On the old setup, there's one vSwitch per host with 8 port groups - are these actually using VLANs, or is everything just untagged on access ports?