Configuring Networking for Nested VM's in VMware Workstation
Transcript
hi this is Keith Townsen from the virtualized geek.com again with another video on virtualization in today's video we'll be doing nested networking VMware vpar environment within VMware Workstation including the networking required to run a nested VM the image that you have before you is the lab that we'll be creating we have an open Fowler server so server for store we have a Venter server to manage our vpar environment two esxi host a Windows XP host and we'll be going with VMware best practices for creating a
separate Network for our virtual machines a separate Network for vmotion a separate Network for management and a separate Network for storage so first we'll start out by reviewing the virtual machines that we've built so far we built our Venter server which is a Windows 2008 server and two esxi host we using vpar 5.0 and a open fer server currently all of these servers are on a single Network we'll walk through creating multiple Nicks and placing them on the correct Network we'll take a look at our
Windows machine first in our Windows machine we see that it's currently on on a 192.168.20.10 is the current IP address and that's on a nated interface within VMware Workstation currently going back to our Vis drawing we see that the Venter server needs to be on the management Network so we'll designate that 192 16824 Network as our management interface we'll go ahead and annotate that on our Vis drawing now so we've annotated that the Venter server is on the management Network which has a IP address of
1921 16824 which is a 24-bit subnet Max looking at our two esxi servers we see our esxi server currently the management interface is on that 24 Network for host 01 and host 02 is also on that 24 subnet take a look at our open fer server we take a look at our open fer server and we see our open fer server is on a 152 Network and we'll note that that Network actually doesn't currently exist in our VMware Workstation so we'll go ahead and create that
Network now in order to create create a network we're going to use the VMware Network editor So currently you'll notice that we have three networks two of which that we're currently using VM vmet zero which is our default Bridge Network so anytime you want to access a physical machine uh via one of your virtual machines you will put that on your vmet zero to give it a real IP address on your network and then you can choose to net an IP address which is currently what
we're currently using when we net a IP address those IPS will be hidden behind the built-in firewall and VMware Workstation so we want to add a network and we'll call this net nwork vmet 2 it will automatically assign the IP address to that network but we do want to change that IP address to match our Target storage Network which is 152 and we want to leave the subnet mask the same because it still is a 24-bit subnet mask going over a couple of the options on
the screen we can choose to set up a dccp service on this network by default which is how we're going to currently configure this adapter we'll leave those settings the same and we'll go ahead and apply those changes and now we need to go back to our open file server and move its network adapter from the default nated IP address to our custom Network we just created which is vmnet 2 so we've logged into Venter and we're taking a look at the first host the 192
24169 host which is our esxi host one and we'll take a look at the networking and as you can see we only have one Nick and currently both our virtual machine Network and management Network are connected to the default switch so let's take an opportunity again and take a look at our Vis drawing in our Vis drawing again we have our vcenter server on our management Network our esxi server on our management network uh along with the esxi servers being on the management Network a v
motion network uh our storage Network and of course a connection to the virtual machine Network so we need to create this picture within our V Center and we'll start doing that now the first Network we'll create in our V Center will be our storage Network in order to add our storage Network we first need to add a new Nick to each one of our hosts you'll go ahead and hot add a Nick and remember we already created vmnet 2 which is our storage Network and I
do suggest adding ncks one at a time to your esxi host to avoid the confusion of having to have to figure out which Nick is associated with what network so after adding the physical network adapters to our esxi Hol we'll go ahead and add that new V switch so we'll go into V Center and add a virtual switch we want to add a new virtual switch and of course this virtual switch is going to Via VM kernel we automatically select the Nick that we've added choose
defaults we'll have it obtain an IP address from the DHCP and as you see we now have a VM kernel port and V switch connected to our Nick that we just added we'll go ahead and repeat that process for our second host so we've created the storage Network for both exsi hostes and we'll create this we'll repeat this process to add the vo motion Network so let's spend a little bit of time talking about our virtual machine Network here we need to make a design decision
whether or not to have this network to be a network that's accessible outside of our bware host or if we want to have a larger lab and have that these host these virtual guests available outside of the VMware host if we want these networks to be available outside the VMware host we needed to have made our management Network a hoston network and chose to make our virtual machine Network a Ned Network because VMware Workstation limits us to a single Ned virtual Network so we again we'll
make this a host only Network once created we'll repeat that process again of adding those nit cards to our esxi server from vmw workstation and we'll have our networks completely configured so let's take a look at our final Network picture our St network is on the 1552 subnet our management network is on the24 netor n workor and in that's Ned our V Center server can get out to the internet and it can also get direct access to host that exist on our physical Network our esxi
servers are on the 138 Network and our virtual machine Network are on the 175 Network let's take a look at how this looks in V Center so in Venter our esxi post one we have our management interface on a24 network our storage on the 152 our v motion on the 138 and our V switch is on the 75 of course VM networks don't have IP addresses because they don't have C VM kernels assigned to them but we will see that when we publish a Windows XP
workstation to these machines so the first thing we want to do is add our ice scuzzy adapter because our open Fowler is running Ice gy so we'll add a ice gzy adapter to our esxi host in order to attach to the storage located on our open Fowler server well put in the IP address of our open fer server which is on a dedicated Network segment and then we'll scan for volumes and adapters data stores rather and as you can see there's two open fer Longs being
shared by our exsi host so we go to once again 69 we can see those storage volumes and we can see those storage volumes as well on the 171 machine take a look at our storage we can see that the two open fer data stores are listed there so we went ahead and published a Windows XP machine to our ESX I host and now we take a look at the settings we'll see that the network we're on that VM Network that we created for our virtual
machines we'll power up this virtual machine and see what happens so we've started our Windows XP host and if all goes well it should have a 175 IP address so it does 192 128 and if we do a IP config all we should see that the dccp server is 192 75254 which is the default IP address for the DHCP server of our VMware Workstation so we validated both the storage Network and the virtual machine networks work the next step is to validate that the v motion
network is working so we'll go ahead and try attempt to v motion our Windows XP machine from 169 to 171 we'll change the host to 171 leave it as a high priority and watch to see if it will transition to 171 now some of you may be wondering how much RAM or resources I have on my laptop this is a laptop that we're running this lab on I have a total of 16 gig of RAM on this laptop and as you can see I have uh
this lab is currently using 11.1 gig and processor is actually not very packed as at all the v motion has completed and as you can see we've now V motioned from 169 to 171 as the last test we'll go ahead and ping each one of the interfaces that we've created from my VMware Workstation so first we'll ping the VMware host themselves they are reachable now we'll ping our storage array and lastly we'll attempt to ping the V and Lesly will ping our XP workstation that's running
nested in our VM warehose and we can ping that IP as well so that concludes the lab thanks again for walking through another lab with virtualized geek.com you can again visit our blog where you'll find this lab and many others on VMware Zen desktop virtualization and it infrastructure in general thanks and have a great day
