Potential System Impact From Leap Second On June 30, 2015 At 23:59:60 UTC

Asset ID:	1-77-1966268.1
Update Date:	2016-09-26
Keywords:

Solution Type Sun Alert Sure

Solution 1966268.1 : Potential System Impact From Leap Second On June 30, 2015 At 23:59:60 UTC

Applies to:

Oracle Communications EAGLE (Software) - Version ELAP 10.0 to ELAP 10.0 [Release ELAP 10.0]
Oracle Communications EAGLE (Software) - Version E5-MS 45.0 to E5-MS 46.0 [Release E5-MS 45.0 to E5-MS 46.0]
Oracle Communications EAGLE (Software) - Version EAGLE 44.0.0 to EAGLE 46.1 [Release EAGLE 44.0 to EAGLE 46.0]
Oracle Communications EAGLE (Software) - Version EPAP 14.0 to EPAP 16.0 [Release EPAP 14.0 to EPAP 16.0]
Oracle Communications EAGLE (Software) - Version LSMS 13.0 to LSMS 13.0 [Release LSMS 13.0]
Information in this document applies to any platform.

Description

A leap second is a one-second adjustment that is occasionally applied to Coordinated Universal Time (UTC) in order to keep its time of day close to the mean solar time. Without such a correction, time reckoned by Earth's rotation drifts away from atomic time because of irregularities in the Earth's rate of rotation. The purpose of a leap second is to compensate for this drift, by scheduling days with 86401 or 86399 seconds. Insertion of each UTC leap second is usually decided about six months in advance by the International Earth Rotation and Reference Systems Service (IERS).

A leap second will again be inserted at the end of June 30, 2015 at 23:59:60 UTC. This event can cause application and OS level malfunctions on systems with vulnerable operating systems. The table below presents the product matrix for generally availble software. Software that has reached its End of Life (EOL) has not been investigated for any possible vulnerability. Please upgrade to a supported release for continued reliable operation.

Product	TPD Release	Note
EPAP 14.0.0 - > EPAP 16.0.0	4.2.3 -> 5.5.0	No Vulnerability expected (1)
ELAP 10.0.0 -> ELAP 10.0.1	5.8 -> 5.10	No Vulnerability expected (1)
LSMS 13.0.0	5.5.0	No Vulnerability expected (1)
E5-MS 45.0.0 -> E5-MS 46.0	N/A	Please contact you OS Vendor to determine the leap second behavior.
EAGLE STP	N/A	Not Vulnerable

(1) No Vulnerability is expected for this product, but if an issue occurs, please consult the Recovery action section of the Alert.

Occurrence

This alert applies only to those systems that are configured with a NTP source.

Symptoms

Unusually high processor utilization or lockup after the leap second event.

Workaround

Preventive Actions:

This alert applies only to those systems that are configured with a NTP source.
Please use the command below, to determine if a valid NTP source is configured and being used.
Make sure that NTP is running correctly. Use ntpq –p command to reveal the sync status of NTP.

Sample output of ntpq –p command:

remote refid st t when poll reach delay offset jitter

===========================================================================

*ntpserver1 192.168.2.200 13 u 15 64 377 0.191 -137775 43.696

sync-a .INIT 16 u - 64 378 0.000 0.000 0.000

mate 127.0.0.1 13 u 58 64 4 0.001 2.808 0.001

Make sure to understand the system's time difference with GMT.
Make sure that the system is not running under heavy load between June 30, 23:45 PM and July 01, 00:30 GMT.
The leap second event will occur at June 30, 11:59:60 GMT. Post event i.e. at July 01, 00:00:00 ensure there should be no socket hang/coredumps/application/Database crash.

Recovery Actions (if required):

To recover the system from any of above mentioned issue, a reboot of the server will be required. The recovery time depends on size and applications loaded.
Ensure all necessary applications have fully recovered/restarted post reboot of the server.

History

30-01-2015 Initial Draft

Attachments

This solution has no attachment