VMware ESXi Cookbook

3 (2 reviews total)
By Mohammed Raffic Kajamoideen , Aravind Sivaraman
    Advance your knowledge in tech with a Packt subscription

  • Instant online access to over 7,500+ books and videos
  • Constantly updated with 100+ new titles each month
  • Breadth and depth in over 1,000+ technologies
  1. Installing and Configuring ESXi

About this book

VMware ESX and VMware ESXi hypervisors are used for providing the foundation for building and managing a virtualized IT infrastructure. vSphere 5.1 delivers the same industry-leading performance and scalability as prior vSphere releases, with several additional benefits including its improved reliability and security. VMware vSphere 5.1 is based on the ESXi hypervisor architecture, a thin purpose-built hypervisor that does not depend on a general purpose operating system, which does away with the requirement of persistent storage. So we can now store it on a dedicated compact storage device, drastically reducing the hypervisor install footprint to less than 150MB.

"VMware ESXi 5.1 Cookbook" explores every aspect of VMware administration. We will learn to configure and to administer vSphere including high availability (HA), distributed resource scheduler (DRS), fault tolerance (FT), vMotion , svMotion, virtual machine provisioning, update manager, and distributed virtual switches. We will also explore advanced level operations with lots of tips and tricks to ease your job.

"VMware ESXi 5.1 Cookbook" offers a comprehensive understanding of new features released with vSphere 5.1 and how it enhances your VMware virtual environment. Starting with the installation and configuration of ESXi and vCenter and followed by the configuration of various core components including the network, storage, virtual machine administration, security, performance, and patching, along with the high availability of the virtual infrastructure.

Also exploring how the vSphere environment can be secured, learn to monitor your virtual environment using default alarms available with the vCenter server and to collect performance reports for your vSphere environment.

Publication date:
March 2014
Publisher
Packt
Pages
334
ISBN
9781782170068

 

Chapter 1. Installing and Configuring ESXi

In this chapter, we will cover the following topics:

  • Installing ESXi using Interactive Mode

  • Deploying ESXi hosts using scripted installation

  • Deploying ESXi hosts using Auto Deploy

  • Installing vSphere Client

  • Configuring NTP settings on ESXi hosts

  • Configuring DNS and Routing

  • Licensing an ESXi host

 

Introduction


VMware ESXi is a hypervisor that is built directly on top of an x86 hardware. It abstracts the underlying hardware and allows multiple virtual machines to use the same hardware resources. It includes an ultra-thin architecture, and the footprint in the memory is 32 MB, which makes it more reliable and it only takes a few minutes to install. ESXi is offered in two different types: ESXi Embedded and ESXi Installable, and there is no functional difference between them. Both use the same code and provide us with the same functionality and features depending on the license used. The two different types of ESXi are explained as follows:

  • ESXi Embedded: This is available in the Original Equipment Manufacturer (OEM) format, and it is installed on a USB or an SD card when the hardware is being purchased. It saves the cost of purchasing additional hard drives and saves valuable time for vSphere administrators, as there is no need to install hypervisors.

  • ESXi Installable: This is a traditional form of installing the hypervisor on a local disk or SAN using an ISO image.

A VMware vSphere License is based on per physical CPU and the vCenter Server is licensed separately. There are three editions of vCenter and five editions of VMware vSphere license available.

vCenter is available in the following three editions:

  • vCenter Server Essentials: This is bundled with the vSphere Essentials kit, and it allows centralized management of three ESXi hosts.

  • vCenter Foundation: This vCenter edition limits vSphere host management and is limited to only three ESXi hosts. It also doesn't support the vCenter linked mode or include vCenter Orchestrator.

  • vCenter Standard: This is used in large-scale deployments for rapid provisioning, management, automation, and monitoring, and supports up to 1000 ESXi hosts.

The vSphere licenses are categorized for SMB and large enterprise customers. If you are an SMB customer, two kits are available, which are bundled with the hypervisor and the vCenter:

  • The Essentials kit allows you to use up to three ESXi hosts, each with two physical processors, but this license only includes the hypervisor and does not include any other features

  • The Essentials Plus kit allows you to use up to three ESXi hosts, each with two physical processors, and this kit includes features such as vMotion, High Availability (HA), data protection, vShield end point, and vSphere replication, along with the vSphere hypervisor

If you are running more than three ESXi hosts in the environment and looking for more vSphere features, then you might consider using one of the following licenses:

  • Standard

  • Enterprise

  • Enterprise Plus

A full comparison of the features included in each edition can be found at http://www.vmware.com/in/products/vsphere/compare.html.

Choosing hardware for vSphere deployments

You need to make sure that the right hardware is procured to perform the right job, and selecting the hardware plays a major role in the vSphere deployment. VMware has put together a list of supported servers and hardware after the vendors have done extensive testing. VMware Compatibility Guide (http://www.vmware.com/resources/compatibility/search.php) gives us the list of supported vendors and their hardware for the vSphere deployment.

As an example, the following screenshot is filtered to list the supported HP servers for ESXi:

VMware Compatibility Guide is not only for listing the supported servers but you can also drill down to list out the supported storage arrays, I/O devices, guest OS, and many other features.

Requirements for installing ESXi

Every traditional operating system needs to fulfill a certain hardware requirement for its successful installation; similarly, we have a set of hardware requirements that are required for ESXi installation:

  • A supported 64-bit processor with a minimum of two cores

  • CPU with support for LAHF and SAHF instructions

  • NX/XD bit enabled for the CPU in the BIOS

  • 2 GB RAM is required for the successful installation of ESXi, but VMware recommends at least 8 GB RAM in the production environment

  • Hardware virtualization (Intel VT-x or AMD RVI) has to be enabled to run 64-bit virtual machines

  • A minimum of one Gigabit or 10 Gb network adapters

Deploying VMware ESXi

Once you have selected the hardware and fulfilled the requirements for the ESXi installation, you have to decide the deployment option for ESXi. Four deployment options are available and they are as follows:

  • Interactive ESXi installation

  • Scripted ESXi installation

  • Auto Deploy ESXi installation

  • Customizing installation with ESXi Image Builder

The first three deployment methods will be covered in this chapter.

 

Installing ESXi using Interactive Mode


Performing ESXi installation using Interactive Mode is fairly straightforward and it's the easiest method of performing the installation.

Getting ready

Make sure that the installer files are downloaded from http://www.vmware.com/download, and if the installation is performed remotely, make sure you have access to the hardware remote console (ILO, DRAC, RSA, and so on).

How to do it...

Now, let's look at the steps for installing ESXi:

  1. Insert the CD/DVD image into the CD ROM or mount it using a Virtual CD/DVD ROM.

  2. Boot the server from the ISO.

  3. Select ESXi-5.1.0-799733-standard Installer from the boot menu, as shown in the following screenshot:

    Note

    The build number (799733) will change whenever a new security patch or an update is released by VMware.

  4. The ESXi installer image will load, and it will present the following screenshot. Press Enter to continue.

  5. In the next screen, accept the license agreement by pressing F11 to proceed.

  6. Next, the installer will look for the list of available devices to install the ESXi and will display a list of both the local and the remote disks available for the host, as shown in the following screenshot:

    Note

    In case you are using FC SAN and installing the ESXi on a local disk, make sure that you disconnect the FC cables as a precaution, and if you are installing the ESXi as boot from SAN, make sure the correct boot LUN is being selected.

  7. Once you have confirmed the disk on to which the ESXi has to be installed, select the disk and press Enter to continue.

  8. Select the desired keyboard layout and press Enter to continue.

  9. Now, enter the password as per your security standards and press Enter to continue.

  10. If there any errors or warnings, it will be listed in the next screen; if everything looks good, you will be asked for a confirmation to install ESXi, as shown in the following screenshot. Press F11 to allow the installation to complete.

  11. When the installation is complete, as shown in the following screenshot, remove the installation media and press Enter to reboot the server:

  12. After the reboot, the following screenshot will be available on the console and, if DHCP is available in the environment, the host will obtain an IP from the DHCP server:

There's more…

Once the installation of ESXi is complete, you will be able to perform the following tasks using Direct Console User Interface (DCUI):

  • Change the root password

  • Configure the networking settings

  • Enable the ESXi shell and remote SSH to troubleshoot from the console

  • Restart management network and management agents

  • Perform network restore

  • Shutdown or restart/reboot ESXi hosts

  • View system logs

  • Remove custom extensions

  • Reset the system configuration

  • Configure the lockdown mode

 

Deploying ESXi hosts using scripted installation


Performing a scripted installation is an efficient way of deploying multiple ESXi hosts. The installation script (ks.cfg) contains the installation and configuration parameters of ESXi. Using a scripted installation, you can make sure you have a similar configuration for your entire infrastructure. This makes it easy for deploying multiple ESXi hosts in a short amount of time.

Getting ready

Make sure that the hardware used is listed in VMware Compatibility Guide (http://www.vmware.com/resources/compatibility/search.php) for ESXi installation, also make sure that the ESXi installer ISO is available, and that the installation script is placed in any one of the following locations:

  • CD/DVD device

  • USB flash drive or USB storage device

  • NFS

  • FTP

  • HTTP/HTTPS

How to do it…

A scripted installation can be performed using two different methods:

  • When the ESXi installer is booting, press Shift + O to provide the location of the script file:

    Ks=https://10.0.1.65/esxi/ks.cfg ip=10.0.1.150 netmask=255.255.255.0 gateway=10.0.1.1

    Syntax: ks=<location of installation script> <boot command line options>

  • The deployment of ESXi hosts can be fully automated using the PXE infrastructure where the options are passed through the kernelopt line of the boot.cfg file. The boot.cfg file is located in the installation media and the content would look similar to the following. Edit the kernelopt section by changing the script location for automating the deployment:

    bootstate=0
    title=Loading ESXi installer
    kernel=/tboot.b00
    kernelopt=runweasel
    modules=/b.b00 --- /useropts.gz --- /k.b00 --- /
    

The location of the script file is entered when the installer is booted as shown in the following screenshot:

How it works…

Boot options are specified to access the kickstart file; the following table summarizes the ks parameters available during boot for accessing the installation script:

Boot option

Description

BOOTIF<MAC>

This uses the specified network address location when looking for a script

Gateway = <IP Address>

This uses the network gateway as the default gateway

ip = <IP Address>

This uses a static IP address

Nameserver = <IP Address>

This looks for the specified domain name server

netmask=subnet mask

Subnet mask is specified for the network adapter

vlanid=vlanid

A specific vLAN ID is used for the network adapter

ks=protocol://<serverpath>

This uses the given URL to locate the installation script

ks=file://<path>

This uses the scripts that are specified in the path

ks=cdrom:/<path\>

This uses the script that is located in the specified CDROM path

ks=usb

This looks for the ks.cfg file on the attached USB disk and performs the installation

ks=usb:/path

This uses the specified path on the USB disk for the installation script

There's more…

VMware has made available a standard installation script that can be used, or you can create a customized script based on your environment with the required parameter. The standard installation script is located on ESXi under the /etc/vmware/weasel path and the content of the ks.cfg file would be as follows:

#
# Sample scripted installation file
#
# Accept the VMware End User License Agreement
vmaccepteula
# Set the root password for the DCUI and Tech Support Mode
rootpw mypassword
# The install media is in the CD-ROM drive
install --firstdisk --overwritevmfs
# Set the network to DHCP on the first network adapter
network --bootproto=dhcp --device=vmnic0
# A sample post-install script
%post --interpreter=python --ignorefailure=true
import time
stampFile = open('/finished.stamp', mode='w')
stampFile.write( time.asctime() )

In the previously mentioned script, the end user agreement will be accepted. The password for the host will be mypassword, and this will obtain the IP address via DHCP on VMNIC0. The installation will happen on the first disk, and it will overwrite the existing VMFS partition. In case you are interested in using a customized script, you have the following list of commands:

  • install: This command specifies that it's a fresh installation of the ESXi host.

  • upgrade: This command specifies that it's an upgrade of the ESXi host.

  • --overwritevmfs: This command is used in case you want to overwrite the existing datastore.

  • --preservervmfs: This command will preserve any existing VMFS partition on the disk.

  • --firstdisk: This command is used to specify the disk on which the installation/upgrade should happen; by default, the local disk will be chosen followed by the remote disk and USB. If you want to change the order, you need to specify the order as:--firstdisk=USB,remote,local.

  • keyboard: This is used to set the keyboard layout type.

  • accepteula or vmaccepteula: These commands are required and used to accept the VMware license agreement.

  • rootpw: This command is required, and it's used to set the root password for ESXi.

  • hostreboot: When specified, this command reboots the ESXi host after the script execution.

It is also possible to specify pre, post, and first boot sections with the help of Python or the busybox interpreter command. If you want to enable SSH and create an additional vSwitch, you have to mention that in the first boot section with the help of ESXCLI and vim-cmd. We will now see an example of enabling SSH in the first boot section:

%firstboot --interpreter=busybox
#commands enable and start both Local and remote tech support mode
vim-cmd hostsvc/enable_ssh
vim-cmd hostsvc/start_ssh
vim-cmd hostsvc/enable_esx_shell
vim-cmd hostsvc/start_esx_shell

The preceding syntax enables and starts the Local and Tech Support Modes during the first boot after the installation has been completed.

One caveat with the %firstboot script is that any errors in the script will not be known until the installation is complete. If you just want to parse and check the kickstart file, you can use the dryrun command.

The next deployment method is using Auto Deploy, which is a little complex compared to the other two methods.

 

Deploying ESXi hosts using Auto Deploy


Auto Deploy is another method of deploying ESXi. With the help of Auto Deploy, you can specify the image to be deployed on the host. Auto Deploy is used in two different modes, Stateless caching and Stateful installs, which are explained next.

  • Stateless caching: In this method, the ESXi host configuration is not stored in the disk, but it's linked to an image profile. While rebooting the host, it uses the Auto Deploy server to boot, and when the server is not reachable, the host will boot from the local cache.

  • Stateful installs: In this method, the host is provisioned with Auto Deploy, but the host configuration and state are stored in the local disk. On every reboot, the host boots from the disk just as if it were installed using the ESXi Installer.

Auto Deploy components

The following figure depicts the Auto Deploy components:

Source: VMware

Each component is explained as follows:

  • Auto Deploy server: This has the information of the ESXi image and host profile, which are associated with the hosts.

  • Auto Deploy rules engine: This specifies which image and host profiles have to be used by the ESXi host. The rule definition is being done by Auto Deploy PowerCLI.

  • Image profile: This component specifies VIBs, which are available for download from VMware.

  • Host profiles: This has been created with a reference host that will have the correct set of configuration, such as network, storage, and so on. This profile can be applied to another host to maintain a consistent configuration across the environment.

  • Host customization: This stores the information that will be given by admins when the host profile is applied to the host.

Getting ready

Make sure you have following components with you:

  • Auto Deploy binaries

  • PowerShell and PowerCLI binaries

  • TFTP software

  • DHCP server

  • ESXi 5.1 offline bundle file

How to do it…

In this recipe, we will learn how to deploy ESXi host using Auto Deploy.

Note

The steps for installing Auto Deploy Server have been covered in Chapter 2, Installing and Using vCenter.

Now, let's see the steps involved in deploying ESXi:

  1. Install the Auto Deploy Server and it can be installed on the vCenter Server or on a new server.

  2. Install PowerShell and PowerCLI along with Auto Deploy and Image Builder cmdlets.

  3. Install the TFTP server on vCenter and configure the TFTP root directory (for example, D:\TFTP_Root\).

  4. Download the TFTP Boot Zip file from the Auto Deploy Server. It can be downloaded from the vCenter Server using vSphere Web Client. Navigate to vCenter Server | Manage | Auto Deploy | Download TFTP Boot Zip and extract the content under the TFTP root directory:

  5. Log in to the DHCP server and open the DHCP console, right-click on Scope Options, click on Configure Options..., and configure the following parameters:

    • Select the checkbox for 066 Boot Server Host Name and provide the TFTP server IP address:

    • Select 067 Bootfile Name and configure undionly.kpxe.vmw-hardwired:

  6. Make sure the host is set to PXE boot.

  7. Connect to the vCenter Server using PowerCLI and import the metadata from the software depot or ZIP file using the following cmdlet:

    Add-EsxSoftwareDepot C:\VMware-Esxi-5.1.0-799733-depot.zip
    

    You can see the cmdlet in the following screenshot:

    The deployment rule is a must, and it is created to assign an image profile to the servers, which are specified within the Pattern parameter. In the following example, we have created a rule name called Adrule, and this rule is applicable for the hosts that are within the specified IP range (10.1.1.200-10.1.1.225):

    New-DeployRule –Name "Adrule"–Item "ESXi-5.1.0-799733-standard" –Pattern "ipv4=10.1.1.200-10.1.1.225

    You can see the cmdlet in the following screenshot:

    The rules that are created are not part of the rule sets until we add them manually, and there are two types of rule sets available: active rule set and working rule set. They are explained as follows:

    • Active rule set: When a deployment starts, the Auto Deploy server checks the active rule set for matching rules

    • Working rule set: This allows the rules to be tested before making the changes active

    The deployment rule that was created previously has to be added to the active rule sets, and this can be done with the help of the Add-DeployRule cmdlet. By default, the rules will be added to both of the rules. If you wish to make the rule inactive, use the NoActivate parameter.

    The following syntax will add the rule to both active and working rule sets:

    Add-DeployRule –DeployRule Adrule
    
  8. Now, when you boot the physical host, it will start deploying the ESXi image.

There's more…

Now, let's see some of the PowerCLI cmdlets, which can be used while creating software depots and rules while using Auto Deploy:

  • Add-EsxSoftwareDepot: This is used to import the metadata from the software depot or ZIP file

  • Get-EsxImageProfile: This is used to list down the images that are added to the depots

  • New-EsxImageProfile: This is used to create a new image profile by cloning the existing one or by creating an image profile from scratch

  • Export-EsxImageProfile: This is used to export the image profile as an ISO or ZIP file once the packaging is done

  • New-DeployRule: This is used to create a deployment rule, which matches the physical host configuration such as the host hardware or the servers, that is within a specific IP range

  • Add-DeployRule: This is used to add rules to the working rule sets

  • Get-DeployRuleSet: This lists the current working or active rule set

 

Installing vSphere Client


Now that we have seen the deployment of ESXi, the next step will be to configure the ESXi host, which is done using the vSphere Client. As an alternative to the vSphere Client, the vSphere Web Client provides a web interface for interaction with the vCenter Server system and manages the ESXi hosts through a browser. We will learn more about the vCenter Server and vSphere Web Client in Chapter 2, Installing and Using vCenter.

Note

With the release of vSphere 5.1, VMware has made an entire new feature available only via the Web Client if the host is managed by the vCenter Server.

Getting ready

The installer of the vSphere Client can be found in vCenter Server Installation Media. Alternatively, you can download the installer by accessing the ESXi host via a web browser where you will find a link to download the vSphere Client, which will be redirected to vsphereclient.vmware.com.

How to do it…

The steps involved in installing the vSphere Client are quite simple, and are as follows:

  1. Run the VMware vSphere Client installer.

  2. Select Language and click on OK.

  3. Click on Next in the Welcome to the installation screen.

  4. Click on Next in the End User Patent Agreement window.

  5. Accept the End User Agreement and click on Next.

  6. Change the Destination folder if required and click on Next.

  7. Select Install in the Ready to install program screen.

  8. Allow the installation to complete and click on Finish when done.

 

Configuring NTP settings on the ESXi host


ESXi uses the UTC time by default, and it's not possible to change the time zone on the ESXi host. To ensure that we maintain the correct time system across the environment, it is recommended to synchronize the ESXi host with NTP servers.

Getting ready

Before you start with the NTP configuration, make sure that you have the NTP server details and access to the ESXi host.

How to do it…

In order to configure the NTP settings, perform the following steps:

  1. Log in to the ESXi host using the vSphere Client.

  2. Under the Configuration tab, click on Time Configuration under Software.

  3. Click on Properties... on the top-right corner:

  4. Select NTP Client Enabled and click on Options..., as shown in the following screenshot:

  5. Under the General section in the left pane, select the appropriate Startup Policy as per your environment. VMware recommends that you choose Start automatically if any ports are open, and stop when all ports are closed:

  6. Select NTP Settings on the left pane, click on Add, enter the IP Address of your NTP source, and click on OK.

  7. Select Restart NTP service to apply changes checkbox and click on OK.

There's more...

Alternatively, the NTP setting can be configured using the PowerCLI cmdlet, Add-VmHostNtpServer, which will help us configure the NTP setting. Make sure you connect to the vCenter Server from PowerCLI and use the following command:

Add-VmHostNtpServer -NtpServer "IP Address" -VMHost (Get-VMHost)

As an alternative, you can connect to the ESXi host using PowerCLI and execute the following command:

Add-VmHostNtpServer -NtpServer "IP Address"
 

Configuring DNS and Routing


Similar to the other servers in the network, you need to make sure that the ESXi host is configured with the correct DNS server and Routing details so that you do not encounter any issues.

Getting ready

Make sure that you have the DNS and default gateway details before starting the configuration.

How to do it…

In this recipe, we will learn to configure DNS and its default setting using the vSphere Client.

Note

You need to manually create the DNS records for the ESXi host.

Now, let's see the steps involved in creating the DNS records:

  1. Login to the ESXi host using the vSphere Client.

  2. Select the Configuration tab on the right pane and click on DNS and Routing under Software.

  3. Click on Properties on the top-right corner of the screen.

  4. In the DNS configuration, review the current configuration and make the necessary changes, such as the hostname, Domain, DNS server, and search domain fields:

  5. Click on the Routing tab and make sure that the correct default gateway is listed. If required, make any relevant changes and click on OK:

There's more...

Alternatively, you can also configure DNS and Routing using DCUI by performing the following steps:

  1. Connect to the ESXi console and Press F2 to log in to DCUI.

  2. In the System Customization screen, move the cursor down and select Configure Management Network:

  3. Select IP Configuration and press Enter to assign an IP address for the ESXi host:

  4. If required, make the changes on the screen and press Enter and exit the screen.

  5. Now, you will be back on the Configure Management screen; scroll down to the DNS Configuration and press Enter to modify the DNS IP settings.

  6. You will be presented with the DNS configuration where you need to enter the DNS Server IP address and hostname of the ESXi host. When you have finished entering the details, press Enter to exit the screen.

  7. Now, you will be back on the Configure Management screen. Scroll down to Custom DNS Suffixes and press Enter to change DNS suffixes.

  8. In Custom DNS Suffixes, modify the suffixes as required, press Enter for OK, and exit the screen:

  9. Now, you need to save the configuration that has been changed, so from the Configure Management Network, press Esc to exit and you will be asked for confirmation on the Configure Management Network scene:

  10. Press Y to confirm the settings; this will save the settings and restart the management network to apply the configuration.

  11. You will then be back on the System Customization screen; if you want to make sure that the configuration is correct, you can perform the test management network operation. To proceed with the test, select Test Management Network and press Enter.

  12. The ESXi host will try to ping the DNS servers and the default gateway and resolve the configured hostname:

  13. Press Enter to proceed with the testing, and the test will show the status as OK or Failed. If you notice any failure, make sure that you have configured the correct settings.

 

Licensing an ESXi host


By default, when you install an ESXi host, it will run in the evaluation mode for 60 days. After this period, you need to assign a license key to the host. If you are using vCenter, the license management will be done at the vCenter level by adding the license keys on vCenter and assigning them to the appropriate ESXi host. If you have only a standalone ESXi host, then you have to assign the license directly on the ESXi host.

How to do it…

The following steps have to be performed in order to license an ESXi host:

  1. Connect to the ESXi host using the vSphere Client.

  2. Select the Configuration tab in the right pane and select Licensed Features under Software.

  3. Click on Edit on the top-right corner of the screen.

  4. Select the Assign a new license key to this host radio button:

  5. Click on Enter Key... and this will pop up an Add license key window, where you need to enter the license key.

  6. Click on OK in the Assign License Key window.

About the Authors

  • Mohammed Raffic Kajamoideen

    Mohammed Raffic Kajamoideen (@VMwareArena) is a subject matter expert for VMware virtualization technology and works as a system administrator in VMware Inc. where he provides high-level technical guidance to support and implement VMware's virtualization products. He is an author, a technology enthusiast, and a blogger focusing on virtualization and cloud computing.

    He has over six years of high-level knowledge in remote infrastructure services, consulting, designing, implementing, and troubleshooting VMware virtualization technology. He is well known for his contribution towards the virtualization community through his virtualization blog (http://www.vmwarearena.com).

    He holds many specialized certifications from VMware, Microsoft, and Citrix®, which includes VCP4, VCP5, VCAP4-DCA, VCAP5-DCA, VCP-Cloud, MCTS-virtualization, CCA, and MCSA. Prior to joining VMware, he has served other large organizations such as CGI, Infosys, and Microsoft as a virtualization support engineer and a subject matter expert.

    Browse publications by this author
  • Aravind Sivaraman

    Aravind Sivaraman is a virtualization engineer with over eight years of experience in the IT industry and for the past five years he has been focused on virtualization solutions, especially on VMware products. He holds different certifications from VMware, Microsoft, and Cisco and has been awarded the vExpert for the year 2013. He is a VMware Technology Network (VMTN) and Experts Exchange contributor and maintains his personal blog at http://aravindsivaraman.com/. He can be followed on Twitter at @ss_aravind.

    He is also the technical reviewer for the book Troubleshooting vSphere Storage, Mike Preston, Packt Publishing.

    Browse publications by this author

Latest Reviews

(2 reviews total)
Books never arrived, I was "RIPPED OFF AND SCAMED"
a handy way to get up to speed on vmware esxi and its capabilities
Book Title
Unlock this book and the full library for FREE
Start free trial