Submitted by PhilEddies on Thu, 11/17/2011 - 22:22administrator | 4563 points
Recently I needed to install Citrix Web Interface 5.4 into a Network load balanced cluster on top of VMware vSphere. The installation are configuration went fine however I could not ping the cluster IP from a client machine but I could ping it from the NLB nodes.
The problem and solution seem to be common on the web however but I found most of the pages I looked at were a little confusing or missing some information, so I thought I would create my own.
This post will focus on setting up NLB within VMware and will not cover how to install and configure web interface.
Submitted by PhilEddies on Fri, 09/23/2011 - 15:21administrator | 4563 points
Recently I had a need to upgrade our VMware vCenter server from 4.0 to 4.1 and also as the current server was on a 32-bit OS I also needed to migrate to a new server so I started following the belowVMware KB article.
Submitted by PhilEddies on Wed, 10/01/2008 - 17:58administrator | 4563 points
If you have forgotten to enter the VLAN ID during the VMWare ESX or VSphere installed or you have entered the wrong VLAN ID you will find you will be unable to manage the VMWare host remotely, the only way to resolve this is to change the VLAN ID via the command line shell.
First you will need to log on locally to the server, the username will be root and you will have had to enter a password as part of hte install.
You will then need a couple of bits of information
Submitted by PhilEddies on Sun, 08/03/2008 - 21:11administrator | 4563 points
Restarting the VMware management service can resolve lots of problems mainly problem where the VMware Host cannot be contacted correctly by the vSphere Client, or a Virtual machine will not start or vmotion
Restarting the service does the same things as restarting the host but done properly it leaves the Virtual Servers running!