Beruflich Dokumente
Kultur Dokumente
x Infrastructure Components
Objective 1.1 - Perform Advanced ESXi Host Configuration
Stateless caching
Stateful installs
specify the behavior of the Auto Deploy server by using a set of rules written in Power CLI
The Auto Deploy rule engine checks the rule set for matching host patterns to decide
which items (image profile, host profile, or vCenter Server location) to provision each host
with
Add-EsxSoftwareDepot C:REPOVMware-ESXi-6.0.0-2494585-depot.zip
Get-EsxImageProfile
Example
Get-DeployRule
Get-DeployRuleSet
o Create and associate Host Profiles for an Auto Deploy reference host
In the vSphere Web Client, click Rules and Profiles and click
Host Profiles.
For a new profile, click the Create Profile from a host icon, or
right-click a profile that you want to modify and select Edit
Host Profile.
Set up syslog for the host with the esxcli system syslog
command.
The default ks.cfg installation script is located in the initial RAM disk
at /etc/vmware/weasel/ks.cfg.
#
# Sample scripted installation file
#
# Accept the VMware End User License Agreement
vmaccepteula
# Set the root password for the DCUI and Tech Support Mode
rootpw mypassword
# Install on the first local disk available on machine
install --firstdisk --overwritevmfs
# Set the network to DHCP on the first network adapter
network --bootproto=dhcp --device=vmnic0
# A sample post-install script
%post --interpreter=python --ignorefailure=true
import time
stampFile = open('/finished.stamp', mode='w')
stampFile.write( time.asctime() )
Download the ESXi ISO image from the VMware Web site.
XXXXXX is the ESXi build number for the version that you
are installing or upgrading to.
cp ks_cust.cfg /esxi_cdrom
kernelopt=runweasel ks=cdrom:/KS_CUST.CFG
cp -r /esxi_cdrom_mount /esxi_cdrom
Swap file
VMkernels swap file is serves as a backing store for the virtual machines RAM contents. By default, its created
in the same location as the virtual machine configuration file. Its created by the ESXi host when the virtual
machine is powered on. So if this file cannot be created then the Virtual machine cannot power on. So if we
consider a clustered environment the Swap settings can be configured on a VMware cluster level.
Open the Web Client Right click on your Cluster object and select the Settings. Under the Configuration click
on General. There you will see an option to edit Swap File Location.
We basically have two option either to store the swap files in the same directory as the virtual machine or store
the swap files in the Datastore specified by the host.
We will choose the second option here to select a Datastore to manage the swap file creation.
But keep in mind as the VMware warns that using Datastore that is not visible to all the hosts in the cluster will
affect the vMotion performance.
Open the VMware Client and Select the host you want to change its swap file location and click
on Configurations then under the Software tab click on the Virtual Machine Swap File Location Then Edit and
choose the Datastore you wish to use for managing swap files.
Scratch partition
Its basically a 4 GB sized VFAT partition to hold such as troubleshooting information such as logs and core files
for VMware Support. Even if this partition is not available ESXi will still function and keep the information in
RAMDisk. However, RAMDisk information will not stay beyond a restart. If there are storage resource constrains
we can move the scratch partition to a shared storage.
SSH in to any host and find out below Unique Datastore identified information.
We will need the ID corresponding to the Datastore02-SDD where we have already created a Root folder named
Scratch and created a folder structure for all the 3 VMHosts.
/vmfs/volumes/57167100-c02b5a34-b7d5-b8aeed7e47be/Scratch/VMHOST01
Right click the HOST and click on Settings>Advanced System Settings and search for scratch it will show two
entries as below from that edit the entry ScratchConfig.ConfiguredScratchLocation
Once the configuration has been applied take a restart of the particular VMHosts. After the restart if you browse
the corresponding location in the Datastore you will see below folder structure.
The core dump configuration allows us to configure a location for ESXi to store its dump files during a PSOD (Purple
Screen of Death).
First, we need to start the VMware vSphere ESXi Dump Collector service on the VCSA.
From the vSphere Web Client, browse to Administration > Deployment > System Configuration > Services > VMware
vSphere ESXi Dump Collector. Choose the Actions menu, and change the startup type to Automatic.
Now, choose the actions menu again, and Start the service.
Finally, we need to configure the ESXi hosts to send dumps to the collector on the VCSA. We can do this via
ESXCLI, or using a host profile (preferred) .
To configure using Host Profiles:
Connect to vCenter Server using the vSphere Client.
Click Home and select Host Profiles.
Create or edit a host profile.
Select Networking Configuration.
Select Network Coredump Settings.
Specify the VMkernel network interface to use for outbound traffic, such as vmk0.
Specify the IP address and UDP port number of the remote network coredump server.
Save and apply the host profile.
Create / Configure multiple VMkernels for use with iSCSI port binding
Expand (Scale up / Scale Out) Virtual SAN hosts and disk groups
Objective 3.1 - Implement and Manage vSphere Standard Switch (vSS) Networks
Objective 3.2 - Implement and Manage vSphere 6.x Distributed Switch (vDS) Networks
Configure appropriate NIC teaming failover type and related physical network
settings
Determine and configure vDS port binding settings according a deployment plan
Configure VMware Fault Tolerance for single and multi-vCPU virtual machines
Analyze a sample script, then modify the script to perform a given action
Use PowerCLI to configure and administer Auto Deploy (including Image Builder)
Evaluate use cases for and apply esxtop / resxtop Interactive, Batch and Replay
modes
Given esxtop / resxtop output, identify relative performance data for capacity
planning purposes
Backup and restore a Virtual Machine (file level restore, full VM backup)