Cisco Bug: CSCvt63600 - CUCM ILS Service cores on Cluster A if it has Cluster B identity cert BUT not vice versa.
Oct 30, 2020
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
Symptom: Core occurs with following backrace backtrace - CUCM =================================== #0 0x08129138 in Ils::decodeIlspMsg (this=0xf76044c8, msg=0xee841008, msgData=0xf762a530 "\002_", msgLen=1940) at ProcessIls.cpp:5744 #1 0x081187fc in Ils::PreRecvInd (this=0xf76044c8, buf=..., msg=...) at ProcessIls.cpp:1327 #2 0x081188a8 in Ils::RecvInd (this=0xf76044c8, key=..., buf=...) at ProcessIls.cpp:1348 #3 0x081156f0 in Ils::sendIlsDataInd (this=0xf76044c8, tcpPID=..., ilsHandleInfo=0xf7625218, msg=0xf7629d98 "\002_", msgLen=1940) at ProcessIls.cpp:576 #4 0x08115baa in Ils::wait_SdlDataInd (this=0xf76044c8, s=...) at ProcessIls.cpp:637 #5 0x08135d10 in Ils::fireSignal (this=0xf76044c8, sdlSignal=...) at ../Include/ProcessIls.hpp:323 #6 0x081eaf9f in SdlProcessBase::inputSignal (this=0xf76044c8, rSignal=0xf7626998, traceType=SdlSystemLog::SignalRouterThread, highPriority=0, normalPriority=0, lowPriority=0, veryLowPriority=0, lazyPriority=0, dbUpdatePriority=0) at SdlProcessBase.cpp:406 #7 0x081efb16 in SdlRouter::callProcess (this=0x8ab5b90, _sdlSignal=0xf7626998, _deleteSignal=@0xf29e82ff, _traceType=SdlSystemLog::SignalRouterThread, _hp=0, _np=0, _lp=0, _vlp=0, _lzp=0, _dbp=0) at SdlRouter.cpp:257 #8 0x081efdc0 in SdlRouter::scheduler (this=0x8ab5b90) at SdlRouter.cpp:164 #9 0x081f02bf in SdlRouter::schedulerInit (sdlRouter=0x8ab5b90) at SdlRouter.cpp:107 #10 0x0081ebc9 in start_thread () from /lib/libpthread.so.0 #11 0x0640f04e in clone () from /lib/libc.so.6 Conditions: ILS setup with hub and spoke clusters. Identity certificates of spoke clusters have been imported into Hub cluster but Hub identity certificate has not been imported into spoke cluster. Other scenario is that Hub identity certificate has been imported into Spoke clusters but Spoke identity certificates have not been imported into Hub cluster.
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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases