IBM Support

Time set clock CLI command does not set the time on Cast Iron Hypervisor Edition running VMware

Troubleshooting


Problem

When you attempt to change the time using the command line interface (CLI) on a Cast Iron Hypervisor Edition appliance running VMware tools, the time doesn't change. Following is an example: hostname/Standalone> time show Time Zone: GMT Local Time (GMT): Wed Jul 27 14:41:19 2011 UTC: Wed Jul 27 14:41:19 2011 hostname/Standalone> time set clock Sat Jan 1 00:00:00 2005 hostname/Transitioning> Broadcast message from root@civ1m.hursley.ibm.com (unknown) at 0:00 ... The system is going down for reboot NOW! hostname/Standalone> time show Time Zone: GMT Local Time (GMT): Wed Jul 27 14:44:49 2011 UTC: Wed Jul 27 14:44:49 2011

Resolving The Problem

To resolve this issue:

  1. Run NTP on the host. (This is a best practice). The host should have the proper time and is especially important considering the one-time-setting behavior with VMware tools.
  2. Run NTP on the guest. This is a recommendation from VMware and testing confirms that this is a best practice. Doing so prevents time drift on long-running VMs.
  3. Avoid time set clock in favor of NTP. You can use time set zone. The time zone is a user convenience and does not affect system behavior. System time is always UTC.

[{"Product":{"code":"SSGR73","label":"IBM Cast Iron Cloud Integration"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Not Applicable","Platform":[{"code":"PF009","label":"Firmware"}],"Version":"6.0.0.4","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 June 2018

UID

swg21566771

Page Feedback