05-07-2014 12:19 PM - edited 03-07-2019 07:22 PM
Hi,
I have configured a Kron schedule for my 3650 to copy its config to a tftp once a week, the problem is that it does not work even though I have the exact same config on a 1921 router and all of my 2960 switches. The config is exactly:
kron occurrence BACKUP_SUNDAY at 22:00 Sun recurring
policy-list BACKUP
kron policy-list BACKUP
cli copy run tftp://192.168.20.34
I know it is not because of the confirmation because I have already specified: file prompt quiet to avoid that issue. My question now is why does the 3650 not work while everything else does with the exact same config? Or should I use the EEM to do this kron job? and if so, how should the config look for the EEM because the documentation is not clear on how to do this.
Edit*
Just to add a little detail, this is version 3.3.1SE and after the job is supposed to occur, the kron policy-list disappears from the config.
Thanks,
Waqas
Solved! Go to Solution.
05-07-2014 03:12 PM
Hello Waqas,
The first thing we need to do is upgrade to 3.3.3 if possible. 3.3.1 is susceptible to a known Kron bug (see CSCtk68692) that will lock NVRAM. However if you cannot upgrade at this time, you can use this simple archive script that I put together for another customer the other day with the same issue:
<sample config>
conf t
no archive
archive
path ftp://192.168.12.12/backup/configs
write-memory
time-period 1440 <--- daily backup (use 10080 for weekly)
end
wr
** in minutes
1440 = daily
10080 = weekly
Hope that helps
Luke
05-07-2014 10:35 PM
path ftp://192.168.12.12/backup/configs
path ftp://192.168.12.12/backup/configs/$h-
.05-07-2014 03:12 PM
Hello Waqas,
The first thing we need to do is upgrade to 3.3.3 if possible. 3.3.1 is susceptible to a known Kron bug (see CSCtk68692) that will lock NVRAM. However if you cannot upgrade at this time, you can use this simple archive script that I put together for another customer the other day with the same issue:
<sample config>
conf t
no archive
archive
path ftp://192.168.12.12/backup/configs
write-memory
time-period 1440 <--- daily backup (use 10080 for weekly)
end
wr
** in minutes
1440 = daily
10080 = weekly
Hope that helps
Luke
05-07-2014 10:35 PM
path ftp://192.168.12.12/backup/configs
path ftp://192.168.12.12/backup/configs/$h-
.05-08-2014 05:18 PM
Thanks for taking the time to rate our posts, Waqas.
05-07-2014 03:40 PM
Thanks for the input Luke
I checked for bug CSCtk68692 and it doesn't look like 3.3.1 is being affected by it.
Although I should probably upgrade just in case.
Cheers,
Waqas
05-07-2014 06:28 PM
Hello Waqas,
Sorry, I will work on getting the bug notes updated. Your version is indeed susceptible to CSCtk68692, I just worked on this issue last week with a customer. If you take a look at the link below, you will see that under "resolved caveats" in 3.3.3, CSCtk68692 is listed first.
http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3650/software/release/3se/release_notes/OL30563.html#pgfId-752762
Luke
05-08-2014 11:31 AM
Hi Luke,
I tried to use the archive command but the NVRAM is locked on me, looks like this version and IOS XE 3.3.2 SE is also susceptible to the same bug.
Waqas
05-08-2014 11:46 AM
Yes, the fix is in release 3.3.3
luke
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide