Oct
6
2017

Testdrive Infinio Accelerator 3.0

Nowadays, many legacy storage devices (SAN/NAS) have the option for hosting flash devices in their solution. Flash devices leverage high IOPS and low latency.
Most common used storage protocols (iSCSI, NFS and even Fiber Channel) are bandwidth optimized, and are not latency optimized. Of course Fiber Channel (FC) has a lower latency, as Ethernet based protocols like iSCSI and NFS. But still remote device will have a higher latency as local devices. In this blog post from Mellanox, they explain why FC is doomed according to them.

In the past I wrote a blog post explaining why you want your flash devices as close as possible to your applications. Hence why Hyper Converged Infrastructure (HCI) are so popular nowadays.

But what if you have a legacy storage solution, and still want low latency for your applications?

Continue Reading »

Sep
7
2017

VMworld 2017 US Recap

This year, I was rewarded with a blogger pass for VMworld.

In this blogpost I want to highlight, what was striking to me.

Solutions exchange

Every year I like to walk around the Solution Exchange, talking with vendors and learning about their solutions.
What was surprising to me this year, was the size and the quality of boots. Comparing to other VMworld, the boots where much larger and had more lighting and some of the even LED screens. I know that the development and a spot on the Solution Exchange is not cheap, so clearly these vendors see the importance of being present and want to invest in an event like VMworld.

Sessions

I’ve attended a couple of sessions, as most session are recorded and can be watched online after VMworld. The sessions I’ve attended, these sessions were striking to me.
Most of these session will also be in VMworld Barcelona.

Continue Reading »

Aug
3
2017

VMworld US 2017

VMworld US is in a few weeks. This year I have been lucky to get a blogger pass from VMware. Every year I go to Barcelona, and if I can, also to VMworld US. For me VMworld US is more interesting. Why?

One of the main reason why go to VMworld, is the Solution Exchange (SOL). The SOL is a great place to meet a lot of different vendors who add value to the VMware portfolio. Talking with the people from the traditional vendors, is always great. You get a good understanding what they’re up to. What will be available in the near future, and their future roadmaps (nothing guaranteed of course).

Continue Reading »

May
23
2017

Migrating a datacenter with PowerCLI – Introduction

For the last few months, I have been working on a project to migrate 1000 virtual machines from one datacentre to another datacentre. Both datacentres are 50KM in distance from each other. The building where the source datacentre is situated, will be stripped and will be rebuild conform current standards.
This means that every window, door, wall and all cables will be removed.
You can imagine that moving all the physical hardware (3 blades chassis, 42u of storage hardware and physical switches) and virtual machine from one datacentre to another datacentre is a huge operation. Because the virtual machine hosted in this datacentre are running production workloads, user impact should be minimal, and if user impact is expected, and migrations should be done during maintenance windows.
Both datacentres have their own vCenter servers (6.0), multiple vSphere (6.0) clusters and storage (Fiber Channel), and are connected at L2 level. The vCenter servers are members of the same SSO domain.[expand title=”Read more…”]
Because of this, I can use long distance vMotion to move the virtual machines from one datacentre to the other datacentre.
Of course, this can be done, using the vSphere web Client, but because of the number of virtual machines, we decided to write a Powershell script, that will do the job for us.
This script is scheduled to run during maintenance hours, and will read text file (batchXX.txt) to determine which virtual machines should be migrated.

In this blog series, I will explain the PowerCLI script I created, step by step, and eventually, how the migration went.

Table of content
Introduction
Chapter 1: Log function
Chapter 2: Notifications
Chapter 3: Reading VM attributes
Chapter 4: Storage space
Chapter 5: Move-vm
Chapter 6: Testing
[/expand]

May
5
2017

Install VMware PSC fails: vdcsetupldu failed. Error [9234] – User invalid credentials

I was setting-up a redundant VMware PSC setup stretching 2 datacenters. Every datacenter has 2 PSC and an load balancer.

Eventually, the virtual machines who run the PSC services, will run in a management cluster consisting of 3 nodes. These nodes are using Virtual SAN (VSAN) for storage.

I first installed 1 node with VMware vSphere and created on one of the SAS disks a datastore. Later on, the VMs will be moved to a VSAN datastore.

The first datacenter went as expected. No problems. But the second datacenter the installation of the PSC software failed with an error: Encountered an internal error
[expand title=”Read more…”]
PSC Error

Looking in the logfile vmafd-firstbood-py-xxxx_stderr.log, vdcsetupldu failed with Error [9234] – User invalid credential

PSC Error

I was sure that the password provided was ok. Diving deeper into the log files, I found that after installation, VMware Identity services starts and the install tries to make a LDAP connection on TCP 389, who would fail. I created a PowerShell script that would check TCP 389 every 5 seconds. I find out that eventually, I could make a connection on TCP 389, but the install already gave up.

Ok, so the services will start, but too late.

Looking at ESXTOP (best troubleshooting program for ESXi), I saw, that when the VMware Identity services start, the disk latency went up to 100ms. Could it be that the disk is slowing down the virtual machine, so that the installation would fail? I moved the virtual machine to a SSD disk, restart the installation, and guess what. Install successful.

So, probably the PSC installation program does not check if the service is available, before trying to login. I will fail, saying that the credentials are not valid, rather than saying that it cannot make a connection.[/expand]