also in RTMT you can do a device search for phones and include parts of the IP address of the phones in question and you will see a column that has the time the phones reconnected with CM. this should give a clear indication of the time frame for the event.<br>
<br><div class="gmail_quote">On Fri, Jun 11, 2010 at 10:18 AM, Jason Aarons (US) <span dir="ltr"><<a href="mailto:jason.aarons@us.didata.com">jason.aarons@us.didata.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div bgcolor="white" link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">RTMT Alert Central should have an alert when a large number of
devices unregister. Might give a timestamp on about what time to start looking
in ccm trace files, etc.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<div>
<div style="border-width: 1pt medium medium; border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span style="font-size: 10pt; color: windowtext;">From:</span></b><span style="font-size: 10pt; color: windowtext;"> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>
[mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Wes Sisk<br>
<b>Sent:</b> Friday, June 11, 2010 10:15 AM<br>
<b>To:</b> <a href="mailto:dwolgast@gmail.com" target="_blank">dwolgast@gmail.com</a><br>
<b>Cc:</b> Cisco VOIP Newsletter - <a href="http://puck.nether.net" target="_blank">puck.nether.net</a><br>
<b>Subject:</b> Re: [cisco-voip] Many phones resetting spontaneously -- Traces?</span></p>
</div>
</div><div><div></div><div class="h5">
<p class="MsoNormal"> </p>
<p class="MsoNormal">In General:<br>
<br>
the traces actually say 'unregister' with device name. If phones went
down enmass then typical approach is:<br>
1. check CM system and application logs. look for any critical system
events (cm crash/restart?)<br>
2. pull CM SDI and SDL traces. when phones next re-register they send a
reason code for the last unregistration in an ALARM message<br>
3. parse traces to identify phones that *did* and *did not* unregister.
identify patterns in the groups of phones such as subnet, primary cm, phone
model, device pool, etc.<br>
<br>
/Wes<br>
<br>
On Thursday, June 10, 2010 7:17:25 PM, Dave Wolgast <a href="mailto:dwolgas1@rochester.rr.com" target="_blank"><dwolgas1@rochester.rr.com></a>
wrote:<br>
<br>
</p>
<p class="MsoNormal">CUCM 6.1(4)<br>
7940/42/60/62 running 8.5(3)<br>
<br>
I got a report late this afternoon that a fair number of calls were dropped
when phones reset spontaneously. All phones were registered to a single
subscriber. I am trying to narrow down the cause of the event.
Unfortunately, nobody thought to record an accurate time when the event
occurred. Thus, I have to dig through the traces (I don't see unregisters
in the Application logs).<br>
<br>
What does an unregister look like in traces, or what else could I search on
that might identify the moment when this occurred?<br>
<br>
If there is any additional info I can provide that would help, please let me
know.<br clear="all">
<br>
-- <br>
Dave Wolgast<br>
Livonia, NY<br>
<br>
</p>
<pre> </pre><pre style="text-align: center;"><hr align="center" width="90%" size="4">
</pre><pre> </pre><pre>_______________________________________________</pre><pre>cisco-voip mailing list</pre><pre><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a></pre><pre><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a></pre>
<pre> </pre>
<p class="MsoNormal"> </p>
</div></div></div>
</div>
<div><p></p><hr size="1"><div class="im">
<p><b>
Disclaimer:
This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.
</b></p></div></div><br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br>