I'm trying to understand:
1. Host with 2 vswitch (standard)
2. vSwitch 1 has 1 vmkPort and a port-group1 (for VM) with no vlan
3.vSwitch 2 has 1 vmkPort and a port-group2 (for VM) with no vlan
4 VM has 2 vnic: vnic1 connected to port-group1 and vnic2 connected to pg2
If the scenario is correct I need some extra infos:
1. physical net (physical switch) (problem seems to be here)
2. vlan's and ip's
3. network screenshots
4. test screenshot
your summary is correct. there are no vlan's at the moment. i am siply tryin to leverage my existing hardware by virtualizing the gateway/router vm. i am using a cisco catalyst 2950 as my physical switch on the internal network. the external network has a ubiquiti wireless modem which i don't control. there is no issues with that part of the network. the ip's i'm using are as follows:
- vswitch 2 (192.168.2.206/24) which is connected to the external physical adapter (i.e this cable runs directly to the ubiquiti device). on this vswitch the one vnic of the gateway has ip 192.168.2.205/24.
- vswitch 1 (192.168.0.2/26) is my management vswitch and connects to a second physical adapter which is plugged into the cisco catalyst. i have not changed its management ip yet, since i did not think it was required at this stage. the other vnic is connected here with ip 192.168.0.1/26.
when i give my desktop machine an ip 192.168.0.10/26 (gateway set to internal vnic of gateway vm) i cant ping the "internal" vnic (0.1) and from the linux gateway vm i can't ping anything other than its own interfaces. what should my gateways be?
First, be sure to take into account the vSwitch has no IP - the VMkernel Virtual NIC and the Ubuntu VM are the only entities attached to each vSwitch that actually can have an IP assigned.
Second, what version of Ubuntu? You may need to remove the persistent net rules (bindings) (/etc/udev/rules.d/70-persistent-net.rules) to get the Ubuntu OS to acknowledge the NIC. In the old days, back when I walked to school in the snow uphill both ways, most Linux OS didn't take kindly to adapter changes, and you had to either delete or edit the persistent-net-rules files to make the OS acknowledge the adapter(s)