cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3111
Views
0
Helpful
7
Replies

SPA122 'Resync fails on FNF' bug!

raisacomhb
Level 1
Level 1

Hello,

the option 'Resync fails on FNF' does not seem to work for SPA1x2 in FW 1.2.1 (004).

The SPA logs 'Resync failed: file not found' and associates the 'Resync Error Retry Delay' timer, regardless of the option set to No.

I tried various combinations, but it all comes down to the fact, that this is definetely not working (as it was on SPA-2102).

The main problem now is that this kills our current provisioning system. Oh, Cisco, what have you done???

Kind regards,

  E. Rentzow

7 Replies 7

laharper
Community Member

Hello E. Rentzow,

You are most likely being affected by an issue identified in v1.2.1(004) firmware regarding three "Resync" parameters.

Please refer to the following link for the resolution:

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

Regards,

-Lance Harper

Cisco Systems, Inc.

Hi,

I don't think so. The device was already factory reset and the parameters are as recommended (e.g., no time set).

Setting the 'Resync fails on FNF' has absolutely no effect, it always fails if file not found, even if it should not fail.

So, case remains open!

Regards,

  Eik

Hi, I just tested a spa122 and it seems to be working.

I see in the log file where the spa122 sends out 'Resync failed: file not found' and it doesn't retry a resync when 'Resync Fails on FNF' is set to no.  I have the 'Resync Error Retry Delay' set to 30, so if was supposed to retry, it should have done so in 30 secs.

Please enclose a log file and config of the provisioning so we can verify, thanks.

Curious! Are you using TFTP or HTTP? I'm using the latter.

The way you examined it is the same I did. I took notice of it when the periodic resync (in lab set to 60 seconds) didn't occur and the error timer came into effect. The log definetely states that the resync failed. Because it works with the SPA-2102 I don't think that I've overseen anything - well it's actually not that complicated ;-)

Eik

I used tftp. 

You used http and this fails for spa122 but worked for spa2102, correct? 
Upon your verification, I will give this info to dev.  Thanks.

Affirmative.

Eik

Hello E. Rentzow, I tried 1.2.1(004) and not getting failure via http as well.

Log file shows 'Resync failed: file not found' and the spa122 doesn't retry again when 'Resync Fails on FNF' is no and my 'Resync Error Retry Delay' is at 20 and I'm not see constant retries every 20 secs.

Going to need your assistance on why the problem is happening for you.  Thanks.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: