Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Kiwi CatTools > Kiwi CatTools Documentation > Kiwi CatTools 3.11 Administrator Guide > Activities > Activities list > Device.Backup.TFTP


Table of contents
No headers
Created by Caroline Juszczak, last modified by Caroline Juszczak on Jun 28, 2016

Views: 288 Votes: 0 Revisions: 2


Note: We would recommend using the Device.Backup.Running config activity to backup your config files. However, the Device.Backup.TFTP activity may serve as a useful alternative in certain circumstances.


The Device.Backup.TFTP activity will make a backup of the specified file and optionally compare it to the current file on disk. If there are differences, the current file is moved to the "Dated Configs" folder and the filename is appended with the current date. The newly downloaded file then becomes the current file. A HTML "diff" report is created in the "Reports" folder and a copy is e-mailed to the nominated person.


Although this activity is designed to mostly replicate the Device.Backup.Running config activity via TFTP, it is not limited to the device-config. You can specify other files, such as VLAN.dat. You also have the option whether ??to do the compare. Some files may be in binary format and so can't be compared. Finally you can also specify your own command set to TFTP the file.


How it works:

  1. A connection is made via SSH or telnet to the device.
  2. The commands to TFTP the specified file are issued.
  3. The file is collected and stored in the TFTP folder.
  4. A check is made to see if there is an existing file on disk for this device.
  5. If not, the newly downloaded file is placed in the specified folder as the current file backup.
  6. If a current file is present, it is compared to the newly downloaded file.
  7. A text and HTML report is made of the differences (if any) and stored in the "Reports" folder.
  8. If differences are found, a copy of the difference report is sent via e-mail.
  9. The current ??file is moved into the "Dated configs" folder and appended with the current date.
  10. The newly downloaded file is put in the specified folder and becomes the current file backup.

For more information see Setting up the activity


This activity has only been added to the following scripts:

  • AlliedTelesis.AlliedWare.Plus
  • Cisco.Router.General
  • Cisco.Switch.IOS
  • Cisco.Switch.CatOS
  • Cisco.Firewall.PIX
  • Cisco.Wireless.Lan
  • Fortinet.FortiOS.General
  • Generic.Device
  • HP.Switch.2500
  • NEC.Univerge.IX
  • Nortel.Switch.Ethernet
  • Nortel.Switch.NoCLI
  • Bluecoat.Cacheflow
  • Checkpoint.VPN
  • F5.BigIP.TMSH
  • PaloAlto.FireWall
  • SonicWall.SonicOS
Last modified