Unable to configure NTP from the Virtual Infrastructure Client

Symptoms

• During the configuration of NTP settings from the Virtual Infrastructure Client (VI Client) in VirtualCenter 2.5 configuration fails and the error failed to change host configuration is displayed.
  
  

Purpose

Overview

The ability to configure NTP from the VI Client has been added in VirtualCenter 2.5 and ESX Server 3.5.

Configuration of NTP from the VI Client fails if the ESX Server host is configured to use a non-standard timezone as listed in the timezone description file. For example, if your server is set to ETC/GMT-5 instead of America/New_York configuration of NTP fails.

Upon further inspection of the /var/log/vmware/hostd.log on the ESX Server host, warnings similar to the following are displayed:

• Timezone '' not part of the tz database using the default timezone UTC , where is the value of that is being used for the timezone. For example, ETC/GMT-5.
• Timezone 'UTC' does not exist in the tz database.

Resolution

Note: Before you begin please refer to KB1003490for important information on restarting the mgmt-vmware service.

Verification of the problem

To check which timezone is being used on the ESX Server host:

1. Log in to your ESX Server host as root from either an SSH session or directly from the console of the server.
2. Type cat /etc/sysconfig/clock.

An output similar to the following appears:

[root@server]# cat /etc/sysconfig/clock
ZONE="America/New_York"
UTC=true
ARC=false
[root@server]#

The timezone is listed in the ZONE= section of the output. Compare this value to the information listed in the TZ column of the /usr/share/zoneinfo/zone.tab file.

Note: All values are case sensitive. Ensure that the case is the same between the the clock file and the zone.tab file.

From the example above, when you look in the /usr/share/zoneinfo/zone.tab file, you see:

#country-
#code coordinates TZ comments
US +404251-0740023 America/New_York Eastern Time

If the value is not listed and you receive an error message, follow the steps in the workaround. If the value is listed in this file and you are still receiving this error message please contact VMware Support referencing this KB article for further assistance diagnosing the problem.

Workaround

To workaround this problem you need to ensure that your timezone is set to a value that is listed in the /usr/share/zoneinfo/zone.tab file.

Follow these steps to correct the behavior:

1. Log in to your ESX Server host as root from either an SSH session or directly from the console of the server.
2. Type less /usr/share/zoneinfo/zone.tab .
3. Review this file until you find the appropriate timezone. Take note of the value listed in the TZ column of this file. For example, America/New_York in the example listed in the verification section of this article.
4. Press the Q key to quit from less.
5. Type nano /etc/sysconfig/clock .
6. Change the ZONE= section of this file to be the value noted in Step 3.
   
   Note: All values are case sensitive. Ensure that the case is the same between the clock file and the zone.tab file.
7. Press Ctrl + X and save the changes when prompted.
8. Type service mgmt-vmware restart .
   
   Caution: Ensure Automatic Startup/Shutdown of virtual machines is disabled before running this command or you risk rebooting the virtual machines. For more information, see Restarting hostd (mgmt-vmware) on ESX Server Hosts Restarts Hosted Virtual Machines Where Virtual Machine Startup/Shutdown is Enabled (1003312) .

To Know Which Linux Distribution We Are Using

From the Boot Time messages
Fire up your favourite terminal program and type in the following

dmesg | head -1

Using /proc/version
In the terminal type

cat /proc/version

Using /etc/issue
This method gives the most appropriate answer

cat /etc/issue

FTP Automation

Make a text file that contains your ftp instructions...

OPEN my.ftp.com
mylogin
mypassword
binary
MPUT mylog.rar
BYE

Make a bat file that executes it...

ftp -i -s:C:\script_daily.txt

Fix for Login failed for user “. The user is not associated with a trusted SQL Server Connection:

To set the DisableLoopbackCheck registry key yourself, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.
2. In Registry Editor, locate and then click the following registry key:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. Right-click Lsa, point to New, and then click DWORD Value.
4. Type DisableLoopbackCheck, and then press ENTER.
5. Right-click DisableLoopbackCheck, and then click Modify.
6. In the Value data box, type 1, and then click OK.
7. Quit Registry Editor, and then restart your computer.

--------------------------------------

Wehould now find that the connection will complete successfully. Another place to check is in event viewer. For this particular error we had 3 events logged in event viewer:

1. Failure Audit :: Login Failed for user ‘\’. (CLIENT 127.0.0.1)

2. Error :: SSPI handshake failed with error code 0×8009030C while establishing a connection with integrated security; the connection has been closed. (CLIENT 127.0.0.1)

3. Failure Audit :: Login Failed for user “. (CLIENT 127.0.0.1)

--------------------------------------