Thin Client and Virtual Machines Thread, ESXi v5 & multi-netowrk setup questions in Technical; Currently :
I have a current server running an odd configuration. The box is running SQL 2008 w/ 2 small ...
-
13th October 2011, 04:40 PM #1
- Rep Power
- 0
ESXi v5 & multi-netowrk setup questions
Currently:
I have a current server running an odd configuration. The box is running SQL 2008 w/ 2 small databases. On top of this it is also running VMware Server2 w/ 2 VMs running.
This setup came about because 3 physical machines were needed. These machines use MicroSoft Message Queuing to send data to each other.
The host machine has 2 physical NICs connected to 2 different networks.
1 of these Server2008 virtual machines has 2 physical NICs. One NIC connects to the hospital network 10.*.*.* & the other NIC connects to an autonomous network of spme special gear. All this gear is on the 192.168.*.* network. So this machine talks via the 192.168.*.* network back to the SQL server(host).
The second of these VMs is bridged to the hospital network..
New solution ESXi 5:
This is my first ESX install & i am a little confused how to get both sets of traffic out 1 NIC or... 2 physical NICs.
Currently i have my 3 VMs talking via DHCP.. but when i try to set a VM w/ the second subnet 192.168.*.* i can ping nothing.
*Should i be building a second vSwitch1 and connecting this to a physical NIC? If so i do not see how to set the IP of the physical NICs.. only teaming and vLAN settings for the current NIC getting DHCP.
*Or should i be sending all the traffic for these 3 virtual machines & 2 networks out the 1 physical NIC... and have the hospital setup routing to take care of the 192.168.* traffic?
+Let me know if any of this is to vague
-
-
IDG Tech News
-
20th October 2011, 10:30 AM #2 I guess you've probably figured this out by now but just in case, you will need to set up a new virtual machine vswitch for the 2nd physical nic. When you are configuring ESXi dont think of physical nics in the traditional sense think of them as Uplinks. For virtual machine traffic you do not set an IP address on the physical nic, just configure the vm's with the correct physical route to the network they need to access i.e. vnic connected to vswitch one for 10.x.x.x traffic and or vswitch two for 192.x.x.x traffic and configure the vm's networking as you would normally within the guest OS (be it a windows vm or a *nix vm).
-
SHARE:
Similar Threads
-
By SebastianP in forum Windows Server 2008
Replies: 1
Last Post: 29th November 2010, 09:43 PM
-
By Stuart_C in forum MIS Systems
Replies: 7
Last Post: 7th September 2010, 05:05 PM
-
By fox1977 in forum Thin Client and Virtual Machines
Replies: 2
Last Post: 29th January 2009, 12:34 PM
-
Replies: 5
Last Post: 15th December 2008, 10:42 AM
-
By Zoom7000 in forum How do you do....it?
Replies: 3
Last Post: 22nd July 2008, 10:23 AM
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules