Our subscriber reboots every two or three weeks while the publisher is always up & running. I am looking in the Syslogs using RTMT tool to find out the reason but don't see any messages regarding the reboot. Is there any specific place that I have to look at? Could the switch in which the server is connected be the cause? I really doubt because the publisher is connected to the next port in the same switch but we never had any issue with publisher. What can I do in order to stop the subscriber from rebooting? I am using CCM 5.1.
Below is all I can see in the System & Application logs for the time Subscriber has rebooted
Date: Aug 14 09:23:05
Machine Name: AMMTL1VCMS01
Message: 47950 Aug 14 132305.401 UTC %CCM_CALLMANAGER-CALLMANAGER-3-TspError Error in TSP. Port IsoEthPort0 Port DSL0 Name of DeviceSEP001B54140FED App IDCisco CallManager Cluster IDStandAloneCluster Node IDAMMTL1VCMS01
This is the output of the "show status" from the subscriber server:
Host Name :
Date : Thu Aug 14, 2008 11:29:33
Time Zone : EDT
Locale : en_US.UTF-8
Product Ver : 22.214.171.1240-3
Platform Ver : 126.96.36.199-1
11:29:34 up 1:33, 1 user, load average: 0.24, 0.13, 0.10
Could it be power related? Does someone come in and clean the Server Room once every two weeks?
I had heard a story from someone (can't remember who) but they had a similar problem and they found out that a cleaning person would come in and dust the server room floor and he ended up brushing up against the wires and it would cause a server to reboot, same time, once a week.
Hello - did you get this issue resolved? We have a similiar problem with our Subscriber rebooting about every 20 days. We are on 5.1 as well. This has actually been going on for about 6 months, with the first reboot happening about 2 months after we upgraded to 5.1 on a new server. We have patched it about 4 times since then, as recommended by TAC. We are here now: 188.8.131.5200-4 and still having the same issue. Only on the Subscriber, the Publisher has been good all along. Thanks!
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...