High CPU for CTS v1.9.1 Endpoints once migrated to TMS
Since migrating all endpoints over to TMS 14.2.1 from CTSman, we are randomly getting the follwing SNMP traps from the CTS endpoints.
XYZ@ABC.com.au- SEV:1 - Broken - HIGH CPU UTILIZATION - Fri 16 Aug, 2013 - 09:26:23 - High CPU Utilization. The utilization of 86% for CPU instance 768 named CPU: 768 has exceeded the 85% threshold on model XYZ@ABC.com.au. for more than the acceptable time period. (event [0x00010f03]) - SpectrumRouter
XYZ@ABC.com.au- SEV:1 - Broken - No Associated Text - Fri 16 Aug, 2013 - 09:25:52 - High Aggregate CPU Utilization. The average CPU Utilization of 86% for all CPU instances exceeds the 85% threshold on model XYZ@ABC.com.au(event [0x00010f07]) - SpectrumRouter
Does anyone know what CPU 768 means & why this would be happening ? CTS v 1.9.1.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...