List of Illustrations Chapter 1 Figure 1.1 The VMkernel is the foundation of the virtualization functionality found in VMware ESXi. Figure 1.2 vSphere Virtual SMP allows VMs to be created with more than one virtual cpu Figure 1. 3 The vSphere ha feature will restart any vMs that were previously running on an ESXi host that experiences server or storage path failure. Figure 1.4 vSphere Ft provides protection against host failures with no downtime experienced by the vms. Chapter2 Figure 2.1 Servers on the Compatibility guide come in various sizes and models. Figure 2.2 The initial ESXi installation routine has options for booting the installer or booting from the local disk. Figure 2.3 The installer offers options for both local and remote devices; in this case, only a local device was detected. Figure 2.4 Although local Sas devices are supported they are listed as remote devices. Figure 2.5 Checking to see if there are any vmfs datastores on a device can help you avoid accidentally overwriting data. Figure 2.6 You can upgrade or install ESXi as well as choose to preserve or overwrite an existing vMFS datastore Figure 2.7 Host information is echoed to the server console when it performs a network boot, Figure 2.8 This screen provides information about the auto deploy server that is registered with v Center Server Figure 2.9 Note the differences in the esXi boot process when using Auto Deploy versus a traditional installation of ESXi. Figure 2.10 Editing the host profile to allow Stateless Caching on a
List of Illustrations Chapter 1 Figure 1.1 The VMkernel is the foundation of the virtualization functionality found in VMware ESXi. Figure 1.2 vSphere Virtual SMP allows VMs to be created with more than one virtual CPU. Figure 1.3 The vSphere HA feature will restart any VMs that were previously running on an ESXi host that experiences server or storage path failure. Figure 1.4 vSphere FT provides protection against host failures with no downtime experienced by the VMs. Chapter 2 Figure 2.1 Servers on the Compatibility Guide come in various sizes and models. Figure 2.2 The initial ESXi installation routine has options for booting the installer or booting from the local disk. Figure 2.3 The installer offers options for both local and remote devices; in this case, only a local device was detected. Figure 2.4 Although local SAS devices are supported, they are listed as remote devices. Figure 2.5 Checking to see if there are any VMFS datastores on a device can help you avoid accidentally overwriting data. Figure 2.6 You can upgrade or install ESXi as well as choose to preserve or overwrite an existing VMFS datastore. Figure 2.7 Host information is echoed to the server console when it performs a network boot. Figure 2.8 This screen provides information about the Auto Deploy server that is registered with vCenter Server. Figure 2.9 Note the differences in the ESXi boot process when using Auto Deploy versus a traditional installation of ESXi. Figure 2.10 Editing the host profile to allow Stateless Caching on a
ocal a isk Figure 2.11 You can install the v Sphere Client directly from the vCenter Server installation media. Figure 2.12 Network connectivity won't be established if the ESXi installer links the wrong nic to the management network. Figure 2.1 The ESXi home screen provides options for customizing the system and restarting or shutting down the server. Figure 2.14 In the event the incorrect Nic is assigned to ESXis management network, you can select a different NIC. Figure 2.15 Specifying NtP servers allows eSXi to automatically keep time synchronized. Chapter 3 Figure 3. 1 vCenter Server provides a full spectrum of virtualization management functions Figure 3.2 The steps taken to issue an authenticated session with the SSO component Figure 3.3 The Platform Services Controller can be installed as an embedded or external component of vCenter, just like a database. Figure 3.4 Other applications can extend v Center Servers core services to provide additional management functionality. Figure 3.5 vCenter Server acts as a proxy for managing esXi hosts, but all of the data for v center server is stored in a database. Figure 3. 6 A good disaster-recovery plan for v Center Server should include a quick means of regaining the user interface as well as ensuring that the data is highly available and protected against d amage Figure 3.7 If v Center Server is a vm, its virtual disk file can be copied regularly and used as the hard drive for a new vM, effectively providing a point-in-time restore in the event of complete server failure or loss. Figure 3. 8 The SqL Server database that vCenter Server uses must be owned by the account vCenter Server uses to connect to the database Figure 3. 9 The VMware vCenter Installer offers options for installing
local disk Figure 2.11 You can install the vSphere Client directly from the vCenter Server installation media. Figure 2.12 Network connectivity won’t be established if the ESXi installer links the wrong NIC to the management network. Figure 2.13 The ESXi home screen provides options for customizing the system and restarting or shutting down the server. Figure 2.14 In the event the incorrect NIC is assigned to ESXi’s management network, you can select a different NIC. Figure 2.15 Specifying NTP servers allows ESXi to automatically keep time synchronized. Chapter 3 Figure 3.1 vCenter Server provides a full spectrum of virtualization management functions. Figure 3.2 The steps taken to issue an authenticated session with the SSO component Figure 3.3 The Platform Services Controller can be installed as an embedded or external component of vCenter, just like a database. Figure 3.4 Other applications can extend vCenter Server’s core services to provide additional management functionality. Figure 3.5 vCenter Server acts as a proxy for managing ESXi hosts, but all of the data for vCenter Server is stored in a database. Figure 3.6 A good disaster- recovery plan for vCenter Server should include a quick means of regaining the user interface as well as ensuring that the data is highly available and protected against damage. Figure 3.7 If vCenter Server is a VM, its virtual disk file can be copied regularly and used as the hard drive for a new VM, effectively providing a point-in-time restore in the event of complete server failure or loss. Figure 3.8 The SQL Server database that vCenter Server uses must be owned by the account vCenter Server uses to connect to the database. Figure 3.9 The VMware vCenter Installer offers options for installing
several components. Figure 3.10 The Platform Services controller can be installed either embedded with or separately from vCenter Server Figure 3.11 The vCenter Server installation program will ask for all the configuration options up front before installing the software. Figure 3.12 In a linked mode environment, the vSphere Client shows all the vCenter Server instances for which a user has permission Figure 3.13 The v Center Server virtual appliance can have an embedded vPostgres database and supports up to 1, 000 hosts or 10,000 virtual machines Figure 3. 14 This dialog box provides information on the status of the v Center Server virtual appliance deployment. Figure 3.15 This management screen lets you configure network access to the vCenter Server virtual appliance. Figure 3.16 The vSphere Web client home screen shows the full election of features within not just vCenter Server but also both other services that hook into the vSphere Web client. Figure3.17 Users can create folders above the datacenter object to grant permission at a level that can propagate to multiple datacenter objects or to create folders beneath a datacenter to manage the objects within the datacenter object. Figure 3.18 A departmental vCenter Server inventory allows the It nistrator to implement controls within each organizational department Figure 3. 19 Create folders to organize objects and delegate permissions within the vCenter web client Figure 3.20 Licenses can be assigned to an eSXi host as they are added to vCenter Server or at a later time. Figure 3.21 The right-click menu in the vSphere Web client is now very similar to the vSphere Desktop client. Figure 3.22 When a host is selected in the inventory view, the tabs across the top also provide host-management features
several components. Figure 3.10 The Platform Services controller can be installed either embedded with or separately from vCenter Server. Figure 3.11 The vCenter Server installation program will ask for all the configuration options up front before installing the software. Figure 3.12 In a linked mode environment, the vSphere Client shows all the vCenter Server instances for which a user has permission. Figure 3.13 The vCenter Server virtual appliance can have an embedded vPostgres database and supports up to 1,000 hosts or 10,000 virtual machines. Figure 3.14 This dialog box provides information on the status of the vCenter Server virtual appliance deployment. Figure 3.15 This management screen lets you configure network access to the vCenter Server virtual appliance. Figure 3.16 The vSphere Web Client home screen shows the full selection of features within not just vCenter Server but also both other services that hook into the vSphere Web Client. Figure 3.17 Users can create folders above the datacenter object to grant permission at a level that can propagate to multiple datacenter objects or to create folders beneath a datacenter to manage the objects within the datacenter object. Figure 3.18 A departmental vCenter Server inventory allows the IT administrator to implement controls within each organizational department. Figure 3.19 Create folders to organize objects and delegate permissions within the vCenter Web Client. Figure 3.20 Licenses can be assigned to an ESXi host as they are added to vCenter Server or at a later time. Figure 3.21 The right-click menu in the vSphere Web Client is now very similar to the vSphere Desktop Client. Figure 3.22 When a host is selected in the inventory view, the tabs across the top also provide host-management features
Figure 3.23 The Manage tab of an ESXi host offers a number of commands to view or modify the host's configuration. Figure 3.24 The Events Console lets you view event details, search events, and export events (highlighted) Figure 3.25 Users have a number of options when exporting events out of v Center Server to a csv file. Figure 3.26 Host profiles provide a mechanism for checking and enforcing compliance with a specific configuration. Figure 3.27 To make changes to a number of esXi hosts at the same time, put the settings into a host profile, and attach the profile to the hosts. Figure-3.28 You are able to create both tags and tag categories in the New ag dialog bOX Figure 3.29 You can add metadata to objects by creating and assigning tags Figure 3.30 After you've defined a category and a tag, you can use it as search criteria for quickly finding objects with similar tags. Figure 3.31 You can customize statistics collection intervals to support Droad or detalled logging. Figure 3.32 Licensing vCenter Server is managed through the vCenter Server Settings dialog box. Figure 3.33 You can view logs from vCenter Server or ESXi hosts easily from the log Browser on the home screen. Figure 3.34 These logs are for vCenter Server, a single EsXi host, and the computer running the vSphere Client. Chapter 4 Figure 4.1 Set the owner of the database correctly when you create the database Figure 4.2 Place the database and log files for VUM on different physical drives than the operating system and patch repository Figure 4.3 Supply the correct username and password for the vuM database
Figure 3.23 The Manage tab of an ESXi host offers a number of commands to view or modify the host’s configuration. Figure 3.24 The Events Console lets you view event details, search events, and export events (highlighted). Figure 3.25 Users have a number of options when exporting events out of vCenter Server to a CSV file. Figure 3.26 Host profiles provide a mechanism for checking and enforcing compliance with a specific configuration. Figure 3.27 To make changes to a number of ESXi hosts at the same time, put the settings into a host profile, and attach the profile to the hosts. Figure 3.28 You are able to create both tags and tag categories in the New Tag dialog box. Figure 3.29 You can add metadata to objects by creating and assigning tags. Figure 3.30 After you’ve defined a category and a tag, you can use it as search criteria for quickly finding objects with similar tags. Figure 3.31 You can customize statistics collection intervals to support broad or detailed logging. Figure 3.32 Licensing vCenter Server is managed through the vCenter Server Settings dialog box. Figure 3.33 You can view logs from vCenter Server or ESXi hosts easily from the Log Browser on the home screen. Figure 3.34 These logs are for vCenter Server, a single ESXi host, and the computer running the vSphere Client. Chapter 4 Figure 4.1 Set the owner of the database correctly when you create the database. Figure 4.2 Place the database and log files for VUM on different physical drives than the operating system and patch repository. Figure 4.3 Supply the correct username and password for the VUM database
Figure 4.4 The VUM installation provides the option to configure proxy settings. If there is no proxy, leave the box deselected. Figure 4.5 The default settings for VUM place the application files and the patch repository on the system drive. Figure 4.6 You must configure the UMDS utility at the command prompt. Figure 4.7 Installing the vSphere Desktop Client plug-in is done from within the vSphere Desktop Client. Figure 4. 8 The tabs in the Update Manager Administration area in the vSphere Desktop Client Figure 4.9 Select patch sources so that vuM downloads only certain types of patches Figure 4.10 By default, VM snapshots are enabled for use with VUM. Figure 4.11 The Events tab lists events logged by vUM during operation and can be a good source of information for troubleshooting. Figure 4.12 Events from VUM Manager are included in the Management area of vCenter Server, where information can be exported or filtered. Figure 4.13 The Patch Repository tab also offers more detailed information about each of the items in the repository Figure 4.14 Dynamic baselines contain a set of criteria that determine which patches are included in the baseline and which are not Figure 4.15 Combining multiple dynamic baselines into a baseline group provides greater flexibility in managing the deployment and compliance of patches. Figure 4.16 Use baseline groups to combine host upgrade and dynamic host patch baselines. Figure 4. 17 A baseline group combines multiple individual baselines for a more comprehensive patching capability. Figure 4.18 The Attach Baseline Or group dialog box Figure 4.19 Detaching baselines Figure 4.20 When you're detaching a baseline or baseline group, VUM
Figure 4.4 The VUM installation provides the option to configure proxy settings. If there is no proxy, leave the box deselected. Figure 4.5 The default settings for VUM place the application files and the patch repository on the system drive. Figure 4.6 You must configure the UMDS utility at the command prompt. Figure 4.7 Installing the vSphere Desktop Client plug-in is done from within the vSphere Desktop Client. Figure 4.8 The tabs in the Update Manager Administration area in the vSphere Desktop Client Figure 4.9 Select patch sources so that VUM downloads only certain types of patches. Figure 4.10 By default, VM snapshots are enabled for use with VUM. Figure 4.11 The Events tab lists events logged by VUM during operation and can be a good source of information for troubleshooting. Figure 4.12 Events from VUM Manager are included in the Management area of vCenter Server, where information can be exported or filtered. Figure 4.13 The Patch Repository tab also offers more detailed information about each of the items in the repository. Figure 4.14 Dynamic baselines contain a set of criteria that determine which patches are included in the baseline and which are not. Figure 4.15 Combining multiple dynamic baselines into a baseline group provides greater flexibility in managing the deployment and compliance of patches. Figure 4.16 Use baseline groups to combine host upgrade and dynamic host patch baselines. Figure 4.17 A baseline group combines multiple individual baselines for a more comprehensive patching capability. Figure 4.18 The Attach Baseline Or Group dialog box Figure 4.19 Detaching baselines Figure 4.20 When you’re detaching a baseline or baseline group, VUM