Você está na página 1de 28

vSphere 6.

0: Introduction (Part-1)
Nisar AhmadNovember 27, 2016vSphere
As Im preparing for VCP6-DCV exam and certification, I have decided to start learning vSphere
6 and setting up my home-lab for the same purpose.
This exam preparation will consist of series of posts where installation, configuration, and
management of its components will come into action. As comparing to vSphere previous
version, a lot has been changed with its new version vSphere 6.0.
VMware recently launched its latest version as vSphere 6.5 and it will also be discussed in
future, but currently Im going to share vSphere 6.0 knowledge, because Im interested in taking
part in VMwares vExpert program. Many IT pros have already shared their knowledge and
expertise in vSphere 6.0, and I also want to contribute in this interesting area. So, lets get
started.
Introduction to VMware vSphere 6.0
Ive mentioned earlier that many changes have been made in architecture and some new
features are introduced in Vmware vSphere 6.0. the major changes that have been introduced
in vSphere 6.0 is to remove dependency on built-in database server (MS SQL Express) by
introducing vPostgres SQL as embedded database for vCenter server installation.
However, external database MS-SQL or Oracle (only for windows based vCenter Server) can
also be used. For vCSA (vCenter Server Appliance) we are bounded to use embedded
vPostgres SQL database (which I think a hard move from VMware).

vSphere 6.0 Editions


vSphrere 6.0 is available with 3 editions:
1. Standard: This edition of vSphere 6.0 provides the following features:
HA and FT for 2 vCPU
Data protection (VDP) and vSphere Replication (For replicating VM from one vSphere
Infrastructure to other)
vVOLS (Must be supported by backend storage) for creating virtualization aware
storage
SPBM (Storage Policy Based Management): For creating storage policies and assign it
to VM to place it on appropriate storage. This is achieved via API calls made by vSphere to
storage
Content Library: A centralized place on vCenter to store iso images and vApps for a
centralized management
2. Enterprise: This version of vSphere 6.0 provides all the features provided by Standard
Edition along with the following additional features:
VAAI (vSphere API for Array Integration)
DRS/DPM
BDE (Big Data Extensions)
3. Enterprise Plus: This advance edition covers all the features of Enterprise along with
the following additional features:
FT (Fault Tolerance) for 4 vCPU
vDS, Storage DRS, NIOC, SR-IOV
Host profile/Auto Deploy
Flash Read Cache-Requires SSD disks on each Esxi server. FRC is enabled per VM
and when enabled it increases storage Read IO throughputs.
Long distance and cross vCenter vMotion
For a complete list of new features that are introduced in vSphere 6.0, you can refer to Eric
Sieberts blog, and for more detailed information on version comparison please read Thomas
Krenns Article.
vSphere 6 Configuration Maximums
When VMware announces a new release of vSphere, the first thing which comes into pros mind
is what are the configuration maximums and how a virtual infrastructure can scale-up and scale-
out?
To understand what has been changed with vSphere 6.0 following is the comparison between
vSphere 6.0 and 5.5.

vSphere 6 Architecture
The major change in vSphere 6 architecture is the change in architecture of vCenter Server 6.
In previous version vSphere 5.5, vCenter Server is installed along with 4 components (Inventory
Service, SSO Server, Web Client Server, and vCenter Server). In vSphere 6, the architecture of
vCenter deployment has been changed and new concept Platform Services controller (PSC)
has been introduced which is further continued in latest version vSphere 6.5.
PSC is a replacement for SSO with some additional functionality such as licensing and
certificate authorities. PSC takes SSO to next level by providing and synchronizing SSO,
licenses and certificates across the virtual infrastructure.
Following components will be deployed when PSC is installed
1. VMware Certificate Aurthority (VMCA)
2. Single Sign On (SSO)
Single Token Service (STS)
Identity Management Service
Directory Service
3. VMware Licensing Service (controlled by vCenter Server in vSphere 5.5)
4. Misc services
o VMware Common Logging Service
o VMware Component Manager Service
o VMware HTTP Reverse Proxy
- See more at: http://www.myvirtualjourney.com/vsphere-6-0-
introduction-part-1/#sthash.zghMvwG1.dpuf

vSphere 6.0: Introduction to Virtual Infrastructure


(Part-2)
Nisar AhmadDecember 2, 2016vSphere

In previous post vSphere 6 Introduction, weve briefly discussed about vSphere 6, its editions,
configuration maximums, vSphere 6 architecture, and PSC deployment methods. In this post,
well discuss about Virtual Infrastructure of a data center. Virtualization is a concept that
consolidates the data center environment and enables us to run more workload on a single
physical server. In a virtualized environment, applications run on virtual machines and multiple
virtual machine run on a single server.

Virtualization technology changes the way servers are provisioned. We dont need to wait for
hardware to be purchased, or cabling to be installed. The process of VM provisioning via a GUI,
in contrast, process of deploying physical server, VM can be deployed in minutes.
Figure: Thanks to VMware.com

Virtual Machine (VM) is a software computer that, like a physical computer, runs an operating
system and required applications. VM is installed on a physical server with the help of a
hypervisor. Hypervisor is a software layer which segregates hardware resources such as
processing, memory for each VM installed on that server. Hypervisor enables to install multiple
operating systems and applications on a single server and consolidates the hardware.

Physical Resource Sharing


As I mentioned earlier that, with virtualization, we can run multiple VMs on a single physical host
with each VM sharing same physical resources of a physical server. When multiple VMs run on
ESXi host, each VM is allocated a portion of a physical resources. The hypervisor schedules
VMs like a traditional operating system allocates CPU and memory for and schedule
applications.
Figure: Thanks to VMware.com

Physical and Virtualized Host Memory Usage


In a physical environment, the operating system assumes the ownership of all physical memory
in the system. Memory virtualization emphasizes performance and runs directly on the available
RAM. The memory space is allocated and protected from being accessed by others when VM is
created.

Figure: Thanks to VMware.com

Physical and Virtual Networking


A VM can be configured with one or more virtual Ethernet adapters. Virtual switches enable
VMs on the same ESXi host to communicate with one another by using the same protocols that
are used over physical switches without need for additional hardware. Virtual switches also
support VLANs that compatible with standard VLAN implementations.

With virtual networking, we can link local VMs together and as well as to external network
though virtual switch. Virtual Ethernet adapters and virtual switches are key components of
virtual networking. Virtual switches will be discussed in details in future posts.

Figure: Thanks to VMware.com

Physical File Systems and VMFS


VMware vSphere VMFS is designed, constructed, and optimized for a virtualized environment.
VMFS is a high-performance cluster file system designed for VMs. VMFS increases resource
utilization by providing multiple VMs with shared access to a consolidated pool of clustered
storage.

VMFS provides an interface to storage resources so that several storage protocols (FC, FCoE,
and iSCSI) can be used to access datastores on which VMs reside. Dynamic growth of VMFS
datastores through aggregation of storage resources and dynamic expansion of a VMFS
datastore enables us to increase a shared storage resource pool with no downtime.
Figure: Thanks to VMware.com

In this post, Ive tried to explain some concepts regarding virtual infrastructure.

I hope youve enjoyed reading this post, and if you feel it should be shared on social media you
can.

- See more at: http://www.myvirtualjourney.com/introduction-to-virtual-


infrastructure-part-2/#sthash.0fjOB2jd.dpuf

vSphere 6.0: Lab Setup (Part-3)


Nisar AhmadDecember 13, 2016vSphere
In previous posts of this series, Ive explained about vSphere 6.0 and a brief introduction about
virtual infrastructure. If you have missed last posts, you can find them here.
1. Introduction to vSphere 6.0
2. Introduction to Virtual Infrastructure
In this post, well discuss about how to build a lab, what hardware and software components
will be required to setup a lab to hands-on vSphere 6.0.
Hardware Requirements
If you dont have a proper lab equipment, no worries you can still setup a home-lab to hands-on
vSphere 6.0. To setup a lab you will require a PC or laptop with 32GB RAM (recommended),
core i7 processor (5th Gen or more preferred), and 1TB hard disk drive. Lab can also be setup
with minimum of 16GB RAM. Im also using a laptop with 16GB RAM, core i7 5 th Gen Processor,
and 1TB hard drive.
Lab Requirements
Following are the requirements to setup a lab
1. Win 8.1 or above with above mentioned specs and VMware Workstation 12 installed as
a base machine.
2. Server 2012 R2 Standard as a Domain Controller and DNS Server installed in VMware
Workstation.
3. Another Server 2012 R2 Standard as a vCenter Server with Embedded vPostgres
Database.
4. Two additional disks (or drives of 100GB or more) which are presented as iSCSI LUNs
to my ESXi Hosts.
5. Three ESXi host installed inside VMware Workstation each with 8 GB RAM and 2 vCPU
if you have 32GB RAM, and if you have 16GB RAM available, then you can add 2 ESXi
hosts with 4GB RAM each.
Active Directory and DNS Configuration
Before start building a home-lab, DNS configuration is required. In my lab environment, Im
going to run Windows Server 2012 Standard Edition, and my Domain is configured as vcp.com
and both forward and reverse lookup zones are configured in DNS. You can see in following
figures.

Figure 1: Forward Lookup Zone


Figure 2: Reverse Lookup Zone
Make sure that your name resolution is working properly (test your environment with nslookup
command via CLI interface).
VMware Workstation Configuration
In my lab environment, Im using VMware Workstation 12 Pro, and following table represents
the network configuration for whole lab environment.

In above table, VMnet0 will be used as Management network with network type as Bridged and
192.168.2.0/24 subent, and rest of the virtual network adapters will be used as Host-only for
connecting VMs internally in a private network. VMnet1 will be used for Storage capabilities
such as iSCSI along with 10.1.1.0/24 subnet. VMnet2 will be used for vMotion feature with
10.2.2.0/24 subnet. VMnet3 and VMnet4 will be used for connecting VMs.
I hope youve enjoyed reading this post, and if you feel it should be shared on social media you
can.
- See more at: http://www.myvirtualjourney.com/vsphere-6-0-lab-setup-
part-3/#sthash.6edu9tFT.dpuf

vSphere 6.0: vSphere Client (Part-4)


Nisar AhmadDecember 29, 2016vSpherevCenter Server, vSphere Client, vSphere Web Client
In vSphere 6.0, there are two interfaces vSphere Web Client and vSphere Client are used to
access the virtual environment. If you have missed last posts, you can find them here.
1. Introduction to vSphere 6.0
2. Introduction to Virtual Infrastructure
3. vSphere Lab Setup
vSphere Web Client is a browser-based, fully extensible, platform-independent user interface
used to access your data center environment. Web Client is based on Adobe Flex. All
necessary workings with vSphere, ESXi, and VMware vCenter Server (ESxi and vCenter server
will be discussed in details in upcoming posts) are possible with the vSphere Web Client.
vSphere Client is a legacy user interface for vSphere and can be used to perform a subset of
the vSphere Web Client functionality. If you need to manage ESXi host directly (for example, if
the vCenter Server is currently unavailable), the vSphere Client may be used. vSphere Client
feature has been removed in latest version of vSphere 6.5.
Figure: Thanks to vmware.com
Installing vSphere Client
The vSphere Client is used to connect remotely to ESXi hosts and vCenter Server systems from
a Windows system. Among many other features, vSphere Client provides console access to
virtual machines.
For installation of vSphere Client, VMware vCenter Server installer wizard is used on supported
version of Windows OS, and for installing it standard procedure of installation will be adopted.
In vSphere Client login window, following information will be entered.
Host name or IP address of ESXi host or vCenter Server
User name
Password
Alternatively, you may use your Windows session credentials by ticking in checkbox.
I hope youve enjoyed reading this post, and if you feel it should be shared on social media, you
can.
- See more at: http://www.myvirtualjourney.com/vsphere-6-0-vsphere-
client-part-4/#sthash.6Czv8vQS.dpuf

vSphere 6.0: Install and Configure ESXi 6.0 (Part-


5)
Nisar AhmadJanuary 2, 2017vSphereInstall and Configure ESXi 6.0
In previous posts of this series, we have discussed some basics of install, configure, manage
vSphere 6.0 series. If you have missed previous posts, you can find them here.
1. Introduction to vSphere 6.0
2. Introduction to Virtual Infrastructure
3. vSphere Lab Setup
4. vSphere Client 6.0
in this post, well discuss about what is ESXi 6.0? How will it install and work?
What is ESXi 6?
ESXi is a bare-metal hypervisor that runs directly on server hardware and do not requires the
installation of additional underlying operating system. This virtualization software creates and
runs its own kernel, which is run after a Linux kernel bootstraps the hardware. It has three
interfaces.
Hardware
Guest system
Console Operating System (service console)
Install and Configure ESXi 6.0
There are different ways to install ESXi server. You can use interactive installation (CD/DVD,
USB drive, and PXE boot), scripts or auto deploy. I am installing ESXi 6 in VMware
Workstation on my local SATA hard disk with interactive installation. You
can download installation ISO image from VMware. Lets begin the installation.
Step 1: Attach the Esxi 6 iso image to the virtual machine and boot the system. You will be
presented see the standard ESXi 6.0 Boot Menu as shown below. Press Enter to continue.

Step 2: Let the ESXi load the necessary libraries to install the hypervisor. Welcome screen will
appear Press Enter to continue.
Note: Remember to check VMware Hardware Compatibility List guide to see whether your
hardware is listed or not. If the hardware is not listed, then you cant get the support from
VMware regarding installing ESXi on un-supported hardware. Press Enter to continue.
Step 3: Accept the EULA by pressing F11 key.

Step 4: ESXi will start scanning for available devices on your system.
Step 5: Select the disk for the ESXi installation and press Enter to continue.

Step 6: Select the keyboard layout and press Enter.


Step 7: Set the root password for the ESXi host. Make sure password matches and press
Enter to continue.

Step 8: Press F11 to start the installation process.

Step 9: Installation process will start and continue.


Step 10: After completion of installation process, Press Enter to reboot the host.

Step 11:
ESXi server will take a short time to complete.

Configuring ESXi Host


After installation of ESXi host you will be presented with the familiar screen.
After the reboot, you can see the Direct Console User Interface (DCUI) above. You can see the
ESXi build number, memory and processor information and IP address. As you can see above
by default, ESXi is set to receive IP from DHCP server. You can press F2 to login to DCUI
to configure IP address, DNS, hostname. In next post of this series Ill show you how to
configure IP address, DNS, hostname of ESXi 6.0.
I hope youve enjoyed reading this post, and if you feel it should be shared on social media you
can.
- See more at: http://www.myvirtualjourney.com/vsphere-6-0-install-
and-configure-esxi-6-0-part-5/#sthash.6IDtAKPz.dpuf

Configure IP Address and Hostname of ESXi 6.0


(Part-6)
Nisar AhmadJanuary 3, 2017vSphereDNS, IP address
After installing ESXi 6.0 host, the very first thing you would want to configure IP address and
Hostname in ESXi server. If you have missed previous posts of this series, you can find them
here.
1. Introduction to vSphere 6.0
2. Introduction to Virtual Infrastructure
3. vSphere Lab Setup
4. vSphere Client 6.0
5. Install and Configure ESXi 6.0
By default, the host-name is called localhost, the IP address is set to DHCP client. So, in this
post I will show steps to configure IP address and hostname in ESXi server.
Step 1: Press F2 to start configuration of your ESXi host and login screen will appear. Provide
your credentials and press Enter.
Step 2: From System Configuration menu select Configuration management Network and
press Enter.

Step 3: Select IPv4 Configuration and press Enter.


Step 4: Select Set static IPv4 option and supply the value for IPv4 address, Subnet Mask and
Default Gateway and press Enter.

Step 5: Select disable IPv6 and press Enter.


Step 6: Select DNS Configuration option and press Enter. Select Use the following DNS
Server option and supply the value of Primary DNS Server and hostname etc. and press
Enter.

Step 7: Enter your DNS suffix and press Enter.

Step 8: Press Esc to exit network configuration wizard. It will ask you to restart management
network. Press <Y> to do so.
Step 9: Now test your management network configuration. Select Test Management Network
from system configuration menu and press Enter.

Step 10: Enter your IP address in Ping Address #0: and hostname in Resolve Hostname,
and press Enter. It will test your environment by pinging and resolving a hostname.

Step 11: Press Y for applying changes and reboot the host.
Step 12: Host will be restarted to complete.

Now, your ESXi is ready for fun, and repeat above mentioned steps for configuring more ESXi
hosts for your virtual environment if require.
I hope youve enjoyed reading this post, and if you feel it should be shared on social media, you
can.
- See more at: http://www.myvirtualjourney.com/configure-ip-address-
and-hostname-of-esxi-6-0-part-6/#sthash.4qmRSB2c.dpuf

vSphere 6.0: Configure NTP Client Using vSphere


Web Client (Part-7)
Nisar AhmadJanuary 5, 2017vSphereNTP Client, virtual environment, vSphere Web Client
NTP is a Network Time Protocol which is used to sync time of hosts with NTP server. NTP is
also used to set correct time so that you cannot have issues with the Time. In this post, well
discuss how to configure NTP in ESXi using vSphere Web Client If you have missed last
posts, you can find them here.
1. Introduction to vSphere 6.0
2. Introduction to Virtual Infrastructure
3. vSphere Lab Setup
4. Installation of vSphere Client
5. Install and Configure ESXi 6.0
6. Configure IP Address and Hostname of ESXi 6.0
Lets start the configuration process step-by-step.
Step 1: Login to vSphere Web Client using your credentials
Step 2: Click on the Host and Clusters

Step 3: Click on ESXi host listed on Navigation Pane


1. Click on Manage Tab
2. Click on Settings
3. Click on System > Time Configuration
Step 4: Click on Edit Button on the right side, Time Configuration window will open
Step 5: Click on radio button Use Network Time Protocol (Enable NTP Client)

Step 6: NTP Service status is stopped by default. So, start the service by clicking on the Start
button.
1. Choose NTP Start Service Policy from drop down list.
2. Type NTP Server Name according to your region (you can search on Google with area)
in NTP Servers Box.
Step 7: Click on Start button to start NTP service.
Then, click on OK button, and your NTP Client will be configured.

Perform Step 3 to 7 for each host in your virtual environment, and your whole virtual
environment will be synced.
I hope youve enjoyed reading this post, and if you feel it should be shared on social media, you
can.
- See more at: http://www.myvirtualjourney.com/vsphere-6-0-configure-
ntp-client-using-vsphere-web-client-part-7/#sthash.jOeZ5jR4.dpuf

vSphere 6.0: Understanding Virtual Machine Files


(Part-8)
Nisar AhmadJanuary 7, 2017vSpherevirtual environment, Virtual Machine, VMFS
As we know that virtual infrastructure is a file-based structure. Before creating a virtual machine,
we should understand the basic structure of a VM. When a virtual machine is created, a set of
files for that specific virtual machine are created. Virtual machine files are stored in either the
virtual machines directory or the working directory. Both directories are typically on the host
system. If you have missed previous posts of this series, you can find them here.
1. Introduction to vSphere 6.0
2. Introduction to Virtual Infrastructure
3. vSphere Lab Setup
4. vSphere Client 6.0
5. Install and Configure ESXi 6.0
6. Configure IP Address and Hostname of ESXi 6.0
7. Configure NTP Client using vSphere Web Client
VMware virtual machine files are organized in the Virtual Machine File System (VMFS). Most of
the files start with the actual name of the VM followed by different file extensions that denote the
file type. Following table represents file extensions and their brief descriptions.

Ive created a virtual machine with the name as ESXi1, and you can see in following figure, most
of the files are present with the above mentioned extensions.
Any virtual machine which is created in virtual environment consists of two parts, i. Body part, ii.
Brain part
i. Body Part: Virtual disk files of a VM, which store the contents of the virtual machine hard disk
drive are called body part of a VM. These files use .vmdk extension. They are usually large files
sometimes very large files, and vSphere 6.0 can support up-to 62TB virtual disk file per VM.
ii. Brain Part: The primary configuration file, which stores virtual machine settings, and the
virtual machine paging file, which backs up the guest main memory on the host file system are
called brain part of a VM. These files use .vmx and .vmem file extensions. These files are
usually smaller in size and these types of files transferred from one host to another during
vMotion, HA features (advanced features will be discussed in future posts).
I hope youve enjoyed reading this post, and if you feel it should be shared on social media, you
can.
- See more at: http://www.myvirtualjourney.com/vsphere-6-0-
understanding-virtual-machine-files-part-8/#sthash.uGpaarE7.dpuf

Você também pode gostar