Tag Archives: server

VMWare Tools 10 repository

Most of you may even know the old VMWare Tools repository.

https://packages.vmware.com/tools/esx/index.html

VMWare communicated that the new VMWare Tools 10.x will be developed independed of the vSphere enviroment. So from now on, you will not find anymore the latest tools at the above-mentioned link.

From now on, you can dowload the latest tool versions from here:

https://packages.vmware.com/tools/releases/index.html

vmware_repo

Click on the highest number folder or on the latest folder and you will be redirected to the newest tool version for each supported OS.

vmware_repo2

Regards

Why is the network loadbalancing policy so important?

Last week I returned from my vacation and had allready a lot of tasks waiting for me.

One of them was to add some new ESXi-server to a persistent cluster.

No problem, I thought. This will be a quick task after my vacation.

After looking on the persistent esxi hosts, i’ve seen that they use LACP/etherchannel as network configuration, a lot of VLAN tags and so on.

With this information I went to our network provider and gave him the needed information.

After a hour I recieved an email with the confirmation that  the network was ready.

So I installed the ESXi server, added two vmnics and changed the load balancing policy to “routed based on IP hash” what mean’s that with this configuration you can use LACP. (see KB2006129)

vswitch

Now I began to test the network by removing one vmnic and trying to ping the VMs on the ESXi server.

Every time I removed one vmnic, I loosed the connection to the VMs on the ESXi server. So i tried all possible configurations on the ESXi server but I never had a successful fail over on the network.

cmd

After trying everything on my site I was quite sure that the network guys did not configure the switchs as I’ve told them.

So I went there and we looked at the configuration. They did forgot to activate LACP/etherchannel on the ports. They had no port-channel configured. This was also the reason why I loosed each time the connection to the VMs when I removed one vmnic.

After they changed the configuration I tested it again and I neither loosed one ping when the network had to make a switch over.  This is how it is proposed to run!

While I was troubleshooting my problem I’ve found some interesting posts from other guys and from VMWare which I would like to share with you. They helped me to find out my problem.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2006129

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004088

and here my favorite one (only in German available):

http://www.admin-magazin.de/Das-Heft/2010/05/Redundante-Netzanbindung-mit-VMware-ESX

Hope this can help someone 🙂

vCenter Server Appliance in vSphere 6.0 (vCSA)

The vCenter Server Appliance was in older releases a nice feature that was never ended in development.

A lot of features and functions that you had with the Windows Server based vCenter server, were not possible with the appliance. So the appliance was only interesting for really small vSphere environments or for labs.

With vCSA 5.5 we were going better and better. But there were still some things that weren’t supported like:

  • Less scalability
  • Linked Mode
  • Heartbeat
  • IPv6
  • PowerCLI
  • VUM
  • 3d party software plugin

Now let me show you an actual chart from VMWare where they compare the vCSA with the windows based vCenter:

vCSA_6_0

As you can see, the vCSA has now the same scalability as the Windows based vCenter Server. Quite every feature is also integrated in the appliance.

So why we do not just use the appliance? Well there are unfortunately still some reasons for that we will need the Windows vCenter Server:

  • no MSSQL support
  • no Update Manager (the most critical point in my view)

I can’t understand why they don’t port the VUM to the vCSA. With those features on board, I’m quite sure that the Windows based vCenter will no more be used by SME’s with small vSphere environments.

For this I’m already curious to see the features that the new vCSA release will include and hope that this appliance is getting more and more important for vSphere and VMWare. This appliance will simplify many administrators life!