Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Kiwi CatTools > Kiwi Cat - Knowledgebase Articles > Get Support For Devices Added to CatTools

Get Support For Devices Added to CatTools

Updated June 22, 2018 

Overview

This article talks about how to get support for devices that are added to Kiwi CatTools.

Environment

  • All Kiwi CatTools versions

Details

If your device is not included on the list of CatTools supported device types, and is not covered by one of the CatTools generic scripts, don't worry. Support for new devices is being added and improved all the time. 

 

As of Kiwi CatTools v3.3.2, there is now a facility to create your own custom device scripts. If there is an immediate need to backup the configuration of a device currently not supported by CatTools, you may be able to add support for the device yourself rather than waiting for it to be added in a future CatTools release.

 

Documentation on the custom device script can be found in the online help file:
http://www.kiwisyslog.com/help/cattools/dev_creatingcustomdevice.htm

Requesting support for your device

If you would like us to consider adding your device then please inquire on thwack to let us know your requirements. When considering what devices to add we look at the following factors:

  • If we can get network access to a device.
    This is by far the fastest way for us to add a new device. If you can send us a Username and Password for your device and we can log into it from our labs then adding support for it is so much easier.
  • How many requests we have for support of that device type.
    Obviously, with limited resources and time we want to help as many people as we can, so the more requests we have for a device the higher up our to-do list it moves.
  • How much information we have on the device.
    If we can't gain network access to a device then the next best thing is to see how the device works by examining logs captured from it. We recommend you capture logs using a tool such as PuTTY.

The more information about the device you can provide us with the better.

Sample device responses to report when requesting device support

The following are examples of the sort of responses we need to see from your device. If the action is not obvious, such as a CTRL-Z keypress, then this should be explained:

  • A successful login.

  • A failed login. Showing responses to bad username and password entries
  • An invalid command being entered
  • An incomplete command being entered
  • Successfully entering and exiting enable/privileged mode
  • Successfully entering and exiting configuration mode
  • How to save changes to the configuration, such as write memory or copy running startup
  • How to display the configuration (both running and startup)
  • A show version type command
  • The necessary commands to show Port / MAC / ARP information
  • Results of a Ping command. Success, failure, and unreachable.
  • Commands to enable and disable paging
  • A --More-- prompt (or equivalent paging prompt)
  • A Yes / No prompt (or equivalent confirmation prompt)

 

Last modified

Tags

Classifications

Public