Virtualization Archives - Page 4 of 16 - Mind The Virtualization

Setting up an ODBC connection for Horizon View Composer

Last week I set up VMware Horizon View 6 with View Composer etc and ran into an issue with setting up a proper ODBC connection for View Composer.

Before actually setting up a new ODBC Data Source for VMware View Composer, you’ll need to create a user and password on your database server.

In my case, I used Microsoft SQL Server 2012 and used Microsoft SQL Server Management Studio to set up a new user for my Horizon View DB.

Let’s go through the steps to get everything set up:

Continue reading “Setting up an ODBC connection for Horizon View Composer”

VMware Tools Spamming Logs

I noticed the following message in one of my VM’s vmware.log:

2016-01-17T06:58:41.066Z| vcpu-2| I120: GuestRpc: Channel 2, conflict: guest application toolbox tried to register, but it is still registered on channel 0
2016-01-17T06:58:41.066Z| vcpu-2| I120: GuestRpc: Channel 2 reinitialized.
2016-01-17T06:58:41.066Z| vcpu-2| I120: GuestRpc: Channel 2 reinitialized.
2016-01-17T06:58:41.066Z| vcpu-2| I120: GuestRpc: Channel 2 reinitialized.

Continue reading “VMware Tools Spamming Logs”

Top 4 – ESXi one-liner scripts

bash-148836_960_720 I have caught myself quiet a few times running a bunch of one-liner scripts on ESXi.
Whether I setup ESXi, troubleshoot something or just test a feature, one-liners can often simplify whatever task you’re trying to complete.

Below is the list of one-liner scripts, which I use at least once a week.

Continue reading “Top 4 – ESXi one-liner scripts”

vSphere DRS Migration Thresholds

If you have vSphere DRS configured and you actively use it, you must have one of the vSphere DRS migration thresholds configured. Below is a list of each available vSphere DRS migration threshold and what it means.

Continue reading “vSphere DRS Migration Thresholds”

VMkernel TCP/IP Stacks Reviewed

What are the VMkernel TCP/IP Stacks?

Today, I would like to take a deeper look at the VMkernel TCP/IP stacks with you.
As you might know, the VMkernel networking stack handles standard system traffic to hosts. This includes, but is not limited to vSphere vMotion, vSphere FT, vSphere HA and VSAN.

When talking about different VMkernel TCP/IP stacks, VMware differentiates between 3 major TCP/IP stacks:

Default TCP/IP stack
vMotion TCP/IP stack
Provisioning TCP/IP stack

Let’s take a look at the details of each TCP/IP stack:

Default TCP/IP stack

Management traffic between ESXi hosts and vCenter server are considered as the default TCP/IP stack. Also, host related traffic like vMotion, NFS/iSCSI storage, HA and vSphere FT are part of it.

vMotion TCP/IP stack

By creating a VMkernel port on the vMotion TCP/IP stack you can isolate vMotion traffic to this stack. By doing so, vMotion traffic will be disabled on the default TCP/IP stack. The vMotion TCP/IP stack is used for live VM migrations.

VMware recommends configuring a separate vMotion TCP/IP stack and isolate management traffic from vMotion traffic.

Provisioning TCP/IP stack

The provisioning TCP/IP stack is used for cold VM migration, cloning and snapshotting traffic. In case of a long-distance vMotion (new in vSphere 6), NFC traffic can be configured to use the provisioning TCP/IP stack. Setting up a provisioning TCP/IP stack is useful when you want to isolate this traffic from other TCP/IP stacks. A dedicated provisioning TCP/IP stack is common in VDI environments and in setups with frequent VM snapshots.