Reddit mentions of Networking for VMware Administrators (VMware Press Technology)

I know this isn't the answer you are looking for, but this book might be worth looking in to. I haven't received my copy yet, but so far it seems to have been getting quite good reviews from the VMWare community.

I am sure many people will add to this but what I find is the biggest gap is not having a good base of understanding of why all of this "Infrastructure" is needed.

There is so much content to learn and I am not even scratching the surface. There is much to learn and you are not alone.

Hands-on labs
https://labs.hol.vmware.com/HOL/catalogs/catalog/1212

Physical networking (My teacher)
https://www.pluralsight.com/authors/ross-bagurdes

Virtual Networking
https://www.amazon.com/Networking-VMware-Administrators-Press-Technology/dp/0133511081

Storage
https://www.amazon.com/Mastering-VMware-vSphere-Storage-Victor-ebook/dp/B00YSIL6HQ

vSAN
https://www.amazon.com/VMware-vSAN-6-7-Deep-Dive-ebook/dp/B07L8CNZ53

NSX
https://blogs.vmware.com/networkvirtualization/2018/10/nsx-vmworld-2018-europe-the-technical-geek-guide.html/

ESXi Deep dive
https://pages.rubrik.com/host-resources-deep-dive_request.html

vVols are making a comeback
https://blogs.vmware.com/virtualblocks/2019/07/25/vvols-vmworld-2019/

Project pacific
https://blogs.vmware.com/vsphere/2019/09/project-pacific-at-tech-field-day-extra-at-vmworld-2019.html

Good mentions
https://storagehub.vmware.com/
https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/virtual_networking_concepts.pdf

And any VMware feature you need a walkthrough
https://featurewalkthrough.vmware.com/

Edit: adding newest deep dive for Pacific https://cormachogan.com/2019/11/22/project-pacific-vmworld-2019-deep-dive-updates/

I got a lot of value out of this book. You'll need to understanding networking fairly well if you want to be a decent VMware engineer.

https://www.amazon.com/Networking-VMware-Administrators-Press-Technology/dp/0133511081

Chris Wahl has a great blog as well: http://wahlnetwork.com/

When I said "the network" I meant the physical network. The virtual port will be the secondary's assigned virtual port of course.

The hosts can be connected to the same or to different physical switches, but they'd be connected to the same logical networks/vlans. In either case, the physical switchs will eventually see a frame from the VM on a physical port it had not before. When this happens the switch will add the source MAC address of the VM to it's forwarding table indicating that "this MAC exists on port N". Future frames destined for the VM's MAC will now be sent to this new port.

There is a NIC Teaming policy for each vSwitch called "Notify Switches" related to this. If this policy is enabled the destination host will send out frames with the MAC of the incoming VM so that the physical switches know ahead of time to start sending frames destined for the VM's MAC to the new physical port. This way when the VM stops executing on the source host and starts executing on the destination host, there will be a much smaller number of packets that potentially don't make it to the VM. I'm not sure if this settings applies to FT fail over events, but it would be easy to test with the right equipment in a lab.

If you're interested in knowing more about networking from the perspective of a VMware administrator check out this book. It starts from the very basics of networking (first 6 chapters) and then goes from there to vSphere specific topics. Would probably be a good read for you.