Search the VMware Knowledge Base (KB)
View by Article ID

Support for Leap Seconds in VMware Products (2115818)

  • 29 Ratings

Purpose

This article was created to advise on what preparations VMware recommends to avoid being impacted by the Leap Second.

A leap second is a one-second adjustment that is occasionally applied to Coordinated Universal Time (UTC) in order to correspond to the mean solar time. An adjustment of +1 second took place on 23:59 UTC on the 30th June 2015.
The change was carried out globally and simultaneously at the UTC scheduled time, adjust accordingly for your timezone. For example, the leap second change took place at 19:59 in Eastern Standard Time.

Only systems configured as Network Time Protocol (NTP) clients were potentially affected, as they received a NTP packet with a leap second flag on the day of the adjustment.


Resolution

Note: As the leap second change has now taken place there is no requirement to take any action. Subsequently, the KB articles published for individual products have now been archived.

For customers with valid current Support and Subscription services contracts for a product, VMware will, subject to the terms and conditions for its Support and Subscription services, provide telephone or web-based technical assistance to customer’s technical contact(s) with respect to technical product problems for those products, at the corresponding services level purchased by customer.

VMware recommends customers test their complete solutions.

Product Version Issue Recommendation
vCenter Server Appliance 5.0
Uses SUSE Linux Kernel kernel-default-base-2.6.32.29-0.3.1.x86_64.rpm
Enable Slew Mode
vCenter Server Appliance 5.0 U1b
Uses SUSE Linux Kernel kernel-default-base-2.6.32.29-0.3.1.x86_64.rpm Enable Slew Mode
vCenter Server Appliance 5.0 U2 Uses SUSE Linux Kernel kernel-default-base-3.0.38-0.5.x86_64.rpm Enable Slew Mode
vCenter Server Appliance 5.1.0a Uses SUSE Linux Kernel kernel-default-base-3.0.34-0.7.9.x86_64.rpm Enable Slew Mode
vCenter Server Appliance 5.1.0b Uses SUSE Linux Kernel kernel-default-base-3.0.34-0.7.9.x86_64.rpm Enable Slew Mode
vCenter Server Appliance 5.5.x Enable Slew Mode
vSphere Replication Appliance 6.0.0 Uses SUSE Linux Kernel kernel-default-base-3.0.101-0.46.1.rpm and runs NTP client Upgrade to vSphere Replication 6.0.0.1 or later
vRealize Hyperic 5.0.0 2.6.32.59-0.7-default Upgrade to the latest version.
And then Enable Slew Mode
vRealize Hyperic 5.0.3 3.0.101-0.35-default Upgrade to the latest version.
And then Enable Slew Mode
vRealize Hyperic 5.7.0 2.6.32.59-0.7-default Upgrade to the latest version.
And then Enable Slew Mode
vRealize Hyperic 5.7.2 3.0.101-0.35-default Enable Slew Mode
vRealize Hyperic 5.8.0 3.0.80-0.7-default Enable Slew Mode
vRealize Hyperic 5.8.4 3.0.101-0.40-default Enable Slew Mode
VMware vRealize Log Insight 2.0.5 SuSE 11 SP3 3.0.101-0.15-default Enable Slew Mode
VMware vRealize Log Insight 2.5 SuSE 11 SP3 3.0.101-0.46-default Enable Slew Mode
vCloud Networking And Security All builds Enable Slew Mode
vSphere Big Data Extensions 2.1.0 CentOS kernal 2.6.18-371.12.1.el5 Apply patch, BDE-2.1-2.0-Patch-LeapSecond .tar
vSphere Big Data Extensions 2.0.0 CentOS kernal 2.6.18-371.12.1.el5 Apply patch, BDE-2.1-2.0-Patch-LeapSecond .tar
vCenter Site Recovery Manager / vSphere Replication 6.0.0 SUSE Linux Kernel kernel-default-base-3.0.101-0.46.1.rpm and runs NTP client Enable Slew Mode
vCenter Site Recovery Manager / vSphere Replication 5.8.0.2 Uses SUSE Linux Kernel kernel-default-base-3.0.101-0.31.1 Enable Slew Mode
vRealize Automation
(Including vRealize Code Stream)
6.0 Enable Slew Mode
vRealize Automation
(Including vRealize Code Stream)
6.0.x Enable Slew Mode
vRealize Automation
(Including vRealize Code Stream)
6.1 Enable Slew Mode
vRealize Automation
(Including vRealize Code Stream)
6.1.x Enable Slew Mode
vRealize Automation
(Including vRealize Code Stream)
6.2 Enable Slew Mode
vRealize Automation
(Including vRealize Code Stream)
6.2.1 Enable Slew Mode
vRealize Infrastructure Navigator All builds SUSE Linux Enterprise 11 SP1 for VMware(64-bit) to SP3 Enable Slew Mode

Impact/Risks

Failing to prepare adequately for the leap second addition can cause some issues to manifest. For example:
  • The underlying kernel can become hung and require a reboot due to a deadlock as queued process have the same time-stamp.
  • The Java environment(s) may not handle the leap second processing correctly resulting in 100% CPU usage. This can potentially cause the service to hang or crash.
  • When slew mode is not enabled, services may not handle a 60 second time-stamp, that is 23:59:60.

Additional Information

This article will be updated as more information becomes available.

To be alerted when this article is updated, click Subscribe to Document.

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 29 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 29 Ratings
Actions
KB: