Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Cisco: VOIP

Trouble with upgrading firmware due to firmware bug

 

 

Cisco voip RSS feed   Index | Next | Previous | View Threaded


kinwai at singnet

Nov 3, 2009, 6:28 AM

Post #1 of 8 (675 views)
Permalink
Trouble with upgrading firmware due to firmware bug

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


rratliff at cisco

Nov 3, 2009, 7:11 AM

Post #2 of 8 (650 views)
Permalink
Re: Trouble with upgrading firmware due to firmware bug [In reply to]

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
https://puck.nether.net/mailman/listinfo/cisco-voip


kinwai at singnet

Nov 3, 2009, 7:31 AM

Post #3 of 8 (653 views)
Permalink
Re: Trouble with upgrading firmware due to firmware bug [In reply to]

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]
Sent: Tuesday, November 03, 2009 11:12 PM
To: Kin Wai
Cc: cisco-voip [at] puck
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
https://puck.nether.net/mailman/listinfo/cisco-voip


VanMarenNP at ldschurch

Nov 3, 2009, 7:34 AM

Post #4 of 8 (653 views)
Permalink
Re: Trouble with upgrading firmware due to firmware bug [In reply to]

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]
________________________________
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 [mailto:cisco-voip-bounces [at] puck] On Behalf Of Kin Wai
Sent: Tuesday, November 03, 2009 8:31 AM
To: 'Ryan Ratliff'
Cc: cisco-voip [at] puck
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]
Sent: Tuesday, November 03, 2009 11:12 PM
To: Kin Wai
Cc: cisco-voip [at] puck
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<mailto:cisco-voip [at] puck>
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.
Attachments: image001.png (0.16 KB)
  image002.gif (1.08 KB)
  image003.png (0.16 KB)


jason.aarons at us

Nov 3, 2009, 7:44 AM

Post #5 of 8 (648 views)
Permalink
Re: Trouble with upgrading firmware due to firmware bug [In reply to]

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



From: cisco-voip-bounces [at] puck
[mailto:cisco-voip-bounces [at] puck] On Behalf Of Nate VanMaren
Sent: Tuesday, November 03, 2009 10:35 AM
To: Kin Wai; 'Ryan Ratliff'
Cc: cisco-voip [at] puck
Subject: Re: [cisco-voip] Trouble with upgrading firmware due to
firmware bug



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.

________________________________



________________________________

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
[mailto:cisco-voip-bounces [at] puck] On Behalf Of Kin Wai
Sent: Tuesday, November 03, 2009 8:31 AM
To: 'Ryan Ratliff'
Cc: cisco-voip [at] puck
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]
Sent: Tuesday, November 03, 2009 11:12 PM
To: Kin Wai
Cc: cisco-voip [at] puck
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
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.
Attachments: image001.png (0.16 KB)
  image002.gif (1.08 KB)
  image003.png (0.16 KB)


svoll.voip at gmail

Nov 3, 2009, 8:05 AM

Post #6 of 8 (654 views)
Permalink
Re: Trouble with upgrading firmware due to firmware bug [In reply to]

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> wrote:

> Is it a bug or by-design since it’s in the release notes?
>
>
>
> *From:* cisco-voip-bounces [at] puck [mailto:
> cisco-voip-bounces [at] puck] *On Behalf Of *Nate VanMaren
> *Sent:* Tuesday, November 03, 2009 10:35 AM
> *To:* Kin Wai; 'Ryan Ratliff'
>
> *Cc:* cisco-voip [at] puck
> *Subject:* Re: [cisco-voip] Trouble with upgrading firmware due to
> firmware bug
>
>
>
> [image: http://www.cisco.com/en/US/i/templates/blank.gif]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.
> ------------------------------
>
> [image: http://www.cisco.com/en/US/i/templates/note.gif]
> ------------------------------
>
> *Note *[image: http://www.cisco.com/en/US/i/templates/blank.gif]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:
>
> •[image: http://www.cisco.com/en/US/i/templates/blank.gif]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.
>
> •[image: http://www.cisco.com/en/US/i/templates/blank.gif]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 [mailto:
> cisco-voip-bounces [at] puck] *On Behalf Of *Kin Wai
> *Sent:* Tuesday, November 03, 2009 8:31 AM
> *To:* 'Ryan Ratliff'
> *Cc:* cisco-voip [at] puck
> *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]
> *Sent:* Tuesday, November 03, 2009 11:12 PM
> *To:* Kin Wai
> *Cc:* cisco-voip [at] puck
> *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
> 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
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
Attachments: image003.png (0.16 KB)
  image001.png (0.16 KB)
  image002.gif (1.08 KB)


kinwai at singnet

Nov 3, 2009, 8:16 AM

Post #7 of 8 (652 views)
Permalink
Re: Trouble with upgrading firmware due to firmware bug [In reply to]

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]
Sent: Wednesday, November 04, 2009 12:06 AM
To: Jason Aarons (US)
Cc: Nate VanMaren; Kin Wai; Ryan Ratliff; cisco-voip [at] puck
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> wrote:

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



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


Cc: cisco-voip [at] puck
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
[mailto:cisco-voip-bounces [at] puck] On Behalf Of Kin Wai
Sent: Tuesday, November 03, 2009 8:31 AM
To: 'Ryan Ratliff'
Cc: cisco-voip [at] puck
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]
Sent: Tuesday, November 03, 2009 11:12 PM
To: Kin Wai
Cc: cisco-voip [at] puck
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
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
https://puck.nether.net/mailman/listinfo/cisco-voip
Attachments: image001.png (0.16 KB)
  image002.gif (1.08 KB)
  image003.png (0.16 KB)


kinwai at singnet

Nov 4, 2009, 7:34 AM

Post #8 of 8 (619 views)
Permalink
Re: Trouble with upgrading firmware due to firmware bug [In reply to]

Just an update to everyone.



Today I went onsite again and my observation is the issue with 6.0.2
firmware is that when verifying firmware , it appears to be downloading the
image and when it hits around 14000 ~ 15000 packets according to the network
stats counter, it will stop receiving and reloads. To me it's like some sort
of buffer overflow situation.



The resolution so far is to upgrade to 7.0.3 first , follows by 8.5.2 . This
way , the phone didn't crash. This saves me from having to factory reset
each and every phones in the customer environment.



From: cisco-voip-bounces [at] puck
[mailto:cisco-voip-bounces [at] puck] On Behalf Of Kin Wai
Sent: Tuesday, November 03, 2009 11:31 PM
To: 'Ryan Ratliff'
Cc: cisco-voip [at] puck
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]
Sent: Tuesday, November 03, 2009 11:12 PM
To: Kin Wai
Cc: cisco-voip [at] puck
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
https://puck.nether.net/mailman/listinfo/cisco-voip

Cisco voip RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.