I’m hoping to start studying for the VMware VCDX exam process so I did a little research on getting a home VMware Virtual Infrastructure environment setup.
Configuration of NTP is an often overlooked step in setting up a VMware ESX environment. It is important to keep accurate time not only on the guests but also on the hosts. In the 3.5 release of ESX you can configure NTP from the VI Client, but some older releases require configuration from the Service Console. Here are the steps involved in NTP configuration from the Service Console.
For the most part working with networking in a VMware Infrastructure environment can be easily done through the Virtual Infrastructure Client. However, sometimes the need arises to change the IP address of the Service Console. While you can go the route of creating a new Service Console port and removing the old one, I find it easier to change the IP details on the original Service Console port from the actual server console.
I used this to upgrade an ESX host from 3.0.1 to 3.0.2. It is likely that the same procedure can be used with future releases. Use caution when upgrading production servers as this procedure DOES take the host offline.
There are some new features on the horizon for the VMware Virtual Infrastructure in the latest releases of ESX 3.1 and VirtualCenter 2.1. Although we haven’t officially seen anything on these releases the buzz is that we can expect to see some if not all of the following.
No matching cipher found: client aes256-cbc,aes128-cbc server 3des-cbc