<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.17063" name=GENERATOR><!--[if !mso]>
<STYLE>v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Consolas;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; COLOR: black; FONT-FAMILY: "Times New Roman","serif"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; COLOR: black; FONT-FAMILY: "Times New Roman","serif"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; COLOR: black; FONT-FAMILY: "Times New Roman","serif"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
PRE {
FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; COLOR: black; FONT-FAMILY: "Courier New"; mso-style-priority: 99; mso-style-link: "HTML Preformatted Char"
}
SPAN.HTMLPreformattedChar {
COLOR: black; FONT-FAMILY: "Consolas","serif"; mso-style-priority: 99; mso-style-link: "HTML Preformatted"; mso-style-name: "HTML Preformatted Char"
}
SPAN.EmailStyle19 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.WordSection1 {
page: WordSection1
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=EN-US vLink=purple link=blue bgColor=white>
<DIV dir=ltr align=left><SPAN class=655353715-14062010><FONT face=Arial
color=#0000ff size=2>I had to set up such an alert manually. Works pretty well,
aside from the fact that I don't get any sort of idea about which phones went
down.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=655353715-14062010><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=655353715-14062010><FONT face=Arial
color=#0000ff size=2>I'd like to get this:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=655353715-14062010><FONT face=Arial
color=#0000ff size=2>"<FONT face="Times New Roman" color=#000000 size=3>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"</FONT></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=655353715-14062010></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=655353715-14062010><FONT face=Arial
color=#0000ff size=2>as a history - not just the last time, but whether or not
repeated boot/register events are happening to just a few phones, or even just
one phone that I know I want to monitor.</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV align=left><FONT face=Arial size=2>Tim Reimers</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>Systems Analyst II</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>Information Technology
Services</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>City of Asheville</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>70 Court Plaza</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>Asheville, NC 28801</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>phone - 828-259-5512</FONT></DIV>
<DIV align=left><FONT face=Arial size=2><A
href="mailto:timreimers@ashevillenc.gov">treimers@ashevillenc.gov</A></FONT></DIV>
<DIV> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>Jason Aarons
(US)<BR><B>Sent:</B> Friday, June 11, 2010 10:19 AM<BR><B>To:</B>
dwolgast@gmail.com<BR><B>Cc:</B> Cisco VOIP Newsletter -
puck.nether.net<BR><B>Subject:</B> Re: [cisco-voip] Many phones resetting
spontaneously -- Traces?<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=WordSection1>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">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.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 10pt; COLOR: windowtext; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; COLOR: windowtext; FONT-FAMILY: 'Tahoma','sans-serif'">
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net]
<B>On Behalf Of </B>Wes Sisk<BR><B>Sent:</B> Friday, June 11, 2010 10:15
AM<BR><B>To:</B> dwolgast@gmail.com<BR><B>Cc:</B> Cisco VOIP Newsletter -
puck.nether.net<BR><B>Subject:</B> Re: [cisco-voip] Many phones resetting
spontaneously -- Traces?<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></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"><dwolgas1@rochester.rr.com></A>
wrote:<BR><BR><o:p></o:p></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><o:p></o:p></P><PRE><o:p> </o:p></PRE><PRE style="TEXT-ALIGN: center">
<HR align=center width="90%" SIZE=4>
</PRE><PRE><o:p> </o:p></PRE><PRE>_______________________________________________<o:p></o:p></PRE><PRE>cisco-voip mailing list<o:p></o:p></PRE><PRE><A href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><o:p></o:p></PRE><PRE><A href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><o:p></o:p></PRE><PRE> <o:p></o:p></PRE>
<P class=MsoNormal><o:p> </o:p></P></DIV>
<P>
<HR SIZE=1>
<P></P>
<P><STRONG>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. </STRONG></P></BODY></HTML>