Summary

This chapter describes logging capabilities of Traffic Dictator and how to configure it to send syslog to a remote host.

Local logging

By default, Traffic Dictator logs to /var/log/traffic_dictator.log. It can generate up to 10 1MB files before overwriting old logs. You can check logs from TDCLI:

show logging

You can use | grep to filter only logs matching a specific pattern.

Check only last 30 lines:

show logging recent

Print logs in real time (tail -f):

show logging follow

Debugs

Traffic Dictator has a powerful debugging capability which is very useful for troubleshooting.

Warning: debugs can impact performance.

To explore debugging capabilities, use tab and ? in TDCLI:

TD1#debug bgp ?
  server               BGP server debug
  neighbors            BGP neighbors debug

TD1#debug bgp neighbors ?
          BGP neighbors debug

Debug messages are logged to the same file as regular logs. You can disable each debug with “undebug” command. When finished debugging, run “undebug all” to disable all debugs.

Logging to a remote host

Below is an example of syslog configuration to send logs to a remote host:

management syslog
   !
   host 192.168.123.101
      protocol udp
      port 514

Verify that syslog config is active:

TD1#show management syslog 
Configured syslog hosts

  Host                           Port                 Protocol             Active              
  ----                           ----                 --------             ------              
  192.168.123.101                514                  udp                  True    

If protocol or port is not configured, logging to remote host will not be active.