Cisco 2960 archive filename

[kab00m]

Greetings,

I have a number of 2960 switches and noticed strange behavior. All of them have the archive enabled:

archive
path tftp://tftp/cisco/$h-confg.
write-memory

However they leave files of different format on TFTP server:

ethelc-confg.Jan-16-11-44-28-1

etheld-confg..Jan-16-11-44-47-2

This is not even annoying but strange since all the software is equal:

Cisco IOS Software, C2960 Software (C2960-LANBASEK9-M), Version 15.0(2)SE5, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2013 by Cisco Systems, Inc.
Compiled Fri 25-Oct-13 13:34 by prod_rel_team

ROM: Bootstrap program is C2960 boot loader
BOOTLDR: C2960 Boot Loader (C2960-HBOOT-M) Version 12.2(46r)SE2, RELEASE SOFTWARE (fc1)

What can make two of four switches add an extra dot in the filename?

Thanks in advance

[Mark Malone]

Does it only do it when going to the TFTP server , if you stored them to flash locally does it do it , i have archive running to my flash multiple types of switches and i dont see that on any of the internal flash drives adding extra ..s, wondering if its more related to the TFTP server
is the archive still recording correctly all the information is in it ?

[kab00m]

I wrote all configs once again and all switches named files in the right way.

1 tftp://tftp/cisco/otheld-confg.Jan-11-17-52-12-0
2 tftp://tftp/cisco/otheld-confg..Jan-16-11-43-18-1
3 tftp://tftp/cisco/otheld-confg.Feb-13-15-09-31-2 <- Most Recent

It seem to be misconfiguration by someone, which wasn't noticed. 

Sorry for bothering, everything seems to be alright.

[Georg Pauwen]

Hello,

looking at the path, there is a '.' at the end, what if you leave that out ?

path tftp://tftp/cisco/$h-confg. <-- remove ending dot

[kab00m]

I wrote all configs once again and all switches named files in the right way.

1 tftp://tftp/cisco/otheld-confg.Jan-11-17-52-12-0
2 tftp://tftp/cisco/otheld-confg..Jan-16-11-43-18-1
3 tftp://tftp/cisco/otheld-confg.Feb-13-15-09-31-2 <- Most Recent

It seem to be misconfiguration by someone, which wasn't noticed.

Sorry for bothering, everything seems to be alright.