Archive for VMware

vSphere 5 Standard vSwitch Multi NIC vMotion Setup

vSphere 5 offers the new feature of Multi NIC vMotion allowing you to push vMotion traffic simultaneously down more than a single NIC. In previous releases of vSphere, only a single NIC would ever be used even if multiple NICs were part of a network teaming policy.

To configure Multi NIC vMotion, simply follow the below steps:

Step 1. Under the Configuration tab of a host, click Networking then select Add Networking. Select the option VMKernel and click next, select the network adapters you want to use for vMotion and click next.

Step 2. When presented with the below screen, enter a network label for this first VMKernel port, for example “vMotion-1” and check the box “use this port group for vMotion” and click next.

Step 3. On the next screen enter the IP address and subnet mask for this first VMKernal port and click next, then click finish. This will now create the vSwitch with the first port group and assign the two chosen virtual adapters to the switch.

Step 4. When the vSwitch has finished building, click the Properties button for the switch and you will be presented with the below screen. Click the Add button and go through creating a second VMKernel port for vMotion as you did in the previous steps.

Step 5. Once you have created your second VMKernel port, go back to the vSwitch properties windows, select the first vMotion VMKernel port and click edit.

Step 6. Click the NIC Teaming tab, then under Failover Order, check the box “Override switch failover order”. The NIC teaming options will now become available as shown below.

Step 7. In the NIC teaming policy editor, ensure only one NIC is moved under Active Adapters and any others placed under Standby Adapters. Once completed, click OK and the changes will apply. This will force this VMKernel port to only use a singular NIC in the networking team.

Step 8. Follow steps 5 to 7 for the second VMKernel port and remember to invert the NIC teaming policy from what you set for the first VMKernel port. For example, if vMotion-1 has vmnic1 as active and vmnic2 as standby, vMotion-2 should have vmnic2 as active and vmnic1 as standby.

The configuration of Multi NIC vMotion is now complete and you should experience much fast vMotion operations. To confirm your setup is working correctly, examine the performance statistics for the virtual adapters you chose during the setup, and issue a vMotion operation. You should see simultaneous active across all NICs.

Copy and Paste Through A Virtual Machine Console

This post will detail how to enable the copy and paste function through a VMware virtual machine console.

Step 1. Power down the virtual machine you want to enable copy and paste for.

Step 2. Edit the virtual machine settings and navigate to the Options tab, then click General under Advanced. On the bottom right of the options screen, click Configuration Parameters.

Step 3. In the Configure Parameters option window, click Add Row to create a new configuration entry.

Step 4. Create two entries with the following Names and Values:    false   false

Note, this feature only allows you to copy and past text from your clipboard. This unfortunately does not allow you to copy files through the virtual machine console. If this is what you are trying to achieve, I would recommend using a similar method I use of creating an ISO of your files using CDBurnerXP (very easy to use) and attach the ISO to your virtual machine.

Thanks for reading.

How To Install VMware Tools Without Rebooting

This post will detail how to upgrade VMware tools on virtual machines without having to reboot by using PowerCLI. Personally I have found this quite useful when having to upgrade VMware tools on production servers that require 24×7 up time. I have tried this update method on Windows Server 2008/R2 and RHEL 5/6 with success.

First you need to connect to your vCenter server via PowerCLI and choose one of the two methods of deployment detail below.

Upgrade VMware tools on a singular virtual machine:

Get-VM “yourvm” | Update-Tools –NoReboot

Upgrade VMware tools on all virtual machines:

Get-VM | Update-Tools –NoReboot

Thanks for reading and remember to lookout for my other posts on PowerCLI.

How To Export PowerCLI vCenter Reports

This is a quick post on how to generate some reports from vCenter through PowerCLI.

Log in to your vCenter server via PowerCLI and run a report of your choice:

Virtual Machine Report:

Get-VM | Export-Csv -Path “c:\vmreport.csv”

Snapshot Report:

Get-VM | Get-Snapshot | Export-Csv -Path “c:\snapshotreport.csv”

Datastore Report:

Get-Datastore | Export-Csv -Path “c:\datastorereport.csv”

Host Report:

Get-VMHost | Export-Csv -Path “c:\hostreport.csv”

Cluster Report:

Get-Cluster | Export-Csv -Path “c:\clusterreport.csv”

Thanks for reading.

Connect All Virtual Machine Network Adapters With PowerCLI

In this post I will explain how to run a PowerCLI command to connect or disconnect all virtual machine network adapters. Recently I experienced a power failure in one of my data centres that took out one of my SANs as well a host that held my vCenter server. When the kit was powered back on and vCentre was responding, an odd occurrence took place where all virtual machines managed by this vCenter server had the “Connect On Power On” check box enabled but the “Connected” check box wasn’t. At the time the only way to rectify this issue was to manually go though each virtual machine and check the box for the adapter to be connected. Not a fun experience.

To avoid the requirement for manual intervention to solve this issue for each virtual machine in the future, I have put together a PowerCLI command that will run though all virtual machines and connected their respective network adapters.

To do so, first load PowerCLI and connect to your vCenter server with the following command:

Connect-VIServer -Server vcenter.domain.local  -User domain/usernamePassword yourpassword

Following this, run the below command. This will run through all virtual machines managed by vCentre and connect network adapters 1 and 2. You can add additional adapters to be connected by simply adding more into the command e.g. “Network adapter 3″,”Network adapter 4” etc.

Get-VM | Get-NetworkAdapter -Name “Network adapter 1″,”Network adapter 2” | Set-NetworkAdapter -Connected:$true -Confirm:$false

I hope you found this post useful, and remember to look out for my future posts on PowerCLI.

VMworld 2011 Photos

Below are some photos i took during my time at VMworld 2011 in Copenhagen.



Installing VMware Tools in Linux Command Line (CLI)

This post details how to install VMware tools through a Linux command line by auto mounting the tools ISO through the vSphere client.

Step 1. Click right on your Linux virtual machine, highlight guest and click ‘Install/Upgrade VMware Tools’.



Step 2. Run through the below commands to extract and run the installation.


mount /dev/cdrom /mnt/

tar -C /tmp -zxvf /mnt/VMwareTools-5.5.3-34685.tar.gz      //Press tab for file name

umount /mnt

cd /tmp/vmware-tools-distrib



Step 3. Press enter to all the default options.

Once rebooted, VMware tools will be installed.

Installing VMware ESXi on VMware Workstation

Installing ESXi on VMware Workstation  is a great way of building a test lab for a vSphere infrastructure. Emulating ESXi in Workstation offers pretty much all the functionality you would have from an installing directly on you hardware minus the performance benefits. The following video demonstrates how easy this installing is to complete, and begin the steps on build a fully function VMware vSphere test lab. Take a look at ‘Initial ESXi Configuration Guide’ which follows on from this post.


Initial VMware ESXi Configuration Guide

After installing the ESXi hypervisor, the network configuration options need setting to allow any connection from the vSphere client. To do so, the management password should first be changed from its default of being blank. Following this the network management options can be configured as demonstrated ion the below video guide.