Need to configure sandbox file for debugging

Products

• ASG-S200
• ASG-S400

Issue/Introduction

You have been tasked to get SandBox debugging file.

Resolution

Go to Settings > Logging > Module Sandbox File = DEBUGGING 

Once that is done, go to Utilities > System Logs > get the CAS filename and attached it to case.

Log parameter configuration is available in Settings > Logging.

Use these settings to set logging options for various Content Analysis modules. Each entry under Module is a section of
code that serves a certain purpose (such as AUDIT, ICAP, INTERNAL, and SNMP). Logging by module allows a more
finite understanding of what is occurring in the product. Use the File column to define how much detail is included in the log
file that is saved to the appliance, and the Syslog column to specify the detail level of events sent to your Syslog server.

1. In the File and Syslog columns, click the row corresponding to the module for which you want to set the log severity.
The interface displays a drop-down, as shown below.

NONE

ERROR

ERROR

Depending on the log file, some or all of the following options are available: None, Critical, Error, Warning, Info,
Debugging. Setting the severity alters how verbose each log message is, from most verbose, (DEBUGGING) to
least (CRITICAL). Select NONE to disable log reporting for each of the output options.

NONE

CRITICAL

ERROR

WARNING

INFO

DEBBUGING