Righty ho, not sure how many people will know the answer to this, but what they hey!
I've got 5 sets of switches here (iSCSI, Backup, Core, Client and Print), all of which have the same KRON jobs set to copy their configs to TFTP 7 days a week (one job per day). 4 of the 5 sets of switches will happily send their running-config over to the tftp server, 1 of the 5 refuses to play ball.
Now, they are not all the same. We have a 3-way stack of 3750X's in Core, a stack of 2 3750G-24TS-1U's in iSCSI, and the same again in Backup. The Client stack consists of 3750G-48TS-1U and a 3750G-24TS-1U, and finally Print is a single 3560-48TS.
Print is the one that's not playing ball.
Essentially all the switches have the following (obviously with 7 occurrences):
IP address of TFTP and Switch Name changed in the above example.
What is incredibly odd however, is that on the one switch that doesn't work, the kron policy-list gets deleted from the running config after a scheduled recurrence, so subsequent attempts will fail to run due to there not being a policy-list to execute!
Am I missing something obvious with the 3560? Does it not support Kron?
Thanks!
I've got 5 sets of switches here (iSCSI, Backup, Core, Client and Print), all of which have the same KRON jobs set to copy their configs to TFTP 7 days a week (one job per day). 4 of the 5 sets of switches will happily send their running-config over to the tftp server, 1 of the 5 refuses to play ball.
Now, they are not all the same. We have a 3-way stack of 3750X's in Core, a stack of 2 3750G-24TS-1U's in iSCSI, and the same again in Backup. The Client stack consists of 3750G-48TS-1U and a 3750G-24TS-1U, and finally Print is a single 3560-48TS.
Print is the one that's not playing ball.
Essentially all the switches have the following (obviously with 7 occurrences):
Code:
kron occurrence MON-BACKUP at 14:00 Mon recurring
policy-list cfg-bu
!
kron policy-list cfg-bu
cli copy system:/running-config tftp://1.1.1.1/SWITCHNAME-CFG.txt
!IP address of TFTP and Switch Name changed in the above example.
What is incredibly odd however, is that on the one switch that doesn't work, the kron policy-list gets deleted from the running config after a scheduled recurrence, so subsequent attempts will fail to run due to there not being a policy-list to execute!
Am I missing something obvious with the 3560? Does it not support Kron?
Thanks!
