You don't need an IP address on a physical NIC for a VM to access it.
Remember, the Service Console is basicly a VM running on top of the VmKernel. ESX is not a linux product, it is a proprientry kernel. The Service Console sits on top of this. VM's do not run on the service console, they run on the VMKernel, the Service Console just has more hooks into the VMKernel. So if you configure a vSwitch with access to a NIC, the VMKernel will basically bridge the physical NIC to the virtual NIC.
So you setup NIC1 with your internal VM Network, and the Service Console on their own vSwitch.
Then setup NIC2 with just a VM Network attached to a vSwitch . Build you WAN VM here.
The two vSwitches will not route traffic between each other, so in essence, they are isolated (plenty of white papers on this prooving the security). So if you needed to route traffic between the two, you would need to either setup an external router to do so, or setup something in side ESX to do so.
If the WAN link is actually an Internet line, then there are security conserns you would need to follow, yet it is still do able. You can do some neat things putting a DMZ inside of an ESX server. Yes, some companies do choose to dedicate an ESX server to a DMZ, this is just a choice, not a required setup, nor even a best practice recomendation.
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Brent Schmidt SPOOOOON!!!!! ![[hippy] [hippy] [hippy]](/data/assets/smilies/hippy.gif)
Senior Network Engineer
Keep IT Simple