mjmalleo's Posts

Makes perfect sense. I appreciate you and your generous time. It clicked.  thank you I noticed you removed vmnic from the equation.  Are they for if you were to use multiple ip’s (same network) on  vswitch. i.e 192.168.1.2, 192.168.1.3

I won't keep bugging you with initial configuration stuff. But this is kind of where I begin to lose my understanding.   In the end, the VM needs to see 2 Network Adapters. One coming from a 192.168.5.0 Network and one from a 192.168.2.0 Network. Where I get lost is what do I add to the VM when I create it. Would I be adding ONE PortGroup as an Adapter and that consists of both vmnics or would I b e adding TWO PortGroups, one going to their own vSwitch which goes to their own vmnic. Initially I thouhht you meant to create a (1) vSwitch and add 2 vmnics, each going to their own Physical NIC on the ESXi and then create a PortGroup that houses that vSwitch and then I add (1) Adapter to my VM... But I suppose that would translate to the VM as "one" NIC. So then I assume you now mean; create a vswitch and add a vmnic and then create a portgroup that houses that. then create a 2nd vswitch and add a vmnic and create a 2nd portgroup. Both vmnics associate to their physical esxi NIC's. When I create the VM I will add 2 (total) Adapter's which the VM will see as 2 NIC's? Or did I miss it again?

Alright aright, that is coming together.   Unless I misunderstand, could I do this. I would still need 2 PHYSICAL NIC's because of the 2 networks not connected.  I would create vmnic1 going to NIC 1 and vmnic2 going to NIC 2 I would create, let's say, virtual switch called SERVER and add both vmnic1 and vmnic2 (both going to 2 separate physical NIC's). I would create, again, Portgroup called SERVER and when I create the VM, I use that (SERVER[portgroup])  as the Network Adapter... When VM is installing and setting up, it will see TWO Network Cards (vmnic1 vmnic2) and then there I can assign the IP's, obviously according to their subnets?   Or did I miss the mark.