<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.emailstyle18
{mso-style-name:emailstyle18;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.emailstyle19
{mso-style-name:emailstyle19;
font-family:"Times New Roman","serif";
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>For minor revisions we just implement a change freeze on the
Friday of the upgrade and upgrade the inactive partition. Come in the next
morning and reboot and test.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On
Behalf Of </b>Maniccia, Thomas<br>
<b>Sent:</b> Wednesday, December 10, 2008 2:36 PM<br>
<b>To:</b> 'cisco-voip@puck.nether.net'<br>
<b>Subject:</b> Re: [cisco-voip] CUCM 6.1(2) upgrade<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='color:blue'>Sorry I should have specified
I’m going direct 6.1(1a) to 6.1(2) with an .iso file via sftp. The best I
can tell with the RTMT is that only 16% of the CUCM database space is consumed.
I couldn’t readily find a way to determine the exact size from the cli.</span><o:p></o:p></p>
<p class=MsoNormal><span style='color:blue'> </span><o:p></o:p></p>
<p class=MsoNormal><span style='color:blue'> </span><o:p></o:p></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Jason Aarons (US)
[mailto:jason.aarons@us.didata.com] <br>
<b>Sent:</b> Wednesday, December 10, 2008 15:28<br>
<b>To:</b> Lelio Fulgenzi; Maniccia, Thomas<br>
<b>Cc:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> RE: [cisco-voip] CUCM 6.1(2) upgrade</span><o:p></o:p></p>
</div>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I did a two node 300 phone system from 4.1(3) to 6.1(2), all
included with Attendant Console upgrades and extensive user and application
testing it took 9 hours the day of, plus another 8 hour maintenance window the
week before to resolve all DMA/Upgrade assistant issues and reboot with latest
BARS and get a good backup, plus we staffed up for post cutover support on
Monday after cutover for issues like IE shortcuts no longer working for new
ccmuser, etc.</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I used to start at 5pm on Friday but it would be 11pm when
issues surfaced and everyone would be half asleep and not paying attention to
details. I’ve moved to starting at 8am Saturday so everyone is
thinking and on their toes still by 3pm, no one is ready to leave because they
are too tired….I once had a customer tell me at 9pm she was tired and
locking us out, she was going home regardless if the phone system worked or not
for the campus! Seems she had something called tenure and couldn’t be
fired regardless what she did. Almost sounds better than a union.</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> </span><o:p></o:p></p>
</div>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=1 width="100%" align=center>
</div>
<p><strong>Disclaimer: This e-mail communication and any attachments may
contain confidential and privileged information and is for use by the
designated addressee(s) named above only. If you are not the intended
addressee, you are hereby notified that you have received this communication in
error and that any use or reproduction of this email or its contents is
strictly prohibited and may be unlawful. If you have received this
communication in error, please notify us immediately by replying to this
message and deleting it from your computer. Thank you. </strong><o:p></o:p></p>
</div>
</body>
</html>