vmware vsphere 5

Upload: tarungupta0311

Post on 13-Apr-2018

259 views

Category:

Documents


0 download

TRANSCRIPT

  • 7/27/2019 VMware vSphere 5

    1/40

    VMware vSphere 5.1 lab on our laptops

    Lets say we want to learn a VMware vSphere products, such as ESXi server, vCenter server, HA,vMotion, FT. We could do that with two physical servers on which we would install ESXi hypervisor, butwe dont have servers to spare, we dont want extra heat generated and electricity consumed in ourdatacenter. Perhaps we want our test environment to travel with us. We can do this on our laptops!

    So, we will create the lab that is depicted in the following diagram:

    We have two ESXi hosts that are connected to various networks for various purposes: management,

    NFS, iSCSI, vMotion and FT. Although some of these features (perhaps all?) could use single adapter,this is not considered a best practice.

    The only physical thing in this lab is my laptop. Everything else is virtual! Im running this lab onWindows8 and VMware workstation 9.To create this lab, we will go through these steps: Installing and setting up VMware Workstation Installing the ESXi host as a virtual machine Installing a vSphere Client Installing a vCenter Server Configuring networking for NFS and vMotion Try this all out

    http://popravak.wordpress.com/2013/07/26/vmware-vsphere-5-1-lab-on-our-laptops/http://popravak.wordpress.com/2013/07/26/vmware-vsphere-5-1-lab-on-our-laptops/hr1http://popravak.wordpress.com/2013/07/26/vmware-vsphere-5-1-lab-on-our-laptops/hr1http://popravak.files.wordpress.com/2013/07/image49.pnghttp://popravak.wordpress.com/2013/07/26/vmware-vsphere-5-1-lab-on-our-laptops/hr1http://popravak.wordpress.com/2013/07/26/vmware-vsphere-5-1-lab-on-our-laptops/
  • 7/27/2019 VMware vSphere 5

    2/40

    Installing and setting up VMware WorkstationAfter downloading this product from VMwares site, we start the installation. This is an easy, severalsteps process. Lets begin

    After starting the installer we click Next.

    We will be OK with the Typical installation.

    Lets leave a default installation location and click Next.

    http://popravak.files.wordpress.com/2013/07/snaghtml9cedef5.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9cd8745.pnghttp://popravak.files.wordpress.com/2013/07/image9.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9cedef5.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9cd8745.pnghttp://popravak.files.wordpress.com/2013/07/image9.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9cedef5.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9cd8745.pnghttp://popravak.files.wordpress.com/2013/07/image9.png
  • 7/27/2019 VMware vSphere 5

    3/40

    We deselect Check for product updates on startup.

    Right now we dont want to participate inVMwares improvement program. So we deselect Helpimprove VMware Workstation and click Next.

    We want to create shortcuts.

    http://popravak.files.wordpress.com/2013/07/snaghtml9d35470.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9d276f1.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9d02d20.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9d35470.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9d276f1.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9d02d20.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9d35470.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9d276f1.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9d02d20.png
  • 7/27/2019 VMware vSphere 5

    4/40

    We click Continue.

    And the process is done.

    Now its time to start the Workstation and go to the Virtual Network Editor. We select Edit->VirtualNetwork Editor. The defaults should look like this:

    http://popravak.files.wordpress.com/2013/07/snaghtml9d76ff3.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9d5a1bb.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9d4b586.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9d76ff3.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9d5a1bb.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9d4b586.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9d76ff3.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9d5a1bb.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9d4b586.png
  • 7/27/2019 VMware vSphere 5

    5/40

    This is not what we want, so we will first delete all networks by selecting each of them and clicking

    Remove Network. Then we will add our networks to match our diagram. We click Add Network, and

    then select VMnet1 for our management network and click OK. Then we make sure that the Host-only (connect VMs internally in a private network) option is selected, the Use local DHCP service todistribute IP address to VMs deselected, the Subnet IP is 1.1.1.0 and the Subnet mask is255.255.255.0. When we click Apply our settings should look like this:

    We repeat the process for all other networks. When we are done, within network connections we shouldsee all our networks:

    http://popravak.files.wordpress.com/2013/07/snaghtml9e6c406.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9d945fb.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9e6c406.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9d945fb.png
  • 7/27/2019 VMware vSphere 5

    6/40

    We will rename all connections, so it is clearer to us which network is for which purpose. Right click anetwork, selecting Rename, repeated for each connection will eventually yield to this situation:

    Now we make sure that each connection has proper IP settings. For example the Management network:

    And the FT network:

    http://popravak.files.wordpress.com/2013/07/snaghtml9ed46f4.pnghttp://popravak.files.wordpress.com/2013/07/image10.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9e8eca3.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9ed46f4.pnghttp://popravak.files.wordpress.com/2013/07/image10.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9e8eca3.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9ed46f4.pnghttp://popravak.files.wordpress.com/2013/07/image10.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9e8eca3.png
  • 7/27/2019 VMware vSphere 5

    7/40

    We should have in mind that these settings will break communications to real IP addresses used here.For example we wont be able to reach anything that belongs to the 1.1.1.0/24 segment from ourlaptop. Perhaps we should use 192.168.0.0/24 or similar networks, but this will do for the lab.

    http://popravak.files.wordpress.com/2013/07/snaghtml9ee16a8.png
  • 7/27/2019 VMware vSphere 5

    8/40

    Installing the ESXi host as a virtual machineFrom the Workstation we select File->New Virtual Machine and start the wizard. We selectCustom(advanced):

    On the Choose the Virtual Machine Hardware Compatibility screen we click Next:

    Now we browse for an ESXi 5.1 ISO image and Workstation will detect what OS is in the ISO:

    http://popravak.files.wordpress.com/2013/07/snaghtml9f95ff0.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9f82713.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9f95ff0.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9f82713.png
  • 7/27/2019 VMware vSphere 5

    9/40

    Next we give a name and specify location for the VM:

    On the Processor Configuration screen, we select one for Number of processors and two forNumber of cores per processor. These are minimums for ESXi 5.1. We could go higher here,depending on our laptops hardware:

    For memory size, again the minimum is 2GB, but we could go above:

    http://popravak.files.wordpress.com/2013/07/snaghtmla04f13e.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla02b008.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla0103c0.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla04f13e.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla02b008.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla0103c0.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla04f13e.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla02b008.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla0103c0.png
  • 7/27/2019 VMware vSphere 5

    10/40

    On the Network Type we can select any option, because we will have to change it later, no matterwhat we select now:

    On the following several screens, we just accept defaults:

    http://popravak.files.wordpress.com/2013/07/snaghtmla082148.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla076cdd.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla063392.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla082148.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla076cdd.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla063392.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla082148.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla076cdd.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla063392.png
  • 7/27/2019 VMware vSphere 5

    11/40

    http://popravak.files.wordpress.com/2013/07/snaghtmla09565d.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla08bfca.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla08745a.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla09565d.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla08bfca.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla08745a.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla09565d.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla08bfca.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla08745a.png
  • 7/27/2019 VMware vSphere 5

    12/40

    Finally, on the Ready to Create Virtual Machine we deselect Power on this machine after creationand click Customize Hardware:

    In the Hardware dialog, we only need to change the network adapter to match our requirements. Forthe management network we will select VMnet1, forFT network VMnet5 and so on:

    Our summary portion of the Workstation windows should now look like this:

    http://popravak.files.wordpress.com/2013/07/image11.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla0af930.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla09a057.pnghttp://popravak.files.wordpress.com/2013/07/image11.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla0af930.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla09a057.pnghttp://popravak.files.wordpress.com/2013/07/image11.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla0af930.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla09a057.png
  • 7/27/2019 VMware vSphere 5

    13/40

    Now we are ready to power the machine on, and begin installation of the ESXi. This is illustrated in thefollowing pictures:

    http://popravak.files.wordpress.com/2013/07/image15.pnghttp://popravak.files.wordpress.com/2013/07/image14.pnghttp://popravak.files.wordpress.com/2013/07/image13.pnghttp://popravak.files.wordpress.com/2013/07/image12.pnghttp://popravak.files.wordpress.com/2013/07/image15.pnghttp://popravak.files.wordpress.com/2013/07/image14.pnghttp://popravak.files.wordpress.com/2013/07/image13.pnghttp://popravak.files.wordpress.com/2013/07/image12.pnghttp://popravak.files.wordpress.com/2013/07/image15.pnghttp://popravak.files.wordpress.com/2013/07/image14.pnghttp://popravak.files.wordpress.com/2013/07/image13.pnghttp://popravak.files.wordpress.com/2013/07/image12.pnghttp://popravak.files.wordpress.com/2013/07/image15.pnghttp://popravak.files.wordpress.com/2013/07/image14.pnghttp://popravak.files.wordpress.com/2013/07/image13.pnghttp://popravak.files.wordpress.com/2013/07/image12.png
  • 7/27/2019 VMware vSphere 5

    14/40

    Now we must specify and verify the root password and carry on:

    After the VM is rebooted, we are presented with the ESXi console screen:

    http://popravak.files.wordpress.com/2013/07/image20.pnghttp://popravak.files.wordpress.com/2013/07/image19.pnghttp://popravak.files.wordpress.com/2013/07/image18.pnghttp://popravak.files.wordpress.com/2013/07/image17.pnghttp://popravak.files.wordpress.com/2013/07/image16.pnghttp://popravak.files.wordpress.com/2013/07/image20.pnghttp://popravak.files.wordpress.com/2013/07/image19.pnghttp://popravak.files.wordpress.com/2013/07/image18.pnghttp://popravak.files.wordpress.com/2013/07/image17.pnghttp://popravak.files.wordpress.com/2013/07/image16.pnghttp://popravak.files.wordpress.com/2013/07/image20.pnghttp://popravak.files.wordpress.com/2013/07/image19.pnghttp://popravak.files.wordpress.com/2013/07/image18.pnghttp://popravak.files.wordpress.com/2013/07/image17.pnghttp://popravak.files.wordpress.com/2013/07/image16.pnghttp://popravak.files.wordpress.com/2013/07/image20.pnghttp://popravak.files.wordpress.com/2013/07/image19.pnghttp://popravak.files.wordpress.com/2013/07/image18.pnghttp://popravak.files.wordpress.com/2013/07/image17.pnghttp://popravak.files.wordpress.com/2013/07/image16.pnghttp://popravak.files.wordpress.com/2013/07/image20.pnghttp://popravak.files.wordpress.com/2013/07/image19.pnghttp://popravak.files.wordpress.com/2013/07/image18.pnghttp://popravak.files.wordpress.com/2013/07/image17.pnghttp://popravak.files.wordpress.com/2013/07/image16.png
  • 7/27/2019 VMware vSphere 5

    15/40

    There are several more steps that need to be completed. We start completing them by pressing the F2key. From the menu presented to us, we go under Configure Management Network. Under the IPConfiguration we specify the IP address of 1.1.1.2 and subnet mask of 255.255.255.0. Remember, thishas to be in the same segment as the IP address we specified under the VMnet1 adapters

    configuration. The default gateway has no meaning to us in our lab, but we must specify something, sowe pick 1.1.1.1:

    Under the DNS Configuration we need to specify a primary DNS server and a hostname. Here we canmake choices. If our laptop is running Windows7/8, we would need another VM inside Workstation toact as a DNS server, or we could install a VM inside the ESXi host that we installed inside theWorkstation. Funny, isnt it:) If our laptop is running Windows server OS or Linux, we could install a

    DNS directly in the OS that laptop is running. Im running Windows8, so for now I will choose 1.1.1.1for DNS server and change it later when we install a DNS server as one of available options:

    Finally, we press Escape and confirm our changes with Yes:

    http://popravak.files.wordpress.com/2013/07/image23.pnghttp://popravak.files.wordpress.com/2013/07/image22.pnghttp://popravak.files.wordpress.com/2013/07/image21.pnghttp://popravak.files.wordpress.com/2013/07/image23.pnghttp://popravak.files.wordpress.com/2013/07/image22.pnghttp://popravak.files.wordpress.com/2013/07/image21.pnghttp://popravak.files.wordpress.com/2013/07/image23.pnghttp://popravak.files.wordpress.com/2013/07/image22.pnghttp://popravak.files.wordpress.com/2013/07/image21.png
  • 7/27/2019 VMware vSphere 5

    16/40

    Now we have our first ESXi host installed and set up:

    We can now ping the 1.1.1.2 from our laptop:

    Installing a second ESXi host is almost identical. After we are done we have this screen:

    http://popravak.files.wordpress.com/2013/07/snaghtmla24ef10.pnghttp://popravak.files.wordpress.com/2013/07/image25.pnghttp://popravak.files.wordpress.com/2013/07/image24.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla24ef10.pnghttp://popravak.files.wordpress.com/2013/07/image25.pnghttp://popravak.files.wordpress.com/2013/07/image24.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla24ef10.pnghttp://popravak.files.wordpress.com/2013/07/image25.pnghttp://popravak.files.wordpress.com/2013/07/image24.png
  • 7/27/2019 VMware vSphere 5

    17/40

    http://popravak.files.wordpress.com/2013/07/image26.png
  • 7/27/2019 VMware vSphere 5

    18/40

    Installing a vSphere ClientNow when we have two virtual ESXi hosts, we need a tool to manage them. This tool is called vSphereClient. We can download this tool from VMware site. We have several choices here about where wewould install this client. Similar to a DNS server installation. We could run it from a host OS, which isWindows8 in our case, we can run it from a VM inside the VMware workstation, or we could run it froma VM installed within a ESXi host that is running as a VM inside the Workstation.

    Lets run it from a Windows8 host OSWe have a VMware vSphere ISO image downloaded and unpacked. Then we start the installation:

    http://popravak.files.wordpress.com/2013/07/snaghtml18630f44.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18626373.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml1861dccf.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18630f44.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18626373.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml1861dccf.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18630f44.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18626373.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml1861dccf.png
  • 7/27/2019 VMware vSphere 5

    19/40

    http://popravak.files.wordpress.com/2013/07/snaghtml186484cd.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml1863fd3e.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18637e3a.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml186484cd.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml1863fd3e.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18637e3a.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml186484cd.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml1863fd3e.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18637e3a.png
  • 7/27/2019 VMware vSphere 5

    20/40

    Now we start vSphere client, and connect to one of our ESXi hosts:

    First time we will be presented with this certificate warning, which we will acknowledge. We will also

    acknowledge the evaluation dialog box warning:

    http://popravak.files.wordpress.com/2013/07/snaghtml1865653a.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml186839f5.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml1865653a.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml1864ef6e.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml186839f5.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml1865653a.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml1864ef6e.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml186839f5.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml1865653a.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml1864ef6e.png
  • 7/27/2019 VMware vSphere 5

    21/40

    And now we have our ESXi hosts managed with vSphere client, and we are ready to install our firstvirtual machine, which will be a vCenter Server.

    http://popravak.files.wordpress.com/2013/07/image27.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml186a4805.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml1869c875.pnghttp://popravak.files.wordpress.com/2013/07/image27.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml186a4805.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml1869c875.pnghttp://popravak.files.wordpress.com/2013/07/image27.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml186a4805.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml1869c875.png
  • 7/27/2019 VMware vSphere 5

    22/40

    Installing a vCenter ServerFrom vSphere client, we select File->New->Virtual Machine, and complete a wizard. First we select

    Custom for virtual machine creation type:

    We give it a name:

    For now, we only have a local datastore. So we will create this VM on that store, and later we willmigrate it on the shared datastore:

    The hardware version should always be as higher as possible:

    http://popravak.files.wordpress.com/2013/07/snaghtml18d3f2ec.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18d27891.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18d178b5.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18d3f2ec.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18d27891.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18d178b5.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18d3f2ec.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18d27891.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18d178b5.png
  • 7/27/2019 VMware vSphere 5

    23/40

    For guest OS version we select Microsoft Windows Server 2008 R2 (64-bit). We could say here

    Microsoft Windows 2003 (64-bit) as well, but we have to have in mind that vCenter 5.1 can only beinstalled on 64-bit version of Windows:

    Depending on several choices, the amount of RAM required can vary. For lab environment I would

    suggest at least 2GB. More is better, but we are limited by the max amount of physical RAM on ourlaptop. For CPU, we can go with the defaults in our environment:

    http://popravak.files.wordpress.com/2013/07/snaghtml18de8cca.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18d61d7d.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18d4fdb5.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18de8cca.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18d61d7d.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18d4fdb5.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18de8cca.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18d61d7d.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18d4fdb5.png
  • 7/27/2019 VMware vSphere 5

    24/40

    Although we created several networks, only one, VMnet1 or Management network is available to us atthis moment. This is OK for now:

    Next several steps, we will go with the defaults, except for disk size. We cannot accept default of 40GB,because we created our ESXi host with 40GB, but ESXi itself took some space:

    http://popravak.files.wordpress.com/2013/07/snaghtml18e4d947.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18e3b6ef.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18e1a6cc.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18df571f.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18e4d947.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18e3b6ef.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18e1a6cc.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18df571f.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18e4d947.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18e3b6ef.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18e1a6cc.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18df571f.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18e4d947.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18e3b6ef.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18e1a6cc.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18df571f.png
  • 7/27/2019 VMware vSphere 5

    25/40

    After reviewing our settings, we need to mount an ISO image containing the installation of MicrosoftWindows Server 2008 R2 (64-bit):

    Before we power on the VM, we should edit settings, go under Options, Boot Options, and we selectForce BIOS Setup. This is to ensure that when we power on the VM for the first time, it will go in theBIOS, so we can say that we want it to boot from CD/DVD drive:

    http://popravak.files.wordpress.com/2013/07/image28.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18e64a3c.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18e59f56.pnghttp://popravak.files.wordpress.com/2013/07/image28.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18e64a3c.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18e59f56.pnghttp://popravak.files.wordpress.com/2013/07/image28.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18e64a3c.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18e59f56.png
  • 7/27/2019 VMware vSphere 5

    26/40

    Now we power on the VM and install Windows server. I guess we all know how to do that, so I will notshow these steps.

    Now from within the VM we mount an ISO image that contains a vSphere Server installation files, andrun the setup. Previously, we used the same installer to install the client and now we will use it to

    install the server. So we select VMware vCenter Simple Install. We could install all of componentsseparately, such as database, Single Sign On and so on, but for the sake of simplicity, we will use theoption of simple install. This option will install all needed components for us: the database, Single SignOn, Inventory Service and vSphere Server itself.

    After clicking Install, a simple wizard is run. First, the SSO install will begin. We can safely disregardthis warning:

    http://popravak.files.wordpress.com/2013/07/image29.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml4c7fec.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18eb1912.pnghttp://popravak.files.wordpress.com/2013/07/image29.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml4c7fec.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18eb1912.pnghttp://popravak.files.wordpress.com/2013/07/image29.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml4c7fec.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml18eb1912.png
  • 7/27/2019 VMware vSphere 5

    27/40

    After several next, we need to provide the administrators password for the SSO service. Any otherservice that needs to connect to SSO service will need this password:

    For the database, we will use the defaults, because this is a lab installation:

    Next, we can use the IP address or FQDN. It is recommended to use FQDNs, but we so far dont have a

    DNS and the IP address will do for the lab:

    http://popravak.files.wordpress.com/2013/07/image33.pnghttp://popravak.files.wordpress.com/2013/07/image32.pnghttp://popravak.files.wordpress.com/2013/07/image31.pnghttp://popravak.files.wordpress.com/2013/07/image30.pnghttp://popravak.files.wordpress.com/2013/07/image33.pnghttp://popravak.files.wordpress.com/2013/07/image32.pnghttp://popravak.files.wordpress.com/2013/07/image31.pnghttp://popravak.files.wordpress.com/2013/07/image30.pnghttp://popravak.files.wordpress.com/2013/07/image33.pnghttp://popravak.files.wordpress.com/2013/07/image32.pnghttp://popravak.files.wordpress.com/2013/07/image31.pnghttp://popravak.files.wordpress.com/2013/07/image30.pnghttp://popravak.files.wordpress.com/2013/07/image33.pnghttp://popravak.files.wordpress.com/2013/07/image32.pnghttp://popravak.files.wordpress.com/2013/07/image31.pnghttp://popravak.files.wordpress.com/2013/07/image30.png
  • 7/27/2019 VMware vSphere 5

    28/40

    We could change the port number, but for most installation, the default will do:

    Now we wait for the SSO installation to complete. Time for coffeeAfter the SSO and its database is installed, the wizard will install the database for the vCenter server:

    Same warning for IP/FQDN choice:

    http://popravak.files.wordpress.com/2013/07/image36.pnghttp://popravak.files.wordpress.com/2013/07/image35.pnghttp://popravak.files.wordpress.com/2013/07/image34.pnghttp://popravak.files.wordpress.com/2013/07/image36.pnghttp://popravak.files.wordpress.com/2013/07/image35.pnghttp://popravak.files.wordpress.com/2013/07/image34.pnghttp://popravak.files.wordpress.com/2013/07/image36.pnghttp://popravak.files.wordpress.com/2013/07/image35.pnghttp://popravak.files.wordpress.com/2013/07/image34.png
  • 7/27/2019 VMware vSphere 5

    29/40

    Its best to leave ports to defaults. Because we have small numbers of VMs, we dont need additionalrandom ports:

    Then again, the defaults:

    After another coffee, the vCenter database is installed, as well as the Inventory Service and the

    vCenter itself. This is what we want to see:

    Before we connect to vCenter server, one thing we should keep in mind: in the lab like this, starting ofvCenter server can take some time. So we need to be patient and wait for services to start:

    http://popravak.files.wordpress.com/2013/07/image40.pnghttp://popravak.files.wordpress.com/2013/07/image39.pnghttp://popravak.files.wordpress.com/2013/07/image38.pnghttp://popravak.files.wordpress.com/2013/07/image37.pnghttp://popravak.files.wordpress.com/2013/07/image40.pnghttp://popravak.files.wordpress.com/2013/07/image39.pnghttp://popravak.files.wordpress.com/2013/07/image38.pnghttp://popravak.files.wordpress.com/2013/07/image37.pnghttp://popravak.files.wordpress.com/2013/07/image40.pnghttp://popravak.files.wordpress.com/2013/07/image39.pnghttp://popravak.files.wordpress.com/2013/07/image38.pnghttp://popravak.files.wordpress.com/2013/07/image37.pnghttp://popravak.files.wordpress.com/2013/07/image40.pnghttp://popravak.files.wordpress.com/2013/07/image39.pnghttp://popravak.files.wordpress.com/2013/07/image38.pnghttp://popravak.files.wordpress.com/2013/07/image37.png
  • 7/27/2019 VMware vSphere 5

    30/40

    We connect to vCenter server using the same interface as before, but now we use the IP address ofWindows server and credentials of local administrator:

    Because now we dont talk to the ESXi server, but to the vCenter server, we again have the certificatewarning. We can safely ignore it.

    Now we create a virtual datacenter:

    And we add first ESXi host:

    http://popravak.files.wordpress.com/2013/07/image42.pnghttp://popravak.files.wordpress.com/2013/07/image41.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml8e2d08.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml93f4f4.pnghttp://popravak.files.wordpress.com/2013/07/image42.pnghttp://popravak.files.wordpress.com/2013/07/image41.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml8e2d08.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml93f4f4.pnghttp://popravak.files.wordpress.com/2013/07/image42.pnghttp://popravak.files.wordpress.com/2013/07/image41.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml8e2d08.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml93f4f4.pnghttp://popravak.files.wordpress.com/2013/07/image42.pnghttp://popravak.files.wordpress.com/2013/07/image41.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml8e2d08.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml93f4f4.png
  • 7/27/2019 VMware vSphere 5

    31/40

    The wizard is fairly simple:

    We accept the certificate:

    And use the evaluation license:

    For now, we will not engage the Lockdown Mode:

    http://popravak.files.wordpress.com/2013/07/snaghtmla1058e.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9ce2f6.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9c1c0c.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla1058e.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9ce2f6.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9c1c0c.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla1058e.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9ce2f6.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9c1c0c.png
  • 7/27/2019 VMware vSphere 5

    32/40

    Now we select the datacenter. We only have one. Finally, we review the summary and click Finish.The agent will be installed on ESXi host that will be used by the vCenter server to centrally manage this

    host:

    This process of adding the ESXi host should be repeated for the another ESXi host. Then we will havethis situation:

    We have now two ESXi hosts managed by a single virtual vCenter server running on one of ESXi hosts.

    Next thing is creating a shared storage and try one of advanced features, such as vMotion.

    http://popravak.files.wordpress.com/2013/07/image43.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla40050.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla1b026.pnghttp://popravak.files.wordpress.com/2013/07/image43.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla40050.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla1b026.pnghttp://popravak.files.wordpress.com/2013/07/image43.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla40050.pnghttp://popravak.files.wordpress.com/2013/07/snaghtmla1b026.png
  • 7/27/2019 VMware vSphere 5

    33/40

    Configuring networking for NFS and vMotionRemember our diagram and network settings in host OS? At this time we only have our managementnetwork set up:

    Now we should add two additional network adapters to our ESXi hosts. One will be VMnet2 and will beused for the NFS and one will be VMnet4 for VMotion. First we power off ESXi hosts and add twoadapters in each hosts. Within the Workstation, we select Edit virtual machine settings, then click

    Add, select Network Adapter and click Next:

    For the Network Adapter Type we select Custom and then VMnet2 for NFS and VMnet4 for vMotion:

    http://popravak.files.wordpress.com/2013/07/image44.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml4cb5b00.pnghttp://popravak.files.wordpress.com/2013/07/image44.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml4cb5b00.png
  • 7/27/2019 VMware vSphere 5

    34/40

    Now we power ESXi hosts back on and go under the network configuration. We should setup our newlyadded network adapters. First we add a NFS adapter. We click Add Networking, select VMkerneltype and click Next. We can see our two adapters with proper network addresses listed along eachadapter:

    We select vmnic1 and click Next. We give this network a name, check Use this port group formanagement traffic and click Next. The NFS communication is handled through the management

    enabled interface, and hence this option:

    http://popravak.files.wordpress.com/2013/07/snaghtml50de6f3.pnghttp://popravak.files.wordpress.com/2013/07/image45.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml50de6f3.pnghttp://popravak.files.wordpress.com/2013/07/image45.png
  • 7/27/2019 VMware vSphere 5

    35/40

    Next we specify the IP address settings:

    Then we repeat these steps for vMotion network. The differences are in IP settings and the option Use

    this port group for vMotion:

    http://popravak.files.wordpress.com/2013/07/snaghtml511d944.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml51100d6.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml511d944.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml51100d6.png
  • 7/27/2019 VMware vSphere 5

    36/40

    Now our network settings look like this:

    Behind the scenes I have installed another VM, a SLES Linux which will be used as a NFS shared

    storage. I wont be showing here how to install this Linux and set up a NFS share, but I will show howthe NFS setup screen should look like:

    http://popravak.files.wordpress.com/2013/07/snaghtml51564dc.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml5146500.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml51564dc.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml5146500.png
  • 7/27/2019 VMware vSphere 5

    37/40

    Here we can see that we publish the /NFS folder, which must be created on the file system. Also wecan see that the wildcard list is 2.2.2.*, which means that only hosts form only NFS network canactually access the NFS store. Finally, we set up rw and no_root_squash options.To use this NFS storage, under Configuration->Storage we click Add Storage. Then we select

    Network File System as a storage type and click Next:

    Now we give the IP address of our Linux NFS VM, folder that we share from that server and a datastorename:

    Please note that the NFS share should have these options enabled: rw, no_root_squash and appropriatehost access wildcard (in our case 2.2.2.*). If everything goes well, we should see our shared storage:

    http://popravak.files.wordpress.com/2013/07/snaghtml51970b0.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml5179420.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml94bf76c.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml51970b0.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml5179420.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml94bf76c.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml51970b0.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml5179420.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml94bf76c.png
  • 7/27/2019 VMware vSphere 5

    38/40

    http://popravak.files.wordpress.com/2013/07/snaghtml51de456.png
  • 7/27/2019 VMware vSphere 5

    39/40

    Try this all outAfter we set up the other ESXi host the same way, we can first migrate our vCenter Server to theshared storage and vMotion it from one host to another. First, lets move vCenter Server from ESXi-1 toESXi-2. We select Virtual Center VM, right click and click Migrate. Then we select Changedatastore and select NFS datastore. This could take a while, so its time for coffee.Ok, finally! Now we have our vCenter Server on the shared storage and is powered on on the host

    1.1.1.2:

    Lets now vMotion this VM to another host, without interrupting the service. Right click the VM, select

    Migrate, select Change host, select the 1.1.1.3 and complete the wizard. After a while we can seethat the VM is now running on another host and no service was interrupted:

    In a similar fashion we can play with a cluster and other features. One final thing I would like to pintout. I created this lab on a HP ProBook 4740s with 8GB of RAM and here is its health with only one

    VM powered on:

    http://popravak.files.wordpress.com/2013/07/image46.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9783bb2.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml952d859.pnghttp://popravak.files.wordpress.com/2013/07/image46.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9783bb2.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml952d859.pnghttp://popravak.files.wordpress.com/2013/07/image46.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml9783bb2.pnghttp://popravak.files.wordpress.com/2013/07/snaghtml952d859.png
  • 7/27/2019 VMware vSphere 5

    40/40

    Of course, powering a few more VMs wont affect the memory usage, because they will use the memoryalready consumed by ESXi hosts, but disk here is a big issue. So I would recommend a 16GB of RAM

    and SSD disk. This way we could try many vSphere 5.1 features.Thanks for reading!

    http://popravak.files.wordpress.com/2013/07/image47.png