Samba Diagnostic Logs

The Samba diagnostic log utility allows you to view trace and debug the samba troubleshooting messages on the new AD authentication server. When samba diagnostic logging is enabled, the internal logs related to AD authentication server is generated.

Observe the following guidelines:

  • Diagnostic logging affects system performance.
  • Must be used only when the admin UI error messages, event logs and admin logs are not very useful.
  • Enabling/Disabling samba logs will restart certain modules and user log ins may fail during the restart.
  • The default debug log setting will generate minimal logs. Enabling debug log with event AAA or AAA::samba along with this feature can generate more logs based on the debug log level.

Enabling samba logs will cause logs to be generated from all configured AD authentication servers. Logs from multiple AD servers are interleaved and can be identified by the header in each line of the logs.

To use samba diagnostic logging:

  1. Select Troubleshooting > Monitoring > Diagnostic Logs to display the configuration page.
  2. Complete the configuration as described below.
  3. Click Save Changes. When you save changes with Samba Diagnostic Logging On selected, the system begins generating diagnostic log entries.
  4. Initiate the action you want to debug, such as a user sign in.
  5. Manage the resulting log:
    • Click Save Log to save the log files in a zipped format.
    • Click Clear Log to remove previous logs and start diagnostic logging with a fresh file.
    • Click Save And Clear Log to save the diagnostic log to a file that you can send to PSGSC. The existing logs in the device will be cleared after saving.
  6. Unselect Samba Diagnostic Logging On and click Save Changes to turn off diagnostic logging.

Settings

Guidelines

Samba Diagnostic Logging On

Select this option to generate logs related to AD server.

Max Diagnostic Log Size

Specify a maximum log file size.

IPS

•Default (MB)- 10

•Maximum (MB)-100