Hi,
I've a question. I attached the scenario with this post. To define it breiefly,
(1) I'm having an ESX Host with a Single Physical Network Adapter VMNIC0
(2) I've created 2 vSwitches with the default one. So totally 3 vSwitches there
(2.1) vSwitch0 -- Dedicated for Service Console and VMKernel and connected to VMNIC0 for the External N/W connectivity
(2.2) vSwitch1 -- Two VMs are connected to it
(2.3) vSwitch2 -- Two VMs are connected to it.
Please note that the 2 vSwitches (vSwitch1 & 2) are not connected with each other and also not connected with the Physical N/W adapters
(3) Both VMs in vSwitch1 can communicate with each other without any issues
(4) Both VMs in vSwitch2 can communicate with each other without any issues
My Question is;
How can I connect these 2 vSwitches (vSwitch1 & 2) with each other so that the VMs connected to both vSwitches can communicate with each other
This question may sound very simple for most of you....I understand....but I don't know how to do this. Thanks for any help/inputs in this...
Thank You.
vSwitches can't be connected together.
If these guests must communicate with each other they must be on one vSwitch. Traffic between two vSwitchws must cross the physical wire. So you need at least two NIC's to connect two vSwitches as a pNIC can only be connected to one vSwitch.
You can still separate the guests by using different port groups.
AWo
VCP 3 & 4
\[:o]===\[o:]
=Would you like to have this posting as a ringtone on your cell phone?=
=Send "Posting" to 911 for only $999999,99!=
vSwitches can't be connected together.
If these guests must communicate with each other they must be on one vSwitch. Traffic between two vSwitchws must cross the physical wire. So you need at least two NIC's to connect two vSwitches as a pNIC can only be connected to one vSwitch.
You can still separate the guests by using different port groups.
AWo
VCP 3 & 4
\[:o]===\[o:]
=Would you like to have this posting as a ringtone on your cell phone?=
=Send "Posting" to 911 for only $999999,99!=
Hi,
You cannot communicate two vSwitch each other if those don't have physical uplinks. Despite both vSwitch are in the same host, the traffic passes through the physical wire and the physical switch where the host is connected.
If you want to communicate all the VMs without physical NICs, you have to group all the VMs in the same vSwitch. As Awo says, you can separate the guests by using different port groups
Regards / Saludos
-
Patricio Cerda !http://www.images.wisestamp.com/linkedin.png!
VMware VCP-410
Join to Virtualizacion en Español group in Likedin
-
Si encuentras que esta o cualquier otra respuesta ha sido de utilidad, vótalas. Gracias.
If you find this or any other answer useful please consider awarding points by marking the answer helpful or correct. Thank you.
Hello,
Okay, I gotta say YOU CAN CONNECT 2 vSWITCHES TOGETHER without physical NIC capability.
To do this you need a VM that has 2 vNICs and acts as a bridge, router, firewall, gateway between the 2 vSwitches. 1 vNIC on one portgroup of vSwitch A and 1 vNIC on another portgroup on vSwitch B.
So yes it is possible, but you need A VM to act as a bridge, router, firewall, gateway device.....
Best regards,
Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009, 2010
Now Available: 'VMware vSphere(TM) and Virtual Infrastructure Security'[/url]
Also available 'VMWare ESX Server in the Enterprise'[/url]
Blogging: The Virtualization Practice[/url]|Blue Gears[/url]|TechTarget[/url]|Network World[/url]
Podcast: Virtualization Security Round Table Podcast[/url]|Twitter: Texiwll[/url]
Why do you always suggest so easy solution?
AWo
VCP 3 & 4
\[:o]===\[o:]
=Would you like to have this posting as a ringtone on your cell phone?=
=Send "Posting" to 911 for only $999999,99!=
Hello,
AWo, I just think differently than most people?
Best regards,
Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009, 2010
Now Available: 'VMware vSphere(TM) and Virtual Infrastructure Security'[/url]
Also available 'VMWare ESX Server in the Enterprise'[/url]
Blogging: The Virtualization Practice[/url]|Blue Gears[/url]|TechTarget[/url]|Network World[/url]
Podcast: Virtualization Security Round Table Podcast[/url]|Twitter: Texiwll[/url]
A little tricky the solution, but i think it can be very useful in some situations.
Thanks!!!
Regards / Saludos
-
Patricio Cerda !http://www.images.wisestamp.com/linkedin.png!
VMware VCP-410
Join to Virtualizacion en Español group in Likedin
-
Si encuentras que esta o cualquier otra respuesta ha sido de utilidad, vótalas. Gracias.
If you find this or any other answer useful please consider awarding points by marking the answer helpful or correct. Thank you.
Hi All,
Thank You Very Much for all your help in this.....Now I got a clear idea of this task.
@Sometimes the easy sollutions will help in a very critical situations....
I'm marking this question as Answered....
Thanks Again..
If you setup a VM with two vNICs and acting as a bridge, that is a layer 2 connector, be very careful to never link the other vSwitch to a VMNIC, as that will create a layer 2 loop and bring down the network.
If the VM with two vNICs is a layer 3 routing then there is no big risk.
Used this today, thank you for the suggestion!