ESX purely for testing purposes 1

[Argetlam]

Hi,

Can anybody tell me how it is safe to set up ESX for testing only.
We have a ESX-server with only one NIC installed, on a seperate LAN.
We want to connect this ESX-server to our production-LAN, without having the risk of having VM's messing up our production environment.
This enabling us to connect to our ESX from our own workstations and being able to start, shutdown, suspend, configure and control VM's.

Kind regards,

Marcel Verdonk
The Netherlands

With kind regards,

Argetlam

SysAdmin

 

[comtec17]

Why not create a seperate VLAN?

 

[Chacalinc]

or even creating a VM with linux as a firewall... (iptables)

Chacal, Inc.

 

[tuliphead]

I am uncertain about what you mean with "messing up".
If you want your ESX-server on your production network, while still keeping your virtual machines unable to communicate with any other machines on your production network, just connect your VM´s to an internal switch (that is, a virtual switch that is not bound to your physical network interface card.

 

[Argetlam]

Thank you all for your answers, especially tuliphead!

What does this mean for the communication between a VM and the controlling workstation running VMware Console?
Is there any communication going in between, except from keyboard, video and mouse-info?

With kind regards,

Argetlam

SysAdmin