Yellow Bricks

by Duncan Epping

esxi

FT_HOSTS, where is it in ESX 3.5 U2?

· ·

This seems to be High Availability day! I was just testing my previous blog when I discovered a weird DNS or host file related error. So I opened up my console and typed “vi /etc/FT_HOSTS”. “vi” opened a blank file and reported back “new file”. What the heck, so I did a find and found that the FT_HOSTS file has been relocated to: /etc/opt/vmware/aam/. So if you’re looking for FT_HOSTS….

And for ESXi, you should be looking here “/var/run/vmware/aam/” by the way.

Response on the DABCC VMware HA vs Citrix HA article

· ·

I clearly don’t know much about Citrix version of HA, but I do know a thing or two about VMware’s version of HA.

The following are outtakes of the article over at DABCC:

VMware’s HA is heavily dependent on DNS or alternatively hosts entries being in place. The VMware implementation is based on the Legato Automated Availability Management (AAM), in fact some of us will recall that it used to place those logs into /opt/LGTOaam512/logs/ (since 3.5 this has been moved /opt/vmware/aam).

VMware’s HA uses the network to establish a heartbeat between all the ESX Hosts participating, So practically, what does this mean to the poor bloke who has to support the servers? If you network has a bit of a flap (personally I always blame the Network guysJ), your servers will implement an “isolation response”, the default server response will shut down your Virtual Machine to release the shared storage locks, this will allow the machine to be restarted on another host, this of course may not be desirable if the server is busy doing something, i.e. you may cause corruption or other issues with the Application/Database. In other words it won’t perform a clean shutdown. This is configurable such that you can keep the machines powered on, but this isn’t recommended in the case of NAS or iSCSI (as they are also network dependant) and you may end up with a split-brain situation.

There is now also experimental support for component level HA, i.e. if a Virtual Machine fails, then VMware will try to restart it.

  1. As of ESX 3.5 U2 High Availability doesn’t heavily lean on DNS anymore, it gets its hostname and ip info from VirtualCenter.
  2. ESX 3.5 U2 gives you the possibility to cleanly shutdown a VM in case of an isolation.
  3. Normally one would indeed provide it’s SC with redundancy, and preferably via two separate switches to avoid the problems you are describing.
  4. Virtual Machine High Availability isn’t experimental anymore as of ESX 3.5 U2.

ESX vs ESXi

· ·

I’ve had this question about a kazillion times by now, what’s the difference between ESX and ESXi. How do they compare… Can I do this with ESX, can I do that with ESXi.

Here’s the answer! This KB article contains a table with features and a description of what you can and can’t do in VirtualCenter. Check it out, it’s definitely worth reading.

And in addition to that, it is possible to do most configurations post installation via powershell. Check this topic on the VMTN forum by Lance!

Why I dislike agents in my Service Console

· ·

I’ve never been a huge fan of agents in the Service Console. Too many times I’ve seen hosts fail because of an agent that had a memory leak etc. Now it seems that running the HP IM agents causes your ESX 3.5 U2 to become unavailable after a certain amount of time.

The errors that appear:

0 Z root 8536 3673 0 79 0 – 0 nct> Aug05 ? 00:00:00 cimservera
0 Z root 8537 3673 0 79 0 – 0 nct> Aug05 ? 00:00:00 cimservera
0 Z root 8543 3673 0 78 0 – 0 nct> Aug05 ? 00:00:00 cimservera
0 Z root 32350 3673 0 79 0 – 0 nct> Aug06 ? 00:00:00 cimservera
0 Z root 32351 3673 0 79 0 – 0 nct> Aug06 ? 00:00:00 cimservera
0 Z root 32352 3673 0 79 0 – 0 nct> Aug06 ? 00:00:00 cimservera
0 Z root 32353 3673 0 78 0 – 0 nct> Aug06 ? 00:00:00 cimservera

HStrydom on the VMTN forum posted the following:

I am having the same issue. What happens after 17 days is that there are about 32000 of these processes. ESX has a max value of +- 32000 PID’s. Thus when all have been used up, one cannot SSH into the server, log in from the console or the ESX server disconnects from VC.

Also we have HP servers with the HP agents loaded. Our Dell servers does not have this problem.

Have a look at your cron log, /var/log/cron & cron.1. you might see that some of the job have not run. Also look in your /var/log/messages. There is a lot of login failures.

In other words, if you see the same thing happening call HP and let’s hope they release a fix soon! And in the meanwhile start thinking about ESXi, it’s problems like these that makes you think about why you even need a Service Console in the first place.