Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Kiwi CatTools > Kiwi CatTools 3.11 Administrator Guide > Troubleshooting > Debug Log

Debug Log

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

Views: 302 Votes: 0 Revisions: 1


What is Debug Log?

Debug log gives the exact picture of communication between devices and CatTools. Debug log is used when there may be some communication errors.

4 main notations used in Debug log are:

  • <R-Read - when something is read from the device
  • <W-Write - when something is written from device
  • <C- Connected to device
  • <D- dis-connected from device

A sample Debug logs is given below:


<NEWSESSION CatTools 3.10.0 1/29/2014 3:47:29 AM>


<DEVICE TYPE=Cisco.Router.General>

<ACTIVITY TYPE=Device.Backup.Running Config>

<ACTIVITY SCRIPT=C:\Program Files\CatTools3\Scripts\Client.Device.Backup.Running Config.txt>


<C OK 3:47:30 AM>

<R-3:47:30 AM>[13][10][13][10]User Access Verification[13][10][13][10]Username:

<W-3:47:30 AM>admin[13]

<R-3:47:31 AM>admin

<R-3:47:31 AM>[13][10]Password:

<W-3:47:31 AM>password[13]

<R-3:47:31 AM>[13][10]bgp-2651-03#

<W-3:47:31 AM>[13]

<R-3:47:31 AM>[13][10]bgp-2651-03#

<W-3:47:36 AM>enable

<R-3:47:36 AM>enable

<W-3:47:37 AM>[13]

<R-3:47:37 AM>[13][10]% No password set[13][10]bgp-2651-03#

<W-3:47:37 AM>term no mon

<R-3:47:37 AM>term no mon

<W-3:47:37 AM>[13]

<W-3:47:38 AM>term len 0

<R-3:47:38 AM>term len 0

<W-3:47:38 AM>[13]

<R-3:47:38 AM>[13][10]bgp-2651-03#

<W-3:47:39 AM>show running

<R-3:47:39 AM>show runni

<R-3:47:39 AM>ng

<W-3:47:39 AM>[13]

<R-3:47:39 AM>[13][10]

<R-3:47:39 AM>Building configuration...[13][10]


W-3:47:40 AM>[13]

<R-3:47:41 AM>[13][10]bgp-2651-03#

<W-3:47:41 AM>logout[13]

<D 3:47:41 AM>



<PROMPT VTY="bgp-2651-03>">

<PROMPT ENABLE="bgp-2651-03#">


A sample debug log where activity is not running is given below:


<NEWSESSION CatTools 3.10.0 1/29/2014 3:52:23 AM>


<DEVICE TYPE=Juniper.Router>

<ACTIVITY TYPE=Device.Backup.Running Config>

<ACTIVITY SCRIPT=C:\Program Files\CatTools3\Scripts\Client.Device.Backup.Running Config.txt>

<USERS NAME FOR DEVICE=Juniper Router 1>

<C OK 3:52:24 AM>

<R-3:52:25 AM>[13][00][13][10]stp-j2320 (ttyp0)[13][00][13][10][13][00][13][10]login:



WFMDRetVal=1 Waiting for: "Username:"

WFMDRetVal=2 Waiting for: "Password"

WFMDRetVal=3 Waiting for: "Password required, but none set"

WFMDBuffer="[13][00][13][10]stp-j2320 (ttyp0)[13][00][13][10][13][00][13][10]login: "


How to use debug log:

Using the debug log you can check the exact communication between the device and CatTools.

If you get an output as in 2nd sample above, then CatTools is waiting for a username prompt, but the prompt given by device is 'login' from buffer. So, using the variations functions we can change the device scripts and manually enter information for the prompts.

In Variations, a user can add the prompt which will be added to the return value from the buffer and when the activity is running the next time, the return value is matched and communication is continued.

Last modified