[cisco-voip] Trouble with upgrading firmware due to firmware bug

[Nate VanMaren]

For all SCCP firmware upgrades from firmware release versions earlier than 8.3(3) to version 8.5(3) or greater, you must first upgrade your firmware to version 8.5(2). Once you have upgraded to version 8.5(2), you can upgrade your IP Phone to version 8.5(3) or later.
________________________________
[cid:image002.gif at 01CA5C60.86497FA0]
________________________________
Note This section applies to the Cisco Unified IP Phone 7971G-GE, 7970G, 7961G-GE, 7961G, 7941G-GE, 7941G, 7911G, and 7906G.
________________________________
The following upgrade issues apply:
*If you are currently running firmware earlier than 6.0(2) on a Cisco Unified IP Phone and want to upgrade to 8.x(x), you must first install an intervening 7.0(x) load to prevent upgrade failure. Cisco recommends using the most recent 7.0(3) load as the intervening load to avoid lengthy upgrade times.
*If you are currently running firmware 6.0(2) to 7.0(2) on a Cisco Unified IP Phone and want to upgrade to 8.x(x), you can do so directly. However, expect the upgrade to take twice as long as usual.

So I guess 6.0(2) should upgrade, but I'd probably step it to a 7.0(3) load since your having trouble.

-Nate

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Kin Wai
Sent: Tuesday, November 03, 2009 8:31 AM
To: 'Ryan Ratliff'
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Trouble with upgrading firmware due to firmware bug

It's running on 6.0.2 now, I'm trying to upgrade to 8-5-2. By the way, it's a 7970. According to bug toolkit, there's some documented bug which mention it happens 'occasionally' but for me the hit rate is 100%.

With a factory default (I tried the way using 1234567890*#) , it's not working. As mentioned, after it boots up, it connects to the new callmanager successfully without upgrading to the latest firmware specify inside default.loads. When I look at the firmware field on the phone, it shows term70.default.loads.

I have yet to try  the (3491672850*#) method so far. Seems like I'm facing multiple issues here.

As customer is moving from 4.0 to 7.1, with the old firmware(after the factory default) I guess I will lose some features?

From: Ryan Ratliff [mailto:rratliff at cisco.com]
Sent: Tuesday, November 03, 2009 11:12 PM
To: Kin Wai
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Trouble with upgrading firmware due to firmware bug

Is your phone running 6.0.2 now or trying to upgrade to that load and failing?  If it is running 6.0.2 now what version is it trying to upgrade to (specified ind device defaults)?

When you do a factory reset the phone will look for the term7.default file on the TFTP server it gets from DHCP and then upgrade its load to that specified in the defaults file.

-Ryan

On Nov 3, 2009, at 9:28 AM, Kin Wai wrote:

Hi Folks,
I'm having trouble with this firmware load "TERM70.6-0-2-0S". In the current environment, it's DHCP based. I manually disabled DHCP and point the TFTP server to another TFTP server (new callmanager with latest firmware)

It seems like the phone is stuck with a reboot loop with "verifying firmware" showing on the screen. It didn't download the latest firmware at all.

The only workaround I can find so far is to either do factory default else if factory reset. So far I tried 4 of them, none of them manage to retrieve the firmware successfully by itself without any user inference.

Something interesting is occasionally when I do a factory default on the phone (the step with 1234567890*#) , it will connect to the new callmanager without upgrading to the latest firmware, instead it boots up and connect using term7.default(the default firmware load). Is this normal?

In a successful example, after the factory default command, it will download the latest default firmware load, follows by the latest firmware load.

Anyone face  similar problem before? Having to factory reset/default is really not something I want to happen during the migration day or before the migration day during late evenings.

Regards,
Kin Wai
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip


 NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091103/25f0e4ff/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 168 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091103/25f0e4ff/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.gif
Type: image/gif
Size: 1111 bytes
Desc: image002.gif
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091103/25f0e4ff/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 168 bytes
Desc: image003.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091103/25f0e4ff/attachment-0001.png>