Virtualization on ML350 G5
I'm planning to buy HP server ML350G5 (QC X2.0/6GB RAM, 4x146GB HDD, DVDRW). It will be used as test lab for virtual Windows Server 2003/2008 installations.
What I didn't decide yet is if to use ESX, ESXi or XenServer. Are there any known issue with above hardware? What is in general better virtualization server to use? I have basic knowledge about ESX, but I'm open to learn new stuff.
What I didn't decide yet is if to use ESX, ESXi or XenServer. Are there any known issue with above hardware? What is in general better virtualization server to use? I have basic knowledge about ESX, but I'm open to learn new stuff.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for comments.
One thing I forgot to mention earlier. What I need for vSwitch functionality?
One thing I forgot to mention earlier. What I need for vSwitch functionality?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I will think about it, although it is only test server. My mine concern is if I can create some basic virtual topology. Two virtual switches would be perfect for me.
If you want it for testing, you can absolutely add two vSwitches to it with just the one NIC.
Matt
Matt
You can do two things, create a second vSwitch (in VI client, log into ESX server > Configuration tab > Networking > Add Networking... > Virtual Machine connection type > Create a virtual switch > name the Network Label and assign a VLAN ID if necessary > Finish) or create a port group on the same switch (Under Networking, click Properties... for vSwitch0 > click Add > Virtual Machine connection type > name the Network Label and assign VLAN ID if necessary > Finish).
Both provide a logical segmentation of devices. Since you have one NIC, your second vSwitch acts as a host only network - no connection to the outside world unless you build a router appliance to route traffic from vSwitch1 to vSwitch0 or create an Internet connection sharing on the VM on vSwitch0.
What type of scenario are you trying to do?
Both provide a logical segmentation of devices. Since you have one NIC, your second vSwitch acts as a host only network - no connection to the outside world unless you build a router appliance to route traffic from vSwitch1 to vSwitch0 or create an Internet connection sharing on the VM on vSwitch0.
What type of scenario are you trying to do?
I've attached an example of how your VMs would interact with 2 vSwitches.
haldoxp2.png
haldoxp2.png
ASKER
Great. So after I install ESX or ESXi with VI client I should be able to create vSwitch.
After I saw last picture I realized that after I will install ISA2006 I will need 2nd NIC to be able to connect from network to test infrastructure without opening ISA.
After I saw last picture I realized that after I will install ISA2006 I will need 2nd NIC to be able to connect from network to test infrastructure without opening ISA.
You are correct. Create a new Virtual Machine switch (vSwitch1). By default you'll have vSwitch0.
ISA will definitely help you route traffic (NATting) from your internal (VMs on vSwitch1) network to your IP network.
ISA will definitely help you route traffic (NATting) from your internal (VMs on vSwitch1) network to your IP network.
ASKER
What I have in plan is to have ISA server connected via 1 NIC directly to Internet. Behind it two servers in DMZ (I need to test OMA, OWA, VPN access) and rest in "normal" (virtual) network (AD, Exchange, what will be needed for testing). So I will use 2nd NIC to connect to the "normal" (virtual) network. Hopefully this can be done.
ASKER
Thanks for all the info, hopefully the server will come soon :).
http://www.vmware.com/pdf/vi35_systems_guide.pdf
If you already know ESX and don't want to use HA or DRS features on this test box, you should probably go with ESXi, since the hypervisor is the same and it's free.
http://www.vmware.com/products/esxi/
Cheers.