Field Notice: FN - 64244 - December 31, 2016 Leap Second Impact to Voice and Unified Communications Devices
Available Languages
NOTICE:
THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.
Revision History
| Revision | Date | Comment |
|---|---|---|
1.1 |
11-JAN-2017 |
Posted to Additional Product Pages on Cisco.com |
1.0 |
22-DEC-2016 |
Initial Public Release |
Products Affected
| Products Affected |
|---|
Cisco Finesse - 11.5(1), 11.0(1), 10.5(1), 10.0(1), 9.1(1), 9.0(1) |
Cisco Unified Intelligence Center - 11.5(1), 11.0(1), 10.5(1), 10.0(1), 9.1(1) |
Cisco Virtualized Voice Browser - 11.5(1), 11.0(1) |
MediaSense - 11.5(1), 11.0(1), 10.5(1), 10.0(1), 9.1(1) |
SocialMiner - 11.5(1), 11.0(1), 10.6(1) |
Unified Contact Center Express IP IVR - 11.5(1), 11.0(1), 10.6(1), 10.5(1), 10.0(1), 9.0(2) |
Cisco Identity Service (IdS) 11.5(1) |
Cisco Live Data 11.5(X), 11.0(X), 10.5(X), 10.0(X) |
Problem Description
An addition of one second to Universal Coordinated Time (UTC) causes the system clock used by the kernel to be out of sync with UTC by a second. The tzdata file can be updated in order to fix this issue.
Background
The U.S. Naval Observatory announced that a leap second will be added again on December 31, 2016 at 23:59:60 UTC. That means your day and year will officially be one second longer.
Problem Symptoms
The impact will be on reporting and other cron jobs scheduled on the server.
Impacts of Leap Second
- Impact to kernel - The leap second vulnerability detector script published by RedHat has exposed the kernel to be vulnerable and the impact could be none to as high as a kernel crash during the leap second transition period.
- Impact to application - Anomalies in reporting (could be a day off on scheduled reports) and scheduled cron job anomalies.
Workaround/Solution
All defects listed are an amendment to Leap Second Guide, Product Information, Voice and Unified Communication Devices.
Workarounds
Option 1
Turn off the server at the transition time of the leap second so the server kernels do not get impacted at the transition point. However, after this action there will be a one second drift with UTC permanently that will continue to exist.
Option 2
Break the connection with NTP before the leap second and restore it after the leap second. This could affect clustering and database replication.
Solution
Apply the leap second Cisco Options Package (COP) file posted in CCO for each of these versions for all the components. This COP file updates the tzdata to the latest version, 2016g and later, that has the fix for leap second 2016.
| Product Version | Location of Leap Second Fix | CDETS |
|---|---|---|
| Unified Contact Center Express/IVR | 9.0(2), 10.0(1): Location 10.5, 10.6, 11.0, 11.5: Location |
CSCvc22335 |
| SocialMiner | Location | CSCvc22333 |
| Cisco Unified Intelligence Center (CUIC) | Location | CSCvc22332 |
| Cisco Virtualized Voice Browser (CVVB) | Location | CSCvc22338 |
| Cisco Finesse | Location | CSCvc22336 |
| Cisco Live Data | Location | CSCvc22332 |
| Cisco IdS | Location | CSCvc22332 |
| MediaSense | Location | CSCvc22337 |
CDETS
To follow the bug ID link below and see detailed bug information, you must be a registered customer and you must be logged in.
| CDETS | Description |
|---|---|
| CSCvc22335 (registered customers only) | TZData Update for 2016g Changes and 2016 Leap Second |
| CSCvc22333 (registered customers only) | TZData Update for 2016g Changes and 2016 Leap Second |
| CSCvc22332 (registered customers only) | TZData Update for 2016g Changes and 2016 Leap Second |
| CSCvc22336 (registered customers only) | TZData Update for 2016g Changes and 2016 Leap Second |
| CSCvc22337 (registered customers only) | TZData Update for 2016g Changes and 2016 Leap Second |
| CSCvc22338 (registered customers only) | TZData Update for 2016g Changes and 2016 Leap Second |
For More Information
If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:
Receive Email Notification For New Field Notices
Cisco Notification Service—Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)