PDF(242.6 KB) View with Adobe Reader on a variety of devices
ePub(234.7 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(150.9 KB) View on Kindle device or Kindle app on multiple devices
Updated:May 13, 2021
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes the known issue of TFTP service core in Cisco Unified Communications Manager (CUCM) versions 11.5.1 SU7 and 11.5.1 SU8 that require a workaround to fix the issue.
There are no specific requirements for this document.
The information in this document is based on Cisco Unified Communications Manager (CUCM).
CUCM TFTP Service cored once the server clocks the time 00:00 2021
You will receive an alert in the RTMT for TFTP service going down and below are some steps to identify the issue.
Jan 1 00:03:19 ucm-pub local7 6 : 898: ucm-pub.ciscolab.com: Jan 01 2021 07:03:19.321 UTC : %UC_GENERIC-6-ServiceStopped: %[ServiceName=Cisco Tftp][AppID=Cisco Service Manager][ClusterID=][NodeID=cap-86-pub.bldr-caplab.com]: Service stopped.
Jan 1 00:03:21 ucm-pub local7 6 : 899: ucm-pub.ciscolab.com: Jan 01 2021 07:03:21.346 UTC : %UC_GENERIC-6-ServiceStarted: %[ServiceName=Cisco Tftp][ProcessID=6803][AppID=Cisco Se
From Server CLI:
Login to CUCM(TFTP) server and run the command utils core active list. the output will show multiple CTFTP cores.
Run the command "utils core active analyze <core name>"
The output(backtrace) of the core should match with below.
#0 0x07adc3e8 in fputs () from /lib/libc.so.6
#1 0x0876cd38 in SdlSystemLog::writeToFile (this=0xf4a02930,_traceLinePnt=0xf4a05ba0) at SdlSystemLog.cpp:1971
#2 0x0876ce54 in SdlSystemLog::writer (this=0xf4a02930) at SdlSystemLog.cpp:1919
#3 0x0078dbc9 in start_thread () from /lib/libpthread.so.0
#4 0x07b5e07e in clone () from /lib/libc.so.6
Cisco CUCM Syslogs
Jan 1 00:03:19 ucm-pub local7 6 Cisco: Tftp: DBL SDI Initialization successful
Jan 1 00:03:19 ucm-pub local7 6 Cisco: Tftp: SysLevel  UserMask  Enable [TRUE] File [/var/log/active/cm/trace/dbl/sdi/dbl.log]
Jan 1 00:03:20 ucm-pub local7 4 Cisco: Tftp: SDIDBConfigData::Read failed to retrieve SDI folder location, will use location in DB. ServiceID=1, NodeName=ucm-pub.bldr-caplab.com
Jan 1 00:03:24 ucm-pub local7 6 Cisco: Tftp: DBNotify SDI Initialization successful
CUCM Cisco TFTP SDL Logs
SDL001_600_000103.txt:00913050.000 |00:03:17.708 |AppInfo | TID[f660e740] CServiceModule::waitForSignals() TID[f660e740] Signal Received to QUIT, quitting.
Note: After DST update, TFTP service will restarted and no core is observed which is by design.
The core is happening when it tries to write something in the trace file. This may also result in the ability of the TFTP service to start.
Below are the steps.
Step 1. Set os to permissive mode by running "utils os secure permissive" with either Trace settings on or off.
Step 2. Restart/Start TFTP service from Serviceability.
Step 3. Move back the cluster to Enforcing using "utils os secure enforce".
This issue is documented by Cisco bug ID CSCvw94324
Note: Workaround is temporary, Since this issue is being investigated by Cisco Engineering team.