Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Kiwi CatTools > Get Support For Devices Added to CatTools

Get Support For Devices Added to CatTools

Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 51 Votes: 1 Revisions: 6

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 in the list of CatTools supported device types and is not covered by one of the CatTools generic scripts then don't worry. Support for new devices is being added and improved all the time. From CatTools v3.3.2, there is now a facility to create your own custom device scripts. Therefore 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 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 on-line help file at: http://www.kiwisyslog.com/help/cattools/dev_creatingcustomdevice.htm

However, 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 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 config mode
  • How to save changes to the config. eg write mem or copy running startup
  • How to display the config (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)

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

Last modified
19:44, 22 Jun 2016

Tags

Classifications

Public