<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
I've been informed by Wes that there is a slight difference in CM 5 and 6 with regards to deactivating the CCM service. The CTI node IDs are now static and so will not change upon deactivation/reactivation. The server will still be removed from any CM groups and will have the default service parameters however upon reactivation. <div><br><div> <p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">-Ryan</font></p> </div><br><div><div>On Jan 9, 2008, at 9:26 AM, Ryan Ratliff wrote:</div><br class="Apple-interchange-newline">Remember there is a difference between the Service Activation page and the Control Center. Control Center is the way to stop the CM service. I don't know of a way to keep CCM from starting automatically however with CM 5 and later. If you need to keep devices from registering with a server you are better off using an ACL to block traffic if you can't keep the service from starting.<div><div><br><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: 12.0px Helvetica">-Ryan</font></div> </div><br><div><div>On Jan 9, 2008, at 9:24 AM, <<a href="mailto:jean-francois.guay@bell.ca">jean-francois.guay@bell.ca</a>> wrote:</div><br class="Apple-interchange-newline"> <div dir="ltr" align="left"><span class="493052414-09012008"><font face="Arial" color="#0000ff" size="2">Ryan,</font></span></div> <div dir="ltr" align="left"><span class="493052414-09012008"><font face="Arial" color="#0000ff" size="2"></font></span> </div> <div dir="ltr" align="left"><span class="493052414-09012008"><font face="Arial" color="#0000ff" size="2">As a follow up question, what should we do for CCM5 or 6 where Service Activation is the only official way of shutting down the service?</font></span></div> <div dir="ltr" align="left"><span class="493052414-09012008"><font face="Arial" color="#0000ff" size="2"></font></span> </div> <div dir="ltr" align="left"><span class="493052414-09012008"></span> </div> <div> </div><p class="MsoNormal" style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto" align="left"><span lang="FR-CA" style="FONT-SIZE: 10pt; COLOR: blue; mso-ansi-language: FR-CA"> </span><span lang="FR-CA" style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Verdana; mso-ansi-language: FR-CA"> </span><span class="SpellE"><b style="mso-bidi-font-weight: normal"><span lang="FR-CA" style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana; mso-ansi-language: FR-CA">Jean-Francois</span></b></span><b style="mso-bidi-font-weight: normal"><span lang="FR-CA" style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana; mso-ansi-language: FR-CA"> Guay, <span class="SpellE">ing</span>.</span></b><span lang="FR-CA" style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Verdana; mso-ansi-language: FR-CA"><br><span style="mso-spacerun: yes"> </span></span><span lang="FR-CA" style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana; mso-ansi-language: FR-CA"><span style="mso-spacerun: yes"> </span><i style="mso-bidi-font-style: normal">Consultant Technologies IP – Services Professionnels<br><span style="mso-spacerun: yes"> </span>Communications Convergentes et Solutions Mobiles <br> Bell Solutions T.I.C<br></i> </span><span style="FONT-SIZE: 10pt; FONT-FAMILY: 'Wingdings 2'">'</span><span lang="FR-CA" style="mso-ansi-language: FR-CA"> </span><span lang="FR-CA" style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana; mso-ansi-language: FR-CA">514-391-9698</span></p> <div> </div><br> <div class="OutlookMessageHeader" lang="fr" dir="ltr" align="left"> <hr tabindex="-1"> <font face="Tahoma" size="2"><b>De :</b> Ryan Ratliff [<a href="mailto:rratliff@cisco.com">mailto:rratliff@cisco.com</a>] <br><b>Envoyé :</b> 9 janvier 2008 09:16<br><b>À :</b> Lelio Fulgenzi<br><b>Cc :</b> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>; STEVEN CASPER<br><b>Objet :</b> Re: [cisco-voip] CCM Upgrade - Best Practices<br></font><br></div> <div></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><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font style="FONT: 12px Helvetica" face="Helvetica" size="3">-Ryan</font></div></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><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><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><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></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></div><br></div></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">_______________________________________________</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">cisco-voip mailing list</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></div> </div><br></div></body></html>