Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Kiwi CatTools > Kiwi CatTools Documentation > Kiwi CatTools 3.11 Administrator Guide > Menus > File > Import devices from tab delimited file

Import devices from tab delimited file

Table of contents
No headers

Choose the following menu option to import devices from a tab delimited file. The current database is backed up before the import operation occurs.

File >??CatTools database >??Import > Import devices from tab delimited file

This first screen that appears will prompt you to confirm the import operation.


Press Yes to continue. Press No or Cancel to exit the import operation.

Next, you need to select the file to import from. By default, the file mask is set to "Export_Device.txt".

Select the file to import and press Open.

You are now given options as to how to handle imported devices that have the same names as existing devices.


The import process always Adds a new device.

When a duplicate is found, you may elect to:

  • Update existing device with the imported device's data. This overwrites the current device data with any fields that are found in the import data. Any fields that are not found in the import data are not changed in any way.
  • Rename imported device. A new device is created with _imported_0 appended to the current device name. The last character is a sequential digit that is incremented when more than 1 devices with the same name are encountered.
  • Skip imported device. The imported device data is ignored.

Choose action for each imported device. Any time a duplicate name is found the following dialogue is displayed:


You can view the differences between the 2 devices and choose what action to take for that particular device.

Should you wish to you can also choose to Apply to all duplicates subsequent.

Pressing the Cancel button terminates the import process immediately.

When the import operation is complete, a message will appear.


This will tell you how many devices were imported from the file.

If any warnings or error are shown you should check the Info Log for more details.

Device import file format.

The file must start with a header row that defines the fields. The rows following the header are treated as data.

For example:


The fields can be in any order, but must follow the same naming convention as the CatTools Export devices to tab delimited file function.

At a minimum, the file must contain the following 3 fields:

  • Type (The CatTools device type)
  • Name (A unique name for the device)
  • HostAddress (The IP address or hostname for the device)

Below are a list of the device fields:

  • Type
  • Group
  • Name
  • HostAddress
  • Filename (Unique filename for device, no path or file extension required. If not specified, CatTools will derive from the Name field)
  • Model
  • ConnectVia
  • Telnet
  • Session
  • VTYPass
  • ConsolePass
  • EnablePass
  • PrivilegeLevel
  • AAAUsername
  • AAAPassword
  • SSH Username
  • SSH Password
  • SNMPRead
  • SNMPWrite
  • RequireVTYLogin
  • LoginUsesAAA
  • EnableUsesAAA
  • VTYPrompt
  • ConsolePrompt
  • EnablePrompt
  • AAAUserPrompt
  • AAAPassPrompt
  • Address1
  • Address2
  • Address3
  • ContactName
  • ContactPhone
  • ContactEmail
  • ContactOther
  • AlertEmail
  • SerialNumber
  • AssetTag
  • Identification
  • SerialOther
  • ActivitySpecific1
  • ActivitySpecific2

The best way to create a template to start with is to add a few example devices to CatTools first.

Then use the File | Export | Export devices to tab delimited text file menu item. The file created will contain all the required fields you need to use.

Plain text values found in fields that are normally encrypted within the database (e.g. HostAddress, VTYPass, EnablePass SNMPRead, etc) will automatically be encrypted as part of the import process.

Last modified


This page has no custom tags.