Friday, 21 December 2012

Tufin Troubleshooting


Device Specific Communication Problems


1.      The version of SecureTrack; Please verify this by running the #st ver command from CLI.
2.      the output of the #top -cd1 command.


1)  Rise the debug level to high :
# sed -i 's/expect --/expect -d/g' /usr/local/st/*login # sed -I  's/normal/fine/1' /etc/sysconfig/stconf.xml

2) Then use tail for each one of the log files of the problematic device :
# tail -F /var/log/st/var/log/st/securetrack.client.<Device_IP>_<ID> /tmp/device1.log

Make sure to use a capital F ('#tail -F')

3)  Then run the command:
'#st restart'

4) Wait for 10 minutes (depends on the current timeout you have
defined) and let the tail -f collect all information needed.

5) Send all /tmp/client<IP>.log files to the support engineer.

7) When you have finished please run :
# sed -i 's/expect -d/expect --/g' /usr/local/st/*login # sed -i 's/fine/normal/1' /etc/sysconfig/stconf.xml
# st restart

No comments:

Post a comment