*****UPDATE*****
Ok, so I think i got this working the way i wanted.
I have been able to add the second NIC to the VM, using the second bridge of the server. You can see in the attachment, that after it was added, there is one NIC using vmbr0 and another NIC using vmbr1.
IMPORTANT: Please note, in the Node itself, a static route must be added, so PRIVATE traffic goes OUT via the eth1 NIC. Since by default ONLY 1 Default GW can be configured, it is necessary to create a route-file named route-eth1 inside the /etc/sysconfig/network-scripts/ directory.
nano /etc/sysconfig/network-scripts/route-eth1
This file must contain the following information:
++++++++++++++++++++++++++++
ADDRESS0=10.0.0.0
NETMASK0=255.0.0.0
GATEWAY0=10.100.100.1
++++++++++++++++++++++++++++
This configuration assumes you want to access all the 10.0.0.0/8 network via eth1.
Now to the Guest.
The guest was rebooted and showed NO change whatsoever as far as NICs go. SO, this is what I did.
1. Issue the following command: dmesg | grep eth1 | more
This showed me there was INDEED another NIC, besides eth0 on this VM. See attachment.
2. I then did this:
2.1 cd /etc/sysconfig/network-scripts/
2.2 cp ifcfg-eth0 ifcfg-eth1
2.3 nano ifcgfg-eth1. This was done in order to change the name of the NIC as well as the MAC address. From eth0 to eth1, as well as the MAC, to the new MAC.
The MAC adress i used was the one i got from running the dmesg command mentioned above.
I then added the network configuration to the NIC, and ran the ifup eth1 command and YES, the NIC came UP!
Now, this is a Centos VM, so again, static routes needs to be added to the VM itself, so it delivers the private traffic OUT via eth1.
We proceed to do the same thing we did for the node by creating the route-eth1 file, with the appropriate values.
We then restart the network service and YES, IT WORKS.
This is what we get: check final results screenshot.
As you can see, the routing table shows the GW/NIC being used for public and private traffic.
Best Regards,
Foster Banks