<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3243" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY
style="WORD-WRAP: break-word; webkit-nbsp-mode: space; webkit-line-break: after-white-space"
bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Wes also mentioned to turn off the CTI manager
during an online upgrade process to force CTI applications over to another
sub.</FONT></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=rratliff@cisco.com href="mailto:rratliff@cisco.com">Ryan Ratliff</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=lelio@uoguelph.ca
href="mailto:lelio@uoguelph.ca">Lelio Fulgenzi</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=SCASPER@mtb.com
href="mailto:SCASPER@mtb.com">STEVEN CASPER</A> ; <A
title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, January 09, 2008 9:16
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [cisco-voip] CCM Upgrade -
Best Practices</DIV>
<DIV><BR></DIV>Don't ever deactivate the CCM service via Service Activation
unless you are permanently removing a subscriber from the cluster or turning
it off on the publisher for good.
<DIV><BR class=webkit-block-placeholder></DIV>
<DIV>As Lelio saw when you do this you lose all service parameters for the
server. Also when you re-activate the service the server gets a new CTI
node ID. This means that the CCM service on all other nodes in the
cluster will have to be restarted before they pick up this change, ie no SDL
links to this server. The last big thing de-activation does is remove
the server from all CM groups it is in. </DIV>
<DIV><BR class=webkit-block-placeholder></DIV>
<DIV>Stopping/Starting/Disabling the service via the Win2k services.msc
doesn't hurt anything and if you need to prevent CCM from starting
automatically set it to Manual or Disabled there. </DIV>
<DIV><BR class=webkit-block-placeholder></DIV>
<DIV>
<DIV>
<P style="MARGIN: 0px"><FONT style="FONT: 12px Helvetica" face=Helvetica
size=3>-Ryan</FONT></P></DIV><BR>
<DIV>
<DIV>On Jan 9, 2008, at 9:10 AM, Lelio Fulgenzi wrote:</DIV><BR
class=Apple-interchange-newline><SPAN class=Apple-style-span
style="WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: 2; webkit-border-horizontal-spacing: 0px; webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0">
<DIV><FONT face=Arial size=2>Redefining device pools has worked for us in the
past, but they say not to make changes during the upgrade, so there's no way
to really keep a phone away from a subscriber during the upgrade process other
than disabling it or setting it to manual.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I'm guessing setting it to manual in WIN2K should
work, but they've always told us not to do that. ;)</FONT></DIV>
<DIV> </DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(0,0,0) 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message -----</DIV>
<DIV
style="FONT: 10pt arial; BACKGROUND-COLOR: rgb(228,228,228); webkit-background-clip: initial; webkit-background-origin: initial"><B>From:</B><SPAN
class=Apple-converted-space> </SPAN><A title=SCASPER@mtb.com
href="mailto:SCASPER@mtb.com">STEVEN CASPER</A></DIV>
<DIV style="FONT: 10pt arial"><B>To:</B><SPAN
class=Apple-converted-space> </SPAN><A title=rratliff@cisco.com
href="mailto:rratliff@cisco.com">Ryan Ratliff</A><SPAN
class=Apple-converted-space> </SPAN>;<SPAN
class=Apple-converted-space> </SPAN><A title=lelio@uoguelph.ca
href="mailto:lelio@uoguelph.ca">Lelio Fulgenzi</A></DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B><SPAN
class=Apple-converted-space> </SPAN><A title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A></DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B><SPAN
class=Apple-converted-space> </SPAN>Wednesday, January 09, 2008 8:53
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B><SPAN
class=Apple-converted-space> </SPAN>Re: [cisco-voip] CCM Upgrade - Best
Practices</DIV>
<DIV><BR></DIV>
<DIV>Well that is frightening possibility - hence my question!</DIV>
<DIV> </DIV>
<DIV>The CCM service could be set to disable via the Services window in
WIN2K or I think by using the Service Activation window in Call
Manager Serviceability.</DIV>
<DIV> </DIV>
<DIV> I am trying to come up with the least service effecting procedure
for CCM patching and upgrades since we just moved several 24x7 business
critical groups over to IPT.</DIV>
<DIV><BR>>>> "Lelio Fulgenzi" <<A
href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</A>> 1/9/2008 8:42 AM
>>><BR></DIV>
<DIV><FONT face=Arial size=2>I'm not sure what you're using to "disable"
CallManager, but we tried this once (perhaps we de-activated?), and all the
service parameters for that subscriber were lost (set to default) and
anything that relied on that subscriber, i.e. call park numbers, callmanager
group entry, etc, was deleted!</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>It did not make for a fun time.</FONT></DIV>
<DIV> </DIV>
<DIV>--------------------------------------------------------------------------------<BR>Lelio
Fulgenzi, B.A.<BR>Senior Analyst (CCS) * University of Guelph * Guelph,
Ontario N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<SPAN
class=Apple-converted-space> </SPAN><BR>“Life expectancy would grow by
leaps and bounds if green vegetables smelled as good as bacon.”<BR>Doug
Larson</DIV>
<DIV> </DIV>
<DIV> </DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(0,0,0) 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message -----</DIV>
<DIV
style="FONT: 10pt arial; BACKGROUND-COLOR: rgb(228,228,228); webkit-background-clip: initial; webkit-background-origin: initial"><B>From:</B><SPAN
class=Apple-converted-space> </SPAN><A title=SCASPER@mtb.com
href="mailto:SCASPER@mtb.com">STEVEN CASPER</A></DIV>
<DIV style="FONT: 10pt arial"><B>To:</B><SPAN
class=Apple-converted-space> </SPAN><A title=rratliff@cisco.com
href="mailto:rratliff@cisco.com">Ryan Ratliff</A></DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B><SPAN
class=Apple-converted-space> </SPAN><A
title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A></DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B><SPAN
class=Apple-converted-space> </SPAN>Wednesday, January 09, 2008 8:36
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B><SPAN
class=Apple-converted-space> </SPAN>Re: [cisco-voip] CCM Upgrade -
Best Practices</DIV>
<DIV><BR></DIV>
<DIV>I like the idea of :</DIV>
<DIV> </DIV>
<DIV>1.<SPAN class=Apple-converted-space> </SPAN><FONT
color=#1f497d><FONT face=Arial><FONT color=#000000 size=2>stopping the CM
service on the server to fail everyone over to next
server</FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial color=#1f497d>2.<SPAN
class=Apple-converted-space> </SPAN><FONT face="Times New Roman"
color=#000000>disable or set to manual startup the CallManager <SPAN
class=Apple-converted-space> </SPAN><BR> service on
the servers</FONT></FONT></DIV>
<DIV> </DIV>
<DIV> Does it matter if this is done via CCM Control Center in
Serviceability to stop the CCM service and Service Activation to disable
the CCM service or can these actions be done under Win2k
Services? </DIV>
<DIV> </DIV>
<DIV> Does the Call Manager service need to be running on a server
during an upgrade of the application or the OS?</DIV>
<DIV> </DIV>
<DIV>Steve<BR><BR>>>> "Ryan Ratliff" <<A
href="mailto:rratliff@cisco.com">rratliff@cisco.com</A>> 10/24/2007
11:44 AM >>><BR>The easiest way to ensure phones don't register
to servers during the <SPAN
class=Apple-converted-space> </SPAN><BR>upgrade is to disable or set
to manual startup the CallManager <SPAN
class=Apple-converted-space> </SPAN><BR>service on the servers being
upgraded. That way you can do the <SPAN
class=Apple-converted-space> </SPAN><BR>upgrade, reboot the server,
and take a look at things before having <SPAN
class=Apple-converted-space> </SPAN><BR>phones fail back to
it.<BR><BR>-Ryan<BR><BR>On Oct 24, 2007, at 9:53 AM, STEVEN CASPER
wrote:<BR><BR><BR> Looking for some advice for the best way to do
Call Manager <SPAN
class=Apple-converted-space> </SPAN><BR>upgrades to minimize system
disruptions. From a recent ES doc:<BR><BR>"You can minimize
call-processing interruptions if you register all <SPAN
class=Apple-converted-space> </SPAN><BR>devices<BR>to servers that
are running the same version of Cisco CallManager <SPAN
class=Apple-converted-space> </SPAN><BR>during the<BR>entire upgrade
process; i.e., you register all devices to the backup <SPAN
class=Apple-converted-space> </SPAN><BR>Cisco<BR>CallManager servers
or the primary Cisco CallManager servers, but not to<BR>both types of
servers."<BR><BR> I understand what the ES doc is saying what I am
not sure about is <SPAN
class=Apple-converted-space> </SPAN><BR>the best practice to ensure
that all devices stay registered on the <SPAN
class=Apple-converted-space> </SPAN><BR>backup or primary servers
during the upgrade. Should you manipulate <SPAN
class=Apple-converted-space> </SPAN><BR>your Call Manager groups
during the upgrade?<BR><BR> For instance all of our devices are
registered to Subscribers A, B, <SPAN
class=Apple-converted-space> </SPAN><BR>C, & D. We have two back
up subscribers X & Y. Do we:<BR><BR>1. Upgrade the Publisher.<BR>2.
Upgrade X & Y<BR>3. Change our Call Manager Groups so X & Y subs
are the primary.<BR>4. Reset all devices so they re-register to X &
Y.<BR>5. Upgrade A, B, C, & D.<BR>6. Change Call Manager groups so A,
B, C, & D are primary again.<BR>7. Reset
devices.<BR><BR><BR><BR>Thanks!<BR><BR>Steve Casper<BR>Voice
Technologies<BR>M&T Bank<BR>(410)
347-6026<BR>************************************<BR>This email may contain
privileged and/or confidential information <SPAN
class=Apple-converted-space> </SPAN><BR>that is intended solely for
the use of the addressee. If you are not <SPAN
class=Apple-converted-space> </SPAN><BR>the intended recipient or
entity, you are strictly prohibited from <SPAN
class=Apple-converted-space> </SPAN><BR>disclosing, copying,
distributing or using any of the information <SPAN
class=Apple-converted-space> </SPAN><BR>contained in the
transmission. If you received this communication in <SPAN
class=Apple-converted-space> </SPAN><BR>error, please contact the
sender immediately and destroy the material <SPAN
class=Apple-converted-space> </SPAN><BR>in its entirety, whether
electronic or hard copy. This communication <SPAN
class=Apple-converted-space> </SPAN><BR>may contain nonpublic
personal information about consumers subject to <SPAN
class=Apple-converted-space> </SPAN><BR>the restrictions of the
Gramm-Leach-Bliley Act and the Sarbanes-Oxley <SPAN
class=Apple-converted-space> </SPAN><BR>Act. You may not directly or
indirectly reuse or disclose such <SPAN
class=Apple-converted-space> </SPAN><BR>information for any purpose
other than to provide the services for <SPAN
class=Apple-converted-space> </SPAN><BR>which you are receiving the
information.<BR>There are risks associated with the use of electronic
transmission. <SPAN class=Apple-converted-space> </SPAN><BR>The
sender of this information does not control the method of <SPAN
class=Apple-converted-space> </SPAN><BR>transmittal or service
providers and assumes no duty or obligation <SPAN
class=Apple-converted-space> </SPAN><BR>for the security, receipt, or
third party interception of this <SPAN
class=Apple-converted-space> </SPAN><BR>transmission.<BR>************************************<BR><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">https://puck.nether.net/mailman/listinfo/cisco</A>-voip<BR>_______________________________________________<BR>cisco-voip
mailing list<BR>cisco-voip@puck.nether.net<BR><A
href="https://puck.nether.net/mailman/listinfo/cisco">https://puck.nether.net/mailman/listinfo/cisco</A>-voip<BR><BR><BR></DIV>
<P>************************************<BR>This email may contain
privileged and/or confidential information that is intended solely for the
use of the addressee. If you are not the intended recipient or entity, you
are strictly prohibited from disclosing, copying, distributing or using
any of the information contained in the transmission. If you received this
communication in error, please contact the sender immediately and destroy
the material in its entirety, whether electronic or hard copy. This
communication may contain nonpublic personal information about consumers
subject to the restrictions of the Gramm-Leach-Bliley Act and the
Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose
such information for any purpose other than to provide the services for
which you are receiving the information.<BR>There are risks associated
with the use of electronic transmission. The sender of this information
does not control the method of transmittal or service providers and
assumes no duty or obligation for the security, receipt, or third party
interception of this
transmission.<BR>************************************<BR></P>
<DIV><BR class=khtml-block-placeholder></DIV>
<HR>
<DIV><BR
class=khtml-block-placeholder></DIV>_______________________________________________<BR>cisco-voip
mailing list<BR><A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>https://puck.nether.net/mailman/listinfo/cisco-voip</BLOCKQUOTE>
<P>************************************<BR>This email may contain privileged
and/or confidential information that is intended solely for the use of the
addressee. If you are not the intended recipient or entity, you are strictly
prohibited from disclosing, copying, distributing or using any of the
information contained in the transmission. If you received this
communication in error, please contact the sender immediately and destroy
the material in its entirety, whether electronic or hard copy. This
communication may contain nonpublic personal information about consumers
subject to the restrictions of the Gramm-Leach-Bliley Act and the
Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose
such information for any purpose other than to provide the services for
which you are receiving the information.<BR>There are risks associated with
the use of electronic transmission. The sender of this information does not
control the method of transmittal or service providers and assumes no duty
or obligation for the security, receipt, or third party interception of this
transmission.<BR>************************************<BR></P></BLOCKQUOTE></SPAN></DIV><BR></DIV></BLOCKQUOTE></BODY></HTML>