CUCM 7.1(3) TFTP Auth Fail

[keithknowles]

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?

[keithknowles]

.

[fjrubiobarcena]

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?

[thisisshanky]

Was this problem resolved..??

having same issue on 7.1.3

[Jonathan Schulenberg]

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.

[Wilson Samuel]

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

[keithknowles]

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.

[alijames]

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

[keithknowles]

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.

[aech]

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.

[keithknowles]

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. :)

[Telcocapital]

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.

[jgentsch]

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?

[coleman.noc]

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

[jgentsch]

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.

[zzbronski]

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).