1 / 93

Instructor - Allan Ackerman VCA-DCV & VCP5-DCV

CIT 198 Week#3 Virtual Lab Construction (continued & hopefully finished) & Module 2 from the e-book. Instructor - Allan Ackerman VCA-DCV & VCP5-DCV. Click the graphic for assessment. You should have done the following so far -. Digested all the detail of Chapter 2 in the Sybex book.

beck
Télécharger la présentation

Instructor - Allan Ackerman VCA-DCV & VCP5-DCV

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#3Virtual Lab Construction (continued & hopefully finished) & Module 2 from the e-book. Instructor - Allan Ackerman VCA-DCV & VCP5-DCV Click the graphic for assessment

  2. You should have done the following so far - • Digested all the detail of Chapter 2 in the Sybex book. • Completed labs 1 -5 and have them signed off by your instructor. • Make sure the two vSphere Configuration Maximums downloads, 5.1 & 5.5, are available on your computer so you can easily look things up. We will always have a few questions on our weekly exams. As stated last week – learn a few each day and this task will be easy. • You should have read the introduction to the e-book Week#3 vSphere 5.1

  3. This week our objectives will be • Complete labs 6, 7, 8, & 9 • Lab 6 is setting up our iSCSI SAN on vc.vita.local. There is a FreeStarwind folder inside of the _Spring2014 folder. (It is also on the FTP site.) This is a cut down version of the StarWind iSCSI software. It can do a virtual SAN on a Windows Server product. The real product can turn a Windows Server into a true iSCSI SAN. Inside the FreeStarwind folder there is a StarWind_getting_started.pdf. This is a short 10 minute read – try to look this over before the Tuesday night class this week – Feb 4. • Since we have a multi-homed vc.vita.local machine – replace the 127.0.0.1 IP address with the correct NIC address, 192.168.3.20. Week#3 vSphere 5.1

  4. Replace the localhost address By default StarWind sets your iSCSI host to be 127.0.0.1, remove and add a new host using the correct IP – 192.168.3.20. After you do this task add your two iSCSI targets - the two extra drives we added in lab#4.) Week#3 vSphere 5.1

  5. StarWind Setup • When adding your new targets - label your two new drives as S: & T: with a label of iScsi1 & iScsi2 in Disk Management. • When creating your virtual disk for the SAN use the naming convention below: • Make sure you allow for concurrent connections. Week#3 vSphere 5.1

  6. vCenter configuration Part 1 • We will add the datacenter, Training, to our vCenter. • Next we will add the two ESXi hosts to the datacenter. • We will double check our SHA1 thumbprint making sure we are not spoofed. • We will enter the null key (i.e. no key) for our license in ESXi1.vita.local and ESXi2.vita.local giving us 60 days of free use. Week#3 vSphere 5.1

  7. Troubleshooting vCenter • Make sure you have a services shortcut on your desktop. If vCenter does not start – restart the following service, VmwareVirtualCenter Server. • Trouble with authentication – restart the service VMwareVCMDS. Week#3 vSphere 5.1

  8. Troubleshooting vCenter • If your esxi host becomes disconnected just right click and select connect. • If your datastores are inaccessible - right click the datacenter and click on rescan for all datastores. • You can no longer manage your esxi host from vCenter. Go to the DCUI, login, and select Restart Management Network. Week#3 vSphere 5.1

  9. vCenter configuration Part 1 (continued) • ESXi can be a NTP client. We will allow UDP port 123 via the firewall and link our hosts to use the time server, pool.ntp.org. • We will also see that we can setup DNS servers, host name, and default gateway in the vCenter GUI as well as the DCUI. Week#3 vSphere 5.1

  10. vCenter configuration Part 2 • In lab 8 we will learn how to configure our vCenter virtual standard switches. You will see them referenced with the acronym, vSS. • vSwitch0 - will handle our management and our virtual machine network. It will have two NICs for redundancy. This network is on the IP subnet 192.168.246.x/24 • vSwitch1 – will handle vMotion traffic. This network is on the IP subnet 192.168.1.x/24 and will have a single NIC. Week#3 vSphere 5.1

  11. vCenter configuration Part 2 (continued) • vSwitch2 - will handle our fault tolerance logging. This network is on the IP subnet 192.168.2.x/24 • vSwitch3 – will handle iSCSI and NAS traffic. This network is on the IP subnet 192.168.3.x/24 and will have a two NICs. When we setup our iSCSI SAN we will use round robin to multipath between the two NICs. Week#3 vSphere 5.1

  12. vCenter configuration Part 3 • In lab 9 we will learn how to setup a 1-1 mapping between to vmkNics and the two vmnics. • We will setup 2 paths from each of the 2 ESXi hosts for a total of 4 different paths to our two LUNs. • We will learn how to setup a NFS file store in Windows 2008R2 and be able to create a NFS shared datastore inside of vCenter. • Our goal tonight is to get labs 1-9 complete and our basic virtual lab setup is now complete. Week#3 vSphere 5.1

  13. e-Book Module 2 The next few slides are from VMware. They cover the basics from module 2, Introduction to Virtualization. Week#3 vSphere 5.1

  14. You are Here • Module 2 Week#3 vSphere 5.1

  15. Importance • VMware vSphere® software suite is based on many components with which a vSphere administrator should be familiar. • This module describes the basic concept of virtualization and introduces VMware vSphere® ESXi™ and the virtual machine. • This module discusses the fundamental vSphere components and how vSphere can be used in your datacenter. Week#3 vSphere 5.1

  16. Module Lessons • Lesson 1: Introduction to Virtualization • Lesson 2: vSphere User Interfaces • Lesson 3: Overview of ESXi Week#3 vSphere 5.1

  17. Lesson 1: Introduction to Virtualization Week#3 vSphere 5.1

  18. Learner Objectives • After this lesson, you should be able to do the following: • Compare and contrast physical and virtual architectures. • Define a virtual machine. • Describe the benefits of using virtual machines. • Describe how the vSphere interacts with CPUs, memory, networks, and disks. • Describe ESXi architecture. • Describe how vSphere fits into the cloud. Week#3 vSphere 5.1

  19. Different vSphere Editions * Includes previous tier features Week#3 vSphere 5.1

  20. FibreChannel Ethernet Physical Infrastructure applicationsoperating system physical host The Physical Side t Fibre Channelstorage iSCSIstorage NFSstorage Network Week#3 vSphere 5.1

  21. FibreChannel Ethernet VMware vSphere VMware vSphere VMware vSphere VMware vSphere Virtual Infrastructure virtual machines The virtual side hypervisor ESXi host network iSCSIstorage NFSstorage Fibre Channelstorage Week#3 vSphere 5.1

  22. physical architecture virtual architecture application operating system vSphere x86 architecture x86 architecture Physical and Virtual Architecture Both views Week#3 vSphere 5.1

  23. vSphere and the Software Defined Datacenter The software defined datacenter Week#3 vSphere 5.1

  24. Easy to relocate: Encapsulated into files Independent of physical hardware Easy to manage: Isolated from other virtual machines Insulated from hardware changes Provides the ability to support legacy applications Allows servers to be consolidated Why Use Virtual Machines? Virtual machine Physical machine Difficult to relocate: • Moves require downtime • Specific to physical Hardware Difficult to manage: • Requires physical maintenance • Hardware failures cause downtime Hardware has limitations: • Hardware changes limit application support • Servers are physically individual Week#3 vSphere 5.1

  25. Resource Sharing Sharing resources vSphere x86 architecture Week#3 vSphere 5.1

  26. CPU Virtualization Virtual architecture Week#3 vSphere 5.1

  27. Physical and Virtualized Host Memory Usage Virtual Memory Usage Week#3 vSphere 5.1

  28. Physical and Virtual Networking Virtual Networking Week#3 vSphere 5.1

  29. application operating system vSphere vSphere x86 architecture x86 architecture x86 architecture Physical File Systems and VMware vSphere VMFS physical architecture virtual architecture VMFS NTFS,ext3, UFS VMFS Week#3 vSphere 5.1

  30. Encapsulation 1000s of files encapsulate to just a few Week#3 vSphere 5.1

  31. volumes vmfs / opt etc / usr VM 3 VM 4 VM 1 VM 2 File-System Layouts VMFS Windows We will be using VMFS or NFS C: D: E: Linux/UNIX SAN Local Week#3 vSphere 5.1

  32. private cloud public cloud How vSphere Fits into Cloud Computing hybrid cloud • Installing vSphere 5 creates a virtual infrastructure. • Your virtual machines run in this virtual infrastructure. • VMware vCloud Director™ enables you to create a cloud. • Third-party providers can host public or private clouds. • VMware® clouds empower you to run your virtual machines in a private, public, or hybrid cloud to fit your business needs. VMware vSphere

  33. What Is a Private Cloud? • Individual departments or internal corporate organizations (divisions) are able to deploy and manage IT infrastructure through virtual systems as needed. • IT capabilities are provided as a service, over an intranet, within the enterprise, and behind the firewall. Advantages Internet • Self-service provisioning • Elasticity of resources • Rapid and simplified provisioning • Secured multitenancy • Improved use of IT resources • Better control of IT budgets enterprise private cloud Widget division Gizmo division Human Resources Sales

  34. What Is a Public Cloud? • A cloud service provider hosts general IT operations for multiple businesses. • IT resources are provided as a service over the Internet. • A public cloud is similar to a utility or an Internet service provider. Advantages cloud service provider • Public clouds have all of the advantages of a private cloud: • Customer management of IT • Rapid and flexible deployments • Efficient and cost-effective deployments • Secure IT assets • Customer companies no longer have IT as an ongoing overhead expense. company A company B company C

  35. What Is a Hybrid Cloud? • Some cloud-based assets are accessible internally over an intranet. • Some cloud-based assets are accessible externally over the Internet. • Companies first move applications and data to their private cloud. • Companies can reap additional cost savings by moving to an externally accessible cloud. • Applications are transitioned by using software that meets open standards.

  36. Review of Learner Objectives You should be able to do the following: • Compare and contrast physical and virtual architectures. • Define a virtual machine. • Describe the benefits of using virtual machines. • Describe how the vSphere interacts with CPUs, memory, networks, and disks. • Describe ESXi architecture. • Describe how vSphere fits into the cloud.

  37. Lesson 2: vSphere User Interfaces Week#3 vSphere 5.1

  38. Learner Objectives After this lesson, you should be able to do the following: • Download and install the VMware vSphere® Client™. • Use the vSphere Client remotely connect to an ESXi host. • View or configure ESXi settings: • Processor and memory configuration • ESXi system logs • Licensed features • Use the VMware vSphere® Web Client. • Manage ESXi from the command prompt.

  39. User Interfaces Note the C# client can attach to both vCenter and ESXi Week#3 vSphere 5.1

  40. Downloading vSphere Client Point to the vCenter Server or ESXi host. vSphere Client is an interface used to connect remotely to VMware® vCenter Server™ or an ESXi host from a Windows system. To download the vSphere Client: • Use the VMware Infrastructure™ Management Installer. • Download the client from the vCenter Server system or an ESXi host. • Internet access is required. Download the vSphere Client to a supported Windows system.

  41. Using the vSphere Client On the vSphere Client login screen, enter the following: Host name or IP address of ESXi host or vCenter Server User name Password for that user (Optional) Use your Windows session credentials.

  42. vSphere Client: Configuration Tab In ESXi, the configuration tab, is the place to check your hardware status. Week#3 vSphere 5.1

  43. Viewing Processor and Memory Configuration Memory & Processors Week#3 vSphere 5.1

  44. Viewing ESXi System Logs Use vSphere Client to view logs. Export system logs to an archive file: • Send to VMware Support.

  45. Viewing Licensed Features Licensing Week#3 vSphere 5.1

  46. vSphere Web Client • Installer located on ISO image • Install locally to vCenter Server or to remote systems • Remote installations are recommended when possible vSphere Web Client is included with vCenter Server Appliance Week#3 vSphere 5.1

  47. vSphere Web Client Architecture Remember in vCenter the Web Client is a server app Week#3 vSphere 5.1

  48. vSphere Web Client Plug-in Packages Plug-ins Week#3 vSphere 5.1

  49. Breaks the traditional hierarchy view of an object: Objects linked and displayed by relationships The Home screen retains its original appearance Allows an administrator to view objects by solutions Enables administrators to jump to crucial elements faster through relationships and object search Reduces client clutter and repetitive information by simplifying display of objects Displayed objects are all that is communicated between server and browser vSphere Web Client: Object Navigator Week#3 vSphere 5.1

  50. Managing ESXi from the Command Prompt To perform management tasks from a remote command prompt, use: • VMware vSphere® Command-Line Interface (vCLI): • Set of commands run from a remote Linux or Windows system and executed on an ESXi host • Packaged as an application • VMware vSphere® Management Assistant (vMA): • Platform for running a variety of toolkits: • vCLI • VMware vSphere® SDK for Perl • VMware vSphere® API • Packaged as a virtual appliance based on Linux • VMware vSphere® PowerCLI: • Automation tool for administering a vSphere environment • Distributed as a snap-in to Windows PowerShell

More Related