Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

CUCM 7.1(3) TFTP Auth Fail

Since upgrading to CUCM 7.1.3.10000-11 any new phone plugged into the system gets an "auth fail" from the TFTP server when attempting to upgrade the firmware to the version that comes with 7.1(3). Phones that were registered prior to the upgrade work just fine. I am seeing the same behanviour on our non-production environment which is also at 7.1.3-10000-11.

Phone Firmware for 7.1(3) on 7961G set is SCCP41.8-5-2SR1S

Has anyone sle seen this behaviour before...is anyone else running 7.1(3) yet?

1 ACCEPTED SOLUTION

Accepted Solutions
Community Member

Re: CUCM 7.1(3) TFTP Auth Fail

Hi Everybody

My Issue was taht the Phone Firmware first must be 8.5.2 and after taht the phone can go to 8.5.3. This is written in the Relase Notes

http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/firmware/8_5_3/english/release/notes/7900_853.html

Regards

41 REPLIES
Community Member

Re: CUCM 7.1(3) TFTP Auth Fail

Hi

I have the same Problem with this Version 7.1.3.10000-11.

Do you have a workaround?

Re: CUCM 7.1(3) TFTP Auth Fail

I've seen this before where a CTL file was being used? Are you using any type of CTL File?

Community Member

Re: CUCM 7.1(3) TFTP Auth Fail

No we aren't using any CTL files, thats the strange part.

Community Member

Re: CUCM 7.1(3) TFTP Auth Fail

No I don't use any type of CTL files. I don't use secutrity.

Regards

Community Member

Re: CUCM 7.1(3) TFTP Auth Fail

hi

did u get answer to this?

my problem is that I can use the IP Communicator to make calls but the same settings with the same DN on the ip phone does not work and i get the auth-fail message as well. i used the ctl but revreted the mode to the non-secure mode. still the  same.

Community Member

Re: CUCM 7.1(3) TFTP Auth Fail

Hi all,

This thread has split into two different paths.  The original purpose of the thread was to discuss why a two-step firmware upgrade was required and this has been answered.  For the other issue, where it looks like a call is failing, it is probably best to start a new discussion and get a TAC case opened.

Thanks,


Rudy

Community Member

Re: CUCM 7.1(3) TFTP Auth Fail

Hi kelvin,

Any updates on this? i am facing the same problems. I upgraded the firmware to 8.5.2SR1 but still the calls fail. I did use the CTL Client and updated the ctl file. strangely i can use the IP Communicator but not the IP Phones.

Any help will be appreciated

Community Member

Re: CUCM 7.1(3) TFTP Auth Fail

I've got the same issue and we are also not using CTL yet.

Hall of Fame Super Red

Re: CUCM 7.1(3) TFTP Auth Fail

Hi Keith/Guys,

It sounds very much like this bug. I would try a TAC case and load a newer or older firmware for the devices and then change the info in the Device Defaults;

CSCsu73815 Bug Details

7945/7965 cannot recover from file Auth Failure during upgrade/downgrade

Symptom:

If all image files do not pass file authentication during phone load upgrades form 8.4(1)IV6.29 to a new version, phone can not come up using the previously installed image.

Conditions:

Test environment:

phone load : 8-4-1IV6-29S

Call Manager: 7.1.0.39001-1, mixed mode

Reproduce steps:

1. Setup 7945 or 7965 phone with 8-4-1IV6-29S active load. Register it to the CCM.

2. Sign a different phone load on the phone configuration page, for example 8-4-1IV6-26S.

3. Modify one of the new image files on TFTP server, for example, modify 1-2 bytes in apps45.8-4-1IV6-26.sbn.

4. Reset the phone.

5. Phone resets and requests the new image. When downloading the modified image file finished, 'Auth Fail' is shown on the screen.

Workaround:

None

Further Problem Description:

None

Status

Fixed

Severity

3 - moderate

Last Modified

In Last Year

Product

Cisco Unified IP Phones 7900 Series

Technology

1st Found-In

8.5(1)

9.0(2)

Fixed-In

8.5(2)FT1.4

Hope this helps!

Rob

Community Member

Re: CUCM 7.1(3) TFTP Auth Fail

I suspect it to be a firmware issue as well, but why would it only affect new phones added to the system and not the ones that were registered prior to the upgrade? I have verified that phones that were registered prior to the upgrade were able to obtain the firmware from the server without issue.

Hall of Fame Super Red

Re: CUCM 7.1(3) TFTP Auth Fail

Hey Keith,

I hear you :) It's quite possible that the new phones have the factory firmware (referenced in the bug)

phone load : 8-4-1IV6-29S

(or something very similar) where your existing phones had 8-4-3x;

Just a guess here.

Cheers!

Rob

Community Member

Re: CUCM 7.1(3) TFTP Auth Fail

OK, that kinda makes sense...as much as bugs generally do. :) I will give it a shot and post the result. As always, thanks for your help Rob.

Community Member

Re: CUCM 7.1(3) TFTP Auth Fail

Hi Everybody

My Issue was taht the Phone Firmware first must be 8.5.2 and after taht the phone can go to 8.5.3. This is written in the Relase Notes

http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/firmware/8_5_3/english/release/notes/7900_853.html

Regards

Community Member

Re: CUCM 7.1(3) TFTP Auth Fail

I hate to ask, but what is the best way of accomplishing the downgrade and then the upgrade?

Community Member

Re: CUCM 7.1(3) TFTP Auth Fail

.

Community Member

Re: CUCM 7.1(3) TFTP Auth Fail

Hello, I have installed in a callmanager 5.1 the latest device package and I am having the same issue. What do tou think it can be the solution?

unninstall the latest device package and install an older one?

Re: CUCM 7.1(3) TFTP Auth Fail

Was this problem resolved..??

having same issue on 7.1.3

VIP Super Bronze

Re: CUCM 7.1(3) TFTP Auth Fail

It appears you must downgrade the firmware to 8.5(2) - NOT 8.5(2)SR1 - as mentioned in the release notes. Once the phones are at that version, you can upgrade from there.

Re: CUCM 7.1(3) TFTP Auth Fail

I hate to ask such a simple question:

Wont a Factory Reset solve the issue?

I mean, it will rewrite practically everything on the ph.

Just a wild guess as I never had this issue till now.

Regards

Community Member

Re: CUCM 7.1(3) TFTP Auth Fail

Depends on what the factory firmware is that your phone is running. The firmware that ships with 7 requires you to be at a certain version before it can be upgraded...if your factory version isn't at least that then the upgrade wont work.

Community Member

Re: CUCM 7.1(3) TFTP Auth Fail

DON'T TRY A FACTORY RESET OF THE PHONE!!

If you do, and a suitable rev of firmware is not able to load, the phone tries to update the firmware, fails and then just sits there displaying the Cisco Logo screen, but with a circle bottom left, instead of the usual square with a tick in it. Then after a short time, it reboots, and cycles through the above again.

I first had it with 7942 phones, but this was cured by installing 8.5.2S & 8.5.2SR1 variants.

However, I still have the same problem with brand new 7906/7911 phones, even though the above firmwares are also installed.

Cheers,

Alistair

Community Member

Re: CUCM 7.1(3) TFTP Auth Fail

This is very true. The fix for this, should it occur, is to change the DHCP TFTP address to a TFTP server that has an appropriate mid-level of firmware (one that is compatible to be upgraded from what your phone was running), and then let the phone upgrade. If you are fortunate, the mid-level firmware will also be compatible to upgrade to your production formware on the Communications Manager. If this is the case, simply point the DHCP TFTP server back to the CUCM. If not you will have tp upgarde your phone, yet again, to a version that is compatible before going to the CUCM firmware.

Community Member

Re: CUCM 7.1(3) TFTP Auth Fail

This is a big pain!

Especially when one is installing maybe 30 phones per week.

I wonder how many phones actually have left the factory with this renegade sw release and if they are now flushed through the system. How quickly did you realise the problem Cisco? Are we to be plagued by this for the next six months? Looks like we may have to setup all new phones on our development system first. Bah Humbug!!

Regards

Alan.

Community Member

Re: CUCM 7.1(3) TFTP Auth Fail

I feel your pain. Especially since everytime we get phones with this wacky firmware I have to roll my development system back to the old release just to update phones and the return it to the production release. Just think though it could be worse...not everyone has development systems with which to use. :)

Community Member

Re: CUCM 7.1(3) TFTP Auth Fail

I'm getting the auth fail also. After running the tftp debug, I get the following. Looks like the problem could have something to do with the following missing files:

Oct 14 08:01:28.140: TFTP: Looking for CTLSEP002584A383C1.tlv

Oct 14 08:01:52.180: TFTP: Looking for SEP002584A383C1.cnf.xml

Oct 14 08:01:53.068: TFTP: Looking for English_United_States/td-sccp.jar

Oct 14 08:01:53.224: TFTP: Looking for United_States/g3-tones.xml

As search for these on Cisco.com gave the following:

CME-locale-en_US-English-7.0.1.1.tar

----------------------------

Here is the tftp debug info:

WFSBI#debug tftp events

TFTP Event debugging is on

WFSBI(CP-7975)#

Oct 14 08:01:28.140: TFTP: Looking for CTLSEP002584A383C1.tlv

Oct 14 08:01:28.216: TFTP: Looking for SEP002584A383C1.cnf.xml

Oct 14 08:01:28.216: TFTP: Opened system:/its/vrf1/XMLDefault7975.cnf.xml, fd 9,

size 1190 for process 332

Oct 14 08:01:28.216: TFTP: Finished system:/its/vrf1/XMLDefault7975.cnf.xml, tim

e 00:00:00 for process 332

Oct 14 08:01:34.968: TFTP: Looking for SCCP75.8-5-3S.loads

Oct 14 08:01:34.968: TFTP: Opened flash:/SCCP75.8-5-3S.loads, fd 9, size 650 for

process 332

Oct 14 08:01:34.972: TFTP: Finished flash:/SCCP75.8-5-3S.loads, time 00:00:00 fo

r process 332

Oct 14 08:01:52.084: TFTP: Looking for CTLSEP002584A383C1.tlv

Oct 14 08:01:52.180: TFTP: Looking for SEP002584A383C1.cnf.xml

Oct 14 08:01:52.180: TFTP: Opened system:/its/vrf1/XMLDefault7975.cnf.xml, fd 9,

size 1190 for process 332

Oct 14 08:01:52.184: TFTP: Finished system:/its/vrf1/XMLDefault7975.cnf.xml, tim

e 00:00:00 for process 332

Oct 14 08:01:53.068: TFTP: Looking for English_United_States/td-sccp.jar

Oct 14 08:01:53.224: TFTP: Looking for United_States/g3-tones.xml

Oct 14 08:01:53.632: %IPPHONE-6-REG_ALARM: 25: Name=SEP002584A383C1 Load= SCCP75

.8-3-2S Last=Initialized

Oct 14 08:01:53.668: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-92:SEP002584A383C1 I

P:10.100.1.21 Socket:2 DeviceType:Phone has unregistered abnormally.

Oct 14 08:01:53.668: %IPPHONE-6-REGISTER: ephone-92:SEP002584A383C1 IP:10.100.1.

21 Socket:3 DeviceType:Phone has registered.

WFSBI#

7941

Oct 14 09:42:31.051: TFTP: Looking for CTLSEP002584166896.tlv

Oct 14 09:38:55.843: TFTP: Looking for SEP002584166896.cnf.xml

Oct 14 09:38:55.843: TFTP: Opened system:/its/vrf1/XMLDefault7941.cnf.xml, fd 9,

size 1192 for process 332

Oct 14 09:38:55.847: TFTP: Finished system:/its/vrf1/XMLDefault7941.cnf.xml, tim

e 00:00:00 for process 332

Oct 14 09:38:59.739: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-91:SEP002584166896 I

P:10.100.1.22 Socket:1 DeviceType:Phone has unregistered abnormally.

Oct 14 09:39:03.071: TFTP: Looking for SIP41.8-5-2SR1S.loads

Oct 14 09:39:03.071: TFTP: Opened flash:/SIP41.8-5-2SR1S.loads, fd 9, size 654 f

or process 332

Oct 14 09:39:03.075: TFTP: Finished flash:/SIP41.8-5-2SR1S.loads, time 00:00:00

for process 332

Oct 14 09:39:28.959: TFTP: Looking for CTLSEP002584166896.tlv

Oct 14 09:39:29.047: TFTP: Looking for SEP002584166896.cnf.xml

Oct 14 09:39:29.047: TFTP: Opened system:/its/vrf1/XMLDefault7941.cnf.xml, fd 9,

size 1192 for process 332

Oct 14 09:39:29.051: TFTP: Finished system:/its/vrf1/XMLDefault7941.cnf.xml, tim

e 00:00:00 for process 332

Oct 14 09:39:30.467: TFTP: Looking for English_United_States/mk-sccp.jar

Oct 14 09:39:30.663: TFTP: Looking for United_States/g3-tones.xml

Oct 14 09:39:31.271: %IPPHONE-6-REG_ALARM: 25: Name=SEP002584166896 Load= SCCP41

.8-3-1S Last=Initialized

Oct 14 09:39:31.323: %IPPHONE-6-REGISTER: ephone-91:SEP002584166896 IP:10.100.1.

22 Socket:1 DeviceType:Phone has registered.

Community Member

Re: CUCM 7.1(3) TFTP Auth Fail

Ok, a little annoyed as I read this post. I just installed CCM7.1(3). It came on the server pre-loaded from the factory. I plugged a brand new 7945 in and got the auth fail error. The firmware loaded on CUCMBE is 8.5.2SR1S. Anyone have a verified TAC fix for this yet?

Community Member

Re: CUCM 7.1(3) TFTP Auth Fail

I noticed the same issue with one of our customers. After hours of tinkering the fix seemed to be to put 8.5.2 on the affected phones, reset them, and then use SR1. Will be attempting an upgrade to FW 8.5.3 to see if this fixes it

Community Member

Re: CUCM 7.1(3) TFTP Auth Fail

I installed 8-5-2 and 8-5-3 on my production environment, set the device default for my new phones to 8-5-2. Once those phones upgraded, I changed the device default to 8-5-3...all was well. This seemed to be the simplest solution.

Community Member

Re: CUCM 7.1(3) TFTP Auth Fail

I agree with the previous statement about it being a major pain in the tucuss. I just made the jump from 6.1(2) to 7.1(3). I knew of this problem before the jump and pro-actively upgraded all the phones in production to baseline version 8.5.2. However, every time I add a new phone to the system it is running an old firmware version from the factory (SCCP45.8-3-2S). The minimum is 8.3.3 in order to get the 8.5.2sr1 and higher. You must first go to baseline 8.5.2 first.

I would like to know how I could setup a default in the system so that when the new phone auto registers that is will get the baseline first and then go to the new version that comes with 7.1(3).

33161
Views
25
Helpful
41
Replies
CreatePlease to create content