Guest

Preview Tool

Cisco Bug: CSCup37304 - SDL Link Delay and Core on SdlLinkHandler - caused by SNFSubscribeReq

Last Modified

Jul 13, 2018

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

9.1(1.20000.5)

Description (partial)

Symptom:
-ccm process CPU spikes abruptly.
-sdl link in and out signals from the node, appear to be VERY delayed and will get progressively worse as the queues back up further. Happens for all sdl link communication on the affected node. with delay between 5-30 seconds in both directions (in and out)
- However, actual network delay (if you were to take a pcap) does not show any delay.
- no SDL link oos is seen
- other tcp communication on that node is fine.

If Callmanager core is seen than the following backtrace is generated:

backtrace
 ===================================
 #0  0x007ae206 in raise () from /lib/libc.so.6
#1  0x007afbd1 in abort () from /lib/libc.so.6
#2  0x0a4c07ca in SdlMsgQueueCirc::enqueueSignal (this=0xc567ad0, msg=0x951ed730, priority=3) at SdlMs.cpp:140
#3  0x0a4a3e0c in enqueueSignal (this=0xc567928, rSignal=0x951ed730) at /view/BLD-cm_respin_9_1_1-cct-ccm/Common/Include/Sdl/SdlMsgQueue.hpp:66
#4  SdlThreadedProcess::inputSignal (this=0xc567928, rSignal=0x951ed730) at SdlThreadedProcess.cpp:171
#5  0x0a454020 in SdlLinkControl::enqueueSignal (this=0xc567928, sdlSignal=0x6) at SdlLinkControl.cpp:
#6  0x0a479d5f in SdlRouter::enqueueSignal (this=0xc576080, sdlSignal=0x951ed730) at SdlRouter.cpp:298
#7  0x0a4732d7 in SdlProcessBase::prepareSignal (this=0xc567928, _sdlSignal=..., _signalPriority=@0x77stPID=...) at SdlProcessBase.cpp:194
#8  0x0a472b25 in SdlProcessBase::output (this=0xc567928, rSignal=..., rProcessId=..., _signalPriorityiority) at SdlProcessBase.cpp:236
#9  0x0a4bac84 in SdlLinkHandler::enqueue (this=0x9888ef60, sdlSignal=0x6c0fc860) at SdlLinkHandler.cp
#10 0x0a4b7a61 in SdlLink::send (this=0xa2aa1ee8, sdlSignal=0x6c0fc860) at SdlLink.cpp:81
#11 0x0a4544e6 in SdlLinkControl::send (this=0xc567928, sdlSignal=0x6c0fc860) at SdlLinkControl.cpp:10
#12 0x0a47a041 in SdlRouter::scheduler (this=0xc576080) at SdlRouter.cpp:205
#13 0x0a47a58f in SdlRouter::schedulerInit (sdlRouter=0xc576080) at SdlRouter.cpp:107
#14 0x004b16e1 in start_thread () from /lib/libpthread.so.0
#15 0x0085ad3e in clone () from /lib/libc.so.6

Conditions:
Seen in CUCM 9.1.1 but appears more versions could be affected.
based on the code, it could affect anytime SNFSubscribeReq is received on a node.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.