BNS Platform Hardware
 
Tekelec Service Broker
 
Oracle Communications Policy Management
 
Tekelec SIP Signaling Router
 
Oracle Communications Subscriber Data Management (SDM)
 
Oracle Communications Diameter Signaling Router (DSR)
 
Tekelec HLR Router
 

PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec DSR
 

In this Document

Description

Occurrence

Symptoms

Workaround

History

Applies to:

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 available 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.

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

(2)        Software that has reached its End of Life (EOL) has not been investigated for any possible vulnerability. 

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 –np command to reveal the sync status of NTP.

Sample output of ntpq –np command:

ntpq -np

     remote           refid      st t when poll reach   delay   offset  jitter

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

*xx.xxx.xxx.xx   xx.xxx.xx.xx     3 u   19  128  377    0.064    0.077   0.063

Ensure the * exist in front of one of the NTP addresses IPs. 

Note: the above output is only a sample. 

• Make sure to understand the system's time difference with GMT.
• The leap second event will occur at June 30, 11:59:60 GMT. Post event i.e. at July 01, 00:00:00.

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

 24-MAR-2015 Initial Draft Document.

This solution has no attachment