NAT on vSwitches in ESX 3.5
5 pts.
0
Q:
NAT on vSwitches in ESX 3.5
Hi, I am in the process of setting up a separate windows domain in our ESX Environment but I will have to separate this windows domain from the already existing windows domain.
It is possible to set up ESX vSwitches in such a way that a completely separate network is created - no other traffic MUST leave the new network (domain) - and how is this achieved? Would I need to use some form of NAT anywhere?
Hope you can help, many thanks
ASKED: Oct 9 2008  1:14 PM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
0
30 pts.
0
A:
 RATE THIS ANSWER
+1
Click to Vote:
  •   1
  •  0
  • AddThis Social Bookmark Button
To setup a separate network, just change the subnet. If you are using 192.168.0.1/24 then you can use 192.168.1.1/24. This will effectively separate the networks. Network nodes are essentially connected by the network address and the broadcast address which are the first and last ip addresses of each subnet.

Additional Note: You could create the netwrok segment as mentioned above then use VLAN to isolate the network from your other domain. If you wish to not allow traffic to route to the virtual domain.

vmware communities will give you a step in the right direction.
Last Answered: Oct 10 2008  9:23 PM GMT by Ch40slinux   30 pts.
Latest Contributors: Mshen   23535 pts.
0
0
Discuss This Answer:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



0