The CatTools Debug file provides details regarding the communication transactions between CatTools and the target system. This can be helpful when CatTools is returning errors.
\Program Files (x86)\CatTools\Debug\
The debug file contains the following:
The DebugLog file also contains within it, the commands and control characters sent to and received from the device.
Below is an extract from a debug log (header and footer removed) showing a simple password only authentication to arrive at the device non-privileged prompt and then logout:
<C OK 4:06:53 PM>
<R-4:06:53 PM>User Access Verification Password:
<D 4:06:54 PM>
For SSH protocol connections, unless the device is setup with 2 factor authentication (e.g. connection over SSH and local device authentication), you will normally only see the connection <C …>tag and then most likely the device hostname prompt. The authentication for SSH connections is handled internally by the WODSSH connection client, so it is not written to the CatTools device debug file.
Once CatTools is connected and logged in, it will expect one of three things:
If it does not receive either one of these, it will report something like this:
<R-4:06:53 PM>Last login: Fri Dec 18 09:14:56 2008 from 10.0.0.0
<R-4:06:53 PM>Press enter to continue...
WFMDRetVal=1 Waiting for: "EW1_Server_Switch> "
WFMDRetVal=2 Waiting for: "EW1_Server_Switch#"
WFMDRetVal=3 Waiting for: "Username:"
WFMDRetVal=4 Waiting for: "Password:"
WFMDBuffer="Last login: Fri Dec 18 09:14:56 2008 from 10.0.0.0Press enter to continue..."
To resolve this, you will need to set the Device's Variations to compensate for the unexpected responses from the device. More on Variations is found here:
To resolve the above issue, you would set the Post-Login Variations as follows:
1. Post-Login Keystroke: CR
2. Post-Login Message: Press enter to continue