Server Virtualization
Server Virtualization
Prac Signature
No Practical Description
1 Deploying and Configuring Virtual Machines
3. Add Your ESXi Hosts to the vCenter Server Inventory 4. Configure the ESXi Hosts as NTP
Clients
3. Attach Your Virtual Machines to the New Virtual Machine Port Group
1313300
M.SC. IT Sem 3 Server Virtualization using VMware
1. Create a Virtual Switch and a VMkernel Port Group for vSphere vMotion Migration .
2. Prepare Virtual Machines to Demonstrate vSphere vMotion Migration
3. Perform vSphere vMotion Migrations of Virtual Machines
[23]
Select esx-03a
•Username: root
•Password: VMware123!
M.SC. IT Sem 3 Server Virtualization using VMware 1313300
[25]
ESXi Host Client
The ESXi Host, in this case, esx-03a, can now be directly managed. This can be useful in test/dev environments where a vCenter Server is not present or in
a production environment where the vCenter Server is not reachable.
The initial screen shows high-level details and recent tasks. There are also various power options for the host and an Actions menu for the most common
tasks. Note that the server is currently in Maintenance Mode, which will be discussed in a future lesson. 1. Click on Manage
M.SC. IT Sem 3 Server Virtualization using VMware 1313300
You can find that the most common options set are the date and time for the host. It can be set and synchronized with an NTP server or set manually. In
addition, Autostart settings for the host can be configured here as well.
Ha r dw a r e [ 2 7]
Note: Due to this being a nested virtual environment, seeing items such as "Unknown" under 'Technology' is expected behavior. You can safely ignore this
and move on.
This is where power management policies can be set for the host.
Se r v ic es [ 28 ]
Services like SSH access and the Direct Console UI can be stopped and started from this screen.
M.SC. IT Sem 3 Server Virtualization using VMware 1313300
[29]
Security and Users
On the Security & Users tab, security options such as authentication to Active Directory and Certificates can be set here. There is also the ability to create
additional roles and user accounts for the host itself. This option uses accounts that are local only to the host and not shared with any other hosts or vCenter
Server. vCenter Server is set up to use single sign-on which makes account management much easier. This will be reviewed in the lessons that follow. 1.
Click on Security & users
M.SC. IT Sem 3 Server Virtualization using VMware 1313300
The Monitor section includes Performance Charts, Hardware monitoring, an event log and other useful monitoring information.
1. Click on Monitor
On the Logs tab, a support bundle can be created that includes log files and system information that can be helpful in troubleshooting issues.
[31]
Generate Support Bundle
This operation will automatically download the support file. It will take a couple of minutes.
You may be asked to provide credentials. Use the same information you used to log in:
M.SC. IT Sem 3 Server Virtualization using VMware 1313300
•Username: root
•Password: VMware123!
1. Click on Log in
[32]
Save the Support Bundle
2.A pop-up window will appear with the downloaded support file. Review file if needed.
[33]
1. In addition to managing and monitoring the host, Virtual Machines can be created, Storage and Networking can be
configured at the host level.
Since these features will be covered throughout the lab and the actions performed are identical, just at the vCenter Server level, we will not be reviewing
them here.
The ESXi Host Client can be very useful in situations where a vCenter Server is not present to manage the host. However, when a vCenter Server is
present, it is the preferred option and provides better tools to manage your infrastructure as a whole.
M.SC. IT Sem 3 Server Virtualization using VMware 1313300
[44]
Launch Firefox
If you are not already in Firefox, click on Firefox on your desktop. If you are already in Firefox, open a new tab.
[45]
Select vSphere Client
1. Under the Region A Bookmark's Folder, click the vSphere Web Client bookmark.
M.SC. IT Sem 3 Server Virtualization using VMware
[46]
Login to vCenter
If your 'LOGIN' button is grey or cannot be click, you can click on the username and pasword fields, this should enable your 'LOGIN' button.
[47]
vCenter Inventory
By default, you are brought to a view that shows the Hosts and Clusters attached to vCenter. Get a more complete look by viewing the Global Inventory
Lists.
M.SC. IT Sem 3 Server Virtualization using VMware
[48]
1. Click on the Menu hamburger icon on the top left and select Global Inventory Lists.
Clicking Global Inventory Lists will take you to the inventory page where you find all the objects associated with vCenter Server systems such as data
centers, hosts, clusters, networking, storage, and virtual machines.
1. Click the "Virtual Machines" inventory item. By selecting this inventory item, you are presented with a list of the VMs
[49]
Virtual Machine Summary
M.SC. IT Sem 3 Server Virtualization using VMware
[50]
1. You will land in the "Summary" Tab for that virtual machine. In this page, you are able to see all the details regarding the virtual machine.
1. Review the VM Hardware details for the windows10 virtual machine. Note that there is currently only one network adapter.
2.Click on Edit so a second network adapter can be added to the virtual machine. You may need to scroll down to see this option.
M.SC. IT Sem 3 Server Virtualization using VMware
[51]
Add a Second Network Adapter
[52]
1. In the Edit settings window, click the Add New Device drop-down menu.
2.Select Network Adapter from the list. You may need to scroll down to see the option.
M.SC. IT Sem 3 Server Virtualization using VMware
[53]
Configure the Second Network Card
1. Click the arrow next to the New Network to expand and view its settings. Notice that the MAC address is blank at this point. A new MAC address
will be generated once this NIC is added or we are able to specify (with some rules) our own MAC address.
M.SC. IT Sem 3 Server Virtualization using VMware
[54]
2.Click on OK to add the device to the VM. When you select OK a new task will be created.
[54]
1. Click on on the Arrow to view the Recent Tasks to watch the task's progress.
Review the "Recent Tasks" list. Once the task is complete, a second Network Adapter should be shown in the "VM Hardware" section. Note the networks
are in a disconnected state because the VM is powered off.
Once you are done viewing the Recent Tasks list, click the down-arrows to minimize it.
M.SC. IT Sem 3 Server Virtualization using VMware
In the next steps, we will create a virtual machine and then, install an operating system.
[57]
[56]
Select and Expand Datacenter
1. Expand RegionA01 Datacenter if you cannot see the virtual machines under it can be seen.
M.SC. IT Sem 3 Server Virtualization using VMware
[59]
Start the New Virtual Machine Wizard
2.Click New Virtual Machine to start the new virtual machine wizard.
This wizard is used to create a new Virtual Machine and place it in the vSphere inventory.
1. Since the Create a new virtual machine wizard is highlighted, just click Next.
M.SC. IT Sem 3 Server Virtualization using VMware
[61]
Name the Virtual Machine
Server Virtualization using VMware
[62]
1. Enter web-serv01 for the name of the new virtual machine.
2.Click Next.
M.SC. IT Sem 3
M.SC. IT Sem 3 Server Virtualization using VMware
[63]
Because Distributed Resource Scheduler (DRS) is not enabled, you just have to select a host to use for the VM. More details on DRS will be covered
later in this module.
2.Click Next.
Server Virtualization using VMware
[64]
Select Storage
[65]
2.Click Next.
M.SC. IT Sem 3 Server Virtualization using VMware
[66]
Compatibility
In this step, we will be selecting what operating system we will be installing. When we select the operating system, the supported virtual hardware and
recommended configuration is used to create the virtual machine. Keep in mind this does not create a virtual machine with the operating system installed,
but rather creates a virtual machine that is tuned appropriately for the operating system you have selected.
1. For the Guest OS Family, select Linux from the drop-down menu.
[68]
Customize Hardware
The recommended virtual hardware settings are shown as the default. These can be modified if needed.
3.Click Next.
M.SC. IT Sem 3 Server Virtualization using VMware
Note: if you miss choosing "Thin Provision", you will run out of disk space for this lab and your Virtual Machine may not power on. Disk space is limited
in this lab environment.
M.SC. IT Sem 3 Server Virtualization using VMware
[70]
Ready to Complete
The settings for the virtual machine can be verified prior to it being created.
[71]
Newly Created Virtual Machine
[72]
In the next steps, Photon OS will be installed on the virtual machine.
M.SC. IT Sem 3 Server Virtualization using VMware
[73]
Attaching an ISO to a Virtual Machine
M.SC. IT Sem 3 Server Virtualization using VMware
[74]
Server Virtualization using VMware
[75]
M.SC. IT Sem 3
To make it easier to install operating systems on virtual machines, ISO images can be used. These can be kept in the same storage used for virtual
machines. In addition, vCenter offers a Content Library as a repository. Content Libraries can then be synchronized to ensure every location is using the
same versions.
1. To attach an ISO image to the virtual machine we just created, make sure web-serv01 is selected.
M.SC. IT Sem 3 Server Virtualization using VMware
[76]
2.Right-click on web-serv01 and select Edit Settings...
[68]
Content Library ISO File
M.SC. IT Sem 3 Server Virtualization using VMware
1. From the CD/DVD drive 1 drop-down menu, select Content Library ISO File.
Select Photon
2.Click OK.
M.SC. IT Sem 3 Server Virtualization using VMware
[78]
Connect the Drive
Finally, we want to attach or connect the ISO image to the virtual machine.
3.Click OK.
Note: The virtual machine's BIOS is set to boot from CDROM only on first boot. If you miss this step you will need to manually adjust the BIOS to boot
from CDROM just like a physical machine.
M.SC. IT Sem 3 Server Virtualization using VMware
[79]
Power on web-serv01
1. Click the green play button to power on the virtual machine and start the installation.
M.SC. IT Sem 3 Server Virtualization using VMware
[80]
Launch Console
1. To launch the console window, click anywhere in the console window screen. Alternatively, you can click on Launch Remote
Console
Note you also have the option of using the VMware Remote Console (VMRC). This is console is a separate application that needs to be installed on your
local device as opposed to the Web Console which will launch in a new browser tab. The VMRC can be useful in certain situations when you need more
capabilities, like attaching devices or power cycling options.
[81]
M.SC. IT Sem 3 Server Virtualization using VMware
[82]
M.SC. IT Sem 3 Server Virtualization using VMware
1. Run “Sudo apt-get update" command to updates the list of available packages and their
versions stored in the system's package index as shown below:
2. Run “Sudo apt-get install open-vm-tools-desktop -y” command to install VMware Tools.
M.SC. IT Sem 3 Server Virtualization using VMware
1. Run “Sudo apt-get update" command to updates the list of available packages and their
versions stored in the system's package index as shown below:
2. Run “Sudo apt-get install open-vm-tools-desktop -y” command to install VMware Tools.
5. Copy Text/file from main Host machine and try pasting it in VM. You’ll see paste option
will be enabled.
Prac cal No 2 :- Working with vCenter Server Appliance
1. Access your vCenter Server Appliance and Configure Lincenses vCenter Server
1. Mount the ISO on your computer. The VCSA installer is compa ble with Mac, Linux, and
Windows.
5. Read and accept the EULA, and then click Next to con nue.
6. Select the ESXi host on which to install the VCSA as a guest. This must be a host that runs
ESXi 6.5 or later. NVIDIA recommends that the vCenter server (Windows or appliance-
based) run on a separate management cluster from the one designated for VDI workloads.
Enter the IP address or fully qualified domain name (FQDN) of the chosen host, its root
username, and password; then click Next.
7. If your desktop can reach the host, you should see a cer ficate warning as it connects. This
warning is due to the use of a self-signed cer ficate. If you are using a signed cer ficate, you
will not see this warning. Click Yes to con nue.
8. The creden als are validated.
9. When prompted a er a successful connec on, provide a VM name for the vCenter Server 7,
type the passwords in the Set Root password field, and enter the root password again, and
click Next.
10. Select a deployment size appropriate to the number of hosts and virtual machines that
vCenter Server will manage, then click Next.
11. Select the datastore where the VCSA will be deployed, select thin provisioning if required,
and click Next.
12. The installer displays the Configure network se ngs. Before you configure these se
ngs, choose an appropriate sta c IP address, and enter it into local DNS (e.g., on the
Domain Controller). Once you can resolve the address, enter the IP address hostname on
the network se ng page, then scroll down and enter the remaining items. When all desired
se ngs are complete, select Next.
13. Review the se ngs before star ng the vCenter Server deployment and click Finish to start
the installa on.
14. The vCenter Server will start deploying on the specified target ESXi host. Installa on
progress can be viewed on the screen.
15. With the VCSA now deployed, move on to stage 2 by clicking Con nue.
16. Select Next to proceed with Stage 2, se ng up the vCenter Server.
17. Configure the NTP server by selec ng the Time synchroniza on mode and Enabling the
SSH access, then click Next.
18. Enter a unique SSO domain name, configure a password for the SSO administrator, click
Next.
Note
The default SSO domain name is vSphere.local. The SSO domain name should not be the same as
your Ac ve Directory Domain.
19. Select or deselect the customer experience improvement program box and click Next.
20. Review the details on the summary page and click Finish to finalize the setup.
21. The installer displays a warning that you cannot pause or stop the install once you start it.
Click Ok to acknowledge the warning and start the install.
22. When the install process is complete, click Close to exit the installer and en re Stage 2 of
the VCSA setup.
Post Installa on
This sec on describes the post-install and configura on of the vCenter Server.
1. Connect to the vCenter post install using the IP or FQDN of the vCenter. Access vSphere
by selec ng Launch vSphere Client (HTML5).
2. The VMware Single Single-On page displays. Enter the username and password that you
specified during installa on, then click the Login bu on.
5. Click the Menu drop-down, then click Administra on. Select Licenses from the le -hand
menu, then select the Licenses tab. Click Add New Licenses to open the New Licenses
dialog.
6. Enter the vCenter Server Standard license key provided at the vSphere Licensing Portal.
7. Enter a unique name for the license in the License Name field and then click Next.
8. Review your selec ons, then click Finish to close the Enter New License dialog and return
to the VMware vSphere Web Client page.
So, Lets start with installing the Vcenter Single Sign on Server. Click on Run you can see a pop up
window showing the installing services on the le pane.
There are two op ons of installa on process you can choose either a simple install or a custom
install. We go for custom install since we need to know the steps that are processed on installing of
each service.
We mostly had the default values on each step and moved on. Please make sure you given the
master password which you remember the most.
Proceed with the further steps to install the SSO, A er the installa on is done move to the next step
installing Inventory Service.
In the second task we install vcenter inventory services,Inventory service stores vcenter server
applica on and inventory data allowing you to search and access inventory objects across linked
vCenter Server systems.
For the inventory size, I choose the smallest op on available as we won’t be crea ng many virtual
machines at all for this dura on of this lab.
I then entered the password that I defined earlier during the Single Sign-On installa on for the
Administrator account.
VMware vCenter Server allows for the management of mul ple ESX servers and virtual
machines (VMs) from different ESX servers through a single console applica on. Before
installing the Vcenter Server, the applica on configure .Net Framework which i had enabled it
earlier star ng of the lab.
Enter you FQDN details
in the next step Vcenter server must install a database. Once we move from previous to next
step , it asks to select a exist database or a new data source. I choose the op on of installing a
Microso SQL Server 2008 Express instance. The instance we created supports for our available
hosts.
i Just moved on selec ng the default values since it was the first installa on.
Once all the configura on is done we come at the install window.Click on install to begin the
install.
Now the final task installing VSphere update manager. In the update manager it enables
centralised, automated patch and version management for ESXi hosts, virtual machines, and
virtual appliances.
Install update manager by clicking install on the main pop-up window.In this installa on process
we leave the configura on op ons to default and move the process.
For the VMware vCenter Server Informa on, I provided creden als ad le the IP address and HTTP
port as their default values.
Finally we came up near to the end of the project once we finish installing the web client. May be
we don’t need to have a web client service on our vcenter server rather we install the web client on
our windows client machines. I can say two points suppor ng my word. firstly as a security stand
point and second we don’t use much running service of web client on our vcenter server machine.
I just mounted my vcenter.ISO on my windows client and mounted it. Try to install the web client
on it.
3. Add Your ESXi Hosts to the vCenter Server Inventory
2. Select the installer using the arrow keys and press [ENTER] to begin boo ng the ESXi
installer. A compa bility warning is displayed.
3. Press [ENTER] to proceed. The End User License Agreement (EULA) displays.
4. Read the EULA and then press [F11] to accept it and con nue the installa on. The installer
scans the host to locate a suitable installa on drive.
Note
You can install ESXi to a USB drive and then boot and run the system from that USB drive. This
sample installa on shows ESXi being installed on a local hard drive.
7. The installer scans the chosen drive to determine suitability for install
11. Select your desired keyboard layout using the arrow keys and then press [ENTER]. The
Enter a root password window displays.
12. Enter a root password in the Root password field.
Important
To prevent unauthorized access, your selected root password should contain at least eight (8)
characters and consist of a mix of lowercase and capital le ers, digits, and special characters.
13. Confirm the password in the Confirm password field and then press [ENTER] to proceed.
The installer rescans the system.
Important
The installer will repar on the selected disk. All data on the selected disk will be destroyed.
16. Press [ENTER] to reboot the system. (Make sure your installa on media has been ejected
and your bios set to the boot disk.)
A countdown mer displays when you first boot ESXi. You can wait for the countdown to expire or
press [ENTER] to proceed with boo ng. A series of no fica ons displays during boot, which can
take several minutes to complete. The VMware ESXi screen displays when the boot completes.
2. Enter the root account creden als you created during the installa on process and press
[ENTER]. The System Customiza on screen displays.
3. Scroll down to select Configure Management Network and then press [ENTER]. The
Configure Management Network window appears.
4. Select the Network Adapters window and press [ENTER]. Use the arrow keys to select the
adapter to use as the default management network and press [ENTER]. More than one
management network can be selected for redundancy.
5. Exit the menu with [ESC] and select the IPv4 Configura on window
6. Use the arrow keys to select Set sta c IPv4 address and network configura on and then
enter the IPv4 address, subnet mask, and default gateway in the respec ve fields.
7. Press [ENTER] when finished to apply the new management network se ngs.
8. Navigate to and select the DNS Configura on window. Add the primary and (if available)
secondary DNS server address(es) in the respec ve fields. Set the host name for this ESXi
host in the Hostname field.
9. Press [ENTER] to apply the new DNS se ngs and return to the Configure
Management Network menu..
10. Press [ESC] to exit the Configure Management Network menu. The Confirm
Management Network popup window displays. Press [Y] to confirm your selec on.
11. Select Test Management Network on the main ESXi screen to open the Test Management
Network window.
13. Return to the main ESXi screen when you have completed tes ng, and then select
Troubleshoo ng Op ons. The Troubleshoo ng Mode Op ons window displays.
14. To install the NVIDIA VIB in a later step, you will need to enable the ESXi shell. This can
be accomplished by selec ng Enable ESXi Shell.
15. The window on the right displays the status: ESXi Shell is Disabled. Press [ENTER] to
toggle Enable ESXi Shell on.
16. The window on the right displays the status: SSH is Disabled. Enable SSH by selec ng
Enable SSH and press [ENTER] to toggle this op on on.
Se ng the NTP Service on a Host
1. Click a host object in the menu on the le , click Configure > System > Time Configura on
> Network Time Protocol > Edit.
2. Check the Enable box and enter a valid me server and click OK.
Note
3. Set the NTP Service Startup Policy to Start and Stop with host and click okay.
Adding a Host
1. Select the Home icon (house) on the VMware vSphere Web Client page.
2. Select Hosts and Clusters.
4. Enter a name for the datacenter in the Datacenter Name field and click Ok.
5. The new datacenter is visible in the le panel of the vSphere Web Client. Click the ac ons
drop-down and select Add a Host.
6. Enter the hostname or IP address of the vSphere host and click Next.
7. Enter the administrator account creden als in the Username and Password fields and click
Next.
8. Click Yes to replace the host cer ficate.
9. The Host summary dialog displays. Review the se ngs and click Next to proceed.
10. The Assign license dialog displays. Confirm the license selec on and click Next.
11. The Lockdown mode dialog displays. Accept the default se ng (Disabled) and click
Next.
12. The VM loca on dialog displays. Select a cluster or accept the default op on and click Next
to con nue.
13. The Ready to Complete dialog displays. Click Finish to complete adding the new host.
14. The new host is now visible in the le panel when you click the datacenter name.
A folder can contain other folders, or a group of objects of the same type. For example, a single
folder can contain virtual machines and another folder containing virtual machines, but it cannot
contain hosts and a folder containing virtual machines.
You can create these types of folders: Host and Cluster folders, Network folders, Storage folders,
and VM and Template folders.
Lets see how to create a Host folder. Before crea ng a host folder make sure you have a valid host
connected to your data center. For this Login into Vsphere web client url from your client device.
Right Click on the Datastore that you created earlier and click on Add Host.
its ask for authen ca on provide the username and password. Give root as username and enter
your master password.
once the authen ca on is approved you are followed with next steps host summary and licensing
and vm loca on give defaults and click on finish. Once the host is ready you can see it on your
datacenter droplist as below.
Yup! host is ready now we gonna create a folder and add the host to that folder. Its so simple Right
Click on DataCenter> and then All Vcenter Ac ons>Create a Host and Clusters folder.
give a name
to the folder once the folder is been created drag the host into the folder and click yes to
confirm.Thus a host folder is created. Now move to task-2 Task-2 : Crea ng two virtual
machine folders this task is also three simple step process. just goto
Home>vCenter>VMs and Templates Right Click on DataCenter> and then All Vcenter Ac
ons>New VM and Templates Folder type one folder name as Lab VM’s and other one as
Templates if you had done the steps correctly you can see as the below screen.
1. Open your web browser. Enter the IP address of the ESXi host which you configured in the
procedure, Configuring vSphere Hypervisor. (h p://<ESXi host ip address>) and press Enter. This
accesses the web page to download the vSphere Client to your Windows machine. For example, h
p://172.30.58.164
A warning displays followed by a prompt allowing you to accept or reject the cer ficate.
4. Navigate to the loca on on your PC where you downloaded the vSphere Client.
5. Double-click the file to begin the installa on. The file proceeds to extract the applica on
files and con nues the installa on process. The following screen displays.
6. Click Next. Select I agree to the terms in the license agreement and click Next. Con nue the
installa on by following all remaining instruc ons for installing the vSphere Client.
When the installa on is complete, the following screen displays.
7. Click Finish to complete the installa on. The VMware vSphere Client icon appears on your
PC desktop.
8. Double-click the VMware vSphere Client icon. The following screen displays.
9. In the IP address / Name text box, enter the IP address or the domain name of the ESXi
host. For example:
10. In the User name text box, enter the user name assigned to you by the system administrator
of the ESXi host. For example:
11. In the Password text box, enter the password assigned to you by the system administrator
of the ESXi host. For example:
Password: jre453i
13. Place a check mark in the box that indicates: Install this cer ficate and do not display any
security warnings for <ip_address>. The IP address is the address of the ESXi host.
Note:
h ps://www.vmware.com/account/login.do
2. Register for a VMware account by clicking Register. Or if already registered, enter your
email address or VMware customer number, and password, and click Sign In.
VMware sends the following message to the email address you specified during registra on:
Thank you for crea ng a VMware account. To complete the registra on process, please click the bu
on below.
3. Open your email message from VMware and click the Ac vate Now bu on.
4. In the Password text box, enter the password you specified when registering with VMware
and click Con nue.
6. In the box, On how many physical servers do you plan to install VMware vSphere
Hypervisor?, enter the number of servers on which you are installing the VMware vSphere
Hypervisor.
7. Place a check mark in the box, I agree to the terms and condi ons outlined in the VMware
vSphere Hypervisor End User License Agreement. and click Register.
VMware sends you an email message for accessing your VMware ESXi License.
8. Open your email message from VMware and click Access Now.
9. Copy the VMware vSphere Hypervisor license key string. Applying the
1. Click OK to close the VMware Evalua on No ce window that displayed in Step 14. The
following window displays. The ESXi Host IP displays in the le column.
2. Click the Configura on tab.
3. In the le column, under the So ware category, click Licensed Features.
4. In the upper right corner of the window, click Edit. The following window displays.
5. Click the radio bu on Assign a new license to this host. and click Enter Key. A pop-up
displays allowing you to enter the license key string.
6. In the New License Key text box, paste the license key string you copied from Step 24. Or
enter the license key string manually.
on using VMware
M.SC. IT Sem 3 Server Virtualiza
To integrate a vCenter Server Appliance (VCSA) with Microso Ac ve Directory as the iden ty source
simplifies and improves the security of access management. By joining vCenter to an AD domain,
VMware vSphere administrators can use the same iden ty source used to grant access to file servers and
other resources on the network to grant access to vSphere objects. Read on to learn the steps for how to
join vCenter to domain.
Complete data protec on for VMware vSphere VMs and instant recovery op ons. Secure backup targets
onsite, offsite and in the cloud. An -ransomware features.
Ac ve Directory is a common standard for the centralized authen ca on of users in many organiza ons.
Ac ve Directory can also be used to authen cate VMware ESXi and VMware vCenter users.
Then we can assign the needed vSphere permissions for authen cated Ac ve Directory domain users.
Requirements
• An Ac ve Directory domain controller must be configured. The domain controller must be writable
(and not just in read-only mode).
• The DNS suffix used for a fully qualified domain name (FQDN) of the vCenter Server must be
correct.
• The DNS se ngs of VCSA to communicate with the domain controller must be correct.
• vCenter Server Appliance (VCSA) must resolve the DNS name of the Ac ve Directory domain
controller to an IP address.
Ac ve Directory domain user. However, you can use the Use Windows session authen ca
on op on when you integrate vCenter with Ac ve Directory.
2. Once you are logged in to the Web Client as the SSO administrator, click the menu icon in the
top le corner. Click Administra on in the menu that opens.
M.SC. IT Sem 3 Server Virtualiza on using VMware
3. Click Configura on on the Administra on page in the Single Sign On sec on. Select the Iden ty
Provider tab, click Ac ve Directory Domain, and click JOIN AD to join vCenter to domain.
4. This will bring up a dialog box to type in the Domain, Organiza onal unit, Username, and
Password.
o Enter the Ac ve Directory domain name, for example, domain1.net. Note that the
name of your exis ng local SSO domain (vsphere.local in our case) and the Ac ve
Directory domain (domain1.net in our case) must be different. If you use the same AD
domain name, you get an error and won’t be able to join the domain and integrate
vCenter with Ac ve Directory.
o Se ng an organiza on unit can be useful for those who are familiar with LDAP. If
the Organiza on unit field is le empty, then a computer account in AD is created in the
default loca on, which is a Computers container. You can always move a computer
object to the needed organiza on unit on your Ac ve Directory domain controller. An
example of how to fill the Organiza on Unit field:
OU=Unit1,DC=domain1,DC=net
o Enter the username of the Ac ve Directory domain administrator and the password.
Our domain administrator is [email protected]. However, you can create a
dedicated user (for example, vmwareadmin) on the domain controller and add this
user to the appropriate domain administrators group.
A er comple ng the dialog box, click Join and you will be prompted to reboot your vCenter appliance.
M.SC. IT Sem 3 Server Virtualiza on using VMware
5. To reboot vCenter server from the interface of VMware vSphere Client, go to Administra on >
System Configura on, select your vCenter node, and click Reboot node.
Alterna vely, you can log in to VMware Host Client of the ESXi host on which the vCenter Server
Appliance VM is running and reboot the VCSA VM. Another solu on is to use the Direct Console user
interface (DCUI) on the VCSA and use the Reboot op on there.
7. You can also ensure that your vCenter machine has joined the domain in Windows Server ac
ng as a domain controller. For this purpose, open Ac ve Directory Users and Computers, select
your domain, and click Computers. You can see that our vcenter7 machine is a member of our
Ac ve Directory domain in the screenshot below.
A er the vCenter Server Appliance (VCSA) has been joined to the domain and rebooted, we are now
ready to add our Ac ve Directory iden ty source:
M.SC. IT Sem 3 Server Virtualiza on using VMware
1. Go back to Administra on and click Configura on under the Single Sign-On menu. Click the
Iden ty Sources in the Iden ty Provider tab and then click the ADD bu on to add an iden ty source.
2. We select the Ac ve Directory (Integrated Windows Authen ca on) op on. Now that we have
joined our vCenter to the domain, the Domain name field is automa cally populated with our domain
name. We can leave the Use machine account as the default op on here. Finally, complete the
configura on of the iden ty source and click
M.SC. IT Sem 3 Server Virtualiza on using VMware
3. Now, under the iden ty source, we can see our domain. You can click Set as default to use this
Ac ve Directory domain by default.
Then you can create Roles in vCenter and assign privileges to those roles and then a ach a role to an
Ac ve Directory user.
Conclusion
Having a centralized system for user authen ca on in your environment and using Ac ve Directory
for vSphere user authen ca on is useful in many situa ons. Make sure to back up your Ac ve
Directory domain controller and vCenter Server appliance regularly to avoid down me and issues
caused by the inability to authen cate users and manage the infrastructure. NAKIVO Backup &
Replica on is a complete data protec on solu on for VMware vSphere environments. Use the solu on
to back up your VMs and applica ons like Microso Ac ve Directory.
M.SC. IT Sem 3 Server Virtualiza on using VMware
Prac cal No 4
1. how to view the current standard switch Configura on
3. A ach your Virtual Machine to a new Virtual Machine port Group Task-1: View
In the login page provide the user creden als and login on the dashboard click on your ESXi
host> you will be moved to ESXi dashboard page showing the host informa on like health,
processor etc…
in
the host dashboard click on Manage>Networking>Virtual swithces.
The default virtual switch is named as vSwitch0 which is connected to the physical adapted
vmnic0.vswitch0 contains a VMkernel port named Management Network and a virtual
machine port group named VM Network. A virtual machine is connected to VM Network.
Task-2: Crea ng a Standard Switch to create a standard switch goto the same path as above
in the Task-1. Click on globe shaped icon with green plus sign or the first icon on the le
and give the following configura on details
Once the switch is created you can see the switch details in the
Hosts>Manage>Networking>VirtualSwitches
Select the virtual machine you want to a ach to the new network
In the Virtual Hardware tab, click on the Add New Device bu on.
Prac cal No 5 Accessing
iSCSI Storage
In this lab, I was required to do the following tasks:
• connect the iSCSI software adapter to storage validate an existing ESXi host's
iSCSI configuration in VMware, follow these steps: Using the vSphere Web Client
5. Click on Storage.
10. Verify the iSCSI LUNs (Logical Unit Numbers) are visible and accessible.
In the previous post I just created two Standard switches. And now I added VMKernal port to
newly created Standard switches by navigating to vCenter -> Hosts and Clusters’, selected my
first ESXi host, clicked the ‘Manage’ tab, clicked the ‘Networking’ tab, clicked on ‘Virtual
switches’, and finally, selected ‘vSwitch1’.
I continued the execution by clicking next. In the next step i choose Vswitch1 switch I did not
change anything here after and just stuck with the defaults.
For the network label, I entered in IP Storage’. I left the remaining settings at their defaults.
Click on next to give the IPv4 settings. In the IPv4, I had given an IP address based on my
network diagram .This IP may use as a switch two connect virtual machines that i am gonna
create So, finally after creation of VMkernal adapter I observe the following switches port
details.
Pre-work before configuring the ISCSI Adapter: Before making a connection to my vsim and
configuring the ISCSI software adapter in this task. I need to enable my ISCSI services on my
VSIM. For this I had given an ISCSI license key and enabled the services using the command
prompt command ISCSI START.
Configuring my VSIM is done through on NetApp Manager. I just logged into one of my
client system opened the NetApp manager and given a NFS and ISCSI license file in it.
and for starting the ISCSI services i just opened my VSIM VM and entered the command.
ISCSI START
This made me an opportunity to create some luns in my VSIM it will be very useful in future
tasks. Creating a LUN is easy through NetApp Manager. I opened NetApp manager session
and navigated to the LUNS and created two luns namely LUN1 and LUN2. I can’t add the
initiator group at this time because I don’t have the initiator id.
I just logged into my NetApp manager and clicked on LUNS. As you can able to see they are
already build luns LUN1 and LUN2. I am gonna create a new lun named LUN3 in this
session.
I specified the type as Windows 2008 and later and given a size of 5 GB.
After checking that, I navigated to the ‘Network Port Binding’ tab and clicked on the little
green ‘+’ symbol to add a new binding. I selected the VMkernel kernel adapter that I created
earlier and clicked ‘OK’.
I then navigated to the ‘Targets’ tab, ensured ‘Dynamic Discovery’ was selected, and clicked
‘Add’. This prompted me to add in the IP address for my vSIM. I added in the IP of the e0b
NIC that I created earlier on and left the port value as 3260.
After a brief delay, the target appeared in the targets list as seen below:
To test that everything is working as it should, I clicked on the ‘Rescan adapter’ icon and
waited for the scan to finish. I then selected the iSCSI adapter and navigated to the ‘Paths’
tab, but unfortunately, no information was displayed. Its because my initiator is not attached
to my created luns. To do so i copied my EXSi ISCSI adapter name to the dashboard and
pasted it to my initiator group.
Select the ESXi host where you want to connect the iSCSI so ware adapter to storage. Click on
the Configure tab.
Click on Storage.
Select Storage Adapters.
Click on the iSCSI so ware adapter you created earlier.
Click on the Targets tab.
Click on the Add Target bu on.
Enter the iSCSI target IP address and port.
Prac cal No 6
Managing VMWARE Vsphere VMFS
▪ Create a VMFS Datastore
▪ Expand a VMFS Datastore to Consume Unused Space on a LUN
▪ Remove a VMFS Datastore
▪ Extend a VMFS Datastore
▪ create a second shared VMFS datastore using iSCSI in VMware
Changing the Name of a VMFS Datastore
Once you added your host devices to your vCenter you can able to see the datastore’s list in the
storage sec on. I navigated to ‘vCenter -> Datastores’, right-clicked on the datastore named
‘datastore1’, and selected to rename it.
Once i renamed my two hosts datastore’s i rechecked whether they have been changed or not. I
found they were renamed successfully.
Reviewing the Shared Storage Configura on
I carried out this task by naviga ng to ‘vCenter -> Hosts and Clusters -> Lab Servers ->
172.16.61.44 -> Manage -> Storage’, clicking on the iSCSI adapter, and clicking on the ‘Paths’
tab. From here I could see informa on about the LUNs that I had mapped previously under the
‘Adapter Details’ sec on.
I then repeated these steps to add another datastore using my other LUN. I changed only the
name of the datastore, the LUN to use, and I did not make any changes to the par on.
Removing a VMFS Datastore
I started this task by right-clicking on the second datastore that I created (PrivateVMFS01) and
selec ng ‘All vCenter Ac ons -> Delete Datastore’.
This opened a prompt to confirm the dele on on the datastore. I clicked ‘Yes’.
The datastore was then deleted and no longer shows up in the list of datastores.
I then selected ‘Use all available partitions’ from the drop down list. This should now
take advantage of the spare LUN.
After finishing the review and completing the resizing, I navigated to the ‘Device
Backing’ tab to see if both of the extents were being used.
After finishing the review and completing the resizing, I checked out the information
under the ‘Summary’ tab. The datastore now uses all 2GB available (minus a few
MBs for the reservation).
Select Storage Adapters.
Click OK.
M.SC. IT Sem 3 Server Virtualization using VMware
To create a new aggregate along with a new volume to be used as the NFS datastore. I began by enabling
TLS on my vSIM as I plan to use the NetApp OnCommand System manager to create the aggregate and
volume. My first task is to create an aggregate for this I then navigated to ‘Storage -> Aggregates’ and
created a new aggregate. For the aggregate name I chose ‘aggr1’, for the RAID type I chose RAID-DP, and
I left the enable synchronous mirroring tick box unchecked.
NOTE: Please make sure you added the NFS License and Started the NFS service on DATA ONTAP.
then needed to select the number of disks to assign to the aggregate. I choose 4 as my magic number
because i got total 5 disks and I keep one disk un-partitioned for any fail overs.
After I successfully create my aggr1, in the next phase I need a vol name vol1 to be created which acts as an
M.SC. IT Sem 3 Server Virtualization using VMware
NFS data storage. In order to do this, I navigated to ‘Storage -> Volumes’, clicked on create. This brought
up the Create Volume wizard. For the name I entered ‘vol1’, for the aggregate I selected the newly made
‘aggr1’, for the storage type I selected ‘NAS’ (as this is for NFS access), for the size a specified 5GB, and
finally, I selected to make the volume thin provisioned.
Now its time to configure NFS Datastores. Once I was in, I navigated to ‘vCenter -> Storage -> Related
Objects’ and clicked on the ‘Create a new datastore’ button.
M.SC. IT Sem 3 Server Virtualization using VMware
this will set me to a wizard of configuring the NFS-datastore. In my first window I selected my datacenter
that are available to my network.
For the datastore name, I followed the lab manual naming scheme of ‘NFS-<your-name>’ and entered
‘NFS-Vasamsetty’. For the server, I put in the IP address of the NetApp vSIM on the 192.168.255.1
network. Finally, for the folder path, I entered the path of ‘/vol/vol1’, pointing to the volume that I created
earlier in the post. I chose not to mount the NFS as read-only so that I can actually make changes to it.
As far as accessibility to the datastore goes, I allowed both of my ESXi hosts to access the datastore. After
making sure the values in the review were correct, I finalised the creation.
M.SC. IT Sem 3 Server Virtualization using VMware
Once my storage was successfully created. I can see the storage information and its summary right over on
selecting NFS-VASAMSETTY
Create a Template
NOTE: Before uploading any type of data to your datastore we need to make sure that we had installed
VMware Client Integration Plugin in your browser.
M.SC. IT Sem 3 Server Virtualization using VMware
Pre-requirements: Make sure you uploaded your MicroSoft windows 2003 server ISO in your datastore. I
tried very hard to do so, but after the perfect upload i feel really excited to do my further labs that because
am gonna create a new network inside a builtin network its like a “double virtualisation” its really fantastic.
As you can see I just uploaded my Microsoft 2003 server into my datastore.
Now am ready to install a VM on my host. As discussed in our previous lab ” how to install the guest
operating system” i installed my MS 2k3 and powered it on.
M.SC. IT Sem 3 Server Virtualization using VMware
that’s a successful milestone. Now i had a active windows server 2003 running VM and am gonna make a
template of it and clone it.
As we don’t have specific access to confined folders and I had not yet set up the Vcenter Server Appliances
I can’t copy the files right now.At this stage i can able to find the Sysprep folder and tried to learn what are
files in it.
M.SC. IT Sem 3 Server Virtualization using VMware
then navigated to ‘vCenter -> VM Templates’ and the new template showed up in the list.
I just moved my created VM into VM’s folder that i had created in my previous lab.
got a template creation wizard and finished it and finally, I right-clicked the template and renamed it to
‘Win2k3’ as per the VMware lab instructions.
For this i navigated to the ‘Customization Specification Manager’ tab. I then clicked on the icon for
creating a new specification.
M.SC. IT Sem 3 Server Virtualization using VMware
This opened the ‘New Customization Specification’ wizard. For the Target VM OS type, I selected
Windows. For the name, I entered ‘Test-CustomSpecification’ as per the lab book instructions. I also added
in a description.
For setting the computer name, I selected the ‘Use the virtual machine name’ radio button and continued.
M.SC. IT Sem 3 Server Virtualization using VMware
M.SC. IT Sem 3 Server Virtualization using VMware
Prac cal 8 : Using Template and Clones
• Create Customisa on Specifica ons
• Deploy a Virtual Machine from a Template
• Clone a Virtual Machine that is Powered On
Pre-requirements: Make sure you uploaded your Microso windows 2003 server ISO in your datastore. I tried very hard to do
so, but a er the perfect upload i feel really excited to do my further labs that because am gonna create a new network inside
a built in network its like a “double virtualisa on” its really fantas c. As you can see I just uploaded my Microso 2003 server
into my datastore.
Crea ng a Template
I began this task by logging into my vCenter Server via the Web Client and
powering off my Windows Server 2003 virtual machine. Once that was done, I
right-clicked my Windows Server 2003 virtual machine and selected ‘All vCenter
Ac ons -> Convert to Template…’ from the menu. This opened up the template
wizard.
I then navigated to ‘vCenter -> VM Templates’ and the new template showed up
in the list.
I got a template crea on wizard and nished it and nally, I right-clicked the
template and renamed it to ‘Win2k3’ as per the VMware lab instruc ons.
This opened the ‘New Customiza on Speci ca on’ wizard. For the Target VM
OS type, I selected Windows. For the name, I entered ‘Test-CustomSpeci ca on’
as per the lab book instruc ons. I also added in a descrip on.
For se ng the computer name, I selected the ‘Use the virtual machine name’
radio bu on and con nued.
I then entered in my product key for the virtual machine’s opera ng system and le
all of the other elds as their default values.
M.SC. IT Sem 3 Server Virtualization using VMware
For the next four menus I le the default values and clicked ‘Next’.
M.SC. IT Sem 3 Server Virtualization using VMware
For this task i navigated to Vcenter>Host and Clusters selected my second esxi host. From there I right clicked on
my HotClone01-1 virtual machine and selected Edit Se 몭 ings . We will get a window pop-up showing Edit se
몭 ings menu. I changed my hard disk size from 5 GB to 6 GB. My Lab instructions values are different but
ultimately we need to change the hard disk size.
M.SC. IT Sem 3 Server Virtualization using VMware
Unfortunately i can’t see any increase in size on my virtual machine hard disk size. The total hard disk size in my
windows server is still 5 GB.
M.SC. IT Sem 3 Server Virtualization using VMware
In order to expand the drive to accommodate the extra gigabyte that I defined, I needed to download ‘extpart’.
This is because there are no native applications on Windows Server 2003 that allow for the extension of partitions.
For this we need to open a internet connection from your virtual machine goto your Internet Explorer and
downloaded ‘extpart’ from: h 몭 p://download.dell.com/app/ExtPart.exe (h
몭 p://download.dell.com/app/ExtPart.exe) .
External Work: I tried hard for this but i failed to create an internet connection. In the second try i downloaded the
respective files on my local browser,grouped the files into an ISO-1 and copied the ISO-1 into another folder and
created another ISO-2 file and I mounted to my windows client(to tallos network) which made me available to
copy ISO-1 files in my windows client VM.
In my client-OS i copied ISO-1 files to desktop and opened my FQDN:vcenter.vasamse 몭 y.local network and
mounted the ISO-1 file. From this task i can able to view my necessary files on my created VM.
So, now lets come back to our post again. As in this post finally i copied ExtPart.exe file on my Win2003 server
and runned the exe, entered in “C:” as the drive to change, and entered “1024” as the amount (in MB) to extend
the drive by. YUP i can see the hard disk size change
M.SC. IT Sem 3 Server Virtualization using VMware
Previously it showed 4.98 GB total size whereas now it shows 5.98 GB total size.
To start this task, I shut down my Hot-Clone01 virtual machine, switched back to the vSphere Web Client,
rightclicked the Hot-Clone01 virtual machine and selected ‘Edit Se 몭 ings…’.
From here I changed the memory amount to 768 MB. My lab instructions says that to increase the value but
values are different.
M.SC. IT Sem 3 Server Virtualization using VMware
After making the change, I clicked on the Hot-Clone01 virtual machine once again and then navigated to the
‘Summary’ tab. From here I confirmed that the memory had increased in size.
To start this task, I right-clicked my ‘Jamie01-2’ virtual machine and selected ‘Edit Se 몭 ings…’. From the
‘New device’ area, I selected RDM Disk and clicked Add.
M.SC. IT Sem 3 Server Virtualization using VMware
I just tried to add Raw Disk and found no LUN’s available at that time. This is because I just skipped a step in the
previous lab to enable Promiscuous Mode or Forged Transmits on all of my vSwitches, So i just done it before
this step and it went good I can see the new LUN now when i click on add.
M.SC. IT Sem 3 Server Virtualization using VMware
Successfully a raw disk is added to my virtual machine . I just logged into my VM and to see that whether the disk
is initialized if not am gonna initialize it. To initialize goto Computer Management>Disk Management>Run the
wizard that appears,I could see that the disk showed up as ‘Disk 1’.
M.SC. IT Sem 3 Server Virtualization using VMware
In the next step i clicked on my selected VM to check the hard drive details and noted which datastore is on use
and found that it was on my first esxi datastore.I then shut down the virtual machine and navigated to ‘Home ->
Storage’ where I right-clicked my Local-ESXi01 datastore and selected ‘Browse
Files’.
From there i had gone to my virtual machine vasamse 몭 y01-2 and right clicked on vasamse 몭 y01-2 and
clicked on inflate. Simillary i did the same process for the another virtual machine virrtual machine02-1
M.SC. IT Sem 3 Server Virtualization using VMware
After completing the inflation for the new hard drive, I navigated to ‘Home -> vCenter -> Hosts and
Clusters -> Lab Servers -> <TheIPOfMyFirstESXiHost>’, clicked the Related Objects tab, clicked on the
Virtual Machines tab, and powered on my ‘vasamse 몭 y02-2’ host. I paid particular a 몭 ention to the ‘ Used
M.SC. IT Sem 3 Server Virtualization using VMware
Space’ and Provisioned Space’ columns and found that due to the inflation, all of the available disk space was
now being used.
Blog at WordPress.com.
M.SC. IT Sem 3 Server Virtualiza on using VMware
For migra ng virtual machine files with vsphere storage vMo on. I navigated vasamse y01-2 virtual
machine and right clicked and selected migrate. Before that i noted down in which datastore my
vm exits its on GB-ESXi01
I then selected the ‘Change Datastore’ radio bu on (although I didn’t really have a choice).
M.SC. IT Sem 3 Server Virtualiza on using VMware
According to my lab manual i need to change the datastore from previous datastore to the shared
datastore. Since my disk space’s of datastores is not sufficient i created a new datastore named Shared
Datastore with disk space 20 gb and ini ated my change of datastore to the share datastore.
A er making my selec ons, I reviewed the se ngs and confirmed the migra on.
M.SC. IT Sem 3 Server Virtualiza on using VMware
In this image I found that I unable to see the related objects. but in the recent tasks you can see my reloca
on done successful.
Crea ng a Virtual Switch and a VMkernel Port Group for vSphere vMo on Migra on
I think i had done all the tasks for this in my lab 8 and lab 9
M.SC. IT Sem 3 Server Virtualiza on using VMware
I did have to change one se ng however. I opened up the vSphere Client, logged in to my first
ESXi host, navigated to ‘Networking -> Proper es…(for my vSwitch2) -> Selected the VMkernel
> Edit…’ and made sure the vMo on ck box was cked.
To start this task, I navigated to ‘Home -> vCenter -> Hosts and Clusters’, selected each of my
ESXi hosts, and reviewed that their CPUs were compa ble under the ‘Summary’ tab. I assume that
they are both compa ble as I didn’t see anything to say that they weren’t. ESXi host 1’s Processor
Type informa on:
I then switched to the ‘Manage -> Networking’ tab and checked to see that a vSphere vMo on port
group existed for vSwitch2 as well as that the port was a VMkernel port and make sure the physical
adapter has been set correctly ,defined as 1000 and full.
M.SC. IT Sem 3 Server Virtualiza on using VMware
I did the same thing and entered the same configura on on my second ESXi host.
M.SC. IT Sem 3 Server Virtualiza on using VMware
I then navigated to ‘Home -> vCenter -> Storage’, selected the ‘SharedDatastore’ datastore, navigated
to the ‘Manage -> Se ngs -> Connec vity and Mul pathing’ tab, and ensured that both of my ESXi
hosts were displayed in the table.
Verify that your Virtual Machines meet the vSphere vmo on requirements
Vcenter>Hosts and Clusters>vasamse y01-1 VM and right clicked and selected Edit se ngs. In
the Edit se ngs tab i make sure that i unchecked the CD/DVD drive and Network Adapter 1 as these
are the pre-reques es that are need to be done.
M.SC. IT Sem 3 Server Virtualiza on using VMware
As they are no addi onal hard disk a ached to my VM. Next,I verified that the CPU affinity was not
set. There was no value under Scheduling Affinity so that was all good.
M.SC. IT Sem 3 Server Virtualiza on using VMware
A er comple ng these changes, I repeated the process for my other virtual machines. I also deleted the
second hard drive from my ‘vasamse y02-1 virtual machine; the one that was used along with
extpart.exe.
In this task i performed all the ac ons on my second host. From there, i selected my vasamse y02-
1 . To start the process firstly I disconnected my previous portgroup VMNetwork to and
connected my new NIC PoDv-vMo on
M.SC. IT Sem 3 Server Virtualiza on using VMware
I then needed to change the network se ngs for the virtual machine, so I changed them as follows
(as per my network diagram):
Once my configura on is done. I tried few command prompt func ons such as ipconfig, ping a er
that i entered the command
M.SC. IT Sem 3 Server Virtualiza on using VMware
ping -t 192.168.255.1 in order to get con nuously ping the virtual gateway. this gives me an overview and
helps to check the dropping of packets during the vMo on.
at first i got many errors while pinging, some mes it showed me no packets has sent and received and a er
some troubleshoot i got request me out as an error.Finally i figured out what’s the problem its because I am
confused in providing IP addresses to the virtual switches .
This me i make sure to assign the right IP’s and finally the ping was successful.
on using VMware
M.SC. IT Sem 3 Server Virtualiza
on using VMware
M.SC. IT Sem 3 Server Virtualiza on using VMware
I then returned to the vSphere Web Client, right-clicked the ‘vasamse y01-2’ virtual machine, and
selected ‘Migrate…’ from the menu. I was the presented with the Migrate Wizard. I selected the Change
Host radio bu on and clicked next.
M.SC. IT Sem 3 Server Virtualiza
I got many errors while changing the host because it always show me an error sta ng that Failed
to extend the Swap File . This states that my host doesn’t have the sufficient memory to make
an migra on.
on using VMware
M.SC. IT Sem 3 Server Virtualiza on using VMware
So to solve this error i created a shared datastore and make sure that the two host can access the
datastore and con nued my task instruc ons and this me no compa bility issues i had selected the shared
datastore and taken a review and observe my VM has been migrated successfully
M.SC. IT Sem 3 Server Virtualiza on using VMware
M.SC. IT Sem 3 Server Virtualiza on using VMware
VMware provides the vMo on feature for performing VM migra on between hosts and datastores.
Storage vMo on is used when a VM migrates from one storage to another. vMo on allows you to
migrate VMs even if the VMs are running. You can test this great enterprise-level feature in your
own ESXi home lab. Try to ping your nested Linux VM during the migra on process to check
that there is no down me.
Right-click the VM running on the first ESXi host (ESXi01 – 192.168.101.101) and click Migrate in
the Ac ons menu.
1. Select a migra on type. At this step, you can select one of the three op ons:
o Change storage only. Select this op on if you want to remove the VM from one
directly a ached datastore to another. Both directly a ached datastores are connected
to the same ESXi host in this case.
o Change both compute resource and storage. Select this op on if you want to
migrate a VM from one host to another. Thus, both hosts may use different
datastores.
M.SC. IT Sem 3 Server Virtualiza on using VMware
o Cross vCenter Server export. Use to migrate VMs to a vCenter Server that is a
member of another SSO domain.
Server Virtualiza on using VMware
M.SC. IT Sem 3
The third op on is suitable in the case reproduced in the current VMware home lab. Both ESXi hosts have
their own 40-GB datastores. The running VM will be migrated from one host to another
(ESXi01 > ESXi02) and from one 40-GB datastore to another (datastore40 > datastore40-2).
1. Select a compute resource. This op on allows you to define an ESXi host, as well as which
CPU and memory resources will be used to run a VM. Select vCenter8 >
Datacenter01 > 192.168.101.102 (the IP address of ESXi02, which is the second host in this VMware
test environment).
M.SC. IT Sem 3
M.SC. IT Sem 3 Server Virtualiza on using VMware
2. Select storage. At this stage, you should select the des na on storage for the virtual machine migra on.
Select the virtual disk format: the same as the source (thin provisioning in this case). Select the
datastore (datastore40-2 in our example).
3. Select networks. Select des na on networks for the virtual machine migra on. VM Network is selected
for this purpose in our example.
4. Select vMo on priority. You can set vMo on to high priority (recommended) or normal priority. Set to
high priority.
5. Ready to complete. Check your VM migra on parameters and hit Finish to start the migra on.
Wait un l the VM migra on process is completed. You can open the Recent Tasks bar at the bo
om of the VMware vSphere Client web interface to check the task’s progress. A er the VM migra
on task is completed successfully, your VM will begin running on the second ESXi host (see the
screenshot below).
You can see a preview of the Lubuntu VM desktop where the console was opened in order to check
the network and install VMware Tools before migra on. The virtual machine’s running state is
preserved.
Server Virtualiza on using VMware
For this task am gonna use my vasamse y01-2 virtual machine. I right clicked on this virtual
machine clicked on All Vcenter Ac ons and selected Remove from Inventory op ons. Before doing
this i noted down on which datastore my virtual machine exist. My vasamse y01-2 is in GB-ESXi01
datastore.
M.SC. IT Sem 3
M.SC. IT Sem 3 Server Virtualiza on using VMware
Server Virtualiza on using VMware
I clicked yes and seen that my virtual machine is removed from my exis ng host.
I then navigated to ‘Home -> vCenter -> Datastores’, clicked on my ‘GB-ESXi01’ datastore, and
clicked on the ‘Navigate to the datastore file browser’ bu on. That’s a suprise i find vasamse y01-2 s
ll available in the datastore this shows me that if we click on remove from inventory op on it just
removes from the host items. the VM files s ll hold it files in it datastore.
M.SC. IT Sem 3 Server Virtualiza on using VMware
Now i tried to register again the vm to my host items. For this i right clicked on VM and clicked on
Register VM.It made me to start the Guest OS installa on wizard.I con nued the process and finally my
VM is back again.
M.SC. IT Sem 3 Server Virtualiza on using VMware
M.SC. IT Sem 3 Server Virtualiza on using VMware
M.SC. IT Sem 3 Server Virtualiza on using VMware
I then navigated to ‘Home -> vCenter -> Datastores’, selected the ‘SharedDatastore’ datastore on which
the virtual machine resided, and verified that it’s folders/files no longer existed.
Before doing this task i once again mounted IOMeter iso’s to my windows server 2003 and copied
the IOMETER.exe and cpubusy.vib file on the desktop.
M.SC. IT Sem 3 Server Virtualiza on using VMware
I then deleted iometer as per the lab manual instruc ons, switched back to the vSphere Web Client,
right-clicked my ‘vasamse y02-1’ virtual machine, and selected ‘Take Snapshot…’ from the list. This
opened the snapshot wizard.
on using VMware
M.SC. IT Sem 3 Server Virtualiza
I then deleted the cpubusy.vbs file and created another snapshot of the virtual machine with the following
se ngs:
M.SC. IT Sem 3 Server Virtualiza on using VMware
I then copied the cpubusy.vbs file back from my ‘Downloads’ folder to the desktop and created
another snapshot with the following se ngs. Note that I have le the ‘Snapshot the virtual machine’s
memory’ ck box cked this me.
on using VMware
A er the third snapshot had been created, I right-clicked the ‘vasamse y01-2’ virtual machine and selected
‘Manage Snapshots…’.
This opened up the snapshot manager where I could see the three snapshots that I had created.
M.SC. IT Sem 3 Server Virtualiza on using VMware
Rever ng to a Snapshot
For this task i re-opened Snapchat Manager by selce ng on my vasamse y02-1 VM and selected
without IOmeter and CPUbusy.vib. and clicked the ‘Revert’ bu on in order to revert to that snapshot.
I see the task accomplished in the recent tasks menu.This states that my VM is reverted back to the me
in which we deleted the IOmeter and cpubusy.vib files
M.SC. IT Sem 3 Server Virtualiza
on using VMware
M.SC. IT Sem 3 Server Virtualiza on using VMware
A er that, I returned to the snapshot manager for the ‘vasanse y02-1’ virtual machine and no ced
that the ‘You are here’ indicator had shi ed to below the ‘Without iometer and cpubusy’ snapshot.
on using VMware
I then reverted to the ‘With cpubusy’ snapshot. I no ced that the virtual machine did not get
powered off this me. This was probably because I cked the ‘Snapshot the virtual machine’s
memory’ ck box when I created this snapshot and so it preserved that state that the virtual machine
was in at the me of the snapshot. Finally, I checked to see that only cpubusy.exe had returned to the
desktop.
Dele ng an Individual Snapshot For this task i once again navigated to Snapchat Manager on my
vasamse y02-1 VM no ced my you are here posi on seleceted that and clicked on DELETE we get
an warning pop-up and clicked on yes.
on using VMware
I can see my selected snapshot is deleted successfully. I did the same task once again to delete with
CPUBUSY.vib snapshot and am successful.
M.SC. IT Sem 3 Server Virtualiza on using VMware
.Finally, I checked to see whether cpubusy was s ll on the desktop of the virtual machine and found
that it was.
M.SC. IT Sem 3 Server Virtualiza on using VMware
Overall playing with the snapshots i found that dele ng the snapshots or managing the snapshots will
move the virtual machine from one state to its previous state. But it won’t applies to manage the
current state(you are here) posi on.
To begin this task, I logged into the vSphere Web Client, navigated to ‘Home -> vCenter -> VMs
and Templates’, powered on both of my virtual machines, logged in to both of them, and opened
cpubusy.vbs via the command prompt in order to create some CPU ac vity. It appeared to stabilise at
around three seconds.
M.SC. IT Sem 3 Server Virtualiza on using VMware
As per my task i edited the se ngs of both the virtual machines and changed the “Schedule
Affinity ” to “1”
M.SC. IT Sem 3 Server Virtualiza on using VMware
and again i navigated to my virtual machines consoles and found the no difference in showing the me.
They just appeared a li le difference between the two VM’s. Overall the average me taken
by both the VM’s is exactly 3 seconds.
Crea ng a resource pool is an easy task, I just navigated to the Vcenter->Hosts and Clusters’,
rightclicking my first ESXi host, and selec ng ‘All vCenter Ac ons -> New Resource Pool’. The
‘New Resource Pool’ wizard then opened.
M.SC. IT Sem 3 Server Virtualiza on using VMware
For the name, I entered ‘Fin-Test’. For the CPU Shares level, I selected ‘Low’. I le the remaining se ngs
alone and created the resource pool.
M.SC. IT Sem 3 Server Virtualiza on using VMware
Similarly i added one more resource pool For the name, I entered ‘Fin-Pod’. For the CPU Shares level, I
selected ‘High’. I le the remaining se ngs alone and created the resource pool.
I then selected the ‘Fin-Prod’ resource pool and noted it had an available CPU shares amount of 8,000.
to
check the resource pool func onality i moved both VM’s to each resource pool opened the consoles
and run the cpubusy.vib file and checked the average me taken by both of the vm’s
M.SC. IT Sem 3 Server Virtualiza on using VMware
The ‘vasamse y02-1’ virtual machine in the resource pool with 8,000 shares consistently achieved
around two seconds. where as the ‘vasamse y02-2’ virtual machine in the resource pool with only
2,000 shares makes many changes like it is altering its me and finally sets around seven seconds.
M.SC. IT Sem 3 Server Virtualiza on using VMware
I then changed the CPU shares of the ‘Fin-Test’ resource pool from low to normal…
M.SC. IT Sem 3 Server Virtualiza on using VMware
and compared the results of the script again. The vasamse y02-1’ virtual machine remained at two
seconds while the ‘vasamse y02-2’ virtual machine dropped from seven seconds to four seconds.
M.SC. IT Sem 3 Server Virtualization using VMware
• I had done this task many times in my previous lab. I created a CPU activity by
opening my vm consoles and started up the cpubusy.vb script on both of them.
Using vSphere Web Client to Monitor CPU Utilization
• in this task i navigated to one of my VM and navigated to the ‘Monitor ->
Performance -> Advanced’ tab. This displayed a graph of CPU usage.
I then opened a second instance of the vSphere Web Client and configured the same chart
options for my ‘vasamsetty02-2’ virtual machine. After that, I obtained the CPU ready value for
both virtual machines (with the scripts still running on both machines. vasamsetty02-1-2 CPU
ready value:
M.SC. IT Sem 3 Server Virtualization using VMware
I then stopped the cpubusy.vbs script on both of the virtual machines and compared the values again.
Both machines took a significant dip in their milliseconds value. I imagine that this is because there
was no longer a significant strain on the CPU as the script had been disabled. Jamie01-2 CPU ready
value:
This task simply required that I deleted the CPU affinity value that I had set earlier for both of my virtual
machines. In order to do this, I right-clicked each virtual machine, selected ‘Edit settings…’, expanded
the CPU tab, and removed the ‘1’ value.
From here, I entered in ‘Lab Cluster’ for the cluster name, ticked the ‘Turn ON’ tick box for
the vSphere HA, clicked the ‘Percentage of cluster resources reserved as failover space
capacity’ radio button, and then clicked OK.
For this task I navigated to ‘Home -> vCenter->Hosts and Clusters’, selected one of my two
M.SC. IT Sem 3 Server Virtualization using VMware
ESXi host and dragged it to the new ‘Lab Cluster’ cluster. I then selected the new cluster and
navigated to the ‘Monitor -> vSphere HA’ tab. My primary ESXi host (the 172.16.1.17 one) is
listed as the master host, but there is no information about whether the other two virtual
machines are protected or not.
I then clicked on the ‘Heartbeat’ tab and found that there are currently no datastore in use for
heartbeating.
Finally, I navigated to the configuration issues tab and noticed a few errors
M.SC. IT Sem 3 Server Virtualization using VMware
I then selected my ESXi host within the cluster, navigated to ‘Manage -> Networking -> VMkernel
Adapters’, selected my ‘VMkernel-vMotion’ VMkernel adapter, and then clicked on the ‘Edit
Settings’ button.
Once in the settings menu, I ticked the ‘Management traffic’ tick box and clicked OK
M.SC. IT Sem 3 Server Virtualization using VMware
I then right-clicked my ESXi host within the cluster and selected ‘All vCenter Actions -> Reconfigure
for vSphere HA’
After the reconfiguration had finished, the issue regarding the management network had
disappeared.
M.SC. IT Sem 3 Server Virtualization using VMware
I began this task by navigating to ‘Home -> vCenter -> Hosts and Clusters’, selecting the
master ESXi host in the cluster, navigating to the ‘Related Objects -> Virtual Machines’ tab,
and noting the names of the virtual machines. I then simulated a host failure by rebooting my
master ESXi host – the 172.16.61.17 host. I right-clicked the host and selected ‘Reboot…’
from the drop-down menu. I was then presented with the Reboot Host menu. I entered in
‘Testing vSphere HA’ as a reason for the reboot and clicked OK.
M.SC. IT Sem 3 Server Virtualization using VMware
The host initiated a reboot. I then selected the ‘Lab Cluster’ cluster and navigated to the
‘Monitor -> Events’ tab. From here, a variety of messages were displayed. Of particular note
was the one regarding a ‘possible failure of a host’ which was just due to the reboot.
I then selected the ‘Lab Cluster’ cluster and navigated to ‘Monitor -> vSphere HA ->
Summary’. I noticed that the IP address displayed for the Master had changed to the IP of my
second ESXi host.
NOTE: The alarm saying that my first ESXi host was not responding resolved itself after 2-3
refreshes.
I then investigated the CPU and memory usage of my two virtual machines to determine which of the
two was using the most resources. Resource usage for ‘Vasamsetty02-1’ virtual machine:
M.SC. IT Sem 3 Server Virtualization using VMware
I then investigated the CPU and memory usage of my two virtual machines to determine which of the
two was using the most resources. Resource usage for ‘Vasamsetty02-1’ virtual machine:
M.SC. IT Sem 3 Server Virtualization using VMware
It appears that the ‘Vasamsetty02-2’ virtual machine is using more memory than the
‘Vasamsetty02-1’ virtual machine, but they are both using the same amount of CPU power.
From there, I selected ‘vSphere HA’ from under ‘Services, and clicked the ‘Edit…’ button.
This opened the ‘Edit Cluster Settings’ wizard.
M.SC. IT Sem 3 Server Virtualization using VMware
I then expanded the ‘Admission Control’ menu, changed the policy to ‘Define failover capacity by
static number of hosts’, and confirmed the changes.
From there, I selected the ‘Lab Cluster’ cluster, navigated to the ‘Monitor -> vSphere HA ->
Summary’ tab, and reviewed the information regarding resources that are required by the default slot.
M.SC. IT Sem 3 Server Virtualization using VMware
I then navigated to ‘Home -> vCenter -> VMs and Templates’, right-clicked my
‘Vasamsetty02-2’ virtual machine, and selected ‘Edit Settings…’ from the dropdown menu in
order to change the CPU reservation for the virtual machine. I set the CPU reservation to be
512MHz and then confirmed the change.
I then navigated back to ‘Home -> vCenter -> Hosts and Clusters’ , selected the ‘Lab Cluster’ cluster,
navigated to ‘Monitor -> vSphere HA -> Summary’ and observed the change in slot CPU requirements.
It now requires 512MHz rather than 32MHz.
M.SC. IT Sem 3 Server Virtualization using VMware
I then clicked on the ‘View’ link in order to see the virtual machine that required multiple slots. Sure
enough, it was the ‘Vasamsetty02-2’ virtual machine with the reservation requiring two slots.
I then navigated back to the ‘Monitor -> vSphere HA -> Summary’ tab and noticed that the CPU value
for the slot size had changed to 300MHz.
M.SC. IT Sem 3 Server Virtualization using VMware
I then changed the slot size policy back to ‘Cover all powered-on virtual machines…
There is a total of 8GB of memory available and two ESXi hosts. This therefore means that
there is a total of 4GB available for each ESXi host. I noticed that only 5.51GB of the RAM
is free however. This is most likely down to the ESXi hosts needing some, the cluster taking
some (perhaps?), and other settings potentially using some. I then switched to the ‘Monitor ->
Resource Allocation -> Memory’ tab and examined the capacity values. The fact that only
2.42GB of memory is available (rather than the expected 4GB) is likely due to the ESXi host
itself needing some to function.
I then selected the ‘Lab Cluster’ cluster from the inventory, navigated to the ‘Monitor ->
vSphere HA’ tab, and examined the total number of slots in the cluster.
Interestingly, no slots were shown; only a value of N/A. I assume this is because the virtual
machines are not currently running, therefore, no slots are needed/used.
I then powered on my ‘Vasamsetty02-2’ virtual machine and refreshed the Advanced Run
time Info section once again. There is now one less available slot as the other virtual machine
is using one.