<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=utf-8">
<META content="MSHTML 6.00.2900.3243" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY style="MARGIN: 4px 4px 1px" bgColor=#ffffff>
<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: #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=SCASPER@mtb.com href="mailto:SCASPER@mtb.com">STEVEN CASPER</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=rratliff@cisco.com
href="mailto:rratliff@cisco.com">Ryan Ratliff</A> ; <A title=lelio@uoguelph.ca
href="mailto:lelio@uoguelph.ca">Lelio Fulgenzi</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <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 8:53
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> 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>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<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: #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=SCASPER@mtb.com href="mailto:SCASPER@mtb.com">STEVEN CASPER</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=rratliff@cisco.com
href="mailto:rratliff@cisco.com">Ryan Ratliff</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <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 8:36
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [cisco-voip] CCM Upgrade -
Best Practices</DIV>
<DIV><BR></DIV>
<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>
<P>
<HR>
<P></P>_______________________________________________<BR>cisco-voip mailing
list<BR>cisco-voip@puck.nether.net<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></BODY></HTML>