Yellow Bricks

by Duncan Epping

4.1

VUM and MS SQL 2008 support

· ·

I received multiple questions around this so decided to ask around internally. I managed to get ahold of the VMware Update Manager (aka VUM) Product Manager and after exchanging a couple of emails this is the outcome:

VMware vSphere Compatibility Matrixes
Table 13 on page 14 of the above linked document states that VUM doesn’t support MS SQL 2008 Standard. This is however untrue and should be considered as a document bug. It is supported and the document will be modified soon to reflect these changes.

vCenter 4.1: this product can only be installed….

· ·

When installing vCenter 4.1 on Windows 2008 R2 64-bit one of my colleagues ran into the following error message:

This product can only be installed on the following 64-bit operating systems:
Windows XP SP2 or above
Windows 2003
Windows 2008

Although this message is actually correct it was not what was causing this problem as he followed the documentation and installed Windows 2008 64-bit. In this case Active Directory had been installed and that was the reason it was failing. As vCenter installs ADAM it can’t run on top of a server which hosts AD.

Workaround for: ESX(i) 4.1 Password Issue

· ·

As many of you already know there is an issue with the encryption mechanism of ESX(i) 4.1. When passwords are used which are longer than 8 characters the password will be truncated after the 8th character. As such during authentication only the first 8 characters are used. In other words if you have  a 10 character password you will only need to type the first 8 characters correct and the rest can be completely random.

The KB article that was published yesterday contains a workaround to change this behaviour. I recommend everyone to read the article and implement this workaround when your password policy describes passwords longer than 8 characters.

Cool vSphere 4.1 Feature: Cluster Operational Status

· ·

There’s a cool new feature added to vSphere 4.1 for HA. If an error occurs you can easily check what the issue is by going to your cluster and clicking the “Cluster Operational Issues” line on the Summary tab.

If there are no issues the screen will be completely gray. I forced an issue though so you can see what is shows. Note that is also shows the “Role” of the host and in this case it is a Secondary Node!

vSphere 4.1 HA feature, totally unsupported but too cool

· ·

Early 2009 I wrote an article on the impact of Primary Nodes and Secondary Nodes on your design. This was primarily focussed on Blade environments and basically it discussed how to avoid having all your primary nodes in a single chassis. If that single chassis would fail, no VMs would be restarted as one of the primary nodes is the “failover coordinator” and without a primary node to assign this role to a failover can’t be initiated.

With vSphere 4.1 a new advanced setting has been introduced. This setting is not even experimental, it is unsupported. I don’t recommend anyone using this in a production environment, if you do want to play around with it use your test environment. Here it is:

das.preferredPrimaries = hostname1 hostname2 hostname3
or
das.preferredPrimaries = 192.168.1.1,192.168.1.2,192.168.1.3

The list of hosts that are preferred as primary can either be space or comma separated. You don’t need to specify 5 hosts, you can specify any number of hosts. If you specify 5 and all 5 are available they will be the primary nodes in your cluster. If you specify more than 5, the first 5 of your list will become primary.

Please note that I haven’t personally tried it and I can’t guarantee it will work.