<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=utf-8">
<META content="MSHTML 6.00.2900.3199" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px">
<DIV>I like the idea of :</DIV>
<DIV> </DIV>
<DIV>1. <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. <FONT face="Times New Roman" color=#000000>disable or set to manual startup the CallManager <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" <rratliff@cisco.com> 10/24/2007 11:44 AM >>><BR>The easiest way to ensure phones don't register to servers during the <BR>upgrade is to disable or set to manual startup the CallManager <BR>service on the servers being upgraded. That way you can do the <BR>upgrade, reboot the server, and take a look at things before having <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 <BR>upgrades to minimize system disruptions. From a recent ES doc:<BR><BR>"You can minimize call-processing interruptions if you register all <BR>devices<BR>to servers that are running the same version of Cisco CallManager <BR>during the<BR>entire upgrade process; i.e., you register all devices to the backup <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 <BR>the best practice to ensure that all devices stay registered on the <BR>backup or primary servers during the upgrade. Should you manipulate <BR>your Call Manager groups during the upgrade?<BR><BR> For instance all of our devices are registered to Subscribers A, B, <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 <BR>that is intended solely for the use of the addressee. If you are not <BR>the intended recipient or entity, you are strictly prohibited from <BR>disclosing, copying, distributing or using any of the information <BR>contained in the transmission. If you received this communication in <BR>error, please contact the sender immediately and destroy the material <BR>in its entirety, whether electronic or hard copy. This communication <BR>may contain nonpublic personal information about consumers subject to <BR>the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley <BR>Act. You may not directly or indirectly reuse or disclose such <BR>information for any purpose other than to provide the services for <BR>which you are receiving the information.<BR>There are risks associated with the use of electronic transmission. <BR>The sender of this information does not control the method of <BR>transmittal or service providers and assumes no duty or obligation <BR>for the security, receipt, or third party interception of this <BR>transmission.<BR>************************************<BR><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>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></BODY></HTML>