VMware vSphere 6.0 - Troubleshooting Training - Day 1
Download as PPTX, PDF17 likes3,739 views
This document provides an introduction and overview of VMware vSphere: Install, Configure, Manage training course. It discusses how the course aligns with the VCP-Core certification exam blueprint and objectives. It also provides definitions of key data center concepts like tiers and an overview of the evolution of data centers. Finally, it discusses the history and benefits of data center virtualization using VMware technologies like ESXi, virtual machines, and vCenter Server.
VMware vSphere 6.0 - Troubleshooting Training - Day 1
- 1. Introduction to vSphere Day 1 VMware vSphere: Install, Configure, Manage
- 2. Content • Data Center History and Definitions • The Origin of Data Center Virtualization • Cloud • vSphere • ESXi • Virtual Machines • vCenter Server
- 3. VCP-Core Certification Alignment VMware vSphere: Install, Configure, Manage aligns with the VCP-Core certification: • The VCP-Core exam blueprint served as the basis for the design of this course. • You should use the VCP-Core exam blueprint as a reference when preparing for the test. • This course should not be used as the only resource for exam preparation. • VMware certification details can be found at http://mylearn.vmware.com/portals/certification/
- 4. Datacenter
- 5. What is a Datacenter A data center (sometimes spelled datacenter) is a centralized repository, either physical or virtual, for the storage, management, and dissemination of data and information organized around a particular body of knowledge or pertaining to a particular business.
- 6. Data center tiers • Tier 1 (99.671%) status would allow 1729.224 minutes or 28.817 hours • Tier 2 (99.741%) status would allow 1361.304 minutes or 22.688 hours • Tier 3 (99.982%) status would allow 94.608 minutes or 1.5768 hours • Tier 4 (99.995%) status would allow 26.28 minutes or 0.438 hours
- 7. Evolution Systems Solutions Efficiency Components Standardization Customer requirement increase efficiency in design and operation Racks, UPS, PDR, PDU, Cooling, Monitoring, Security Racks, Power, Cooling, Monitoring, Security Complete Data Center Modules, Server Modules, Power Modules
- 8. Individual vs. standardized data centers Individual data centers Individual products: CRAC, UPS, … Tailored Data Center planning Pay as you grow Client-specific solutions Standardized data centers Pre-defined data center modules Standardized Data Center planning ROI can be calculated Short delivery and launch time Types
- 9. Origin of Data Center Virtualization
- 10. Topology of a Physical Data Center Administering and maintaining a physical data center is time consuming and often inefficient. Fibre Channel Storage Fibre Channel Ethernet NFS Storage iSCSI Storage Applications Operating System Physical Host FCoE Storage Local Area Network
- 11. Introduction to Virtual Infrastructure Virtualization consolidates the environment and enables you to run more workloads on a single server. In a virtualized environment, applications run on virtual machines. Hypervisor ESXi Host Fibre Channel Fibre Channel Storage Ethernet NFS StorageiSCSI Storage Local Area Network Virtual Machines FCoE Storage
- 12. About the Software-Defined Data Center All major services of the data center can be virtualized. Software Hardware Virtual Machines Virtual Networks Virtual Storage Compute Capacity Network Capacity Storage Capacity Applications Desktop Internet Virtual Desktop Laptop Tablet Mobile Location Independence Application Consumption
- 13. About Virtual Machines A virtual machine is a software computer that, like a physical computer, runs an operating system and applications. • Operating system • VMware Tools™ • Virtual resources such as: – CPU and memory – Network adapters – Disk controllers – Parallel and serial ports Virtual Machine ComponentsVirtual Machine
- 14. Benefits of Using Virtual Machines Physical Machines Difficult to relocate: • Moves require downtime. • Specific to physical hardware. Difficult to manage: • Require physical maintenance. • Hardware failures cause downtime. Hardware has limitations: • Hardware changes limit application support. • One-to-one relationship between application and server. Virtual Machines Easy to relocate: • Encapsulated into files. • Independent of physical hardware. Easy to manage: • Isolated from other virtual machines. • Insulated from hardware changes. Provide the ability to support legacy applications. Enable servers to be consolidated.
- 15. Physical Architecture and Virtual Architecture Virtualization is a technology that decouples the physical hardware from the operating system and provides solutions to many problems that are faced by IT staff. Virtual Architecture x64 Architecture vSphere Physical Architecture x64 Architecture Operating System Application
- 17. x64 Architecture Operating System Application CPU Virtualization In a physical environment, the operating system assumes the ownership of all the physical CPUs in the system. CPU virtualization emphasizes performance and runs directly on the available CPUs. Virtual Architecture x64 Architecture vSphere Physical Architecture
- 18. Physical and Virtualized Host Memory Usage In a physical environment, the operating system assumes the ownership of all physical memory in the system. Memory virtualization emphasizes performance and runs directly on the available RAM. Physical Architecture Virtual Architecture x64 Architecture Operating System x64 Architecture vSphere Application 1 GB 2 GB 8 GB
- 19. Physical and Virtual Networking Virtual Ethernet adapters and virtual switches are key virtual networking components. Virtual Architecture vSphere Physical Architecture x64 Architecture Operating System Application Virtual Switch x64 Architecture
- 20. Physical File Systems and VMFS VMware vSphere® VMFS enables a distributed storage architecture, allowing multiple ESXi hosts to read or write to the shared storage concurrently. NTFS, ext4, UFS Physical Architecture Virtual Architecture Operating System Application vSpherevSphere Shared Storage: VMFS, NFS, Virtual SAN x64 Architecture x64 Architecturex64 Architecture
- 21. Encapsulation Virtual machine files are stored in directories on a VMFS or NFS datastore. VM 1 VM 2 VM 3 Datastore: VMFS or NFS
- 22. Hypervisor A hypervisor or virtual machine monitor (VMM) is a piece of computer software, firmware or hardware that creates and runs virtual machines. A computer on which a hypervisor runs one or more virtual machines is called a host machine, and each virtual machine is called a guest machine. The hypervisor presents the guest operating systems with a virtual operating platform and manages the execution of the guest operating systems. Multiple instances of a variety of operating systems may share the virtualized hardware resources: for example, Linux, Windows, and OS X instances can all run on a single physical x86 machine.
- 23. Type I These hypervisors run directly on the host's hardware to control the hardware and to manage guest operating systems. For this reason, they are sometimes called bare metal hypervisors. Vmware ESXi Microsoft Hyper-V Citrix XenServer Oracle VM Server Type II These hypervisors run on a conventional operating system just as other computer programs do. A guest operating system runs as a process on the host. Type-2 hypervisors abstract guest operating systems from the host operating system. VMware Player VirtualBox KVM QEMU VMware Workstation Classification
- 24. Cloud Computing
- 25. What is Cloud Computing Cloud computing is a type of Internet-based computing that provides shared computer processing resources and data to computers and other devices on demand.
- 26. With cloud computingWithout cloud computing Virtualized resources Automated service management Standardized services Location independent Rapid scalability Self-service Software Hardware Storage Networking Software Hardware Storage Networking Software Hardware Storage Networking
- 27. Cloud computing helps overcome IT challenges Cloud helps address the challenges using virtualization, standardization, and automation.
- 28. There is a spectrum of deployment options for cloud computing Enterprise Data Center 1) Private Cloud 2) Managed Private Cloud 3) Hosted Private Cloud 4) Community Cloud Services 5) Public Cloud Services Enterprise Data Center 3rd party operated Enterprise 3rd party hosted & operated Private Cloud Managed Private Cloud Hosted Private Cloud Enterprise A Enterprise B Enterprise C User 1 User 2 User 4 User 3 Private PublicHybrid Key features •Scalability •Automatic/rapid provisioning •Chargeback ability •Widespread virtualization •Security Key features •Scalability •Automatic/rapid provisioning •Standardized offerings •Consumption-based pricing. •Multi-tenancy Key features • Internal & external services integrated • Functions allocated to based on requirements, business needs, architecture etc Shared Cloud Services Public Cloud Services
- 29. Cloud delivery models Customers are choosing a variety of cloud models to meet their unique needs.. Private Cloud On or off premises cloud infrastructure operated solely for an organization and managed by the organization or a third party Public Cloud Available to the general public or a large industry group and owned by an organization selling cloud services Hybrid Cloud Traditional IT and clouds (public and private) that remain separate but are bound together by technology that enables data and application portability Traditional IT Appliances, pre-integrated systems and standard hardware, software, and networking
- 30. Cloud Service Models Networking Networking Networking Networking Storage Storage Storage Storage Servers Servers Servers Servers Virtualization Virtualization Virtualization Virtualization O/S O/S O/S O/S Middleware Middleware Middleware Middleware Runtime Runtime Runtime Runtime Data Data Data Data Applications Applications Applications Applications Traditional On-Premises Infrastructure as a Service Platform as a Service Software as a Service Customization; higher costs; slower time to value Standardization; lower costs; faster time to value Client Manages Vendor Manages
- 31. Cloud service models (1 of 2) The following diagram shows the cloud service models.
- 32. Cloud service models (2 of 2) Infrastructure as a Service (IaaS) In IaaS, you outsource the hardware. In such cases, it is not just the computing power that you rent; it also includes power, cooling, networking, and cloud storage. When you choose to run your applications at this cloud service level, you are responsible for everything on the stack that is required to operate above it. Platform as a Service (PaaS) In the middle, we have Platform as a Service, or PaaS. At this service level, the vendor takes care of the underlying infrastructure for you, giving you only a platform with which to build and host your application(s). Software as a Service (SaaS) Software applications that are available only over the internet, fall into the Software as a Service category, or SaaS. The simplest example to understand is email.
- 33. What are the drivers for Cloud? Improve IT efficiency to lower costs Accelerate new business solutions to improve time to value Simplify cloud transformations for agility and cost effectiveness by 2017 90% plan to implement cloud70% of IT operating costs in 2014 will be for management and administration 29% 1996 2014 70% deploy late 34% of new IT Projects Server mgmt & admin costs New server spending Power & cooling costs
- 34. Clouds Six potentially “game-changing” business enablers Cloud’s Business Enablers 2 1 6 5 4 3 Cost Flexibility • Shift CAPEX to OPEX • Scale costs to volumes • PAYG options Business Scalability • Rapidly scale up/down in response to events • Scale on-prem resources for efficiency Business Agility • Speed to market • Quickly adapt to busines changes Ease of consumptio • Self service • Lower the barrier to consumption Eco-system Connectivity • Strategically reinvent customer relationships • Access new services that improve business processes Differentiation & Specialisation • Context-driven Variability • User-defined experiences • Increases relevance
- 35. ESXi
- 36. ESXi VMware ESXi (formerly ESX) is an enterprise-class, type-1 hypervisor developed by VMware for deploying and serving virtual computers. As a type-1 hypervisor, ESXi is not a software application that one installs in an operating system (OS); instead, it includes and integrates vital OS components, such as a kernel. After version 4.1 (released in 2010), VMware renamed ESX to ESXi. ESXi replaces Service Console (a rudimentary operating system) with a more closely integrated OS. ESX/ESXi is the primary component in the VMware Infrastructure software suite. https://www.vmware.com/support/pubs/vsphere-esxi- vcenter-server-6-pubs.html
- 37. Versions 2002 – Vmware 2002 – Vmware ESX Server 1.5 2004 – Vmware ESX Server 2.0 2005 – Vmware ESX Server 2.5 2006 – Vmware Infrastructure 3.0 2008 – Vmware ESXi 3.5 2009 – Vmware ESXi 4.0 2011 – Vmware ESXi 4.1 2012 – Vmware ESXi 5.0 2014 – Vmware ESXi 5.1 2014 – Vmware ESXi 5.5 2015 – Vmware ESXi 6.0 2016 – Vmware ESXi 6.5
- 38. ESXi Hardware Prerequisites Processor: 64-bit x86 CPU: • Requires at least two cores. • ESXi supports a broad range of x64 multicore processors. • Requires NX/XD bit to be enabled for the CPU in the BIOS. Memory: 4 GB RAM minimum One or more Ethernet controllers: • Gigabit, 10 Gigabit, and 40 Gigabit Ethernet controllers are supported. Disk storage: • A SCSI adapter, Fibre Channel adapter, converged network adapter, iSCSI adapter, or internal RAID controller • A SCSI disk, Fibre Channel logical unit number (LUN), iSCSI disk, or RAID LUN with unpartitioned space: SATA, SCSI, or Serial Attached SCSI
- 39. Installing ESXi Select a volume that is not formatted with VMFS. You must have the ESXi ISO file on CD, DVD, or USB flash drive media. Boot from the media to start the ESXi installer. Select a volume that is not formatted with VMware vSphere® VMFS.
- 40. Other ESXi Installation Options In addition to using an interactive installation procedure to install ESXi, the following options are available: • Scripted ESXi installation: – The script contains the host configuration settings. – The script must be stored in an accessible location such as HTTP, HTTPS, FTP, NFS, CD, or USB. – A PXE boot installation is possible. • Automatic ESXi installation with VMware vSphere® Auto Deploy™: – The ESXi host loads the image directly into the host memory. – The ESXi installation can be either stateful or stateless. – PXE boot is used to contact an autodeploy server. – vSphere Auto Deploy uses host profiles. • Remote management applications: – Install ESXi on hosts in remote locations with third-party management applications.
- 41. Booting from SAN You can configure the boot device for an ESXi host. An ESXi host can be booted from SAN: • Supported for Fibre Channel SAN • Supported for iSCSI and FCoE for qualified storage adapters The host boots from the LUNs rather than from its local disk. The ESXi host must have exclusive access to its boot LUN, where the boot image is stored. SAN connections must be made through a switched topology unless the array is certified for direct-connect. Use different LUNs for VMFS datastores and boot partitions. Configure a diagnostic partition to store host fault information. ESXi Boot LUN
- 42. Virtual Machine
- 43. About Virtual Machine Files A virtual machine consists of a set of related files. VM folder Configuration file VM_name.vmx Swap files VM_name.vswp vmx-VM_name.vswp BIOS file VM_name.nvram Log files vmware.log Template file VM_name.vmtx Raw device map file VM_name-rdm.vmdk Disk descriptor file VM_name.vmdk Disk data file VM_name-flat.vmdk Suspend state file VM_name.vmss Snapshot data file VM_name.vmsd Snapshot state file VM_name.vmsn Snapshot disk file VM_name-delta.vmdk
- 44. Virtual Machine About Virtual Machine Virtual Hardware Hardware 3D 2 IDE Controller Devices Up to 3 Parallel Ports Up to 32 Serial/Com ports VMCI Controller 1 USB Controller 20 Devices 1 Floppy Controller 2 Devices Up to 10 NICs 15 Devices per Adapter Up to 4 TB of RAM Up to 4 SCSI Adapters Up to 128 vCPUs AHCI SATA Controller
- 45. Virtual Hardware Versions The virtual hardware version determines the operating system functions that a virtual machine supports. Do not use a version that is higher than supported by the VMware product. Compatibility Hardware Version VMware ESXi™ 6 and later 11 ESXi 5.5 and later 10 ESXi 5.1 and later 9 ESXi 5.0 and later 8 ESXi/ESX 4.0 and later 7
- 47. About Virtual Hardware Version 11 Virtual hardware version 11 provides several features and benefits. Features Benefits xHCI controller updated to version 1.0 USB 3 support for Mac OS X 10.8, Windows Server 2012, and Windows 8 operating systems. Windows VMXNET3 driver support Supports large receive offload, resulting in reduced associated CPU costs by reducing network packet processing. Enhanced NUMA feature Hot-add local memory is distributed across all NUMA nodes. Guest authentication Support for Windows 2000 and later, Linux kernels 2.4 and later, and Solaris operating systems. Host Guest File System (HGFS) shared folder driver Allows sharing of a folder between the virtual machine and the host system. Use this driver if you plan to use the virtual machine with VMware WorkStation™, VMware Player™, or VMware Fusion®. Increased vCPU capacity Hardware version 11 virtual machines can support up to 128 virtual CPUs. Increased RAM capacity Hardware version 11 virtual machines support up to 4 TB of RAM. Increased serial port configuration Hardware version 11 virtual machines can be configured with up to 32 serial ports.
- 48. About CPU and Memory You can add, change, or configure CPU and memory resources to improve virtual machine performance. The maximum number of vCPUs that you can assign to a virtual machine depends on: • The number of logical CPUs on the host • The host license • The type of installed guest operating system A virtual machine running on an ESXi 6 host can have up to 128 vCPUs. Maximum memory size for a virtual machine depends on: • The host’s physical memory • The virtual machine's compatibility setting The maximum memory size of a virtual machine with ESXi 6 compatibility running on ESXi 6 is 4,080 GB.
- 49. About Virtual Disks A virtual machine usually has a least one virtual disk. Sample virtual disk definition: Virtual disk size: 8 GB Datastore: MyVMFS Virtual disk node: 0:0 Virtual storage adapter: LSI Logic SAS Virtual disk files: Server1.vmdk and Server1-flat.vmdk Default disk mode: Snapshots allowed Optional disk mode: Independent: Persistent or Nonpersistent Disk provisioning policy: Thick Provision Lazy Zeroed, Thick Provision Eager Zeroed, or Thin Provision
- 50. About Thick-Provisioned Virtual Disks Thick provisioning uses all the defined disk space at the creation of the virtual disk: • Virtual machine disks consume all the capacity, as defined at creation, regardless of the amount of data in the guest operating system file system. Eager zeroed or lazy zeroed: • Every block in an eager zeroed thick-provisioned disk is prefilled with a zero. • Every block in a lazy zeroed thick- provisioned disk is filled with a zero when data is written to the block. Host Thick Thin Thin Virtual Disks Datastores
- 51. About Thin-Provisioned Virtual Disks Thin provisioning enables virtual machines to use storage space as needed: • Thin-provisioned virtual machine disks consume only the capacity needed to hold the current files. • A virtual machine sees the full allocated disk size at all times. You can mix thick and thin formats. Full reporting and alerts help manage allocations and capacity. More efficient use of storage: • Virtual disk allocation: 140 GB • Available datastore capacity: 100 GB • Used storage capacity: 80 GB Host Thick Thin Thin Virtual Disks Datastores
- 52. About Virtual Networks A virtual network is a network of virtual machines running on a physical machine. The virtual machines are logically connected so that they can send and receive data with each other. When you configure networking for a virtual machine, you select or change: • The network adapter type • The network connection • Whether to connect to the network when the virtual machine powers on
- 53. About Network Adapters When you configure a virtual machine, you can add network adapters (NICs) and specify the adapter type. Whenever possible, select VMXNET3. Supported network adapter types: • Flexible: Can function as either a Vlance or VMXNET adapter. • E1000-E1000E: High-performance adapter available for only some guest operating systems. • VMXNET, VMXNET2, and VMXNET3 are VMware drivers that are available only with VMware Tools. • SR-IOV passthrough: The virtual machine and the physical adapter exchange data without using the VMkernel as an intermediary. – Limited guest operating system support
- 54. About Miscellaneous Devices A virtual machine must have a vCPU and virtual memory. The addition of other virtual devices makes the virtual machine more useful. CD/DVD drive: • Connect to CD, DVD, or ISO image. USB 3.0: • Smart-card readers Floppy drive: • Connect a virtual machine to a floppy drive or a floppy image. Generic SCSI devices: • A virtual machine can be connected to additional SCSI adapters. vGPUs: • Enable a virtual machine to use GPUs on the physical host for high-computation activities.
- 55. About the Virtual Machine Console The virtual machine console provides the mouse, keyboard, and screen features to control the virtual machine. vSphere Web Client vSphere Client
- 57. Learner Objectives By the end of this lesson, you should be able to meet the following objectives: • Create, provision, and remove a virtual machine • Explain the importance of VMware Tools • Describe how to import a virtual appliance OVF template • Discuss how to use VMware vCloud® Air™ to create a virtual machine from a template
- 58. About Provisioning Virtual Machines You can create virtual machines in several ways: • Use the New Virtual Machine wizard to create virtual machines. • Deploy virtual machines, virtual appliances, and vApps stored in Open Virtual Machine Format (OVF). • Use a CentOS, Linux, or Windows template in a vCloud Air catalog to create virtual machines.
- 59. Creating Virtual Machines with the New Virtual Machine Wizard You can use the New Virtual Machine wizard in the vSphere Web Client to create a virtual machine.
- 60. New Virtual Machine Wizard
- 61. Installing the Guest Operating System Installing a guest operating system in your virtual machine is like installing it on a physical computer.
- 62. Deploying OVF Templates You can deploy any virtual machine or a virtual appliance stored in OVF. Virtual appliances are: • Preconfigured virtual machines • Usually designed for a single purpose, for example, a safe browser or firewall • Available from the VMware Solution Exchange vSphere Web Client
- 63. Deploying a Virtual Machine in vCloud Air vCloud Air is a secure, hybrid cloud service built on the vSphere foundation: • vCloud Air is available in the following infrastructure-as-a-service subscription service types: – Dedicated Cloud – Virtual Private Cloud and Virtual Private Cloud OnDemand – Disaster Recovery • vCloud Air includes a catalog that is populated with CentOS, Linux, and Windows templates that you can use to create virtual machines. • Your organization also has its own catalog, My Catalog, which can contain your customized templates. • In vCloud Air, end users select from catalogs to add virtual machines. • You can use virtual machines as desktop or workstation environments, as testing environments, or to consolidate server machines to supply what the end user sees as My Catalog. • Go to http://vcloud.vmware.com for more information.
- 64. About VMware Tools VMware Tools benefits: • Device drivers: – SVGA display – VMXNET/VMXNET3 – Balloon driver for memory management – Sync driver for quiescing I/O • Increased graphics performance • Improved mouse performance VMware Tools features: • Shared folders between host and guest file systems • Copying and pasting text, graphics, and files between the virtual machine and the host or client desktop • Time synchronization • Ability to shut down the virtual machine VMware Tools is a suite of utilities that enhance the performance of the virtual machine’s guest operating system.
- 65. Removing a Virtual Machine You can remove a virtual machine in two ways: • Remove from the inventory: – This type of removal unregisters the virtual machine. – The virtual machine’s files remain on the disk. – The virtual machine can later be registered (added) to the inventory. • Delete from disk: – All virtual machine files are permanently deleted from the virtual machine datastore.
- 66. Key Points • Virtual machines can be provisioned using various methods: – You can use the New Virtual Machine wizard in the vSphere Client or the vSphere Web Client to create virtual machines. – You can create a virtual machine by deploying an OVF template. – You can use vCloud Air to create a virtual machine from a template. • VMware Tools increases the performance of the virtual machine’s guest operating system. Questions?
- 67. vCenter Server
- 68. About the vCenter Server Management Platform vCenter Server is a service that acts as a central administration point for ESXi hosts and their virtual machines connected on a network. This service directs the actions of virtual machines and hosts. vSphere vSphere vSphere vCenter Server Manage
- 69. vCenter Server Architecture The diagram shows the supporting components for vCenter Server. ESXi Host ESXi HostESXi Host vSphere Web Client vCenter Server and Additional Modules Database Active Directory Domain Platform Services Controller with vCenter Single Sign-On
- 70. Additional vCenter Server Services and Interfaces vCenter Server has additional services and interfaces that provide important functions. Database Server Distributed Services Platform Services Controller vSphere API User Access Control ESXi Management Core Services Additional Services: • vSphere Update Manager • vRealize Orchestrator vSphere Web Client Third-Party Applications Plug-In PSC vCenter Server Database
- 71. Platform Services Controller vCenter Server includes the Platform Services Controller: The Platform Services Controller includes a set of common infrastructure services: – VMware vCenter™ Single Sign-On™ – VMware License Server – Lookup Service – Certificate Authority – Certificate Store – VMware Directory Services Other features are installed under the vCenter Server component. You can install vCenter Server and the Platform Services Controller on the same or different machines. Virtual Machine or Physical vCenter Server Platform Services Controller
- 72. vCenter Server Services and Functions The vCenter Server group of services contains: • vCenter Server • VMware vSphere® Web Client (server) • VMware Inventory Service • VMware vSphere® Auto Deploy™ • VMware vSphere® ESXi™ Dump Collector • VMware vSphere® Syslog Collector You cannot distribute these vCenter Server functions across multiple servers. When you install the vCenter Server component, all of these features are included.
- 73. ESXi and vCenter Server Communication vCenter Server ESXi Host hostd vpxa vpxd TCP/UDP 902 TCP/UDP 902 TCP 443 TCP 443, 9443
- 75. vCenter Server Appliance Features vCenter Server Appliance is a preconfigured, Linux-based virtual machine: • Runs on SUSE Linux Enterprise Server 11, Update 3 • Can be used with ESXi 5.5 and later ESXi versions • Is prepackaged with a PostgreSQL embedded database: – Suitable for environments with up to 1,000 hosts and 10,000 virtual machines • Supports an external Oracle database when running in an enterprise • Is equipped with the vCenter Server Appliance console, used for troubleshooting and configuration • Supports centralized authentication
- 76. vCenter Server Appliance Basics vCenter Server Appliance is functionally equivalent to vCenter Server installed on a Windows server: • vCenter Server Appliance can be configured with an embedded Platform Servces Controller. • vCenter Server Appliance can be configured as a distributed vCenter Server instance with an external Platform Services Controller. • You can combine vCenter Server Appliance instances and vCenter Server systems installed on Windows servers in the same architecture. • vCenter Server Appliance supports Linked Mode. vCenter Server Appliance vCenter Server Platform Services Controller vCenter Server Appliance Platform Services Controller vCenter Server Appliance vCenter Server Windows vCenter Server vCenter Server
- 77. Platform Services Controller Deployment Recommendations (1) Deployment Models Recommended for the Platform Services Controller in Enhanced Linked Mode Enhanced Linked Mode with an External Platform Services Controller Without vSphere HA Enhanced Linked Mode with an External Platform Services Controller with vSphere HA
- 78. Platform Services Controller Deployment Recommendations (2) Deployment Models Not Recommended for the Platform Services Controller in Enhanced Linked Mode Enhanced Linked Mode with Embedded Platform Services Controllers Combination Deployments of Both Embedded and external Platform Services Controllers
- 79. Platform Services Controller Deployment Recommendations (3) Deployment Model Not Recommended for the Platform Services Controller in Enhanced Linked Mode External vCenter Server System Linked to an Embedded Platform Services Controller
- 80. vCenter Server Appliance Scalability vCenter Server Appliance scales to the same capacity as vCenter Server installed on a Windows machine. Metric Windows Appliance Hosts per vCenter Server System 1,000 1,000 Powered-on virtual machines per vCenter Server System 10,000 10,000 Hosts per cluster 64 64 Virtual machines per cluster 8,000 8,000 Database Must be Oracle or SQL for full scalability Can be either Oracle or embedded PostgreSQL Linked Mode Yes Yes
- 81. vSphere License Service In vSphere 6, the License Service is part of the Platform Services Controller. It delivers centralized license management and reporting functionality to vSphere and to products integrated with vSphere. It provides an inventory for licenses in the vSphere environment and manages the license assignments for ESXi hosts, vCenter Server systems, and clusters with VMware Virtual SAN™ enabled . It manages the license assignments for products that integrate with vSphere.
- 83. When to Use a Windows Server or a Virtual Appliance Should you use a Windows server or a virtual appliance? Virtual appliance advantages: • A virtual appliance is much easier to install and configure. • No operating system license is required. • All configuration is done through a GUI. • vCenter Server running on a virtual appliance can scale to the same loads as a vCenter Server installed on a Windows server vCenter Server system running on a Windows server advantages: • Better for administrators who are more comfortable with Windows. • More options for external database support. • Configuration is done through a GUI, but individual components appear as Windows services. Both the Windows and the virtual appliance types of installation appear the same and operate the same in the vSphere Web Client, with identical functionality.
- 84. Choosing a Single System or a Distributed System Consider the following options when you install a single (embedded) system or a distributed system: • In a single system all components are installed on one server: – Much simpler to install. – Much simpler to manage. – The user interface calls a single system deployment an embedded deployment. • In a distributed system you have multiple servers: – You can have different components on different servers. – A distributed system can handle higher loads and provide more fault tolerance if it is configured correctly. – The user interface calls a distributed deployment an external install.
- 85. All services bundled with the Platform Services Controller are deployed on the same host as vCenter Server. After a deployment method is selected, it cannot be undone. Virtual Machine or Physical Server vCenter Server in an Embedded Install vCenter Server Platform Services Controller
- 86. Distributed vCenter Server System Configuration The services included with Platform Services Controller and vCenter Server are deployed on different physical servers or virtual appliances. You must first deploy Platform Services Controller on one machine and then deploy vCenter Server on another machine. A single Platform Services Controller is suitable for deployments with eight or fewer vCenter Server instances. Virtual Machine or Physical Server Platform Services Controller Virtual Machine or Physical Server vCenter Server Virtual Machine or Physical Server vCenter Server Virtual Machine or Physical Server Platform Services Controller Virtual Machine or Physical Server vCenter Server Virtual Machine or Physical Server vCenter Server VMDir Replication
- 87. Choosing an Installation Method You must determine which vCenter Server installation method meets the needs of your organization: • A virtual appliance is much easier to install and configure: – No operating system license is required. – All configuration is done through a GUI. – vCenter Server Appliance must be installed on an ESXi host. • vCenter Server Appliance and Windows-based vCenter Server have the same functionality. Both can be used to manage large environments.
- 88. vCenter Server Appliance Benefits VMware vCenter Server™ Appliance™ has many benefits: • Simplified installation and setup. • Contains all of the necessary services, such as vCenter Single Sign-On and the License Service, which can be shared between multiple vCenter Server instances. • The VMware vFabric® Postgres embedded database supports larger environments than databases embedded in previous vCenter Server Appliance versions. • Support for both IPv4 and IPv6 connectivity (no mixed mode deployments).
- 89. vCenter Server Appliance Features vCenter Server Appliance is a preconfigured Linux-based virtual machine, which is optimized for running vCenter Server. • vCenter Server Appliance runs on SUSE Linux Enterprise Server 11, Update 3. • vCenter Server Appliance can reside on a host running ESXi 5.5 or ESXi 6. • Prepackaged with an embedded VMware vFabric® Postgres database : – Suitable for environments with up to 1,000 hosts and 10,000 virtual machines. – Also supports Oracle 11g R2 11.2.0.4 and Oracle 12c as external databases. • Equipped with the vCenter Server Appliance console for troubleshooting and configuration. • Supports vSphere Web Client. • Supports connections by either IPv4 or IPv6 addresses.
- 90. Installing vCenter Server on a Windows Server Instead of using a virtual appliance, you can install vCenter Server on Microsoft Windows Server 2008 SP2 or later: • Validate vCenter Server hardware and software requirements. • Choose a vCenter Server database. – Embedded vFabric Postgres database – External database • Install vCenter Server and the infrastructure services. – Embedded Platform Services – External Platform Services Controller
- 91. User Account for Running vCenter Server You can use the Microsoft Windows built-in system account or a user account to run vCenter Server: • User (administrator) account: – With this account, you can enable Windows authentication for SQL Server. – This account provides more security. • Microsoft Windows built-in system account: – This account has more permissions and rights on the server than the vCenter Server system needs. – This account can contribute to security problems. • The virtual appliance has a built-in administrator account (root).
- 92. vCenter Server Windows Host Requirements At installation, when you select the deployment model, the preinstallation checker determines whether the Windows server on which you install vCenter Server meets the minimum hardware requirements. vCenter Server with an Embedded Platform Services Controller vCenter Server with an External Platform Services Controller Property vCenter Server Platform Services Controller Memory 8 GB 8 GB 2 GB Disk Space 17 GB 17 GB 4 GB Number of CPUs 2 2 2
- 93. Supported Operating Systems for vCenter Server 6 Windows operating systems supported by vCenter Server 6: • Microsoft Windows Server 2008 SP2 64-bit • Microsoft Windows Server 2008 R2 64-bit • Microsoft Windows Server 2008 R2 SP1 64-bit • Microsoft Windows Server 2012 64-bit • Microsoft Windows Server 2012 R2 64-bit
- 94. Before Installing vCenter Server Before beginning the vCenter Server installation, ensure that the following prerequisites are met: • Ensure that vCenter Server hardware and software requirements are met. • Ensure that the vCenter Server system belongs to a Microsoft Windows domain rather than a workgroup. • Create a vCenter Server database, unless you plan on using the embedded vFabric Postgres database: – If you create a database, you must also create a 64-bit data source name. • Obtain and assign a static IP address and a host name to the vCenter Server system: – The name should be resolvable by DNS. – If you plan to use IPv6, the name should be resolvable in IPv6 by DNS. • Create any administrator accounts that are needed.
- 95. Installing vCenter Server and Its Components You use the VMware vCenter Installer to install vCenter Server. Embedded Deployment Distributed Deployment
- 96. Deploying vCenter Server Appliance You can configure vCenter Server Appliance by using the vSphere Web Client, the appliance shell, or the Direct Console User Interface. You must download and install the vCenter Server Appliance installer and the VMware Client Integration Plug-In. The Client Integration Plug-In provides access to a virtual machine’s console in the vSphere Web Client as well as access to other vSphere infrastructure tasks.
- 97. vCenter Server Appliance Installation Media vCenter Server Appliance is distributed as an ISO image, which contains the following components: • vCenter Server Appliance 6 data file (vcsa folder) • Client Integration Plug-In 6 for Windows, Mac, and Linux • vCenter Server Appliance command-line installer • vCenter Server Appliance UI deployment Web page (index.html)
- 98. vCenter Server Appliance Installer The vCenter Server Appliance ISO image contains a UI deployment Web page (index.html). Open this file to begin the installation.
- 99. Connecting to the ESXi Host on Which to Deploy vCenter Server Appliance In the vCenter Server Appliance Deployment wizard, you connect to the target ESXi host where you deploy vCenter Server Appliance.
- 100. Specifying the Virtual Machine Name and Password for Root User Enter the vCenter Server Appliance name and set the password for the root user.
- 101. Selecting the Deployment Type Select a deployment type based on your organization’s needs.
- 102. Configuring vCenter Single Sign-On Configure vCenter Single Sign-On by specifying a password, a domain name, and a site name.
- 103. Selecting a vCenter Server Appliance Size Select the vCenter Server Appliance size based on the size of your vSphere inventory.
- 104. Selecting a Datastore From the list of available datastores, select the location where all the virtual machine configuration files and virtual disks will be stored and, optionally, enable thin provisioning.
- 105. Configuring a Database You can configure vCenter Server Appliance to either use an existing Oracle database or use the embedded PostgreSQL database that is suitable for small-scale deployments.
- 106. Configuring Network Settings You must configure network settings, specify if you want to enable SSH, and select a time sync option.
- 107. Using the vSphere Web Client to Log In to vCenter Server After you deploy vCenter Server Appliance, log in to it by using the vSphere Web Client to manage your vSphere inventory. • Open a Web browser and enter the URL for the vSphere Web Client: https://appliance_IP_address_or_FQDN/vsphere-client.
- 108. vSphere Web Client Home Page The vSphere Web Client Home page appears the first time that you use the vSphere Web Client to log in to your vCenter Server system. The Home page has a Navigator pane on the left and Inventories, Monitoring, and Administration panes on the right.
- 109. Adding License Keys to vCenter Server Assign a license to vCenter Server before its 60-day evaluation period expires.
- 110. Using the vSphere Web Client Navigator You can use the Navigator pane to browse and select objects in the vSphere Web Client inventory. The navigator presents a graph- based view of the inventory, which enables you to navigate inventory objects.
- 111. vCenter Server Views: Hosts and Clusters, VMs and Templates VMs and Templates Inventory View Hosts and Clusters Inventory View
- 112. vCenter Server Views: Storage and Networks Networks Inventory View Storage Inventory View
- 113. Viewing Object Information Because you can navigate to view object information and access related objects, monitoring and managing object properties is easy.
- 114. Configuring vCenter Server Settings You can configure your vCenter Server system from the vSphere Web Client, including settings such as licensing, statistics collection, logging, and other settings. • To access the vCenter Server system settings, navigate to the vCenter Server system in the vSphere Web Client and click the Manage > Settings tabs.
- 115. Managing the vCenter Server Services You can manage vCenter Server services by selecting Administration > System Configuration from the Home page and selecting Services.
- 116. Monitoring Health and Status of Services and Nodes Across vCenter Server Systems The vSphere Web Client enables you to monitor the status of all manageable services and nodes across vCenter Server systems. A list of default services is available in each vCenter Server instance.
- 117. ESXi Host as an NTP Client Network Time Protocol (NTP) is a client-server protocol used to synchronize a computer’s clock to a time reference. NTP is important: • For accurate performance graphs • For accurate time stamps in log messages • So that virtual machines have a source to synchronize with An ESXi host can be configured as an NTP client. It can synchronize time with an NTP server on the Internet or your corporate NTP server. NTP Server NTP Client NTP Server NTP Server ESXi Host The NTP client uses UDP over port 123 to communicate with the NTP server.
- 118. Configuring ESXi Host Time Synchronization Configure Network Time Protocol (NTP) settings for each host:
- 119. Viewing Recent Objects You can quickly navigate to the objects that you visited during your vSphere Web Client session. You can revisit objects without having to search in the inventory tree. You use the Recent Objects icon to view objects that you visited or created in your environment.
- 120. Using Quick Filters You can use quick filters to find an object or a set of objects in the vSphere inventory by using certain display criteria. Show or hide the quick filters options.
- 121. Using Drag-and-Drop Functionality You can drag an inventory object to another location. This action is an alternative way to perform tasks that are available in the context menu. Drag-and-drop icons indicate whether you can move the object. .
- 122. About Data Center Objects A virtual data center is a container for all the inventory objects required to complete a fully functional environment for operating virtual machines: • You can create multiple data centers to organize sets of environments. • Each data center has its own hosts, virtual machines, templates, datastores, and networks. Los Angeles Data Center vCenter Server Toronto Data Center Paris Data Center Munich Data Center
- 123. Organizing Inventory Objects into Folders Items in the data center can be placed into folders. Folders and subfolders can be created to better organize systems. HOSTHOST HOST HOST Los Angeles Data Center File and Print DB Intel AMD
- 124. Using Folders You can use folders to group objects of the same type for easier management. For example, permissions can be applied to folders, enabling you to use folders to group objects that should have a common set of permissions.
- 125. Creating Custom Tags for Inventory Objects Tags enable you to attach metadata to objects in the vSphere inventory to make these objects more sortable. You can associate a set of objects of the same type: • Search for objects by that tag. • Enable a business case where customers want to create groups of virtual machines, clusters, and datastores for ease of management.
- 126. vCenter Server Events Events are records of user actions or system actions that occur on objects in vCenter Server or on a host. Event Type Details of Selected Event
- 127. vCenter Server System Logs vSphere records events in the vCenter Server database. System log entries include information such as who generated the event, when the event was created, and the type of event. You can export system logs for troubleshooting system problems.