Configuring Basic Networking (VMware Workstation vSphere Lab Cont'd)
Transcript
so welcome back to our series on installing a VMware vpar lab inside of VMware Workstation again credit to Jonathan freier over on vert expert.com for inspiring the series of posts this will deviate a little bit differently from Jonathan's series of posts we'll spend a little bit of time talking about network configuration earlier on in his in our series as opposed to his Series so let's overview our existing Network so far we've pretty much gone out of the box with most of our configuration with the VMware
and the domain controller on an nated IP address of 192 16812 and of course our VMware Workstation can see both the physical Network our 1921 161x Network as well as the virtual Network we're going to change this up a little bit we're going to put our virtual host the esxi host as well as the domain controller on the same network segment as our physical IP of our VMware host the next picture I hope to explain why we're making this change one of the limitations with working
with this configuration is even if you have a machine with 24 gig of RAM 32 gig of RAM you're going to run out of memory and you're going to run out of resources on this limited setup if we were working with a esxi cluster this wouldn't be a big deal but again we're working with limited resources so to make the most efficient use of our resources we're going to give ourselves the ability to add another physical VMware Workstation host so on the leftand side of the
screen we have our physical our existing configuration with the change of adding the host to the 192.168.1 network and on the right hand side we have a additional VMware Workstation Hol or this can be a VMware Fusion box with a virtual Network and that virtual network has a uh potentially our V Center so if we run out of resources when we start to do nested in our primary VMware Workstation hold we can move some of the management functionality over to a second host while we can't
do that necessarily with the esxi host simply we can do that with our management resources so our domain controller our DNS whatever secondary Windows servers we have we can have an environment dedicated to that host so we'll go ahead and uh show you how to do that this change is fairly simple we're going to go to our domain controller first make the change there go to settings find our network adapter currently you can see that the network adapter is using the natat network we're going to
just change that to the bridge connected physical Network now there are some considerations with this one we'll be putting this on our physical Network so if you're running a dacp server on your domain controller keep in mind some of the challenges you may run into you may want to disable that because then you'll be serving DCP addresses to physical machines that join your physical Network as well as uh if there's any destructive services that you might run on these machines we want to keep that in
mind as we make changes to our lab that's basically it in changing the networking we will go into deeper detail on changing networks for adding networks for hosted or nested VMS as well as some more complex things so when we want to do v motion and such We'll add some complexity with that and we'll show you how to use the network editor within VMware
