Data Center & IT Infrastructure
Posted on 03.Jun 2010 by Ray Heffer in Business & IT
This is bit of a random post, but I wanted to share some of the reasons I joined IT in the first place. Lets face it, IT infrastructure hardware has evolved very well in the past 10 years. Pictured to the left is the HP c7000 blade chassis, and this was actually taken in March 2010 when I was rolling out VMware vSphere on HP BL460 G6 blades. What I like about the BL460 G6 is that it can run 6 x NIC’s (two on board and a four port card) in addition to an HBA mezzanine card. Top that off with excellent BladeSystem management, ILO and Insight Manager, you can’t get much better. These blades here have 48GB RAM per host and two quad-core Intel x5550 processors. At half-height, you can pack 16 of these in a single chassis. Excellent for consolidation, both in physical terms and virtual!
Hosting the Desktop Part 3: Planning Your Deployment
Posted on 31.Mar 2010 by Ray Heffer in Citrix, VDI, VMware, VirtualisationA few weeks ago I was reading about a recent VDI implementation that Lancashire Police had recently undertaken, where they deployed 4000 virtual desktops to address compliance issues. Their first step was to gain control of the desktop first, gaining an understanding of the applications used, and any bespoke or specialist applications being used. It is often the case that applications are installed that the IT department knows nothing about.
VMware ESX Error: Unable to connect to the MKS: vmx connection handshake failed for mks of…
Posted on 03.Mar 2010 by Ray Heffer in VMware, VirtualisationWhen you power on a virtual machine with VMware ESX VI3 or vSphere it may reach 95% progress in the tasks, but when you open the console you’ll notice the error: “Unable to connect to the MKS: vmx connection handshake failed for mks of /vmfs/volumes…”.
How To Fix Host Not Responding Error with VMware ESX, vSphere in vCenter
Posted on 05.Feb 2010 by Ray Heffer in VMware, Virtualisation
Virtualcenter looses connectivity to an ESX or vSphere host, and all of the virtual machines that are running on the host show as ‘disconnected’. You will also see that the host has ‘not responding’ in brackets next to it’s name.
This one is very simple to fix, as it is usually caused by the host agent service (mgmt-vmware) failing due to a dead process.
