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

Tue Nov 3 11:16:36 EST 2009

Luckily it didn't brick itself just like firewalls. =)

However, according to the release notes, it looks fine. The problem I have I
guess is more towards the "verifying firmware" part where it didn't attempt
to download the new firmware at all despite the amount of reboot done
itself. 

In the meanwhile, I will try to upgrade to 7.x tomorrow or the day after
when I'm onsite again.

From: Scott Voll [mailto:svoll.voip at gmail.com] 
Sent: Wednesday, November 04, 2009 12:06 AM
To: Jason Aarons (US)
Cc: Nate VanMaren; Kin Wai; Ryan Ratliff; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Trouble with upgrading firmware due to firmware
bug

it's just like all of the other Cisco hardware.

Firewalls were the same going from 6.x to 8.x.  had to first go through 7.x.

I'm guessing it's working by design ;-(

On Tue, Nov 3, 2009 at 8:44 AM, Jason Aarons (US)
<jason.aarons at us.didata.com> wrote:

Is it a bug or by-design since it's in the release notes?

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Nate VanMaren
Sent: Tuesday, November 03, 2009 10:35 AM
To: Kin Wai; 'Ryan Ratliff'

Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Trouble with upgrading firmware due to firmware
bug

http://www.cisco.com/en/US/i/templates/blank.gifFor 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. 

  _____  

http://www.cisco.com/en/US/i/templates/note.gif

  _____  

Note http://www.cisco.com/en/US/i/templates/blank.gifThis 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: 

.http://www.cisco.com/en/US/i/templates/blank.gifIf 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. 

.http://www.cisco.com/en/US/i/templates/blank.gifIf 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
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.

  _____  

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. 

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091104/8cf27a53/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 168 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091104/8cf27a53/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1111 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091104/8cf27a53/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 168 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091104/8cf27a53/attachment-0001.png>