VMware vSphere 6.0 Ultimate Bootcamp Course 3 - c.ymcdn.com · Slide 4 3-4 Apache SUSE 11 SP3...

VMware vSphere 6.0 Ultimate Bootcamp

Course 3 - Planning and Installing ESXi

3-1

Course 3

Topic A

Planning the ESXi Deployment

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-2

Physical Hardware Requirements• CPU

– Min: 64 bit Intel or AMD

– Two cores minimum

– Max: 480 Logical cores (320 in 5.5, 160 in 5.1, 5.0 & 4.1 U1 , 128 in 4.1, 64 in 4.0, 32 Cores in ESX/ESXi 3.5)

– Requires the NX/XD bit to be enabled in the BIOS

• Memory– Min: 4 GB RAM (8 GB recommended)

– Max: 6 or 12 TB RAM (12 is OEM only) (4 TB in 5.5, 2 TB in 5.0 & 5.1, 256 GB ESX/ESXi 4.x, 64 GB ESX/ESXi 3.5)

• Networking– Min: 1 Gigabit Ethernet interface (included support for Intel &

Broadcom)

– Max: e1000e NICs (24), e1000 NICs (32), Broadcom NICs (32), 10GigE NICs (8), Mellanox 40Gig (4)

• See Notes for more supported NICs (KB 1020808)

• Other NIC drivers can be installed and are supported by VMware

Topic 1: Planning the ESXi Deployment

New in 5.0

New in 5.1

Updated 6.0

Updated 6.0

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-3

vSphere Hypervisor™ 6.0(VMware ESXi)

• Three Versions: Trial, Free or Paid

• Paid version adds featuresdepending on license purchased

• Installer package ≈ 300 MB

• Each ESXi host has one or two high performance SD cards– 144 MB footprint (70 MB in 5.0)

– Patching allowed on SD Card

• Can upgrade from Free to Paid

• Managed through CIM Apps/Tools

• Device Manufacturers create CIM providers (drivers)

• Added features for vMotion, DRS, SvMotion, SDRS, HA, FT, App HA, etc. when connected to vCenter, depending on license

ESXi 6.x Host

Physical Host

Virtual Machines

OS

APP

OS

APP

OS

APP


New in 5.1

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-4

Apache

SUSE 11 SP3

VMware ESXi 6.0 • The core of vSphere

product suite • Functions as the

hypervisor, or virtualization layer

• Installs directly on physical hardware

• Allows up to 32 vCPUs per core

• VMkernel – Acts as a translator – Separates the

vHardware from the physical hardware

– Dynamically allocates CPU, memory, disk and network

– Provides CIM for Mgtand Device Providers (VIBs – Vendor Information Bundles)

SharePoint or Exchange

Windows 2012 R2

CIM Mgt Virtualization Layer (VMkernel)

Physical Hardware(Host)

X86 Architecture

Common Information

Model component used for Management


Virtual Machines(VMs)

New in 5.5

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-5

Booting ESXi from a SAN LUN (Fibre Channel or iSCSI)

• Blade Center environment

• Disk / Diskless ESXi Host

• Quicker / Faster recovery from physical ESXi Host failure

HBASwitch

/boot

VMkernel

/

VMFS

• All LUNs appear as local disks


BIOS/CMOS

ESXi Host

SAN

LUN

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-6

Booting ESXi from a SAN LUN• Specify the Fibre Channel or iSCSI HBA card

in the CMOS as the primary boot device

• Fibre Channel card must be configured with the WWN of the SAN and the target LUN ID

• For iSCSI, configure the HBA IP address, and the iSCSI Initiator name. Identify the target by IP address, and the boot LUN

• NEW: iSCSI boot from iBFT enabled NIC with Software iSCSI


_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-7

Linux, Windows & ESX/ESXi

Physical disks / LUNsLinux/Unix/ESX/ESXi

ESXi uses mount points because of its roots in Linux. Mount points involve the association of a directory with a partition on the physical disk. Partitioning will define the maximum disk space available in each directory or volume.

Windows

FC or iSCSI LUN

NFS ShareLocal

/bin

/

/var

C:

D:

E:

F:

/vmfs

/volumes /devices

ESX & ESXi


ESXi

/Local

/NFS1

/LUN15

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-8

Course 3

Topic B

vSphere 6.x Deployment Guidelines

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-9

Overview of Deployment Planning

• Factors affecting the design & configuration of a vSphere environment:– Guest Operating Systems – Guest Applications – Number of physical machines to virtualize (P2V)– Planned number of VMs– Distributed Services (vMotion, DRS, HA, FT, SRM, etc.)– Hardware requirements– Storage requirements

• Hardware considerations for each ESXi Host will include processor, memory, NICs, HBA cards, disk drive space, and external storage

• vSphere deployments may include multiple ESXi hosts, vCenter, vCenter plugins, shared storage, etc

• All of VMware publications are found at:

Topic 2: vSphere 5.x Deployment Guidelines

http://pubs.vmware.com

Configuration Maximums

http://www.vmware.com/pdf/vsphere6/r60/vsphere-60-configuration-maximums.pdfhttp://www.vmware.com/pdf/vsphere5/r55/vsphere-55-configuration-maximums.pdfhttp://www.vmware.com/pdf/vsphere5/r51/vsphere-51-configuration-maximums.pdf

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-10

ESXi Compatibility Guides

All hardware and software must be listed on the certified

VMware Systems Compatibility Guides found at: http://www.vmware.com/resources/compatibility/search.php


_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-11

Storage: Capacity and Performance

Capacity:• Need to determine total storage capacity for all VMs,

templates, and ISOs.– Include all Hard drives for VMs (ie. C:, D:, E:)– Take into account RAID technologies (ie. 0, 5, 6, 10, RAID-DP)

Performance:• Spindles = Speed• Disk technologies are designed based upon the

application running in the VM – Datastore separation (ie. Database and log files in separate

datastores (drive subsystems) in case of failure)– Disks are allocated based upon the IOPS (I/O operations Per

Second) needed by the application

• Take into account RAID level (ie. 0, 5, 6, 10, RAID-DP)• Disk interface choice based on Kbps bandwidth

requirements of the applications running in the VMs


_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-12

VMware Capacity Planner

• Hosted application service• Provided by VMware Partners• Web-based capacity planning and analysis

client• Agent-less implementation• Data collection across multiple platforms• Comprehensive discovery of servers in

minutes and complete inventory in hours

• Rich set of capacity utilization metrics• Data for comparisons &

benchmarking• Scenario modeling and analysis• Trend analysis and predictions• Anomaly detection and alerts• Ad hoc analysis and reporting

Topic 2: vSphere 5.x Deployment Guidelineshttp://www.vmware.com/files/pdf/datasheet_capacity_planner.pdf

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-13

Course 3

Topic C

vSphere Hypervisor (ESXi) Installation

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-14

vSphere Hypervisor 6.x Installable

• 1 GB Boot device minimum, 5.2 GB if local disk or LUN (4 GB scratch partition needed)

• Can be installed on local drive (SCSI/USB/SD), FC or iSCSI SAN LUNs, RAID LUN (SATA, SCSI, SAS)

• Adapters support include: FC CNAs, iSCSI iBFT NICs, Local Controllers & RAID Controllers (Dell PERC, HP Smart Array RAID, IBM ServeRAID Controllers)

• ESXi 5.x & higher use GUID Partition Tables (GPT) instead of MBR on clean installs (does not overwrite hardware vendor partitions)

• Supports booting from UEFI (User Extensible Firmware Interface) based BIOS systems– Can boot from hard drives, CD-ROM drives, or USB media

– Do not change from legacy BIOS to UEFI after ESXi install

Topic 3: ESXi Installation

New in 5.0

New in 5.0

http://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface

http://pubs.vmware.com/vsphere-60/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-60-installation-setup-guide.pdf

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-15

• Interactive:– Boot ESXi installer, respond to installer prompts

• Scripted installation:– Script contains host configuration settings

– Script must be in an accessible location such as HTTP, HTTPS, FTP, NFS, CD, or USB

– A PXE boot install possible (UDA, Auto Deploy, etc)

• Automatic installation using VMware Auto Deploy:– vCenter Server system loads ESXi image directly into host

memory (Created or modified with ESXi Image Builder)

– Installation can be either stateful or stateless

– PXE boot is used to contact an Auto Deploy server

– vSphere Auto Deploy uses host profiles

• Remote management applications:– Install ESXi on hosts in remote locations with third-party

management applications

ESXi Installation Options

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-16

Demo: Installation of ESXi 6.0


17

New in 6.0

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-17

Local Configuration of ESXi 6.0using DCUI


3

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-18

UDA 2.0 Script ESXi Installation

• Third Party Program to provide automation and menu for scripted installs of ESXi/ESX– Linux Appliance

– Web based interface

– Allows installation of multiple OSs including ESXi/ESX 3.x/4.x/5.x/6

– Automates VMware Tools Installation

http://www.ultimatedeployment.org


http://www.mikelaverick.com/download/

http://www.mikelaverick.com/?s=UDA

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-19

vSphere 6.x ESXi Image Builder CLI

• PowerCLI cmdlets to provide customized ESXi installation media (ISO or ZIP)

• Manages software depot, ESXi image profiles and software packages (VIBs)

• Key component of vSphere 6.x Auto Deploy


• Requirements:– Microsoft .NET 2.0– Microsoft PowerShell 2.0– vSphere PowerCLI 6.x – Verify Image Builder Snap-in in

PowerCLI

New in 5.0

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-20

vSphere 5.x/6.x Auto Deploy Architecture

Public Depot

VIBs & ESXi Image Profiles

Auto Deploy Server (Web Server HTTP)

Auto Deploy PowerCLI

Rules Engine

Image Builder PowerCLI

ESXi Image profilesHost profiles

& answer files

ESXi Host

HTTP fetch of ESXi image, VIBs & Host

ProfilePXE Boot

DHCP Server TFTP Server

File

re

qu

est

gPX

E Fi

le

Bo

ot req

uest retu

rned

fro

m A

uto

Dep

loy

Server


http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-auto-deploy-guide.pdf

New in 5.0

Video: http://download3.vmware.com/media/flv/vSphereAutoDeploy.html

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-21

vSphere 6.x Auto Deploy for ESXi PXE Boot

• Automated booting of ESXi 6.x hosts using PXE, Host Profiles, ESXi Image Profiles, Answer files and Rules

• Allows management of many ESXi deployments• 3 Modes in vSphere 5.1 & higher

– Stateless – information not stored on host, but through Auto Deploy server via image profile and host profile

– Stateless Cached Mode – host image running in memory is cached to dedicated boot disk (local, SAN, USB, etc.)

– Stateful Install Mode – one time PXE boot to Auto Deploy server to perform full ESXi install, boots from disk there after

• Requirements:– vCenter Server 6.x with Enterprise Plus license (included in VC

Appliance & Windows vCenter Server, but service Disabled)– Host Profiles & Answer files (1 per host max)– PXE Boot Infrastructure

• DHCP & TFTP servers enable Network Boot

– Image Builder ESXi Image Profiles• Public depots contain VMware and VMware Partner image profiles and VIBs• Private depots contain internally created custom image profiles

Topic 3: ESXi Installationhttp://download3.vmware.com/media/flv/vSphereAutoDeploy.html

New in 5.0

New in 5.1

New in 5.1

Updated 6.0

Updated

6.0

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-22

Course 3

Topic D

Configuring Hostname Resolution and NTP

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-23

Configuring DNS Settings

• Host and Domain names are stored in /etc/hosts

• Three or more DNS servers will have to be defined in /etc/resolv.conf

• Multiple Lookup domains can be configured via the VIC or manually by editing/etc/resolv.conf

Topic 4: Configuring Hostname Resolution and NTP

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-24

Time Synchronization

• Uses Network Time Protocol (NTP v4): UDP Port 123

– V4 might prevent synchronizing with some older switches

• Synchronization options:– Windows AD DC can be an NTP Server

http://kb.vmware.com/kb/1035833

– External time server(s)

– Internal appliance or server(s)

– Network component such as a switch or router

• Reasons to synchronize time:

– Accurate timestamps for log messages

– VMware Tools Time synchronization (Possible Kerberos Issues)

• ESXi uses UTC time only, adjusts to local time of VIC for display

Topic 4: Configuring Hostname Resolution and NTP

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-25

Course 3

Topic E

Troubleshooting ESXi

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-26

ESXi Host Health Check

Topic 5: Troubleshooting ESXi

• Host Configuration tab Health Status link

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-27

ESXi Host Boot Process

• BIOS loads bootloader from boot device

• Bootloader loads Hypervisor kernel

• Hypervisor loads necessary drivers

• Hypervisor runs config scripts

• Hypervisor starts daemons (services)

• Boot process ends when DCUI loads


1

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-28

Troubleshooting: hostd

• A process, watchdog-hostd, monitors hostd

and automatically restarts the process if it stops– If both services stop, then hostdmust be manually

restarted /etc/init.d/hostd restart

• Check status of the hostd process

• Restart hostd if it is problematic


_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-29

Troubleshooting ESXi CIM Management Agents

• Use DCUI Restart Management Agents under Troubleshooting Options

• From CLI type /sbin/services.sh restart

automatically restarts multiple CIM services

Topic 5: Troubleshooting ESX/ESXihttp://kb.vmware.com/kb/1003490

7

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

3-30

Purple Screen Of Death (PSOD)

• Machine check exception

– A general hardware problem

– VMware Support can help pinpoint the failing subsystem

• NMI ECC or Parity Memory Errors

– VMware Support can help pinpoint the failing bank

• Physical CPU Failure


_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

_____________________________________________________________________________________

Review Questions:

1. An ESXi 6.x installer finds an existing version of ESXi and a VMFS3 volume

during an upgrade. Which option do you choose if you need to upgrade to

VMFS5 and no virtual machines exist on the host or VMFS3 volume? The

requirement is to upgrade to VMFS5.

A. Upgrade ESXi and preserve the VMFS datastore

B. Install ESXi and preserve the VMFS datastore

C. Install ESXi and overwrite the VMFS datastore

D. Upgrade ESXi and overwrite the VMFS datastore

2. Which of the following two statements below best explain why the vSphere Client

would report N/A for hyper-threading?

A. Hyper-threading is not supported by the physical CPUs in the host

B. Hyper-threading is disabled in the host's BIOS

C. The physical CPUs in the host are not multi-core

D. The number of CPUs meets or exceeds the maximum without hyper-

threading

E. A & B

F. B & C

G. C & D

3. To examine the following log files immediately after installing an ESXi host:

- /var/log/hostd.log

- /var/log/vmkernel.log

- /var/log/vpxa.log

Which of the following two connections can allow you to examine these files?

A. Attaching the vSphere Web Client directly to the ESXi host

B. Attaching the vSphere Client to the vCenter Server managing the ESXi

host

C. Connecting to the Direct Console User Interface

D. Attaching a vSphere Client directly to the ESXi host

E. A & B

F. B & C

G. C & D

4. An administrator plans to deploy ESXi 6.x, but does not want to use CD or DVD

media. What are two alternate ways to provide the ESXi 6.x installation script to

the host?

A. PXE

B. FTP

C. HTTP

D. IPMI

E. A & B

F. B & C

G. C & D

5. During the initial installation of ESXi 6.x, which settings can you choose to create

or set?

A. Upgrade ESXi and preserve the VMFS datastore

B. Provide for the root account

C. Set the VLAN ID of the management interface

D. Choose which interface will be used for the management interface

E. A & B

F. B & C

G. C & D

6. What happens to the status of users already logged into ESXi Shell if you enable

lockdown mode?

A. All users are immediately logged out of ESXi Shell

B. All users remain logged in and can run commands, including disabling

lockdown mode

C. Users on the list of Exception Users and who have administrator privileges

remain logged in and can run commands

D. All users are logged out after a timeout specified by the vSphere

administrator

7. You need to continue using ESXi after the 60-day evaluation period expires. You

received a valid license from VMware. Which step should you do to deploy the

license?

A. Re-install the host with standard ESXi and the obtained license

B. Perform an in-place upgrade of the free vSphere Hypervisor to the paid

version

C. Add the ESXi host to a licensed vCenter Server

D. Add the license to the ESXi host

8. Which of the following installation methods is not available for a new deployment

of ESXi 6.x?

A. Update Manager installation

B. Text-based interactive installation

C. Scripted installation

D. Auto Deploy installation

9. When an administrator attempts to install an ESXi 6.x host, the following error

message is reported:

Hardware Virtualization is not a feature of the CPU, or is not enabled in the

BIOS.

What condition would generate this message?

A. Hyper-threading is not enabled in the BIOS

B. NX/XD is not enabled in the BIOS

C. SSE3 is not enabled in the BIOS

D. LAHF/SAHF is not enabled in the BIOS

10. If an administrator wants a virtual machine to run on a vSphere 6.x host, what is

the minimum virtual machine compatibility setting required for this purpose?

A. ESXi 3.5 and later

B. ESXi 3.0 and later

C. ESXi 4.1 and later

D. ESXi 5.1 and later

Answer Key:

1. C

When an existing ESX/ESXi 4.x installation is detected, the ESXi Installer will

prompt to both migrate (upgrade) the host and preserve the existing VMFS

datastore, or to do a fresh install (with options to preserve or overwrite the VMFS

datastore). As there is no VM that exists, install ESXi and overwrite the VMFS

datastore.

2. E

Hyper-threading technology (sometimes also called simultaneous multithreading,

or SMT) allows a single physical processor core to behave like two logical

processors, essentially allowing two independent threads to run simultaneously.

Unlike having twice as many processor cores - that can roughly double

performance - hyper-threading can provide anywhere from a slight to a significant

increase in system performance by keeping the processor pipeline busier.

If the hardware and BIOS support hyper-threading, ESXi automatically makes

use of it. For the best performance we recommend that you enable hyper-

threading, which can be accomplished as follows:

- Ensure that your system supports hyper-threading technology. It is not enough

that the processors support hyper-threading - the BIOS must support it as well.

Consult your system documentation to see if the BIOS includes support for

hyper-threading.

- Enable hyper-threading in the system BIOS. Some manufacturers label this

option Logical Processor while others label it Enable Hyper-threading.

www.vmware.com/files/pdf/techpaper/VMware-PerfBest-Practices-vSphere6-

0.pdf

3. G

You can use the vSphere Client to connect directly to the ESXi host. If you use

vCenter Server, you can also use the vSphere Client to connect to and operate

vCenter Server. You can use the vSphere Web Client to connect to and operate

vCenter Server by web browser. The Direct Console User Interface (DCUI)

allows you to interact with the host locally using text-based menus. You can use

the Direct Console User Interface to enable local and remote access to the ESXi

Shell. vCenter Server is hosted on top of ESXi Server. vSphere Web Client is

installed after the ESXi installation is complete. Options C & D directly interact

with the ESXi host and are available immediately after ESXi installation.

http://www.vmware.com/files/pdf/techpaper/VMware-PerfBest-Practices-vSphere6-0.pdf

http://www.vmware.com/files/pdf/techpaper/VMware-PerfBest-Practices-vSphere6-0.pdf

4. F

ESXi 6.x allows you to use FTP and HTTP to provide installation scripts to the

host if you don’t want to use DVD or other media.

5. E

When an existing ESX/ESXi 4.x or higher installation is detected, the ESXi

Installer will prompt to both migrate (upgrade) the host and preserve the existing

VMFS datastore, or to do a fresh install (with options to preserve or overwrite the

VMFS datastore). During a clean or new installation of ESXi it will always ask

what the password will be of the root account. The management interface

defaults to the first available physical network card found in the host. It can be

changed in the DCUI after installation, as can the VLAN ID of the management

interface, which is not set during installation.

6. C

Enabling lockdown mode affects which users are authorized to access host

services. If users are logged in to the ESXi Shell or access the host through SSH

before lockdown mode is enabled, those users who are on the list of Exception

Users and who have administrator privileges on the host remain logged in.

Starting with vSphere 6.0, the session is terminated for all other users. This

applies to both normal and strict lockdown mode.

https://pubs.vmware.com/vsphere-60/topic/com.vmware.ICbase/PDF/vsphere-

esxi-vcenter-server-60-security-guide.pdf

7. D

To avoid the consequences from the evaluation period expiry, you must license

the ESXi hosts and the vCenter Server system in your environment.

https://pubs.vmware.com/vsphere-

60/index.jsp#com.vmware.vsphere.vcenterhost.doc/GUID-7AFCC64B-7D94-

48A0-86CF-8E7EF55DF68F.html

8. A

VMware provides three ways to install ESX/ESXi hosts:

- Interactive ESXi installation

- Scripted ESXi Installation

- Auto Deploy ESXi Installation

https://pubs.vmware.com/vsphere-

60/index.jsp#com.vmware.vsphere.install.doc/GUID-B64AA6D3-40A1-4E3E-

B03C-94AD2E95C9F5.html

https://pubs.vmware.com/vsphere-60/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-60-security-guide.pdf

https://pubs.vmware.com/vsphere-60/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-60-security-guide.pdf

https://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.vcenterhost.doc/GUID-7AFCC64B-7D94-48A0-86CF-8E7EF55DF68F.html



https://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.install.doc/GUID-B64AA6D3-40A1-4E3E-B03C-94AD2E95C9F5.html



9. D

LAHF stands for Load AH from Flags and SAHF stands for Store AH into Flags.

LAHF & SAHF are used to load and store instructions for certain status flags.

Instructions are basic commands composed of one or more symbols that are

passed to a CPU as input. These instructions related to LAHF & SAHF are used

for virtualization and floating-point condition handling. Support for LAHF/SAHF is

typically tied into the Virtualization Technology (VT) option in a server BIOS,

which is often referred to as Intel VT or AMD-V, which is their respective support

for virtualization CPU technology.

10. A

The compatibility setting determines the virtual hardware available to the virtual

machine, which corresponds to the physical hardware available on the host.

Virtual hardware includes BIOS and EFI, available virtual PCI slots, maximum

number of CPUs, maximum memory configuration, and other characteristics.

New virtual hardware capabilities are typically released once a year with major or

minor releases of vSphere. Each virtual machine compatibility level supports at

least five major or minor vSphere releases. For example, a virtual machine with

ESXi 3.5 and later compatibility can run on ESXi 3.5, ESXi 4.0, ESXi 4.1, ESXi

5.0, ESXi 5.1, and ESXi 5.5.

VMware vSphere 6.0 Ultimate Bootcamp Course 3 - c.ymcdn.com · Slide 4 3-4 Apache SUSE 11 SP3...

Documents

Transcript of VMware vSphere 6.0 Ultimate Bootcamp Course 3 - c.ymcdn.com · Slide 4 3-4 Apache SUSE 11 SP3...