Cisco 1841 IOS(Firmware) upgrade c1841-adventerprisek9-mz.123-14.T3.bin(support SSH v2)

######################################################
Before procedure need setup ftp Username & Password
######################################################

# Del origin IOS c2800nm-ipbase-mz.124-15.T9.bin
del /force /recursive flash:c1841-ipbase-mz.124-1c.bin

del /force /recursive flash:c1841-adventerprisek9-mz.123-14.T3.bin

del /force /recursive flash:securedesktop-ios-3.1.1.27-k9.pkg

del /force /recursive flash:sdm.tar

# Del origin IOS c2800nm-ipbase-mz.124-24.T6.bin
del /force /recursive flash:c2800nm-ipbase-mz.124-24.T6.bin

# Use ftp service transfer IOS to flash
copy ftp://172.17.200.2/CiscoIOS/c1841-entservicesk9-mz.124-19a.bin flash:

# Verify IOS file
verify /md5 flash:/c1841-entservicesk9-mz.124-19a.bin aefd7bef96f681fddf5bd1019252425b

# Setup Boot from IOS c1841-entservicesk9-mz.124-19a.bin
config term
# Delete old boot config
no boot system flash c1841-adventerprisek9-mz.123-14.T3.bin

# Add New boot config
boot system flash c1841-entservicesk9-mz.124-19a.bin
exit
write

Cisco Archive(Schedule Backup Config)

Cisco Archive(Schedule Backup Config)

config term

archive
 log config
  hidekeys
 path ftp://172.17.200.2/CiscoArchive/$h-config_
 write-memory
 time-period 10080








======================================================================

The next backup will be performed in one week exactly (time in minutes), but what if we would like to configure this periodicity with an explicit date time? Unfortunately with the current Archive features, it is not possible. In that case we could combine the Archive feature with Kron Schedule.

Kron is a command scheduler used to automate tasks in the Cisco IOS Software. With Kron, we can set policies and use them once or with a certain periodicity. For this we configure a Kron Policy List and then apply an occurrence to the global Kron policy. Note that Kron does not work with interactive commands, meaning commands that have some type of dialog for validation. An example would be "copy running-config startup-config". In this case, a dialog would appear in order to validate the execution of the sentence. Since we have this "limitation" with that sentence, we could use the "write memory" command which does not need any validation and use it in the Kron Policy.

R1(config)#kron policy-list CONFIGURATION_BACKUP
R1(config-kron-policy)#cli write memory
R1(config)#kron occurrence Backup BACKUP_OCCURRENCE at 9:00 25 recurring
R1(config-kron-occurrence)#policy-list CONFIGURATION_BACKUP

=============================================================================

Thank you for response, you can see below our used configs.




!

kron occurrence backup-config at 10:09 Wed recurring system-startup

policy-list backup-config

!

kron policy-list backup-config

cli show config | redirect tftp://10.1.1.200/tftp/iznsw25.conf

!