Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Thank you! I had this issue, uploaded new system cert, and that solved it once I pushed telemetry settings again. Note that in openssl request to generate a new system cert (internal pki) to use IP.1 in the SAN field:DNS.1 = test-dnac-1.internalcorp....
OFFICIALYep, Microsoft removed Baltimore CA and that's what caused this.Dead give away for me that it was certificate is how can both router models (8200 and 4300) have the same type of cpu hog and TLS errors.Thanks again, Rene.
I had this problem today - 19/06/25. In my case the 8200 and 4300 series routers were also locking up CPU with the following messages:%SYS-3-CPUHOG: Task is running for (12913)msecs, more than (2000)msecs (2/2),process = CCSIP_TLS_HANDSHAKE.Along wit...
Ok so for anyone like OP that runs into this problem here is how I solved it:*** Updated 19/01/25 ***We ended up still having issues. We fixed this with TAC, there was two things - we used standard vswitch and cabled directly between two hosts (using...
