<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1479" name=GENERATOR>
<STYLE>@page Section1 {size: 595.3pt 841.9pt; margin: 72.0pt 90.0pt 72.0pt 90.0pt; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal-compose
}
SPAN.content1 {
FONT-WEIGHT: normal; COLOR: black; FONT-FAMILY: Arial; TEXT-DECORATION: none
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-GB vLink=purple link=blue bgColor=#ffffff>
<DIV><FONT size=2>It is my hope that I will be able to do something similar when
testing out new versions of Call Manager, basically mimicing all route patterns
etc on the new server and have a few phones testing things live and interacting
with the production service.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>However, I think it's quite an ordeal to migrate things piece
meal. Test as much as you can, then upgrade the cluster. Be sure to have plenty
of outs, i.e. backup and mirrored disks. We have new hardware and will be
building the new publisher exactly as you mentioned. If you don't have new
hardware, you should be able to take your publisher off-line during the upgrade
and then plug it back in when you are done. Obviously database changes can't
happen during that time and will affect things like call
forwarding.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>I think we have to begin letting our clients know that we
<EM>have</EM> to upgrade and there will be changes seen. Many we will be able to
document, but many may slip by our fingers because of lack of change
documentation (sorry Cisco).</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>For your notes, you will have to do a two stage upgrade, from
3.3(3) -> 3.3(4) or 4.0(x) -> 4.1(2). We are choosing to go to 3.3(4) as
our interim step.</FONT></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=c.donnelly@skynetsystems.co.uk
href="mailto:c.donnelly@skynetsystems.co.uk">chris donnelly</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</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> Monday, January 24, 2005 4:57
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> [cisco-voip] Advice on CCM3 to
CCM4 Migration please</DIV>
<DIV><BR></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN class=content1><FONT face=Arial color=black
size=1><SPAN style="FONT-SIZE: 9pt">Hi, </SPAN></FONT></SPAN><FONT face=Arial
color=black size=1><SPAN
style="FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: Arial"><BR><BR><SPAN
class=content1><FONT face=Arial color=black>Hopefully one of you guys have
been through this and can recommend the most painless way forward....
</FONT></SPAN><BR><BR><SPAN class=content1><FONT face=Arial color=black>We
have a customer who currently has an old 3.3.3 CCM Cluster with about 2000
phones hanging of it. </FONT></SPAN><BR><BR><SPAN class=content1><FONT
face=Arial color=black>They need to go to CCM 4.x and want to prove the
environment / product first by staging the new CCM 4 and then gradually moving
users from the old cluster to the new cluster. The downside of this is that it
is not a straightforward upgrade / replacement as the two clusters will live
side by side for a while. </FONT></SPAN><BR><BR><SPAN class=content1><FONT
face=Arial color=black>I have no problem with this apart from the sheer
numbers involved. My initial thought was to use the BAT tool to import all
data from the production cluster to the CCM4 cluster - but that still leaves
me loads of stuff to cross-pollinate i.e. Route patterns, partitions
etc...etc... </FONT></SPAN><BR><BR><SPAN class=content1><FONT face=Arial
color=black>My second thought is to build the CCM4 cluster from the Upgrade
'Replace Server' option whilst building -but that forces me to use the old
CCM3's machine name etc so the two clusters cannot live side by side....unless
there is a way to build the CCM cluster by the 'Upgrade Replace Server' option
and then rename the machine name and change IP addresses etc...
</FONT></SPAN><BR><BR><SPAN class=content1><FONT face=Arial color=black>BTW I
know everyone says that you cannot change machine names because of SQL (but
has anyone actually tried this?) - there are snippets of info available on the
web detailing how to change SQL machine names. </FONT></SPAN><BR><BR><SPAN
class=content1><FONT face=Arial color=black>Any advice gratefully received.
</FONT></SPAN><BR><BR><SPAN class=content1><FONT face=Arial
color=black>Chris</FONT></SPAN></SPAN></FONT><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p></o:p></SPAN></FONT></P></DIV>
<P>
<HR>
<P></P>_______________________________________________<BR>cisco-voip mailing
list<BR>cisco-voip@puck.nether.net<BR>https://puck.nether.net/mailman/listinfo/cisco-voip<BR></BLOCKQUOTE></BODY></HTML>