1 / 108

CIT 198 Week#8 Module 7 from the e-book. Manage Virtual Machines & vApps – Sybex Chapter#7

CIT 198 Week#8 Module 7 from the e-book. Manage Virtual Machines & vApps – Sybex Chapter#7. Instructor - Allan Ackerman VCA-DCV & VCP5-DCV. Click the graphic for assessment. This week our objectives will be. Complete labs 18, 19, 20 on the in-class virtual lab.

cato
Download Presentation

CIT 198 Week#8 Module 7 from the e-book. Manage Virtual Machines & vApps – Sybex Chapter#7

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CIT 198 Week#8Module 7 from the e-book.Manage Virtual Machines & vApps– Sybex Chapter#7 Instructor - Allan Ackerman VCA-DCV & VCP5-DCV Click the graphic for assessment

  2. This week our objectives will be • Complete labs 18, 19, 20 on the in-class virtual lab. • Complete labs 11-0, 11, 12 from the NDG/Cisco • Note 11-0 is a lab I wrote to update our licensing as it expires this week. It is an absolute must that 11-0 lab gets completed this week. • Both chapters are in sync this time • We will be covering creating virtual machines • We will be covering deploying virtual machines from templates and clones. • We will be covering managing and maintaining virtual machines. • We will be covering how to create an answer file. • We will be covering how to create and maintain vApps. Week#8 vSphere 5.1

  3. Important classroom info for the week of March 11 • Our quiz scores are better this week. This week’s average was 74 • We have our new product keys for vCenter and Enterprise Plus • VMware vCenter Server 5.x Standard for vSphere 5.x  - 2 sets - (1 Instance license key) - HJ2C4-NE28N-K874C-0K02M-2H4QM and MN62M-JE29N-68F43-0H90P-2XY7H • vSphere Storage Appliance Add-on for vCenter Server 5.x Standard - M50AD-N0J91-68A8C-00CRM-A66PU • VMware vSphere 5.x Enterprise Plus for 16 processors - 2 sets - PN2AP-V80DN-28241-00380-1W46H and P4234-Z804N-P8C40-0V2K2-88P4M Week#8 vSphere 5.1

  4. Overview of this week’s labsin-class lab#18 • We will setup a new LUN on our iSCSI SAN and do a physical RDM mapping to the new LUN on our e732c vm. • We will practice adding hard drive space to the C: drive on e732c VM. This will be a two step process and we can do a hot-add, that is to say, we can do this process with the machine powered on. • We will go over the procedure from changing a thin to a thick disk. • We will go over the procedure on how to do a hot-add of memory or a vCPU to a VM. Week#8 vSphere 5.1

  5. Our in-class lab#19 • We will learn where to store our sysprep files on a vCenter windows instance. This will be Windows OSs prior to 2007. • We will learn how to create an answer file. • We will learn how to create a template and deploy VMs from this template using an answer file. This will almost be a zero touch install. • We will learn how to update a template – by converting back to a VM, update, and then convert back to a template. • Remember a template can never be powered on. Week#8 vSphere 5.1

  6. Our in-class lab#20 • We will get sound to function in our XPpro VM by going to the host machine and using mstsc.exe to connect to the VM. The VM will then be able to use the audio from the host machine. • We will practice removing a VM from inventory, but not deleting the files from the SAN. • We will practice adding a machine back into inventory, an easy task as long as the .vmx file still lives on the SAN. • We will then practice two methods to get into the BIOS of a VM. Week#8 vSphere 5.1

  7. Our NDG lab#11-0 • This is a lab I wrote for our system down stairs. • Our keys for vCenter and our ESXi hosts expire this week so it is a must to get this lab done tonight. Here are the new keys. • VMware vCenter Server 5.x Standard for vSphere 5.x  - 2 sets - (1 Instance license key) - HJ2C4-NE28N-K874C-0K02M-2H4QM and MN62M-JE29N-68F43-0H90P-2XY7H • VMware vSphere 5.x Enterprise Plus for 16 processors - 2 sets - PN2AP-V80DN-28241-00380-1W46H and P4234-Z804N-P8C40-0V2K2-88P4M • When I did this lab – I had one shot to add the new keys – I did not do this lab very eloquently. I am sure you can do the last three steps in a single step. See if you can come up with a better procedure. Mine works, but I am sure I have a couple of extra steps. Week#8 vSphere 5.1

  8. Our NDG lab#11 • This lab that is not covered in the Gilmore book at all. It is a lab that requires the Enterprise plus version. (Host profiles need a Enterprise plus license.) • We will use host profiles and setup a profile (a.k.a. a template) of ESXi-1 and then apply that profile to ESXi-2 setting up the whole host with almost no effort at all. • We will add the LUN we used for the RDM last week to ESXi-2. Remember at the end of the lab last week you deleted the VM that was using the RDM. That iSCSI target should now be available to use. If it does not show up you forgot to do the last step of last week’s lab. • Note – when we add the storage to ESXi-2 it will automatically show on ESXi-1. Remember this is shared storage. Week#8 vSphere 5.1

  9. Our NDG lab#12 • We will get to see VMware do an amazing magic trick – take a running VM on ESXi-1 and move it over to ESXi-2 without losing a beat. • We will go over all the requirements to get this feat to happen and to verify your VM has this capability. Week#8 vSphere 5.1

  10. Virtual Machine Management Module 7 Week#8 vSphere 5.1

  11. You Are Here Week#8 vSphere 5.1

  12. Importance • You must perform many cumbersome tasks when using physical machines. For example, you must move server storage from one storage array to another, deploy servers with the same configuration, and dynamically add resources. • The ability to clone and deploy virtual machines from a template enables you to capture the state of a problematic virtual machine or deploy a virtual machine from a preconfigured standard. • VMware vSphere® enables you to migrate virtual machines and virtual machine disks from one VMware vSphere® ESXi™ host to another while the virtual machines are running. Week#8 vSphere 5.1

  13. Module Lessons • Lesson 1: Creating Templates and Clones • Lesson 2: Modifying Virtual Machines • Lesson 3: Migrating Virtual Machines • Lesson 4: Creating Virtual Machine Snapshots • Lesson 5: Creating a vApp and Removing a Virtual Machine Week#8 vSphere 5.1

  14. Lesson 1 Creating Templates and Clones Week#8 vSphere 5.1

  15. Learner Objectives • After this lesson, you should be able to do the following: • Create a template. • Deploy a virtual machine from a template. • Clone a virtual machine. • Enable guest operating system customization by VMware® vCenter Server™. Week#8 vSphere 5.1

  16. Using a Template A template is a master copy of a virtual machine. It is used to create and provision new virtual machines. The template is an image that typically includes a guest operating system, a set of applications, and a specific virtual machine configuration. Week#8 vSphere 5.1

  17. Creating a Template Clone the virtual machine to a template. • The virtual machine can be powered on or powered off. Convert the virtual machine to a template. • The virtual machine must be powered off. • Clone a template. • Select the template in inventory first. Week#8 vSphere 5.1

  18. Viewing Templates • Two ways to view templates: • Use the VMs and Templates inventory view. • Use the Virtual Machines tab in the Hosts and Clusters inventory view. Week#8 vSphere 5.1

  19. Deploying a Virtual Machine from Template • To deploy a virtual machine, you must provide such information as the virtual machine name, inventory location, host, datastore, and guest operating system customization data. Week#8 vSphere 5.1

  20. Updating a Template • To update a template: • Convert the template to a virtual machine. • Place the virtual machine on an isolated network to prevent user access. • Make appropriate changes to the virtual machine. • Convert the virtual machine to a template. Week#8 vSphere 5.1

  21. Cloning a Virtual Machine Cloning is an alternative to deploying a virtual machine. A clone is an exact copy of the virtual machine. The virtual machine being cloned can be powered on or powered off.

  22. Customizing the Guest Operating System • VMware® recommends customization of a clone’s guest operating system to prevent software and network conflicts. • During cloning or deploying from template, you can run the Guest Customization wizard. • You can create a specification that you can use to prepare the guest operating systems of virtual machines. • Specifications can be stored in the database. • You can edit specifications in the Customization Specifications Manager. Week#8 vSphere 5.1

  23. Deploying Virtual Machines Across Datacenters Virtual machine deployment is allowed across datacenters. • Clone a virtual machine from one datacenter to another. • Deploy from a template in one datacenter to a virtual machine in a different datacenter. Week#8 vSphere 5.1

  24. Lab 9 • In this lab, you will deploy a virtual machine from a template and clone a virtual machine. • Copy Sysprep files to the vCenter Server instance. • Create a template. • Create customization specifications. • Deploy a virtual machine from a template. • Clone a virtual machine that is powered on. Week#8 vSphere 5.1

  25. Review of Learner Objectives • You should be able to do the following: • Create a template. • Deploy a virtual machine from a template. • Clone a virtual machine. • Enable guest operating system customization by vCenter Server. Week#8 vSphere 5.1

  26. Lesson 2 Modifying Virtual Machines Week#8 vSphere 5.1

  27. Learner Objectives • After this lesson, you should be able to do the following: • Describe virtual machine settings and options. • Add a hot-pluggable device. • Dynamically increase the size of a virtual disk. • Add a raw device mapping (RDM) to a virtual machine. Week#8 vSphere 5.1

  28. Modifying Virtual Machine Settings • You can modify a virtual machine’s configuration in its Properties dialog box: • Add virtual hardware. Some hardware can be added while the virtual machine is powered on. • Remove virtual hardware. • Set virtual machine options. • Control a virtual machine’s CPU and memory resources. • Create an RDM. Week#8 vSphere 5.1

  29. Hot-Pluggable Devices Examples of hot-pluggable devices: USB controllers, Ethernet adapters, and hard disk devices. You can also add CPU and memory while the virtual machine is powered on. Week#8 vSphere 5.1

  30. Creating an RDM • To create an RDM: • Edit settings to modify the virtual machine configuration. • Click the Add button to add a device. • Click Hard Disk. • Select Raw Device Mappings and complete the Add Hardware wizard information by defining the following items: • Target LUN – LUN that the RDM will map to • Mapped datastore – Store the RDM file with the virtual machine or on a different datastore. • Compatibility mode • Virtual Device Node Week#8 vSphere 5.1

  31. Dynamically Increasing a Virtual Disk’s Size Increases the size of the existing virtual disk file Two settings to adjust Dynamically increase a virtual disk from, for example, 2GB to 20GB. Week#8 vSphere 5.1

  32. Inflating a Thin-Provisioned Disk If you create a virtual disk in thin format, you can later inflate it to its full size. To inflate a thin-provisioned disk: • Right-click the virtual machine’s .vmdkfile and select Inflate. Week#8 vSphere 5.1

  33. Virtual Machine Options VM display name VM Options .vmx file location VM directory guest operating system type Week#8 vSphere 5.1

  34. Options: VMware Tools Customize power button actions. VM tools options When to run VMware Tools scripts Update checks and time sync. Week#8 vSphere 5.1

  35. Advanced: Boot Options Advanced options rarely have to be set. Delay power on. Boot into BIOS. Retry after failed boot. Week#8 vSphere 5.1

  36. Lab 10 • In this lab, you will modify a virtual machine’s hardware and add a raw LUN to a virtual machine. • Increase the size of a VMDK file. • Adjust memory allocation on a virtual machine. • Rename a virtual machine in the vCenter Server inventory. • Add a raw LUN to a virtual machine and verify that the guest operating system can see it. • Expand a thin-provisioned virtual disk. Week#8 vSphere 5.1

  37. Review of Learner Objectives • You should be able to do the following: • Describe virtual machine settings and options. • Add a hot-pluggable device. • Dynamically increase the size of a virtual disk. • Add an RDM to a virtual machine. Week#8 vSphere 5.1

  38. Lesson 3 Migrating Virtual Machines Week#8 vSphere 5.1

  39. Learner Objectives • After this lesson, you should be able to do the following: • Describe the types of migration. • Explain the importance of VMware vSphere® vMotion®. • Identify vMotion requirements (virtual machine, host). • Verify vMotion requirements (CPU constraints and guidelines). • Perform a vMotion migration. • Perform a VMware vSphere® Storage vMotion® migration. • Perform an Enhanced vMotion migration. Week#8 vSphere 5.1

  40. Migrating Virtual Machines • Migration – Moving a virtual machine from one host or datastore to another. Types of migrations: • Cold – Migrate a virtual machine that is powered off. • Suspended – Migrate a virtual machine that is suspended. • vMotion – Migrate a virtual machine that is powered on. • Storage vMotion – Migrate a virtual machine’s files, while the virtual machine is powered on, to a different datastore. • Concurrent migrations are possible: • A maximum of eight simultaneous vMotion, cloning, deployment, or Storage vMotion accesses to a single VMware vSphere® VMFS-5 datastore is supported. Week#8 vSphere 5.1

  41. Comparison of Migration Types Great fodder for the exam Week#8 vSphere 5.1

  42. vMotion Migration A vMotion migration moves a powered-on virtual machine from one host to another. vMotion can be used to: • Improve overall hardware utilization • Enable continued virtual machine operation while accommodating scheduled hardware downtime • Enable vSphere Distributed Resource Scheduler (DRS) to balance virtual machines across hosts Week#8 vSphere 5.1

  43. How vMotion Migration Works VM A (network = Production) VM A (network = Production) How it works memory bitmap memory vMotion network Production network Week#8 vSphere 5.1

  44. Virtual Machine Requirements for vMotion Migration • A virtual machine must meet the following requirements: • A virtual machine must not have a connection to an internal standard virtual switch (vSwitch with zero uplink adapters). • A virtual machine must not have a connection to a virtual device (such as a CD-ROM or floppy drive) with a local image mounted. • A virtual machine must not have CPU affinity configured. • If the virtual machine’s swap file is not accessible to the destination host, vMotion must be able to create a swap file accessible to the destination host before migration can begin. • If a virtual machine uses an RDM, the RDM must be accessible by the destination host. Week#8 vSphere 5.1

  45. Host Requirements for vMotion Migration • Source and destination hosts must have: • Visibility to all storage (Fibre Channel, iSCSI, or NAS) used by the virtual machine: • 128 concurrent vMotion migrations per VMFS datastore • At least a Gigabit Ethernet (GigE) network: • Four concurrent vMotion migrations on a 1Gbps network • Eight concurrent vMotion migrations on a 10Gbps network • Identically named port groups connected to the same physical networks • Compatible CPUs: • CPU feature sets of both the source and destination host must be compatible. • Some features can be hidden by using Enhanced vMotion Compatibility (EVC) or compatibility masks. Week#8 vSphere 5.1

  46. CPU Constraints on vMotion Migration CPU constraints Week#8 vSphere 5.1

  47. Hiding or Exposing NX/XD NX – no execute (Intel) XD – execute disabled (AMD) For future CPU features, edit mask at the bit level. Choose between NX/XD security features or broadest vMotion compatibility. Week#8 vSphere 5.1

  48. Identifying CPU Characteristics VMware CPU identification utility https://my.vmware.com/web/vmware/details?productId=136&downloadGroup=CPU%20IDENTIFICATION%20UTILITY To identify CPU characteristics, use the server and CPU specifications, or use the VMware CPU identification utility. Week#8 vSphere 5.1

  49. Verifying vMotion Layout: Virtual Machine Map Maps Week#8 vSphere 5.1

  50. Checking vMotion Errors Make sure nothing is in the CD drive of the VM Week#8 vSphere 5.1

More Related