[cisco-voip] Handsets can't find firmware on TFTP?

Thu Mar 28 11:13:00 EDT 2013

You know there is a 7925 version 3 that can't go lower than the factory firmware version that shipped with the phone.  I recall there was a support forum article about it.

https://supportforums.cisco.com/docs/DOC-29291

migilles<https://supportforums.cisco.com/people/migilles> Jan 29, 2013 1:10 PM<https://supportforums.cisco.com/docs/DOC-29291#comment-16189>

The F.2 image is equivalent to 1.4.3SR1.2 and any new hw revs that require this load or later can not be downgraded.

This is outlined in the 1.4(3)SR1 release notes.

http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7925g_7925gEX_7926/firmware/1_4_3SR1/P256_BK_WC0078A9_00_wireless-phone-release-notes-1_4_3sr1.html#P256_TP_W908AC8A_00

Per the screenshot above, you can see this 7925 is hw rev 3.0, which is the latest rev that requires 1.4.3SR1.2 or later.

New 792x phones pre-loaded wtih the F.2 mfg image will require 1.4.3SR1.2 or later as that release contains an updated LCM driver.

There are restrictions in place to prevent downgrading F.2 or 1.4.3SR1.2 to earlier builds; e.g. 1.4(2).

If you attempt to perform a phone recovery via the bootrom to load a non-supported firmware, then the phone may not boot properly.

So you would need to just perform this process again to recover the firmware by uploading 1.4.3SR1.2 using the TAR file.

So in summary, the recovery process should only be used to recover a phone with a corrupt image and should NOT be used to force a downgrade.

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of William
Sent: Thursday, March 28, 2013 10:07 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Handsets can't find firmware on TFTP?

Hello List,

I'm having some issues with our handsets not being able to find their specified firmware on the TFTP server, I was wondering if anyone could shed light on this?

I have installed CP7925G-1.4.1 firmware on our Call Manager, installation went fine and confirmed the entry on Device Defaults as 'CP7925G-1.4.1' for Cisco 7925G.

The TFTP has been restarted, when the phones reboot I get the 'Firmware update failed' message, here are the logs pulled from the phone:

2013-03-28 09:46:37:0920 CP-7925G user.err fwupdate[316]: downloading CP7925G-1.4.1/CP7925G-1.4.1.LOADS failed: File not found[2]
2013-03-28 09:46:37:0920 CP-7925G user.err fwupdate[316]: [884 at extif.c]: TFTP CP7925G-1.4.1/CP7925G-1.4.1.LOADS fail. err = 0, status = 0x2(File not found)
2013-03-28 09:46:38:0080 CP-7925G user.info<http://user.info> imgauthd: IMG_AUTH: verify with current(new) key RELEASE 7925 key ^M
2013-03-28 09:46:38:0100 CP-7925G user.info<http://user.info> imgauthd: IMG_AUTH: verififed with current(new) RELEASE 7925 key ^M
2013-03-28 09:46:38:0100 CP-7925G user.info<http://user.info> imgauthd: IMG_AUTH: verify SUCCESS ! /var/fwdnld/CP7925G-1.4.1.LOADS ^M
2013-03-28 09:46:38:0110 CP-7925G user.err fwupdate[316]: [884 at update.c]: HW_REV check fail
2013-03-28 09:46:38:0110 CP-7925G user.err fwupdate[316]: [829 at main.c]: Error -4: Load CP7925G-1.4.1.LOADS update fail
2013-03-28 09:46:38:0160 CP-7925G user.info<http://user.info> Cisco7925-Init: Process /sbin/fwupdate -s --cont --nobgchk --memchk 3600 -o /var/log/fwupdate.log run status=1
2013-03-28 09:46:38:0160 CP-7925G user.info<http://user.info> Cisco7925-Init: catchchild:pid =316 cmd=/sbin/fwupdate -s --cont --nobgchk --memchk 3600 -o /var/log/fwupdate.log normal termination
2013-03-28 09:46:38:0160 CP-7925G user.info<http://user.info> Cisco7925-Init:  Child Terminated abnormally.....
2013-03-28 09:46:38:0160 CP-7925G user.debug Cisco7925-Init: run state [networkup]action /sbin/fwupdate -s --cont --nobgchk --memchk 3600 -o /var/log/fwupdate.log done

As you can see, the phone is looking for /CP7925G-1.4.1/CP7925G-1.4.1.LOADS and I believe it should be looking for /CP7925G-1.4.1.LOADS from the root of the TFTP file system.

I have confirmed the IP of our TFTP server within the phones settings and checked the logs on the TFTP server to verify its trying to GET a file/directory that doesn't exist, can you think of any other reason why it is looking inside a directory of the TFTP server and not just the root? I've noticed this behaviour on multiple phones both 7921's and 7925's.

Thank you.

W

itevomcid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130328/f512fb0e/attachment.html>