Not going to lie, that [the one you mentioned view first] was an excellent lesson and truly filled my head with understanding and concept. I have used esxi in a more "fun" scenario and did get my vms up and running and have enjoyed it but I had figured it out "successfully" but without the knowledge behind it, and this video definitely cleared it up.
With that being said, I struggle to see how to implement this in a Cisco vSwitch scenario in regards to "my" description as 'reverse interface' meaning normally the VM gets assigned a NIC/vmnic and it works.. But in this case I assign the vm [Cisco vswitch] a vnic to use backwards from that to assign to VM's. So, I assign the vSwitch 3 Interfaces. 1.) Management, 2.) Uplink to Router [Internet] 3.) The interface to use for the other Vm's on esxi.
My more refined confusion is this; Can I use ONE Physical Interface [assign it to a 2nd Switch on Esxi] and divide it to 3 port groups. 1 - management, isolated from LAN and internet. 2 - uplink to internet/router and isolated from management and LAN and 3 - LAN usage isolated from management and internet for VM's. When I say isolated, I refer to the esxi Switch, not the fact that within the Cisco vSwitch they will be able to communicate.
In this scenario, the Cisco vSwitch can ping 8.8.8.8 for internet [Using 2, Uplink] and any vm that is assigned to it's same port group [3, LAN]. And then when I create VM's, I use the Port Group 3, LAN, interface on the esxi Switch for their access to the Internet as well as other VM's on the same PG 3.
Or, did I miss it altogether still.
P.S I know this might possibly even be an esxi question for their forum but I really want this focus on Cisco vswitch being used on esxi, not just their vSwitch.
