<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Tom, <br>
It will depend on the version of firmware that you had on your
handsets prior to the upgrade.<br>
So if you wanted to upgrade to the latest version 9.2(3)<br>
From the release notes<br>
<br>
<span class="content">For all SCCP firmware upgrades from firmware
release versions earlier than 8.3(3) to <span style="color:
Black; font-style: normal; font-weight: normal">Ve</span>rsion <span
style="color: Black; font-style: normal; font-weight: normal">9.2(3)
o</span>r <span style="color: Black; font-style: normal;
font-weight: normal">later, <br>
y</span>ou must first upgrade your firmware to an intermediate <span
style="color: Black; font-style: normal; font-weight: normal">Ve</span>rsion
(8.3(3) <span style="color: Black; font-style: normal;
font-weight: normal">to 8</span>.5(2)) <span style="color:
Black; font-style: normal; font-weight: normal">and </span>then
upgrade to <span style="color: Black; font-style: normal;
font-weight: normal">9.2(3).</span></span><br>
<br>
<pre class="moz-signature" cols="72">Rgds
Andy</pre>
<br>
On 04/03/2012 01:23, Thomas LeMay wrote:
<blockquote cite="mid:000601ccf9a5$6978db70$3c6a9250$@comcast.net"
type="cite">
<pre wrap="">Lelio,
I recently upgraded from CCM 6.1.4 to 7.1.5 and found that the phone
firmware code did not update . I had to manually update with interim
firmware for the 7965s. Do you know what interim firmware I will need to
update the 7945/7960s\62?
Thank you,
Tom
-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>
[<a class="moz-txt-link-freetext" href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Lelio Fulgenzi
Sent: Saturday, March 03, 2012 7:51 PM
To: Ed Leatherman
Cc: <a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
Subject: Re: [cisco-voip] Upgrade Methods
As someone else mentioned, upgrade the firmware on your phones to the
default version your going to before the upgrade. How long before is your
choice. The biggest issue with this is if you've waited too long, you might
have to do interim firmware upgrades.
Also, if you can't swing a change freeze, implement some sort of change
management records so you can apply the changes after you switch versions.
Sent from my iPhone...
"There's no place like 127.0.0.1"
On Mar 3, 2012, at 11:12 AM, Ed Leatherman <a class="moz-txt-link-rfc2396E" href="mailto:ealeatherman@gmail.com"><ealeatherman@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">1) All in one shot. I try to stage/install all the upgrades ahead of
time the night before so the next morning during the "official"
maintenance window I just have to spend time rebooting and testing.
This is particularly helpful if I find myself needing to upgrade some
other application (coughUCCX) at the same time as CM.
2) This would not work in my environment as there are too many changes
that happen day-to-day. A configuration freeze of more than a day is
not possible.
3) Test plan for me covers all major dial plan features - 911, local,
long distance, International, plus any trunks or special ties to other
systems. Also, conf bridges, MOH. Unity, UCCX, paging, call recording
apps, CDR delivery. I try a few of these features between CM nodes
also (call a phone that's registered to another node etc). Impossible
to test every detail but I try to at least hit things that would
uncover the broadest number of potential issues. I still need to add
something about ITL for my 8.6 upgrade just haven't figure out what
yet. YMMV
I would suggest familiarizing some with the db replication between CM
nodes - I've found they don't always want to fully sync up after
upgrade/reboot and its good to have an idea of what the CLI commands
do around in case you have a problem. TAC is really good at fixing
those issues but it's nice if you can resolve the easy problems
yourself.
Also goes w/o saying but make sure you have any of your license file
that you need in advance.
On Fri, Mar 2, 2012 at 7:22 PM, Frank Arrasmith
<a class="moz-txt-link-rfc2396E" href="mailto:frank.arrasmith@gmail.com"><frank.arrasmith@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hey all,
I have a quick question about best practices/tips during system
upgrade, particularly on the Linux appliance models. My previous
experience with upgrades has been primarily in a lab, which have
always gone fine, However, in my new enterprise, we have an 8 server
cluster(pub,5 subs, 2 tftp) running 7.1.5, with critical uptime
requirements. Other than recommended procedures from the Cisco
Upgrade guides, what other practices or additional procedures do you
employ to ensure a smooth upgrade, and/or to speed the process along?
1. Do you upgrade all in one shot, long maintenance window? Install,
Reboot , Test?
2. Do you do spread out the install over a few days? Install over a
few maintenance windows utilizing inactive partitions, then schedule
restart and testing for another maintenance window? how long of a
time period is it acceptable to spread out?
3. Other then basic call testing, and ensuring that appropriate
services are started/running( we distribute service between the
subs), what other checks do you include?
Thanks in advance.
Frank Arrasmith
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<pre wrap="">
--
Ed Leatherman
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
</body>
</html>