Administration > Support | System Information Files tab
            Using the case diagnostic tool (CDT), IWSVA generates core and/or system file(s) containing
               the system data held in memory when a process abnormally terminates. The Generate System Information File button is an extension of this feature, allowing you to package the current machine
               "state" at the click of a button.
            The core and/or system file(s) that IWSVA generates contains the following information:
            
               - 
                  
                  IWSVA information—Includes IWSVA product version, engine version, build number, and IWSVA hot fixes
                     and service pack information. Product and integration settings are also part of this
                     information 
- 
                  
                  IWSVA/system logs—Includes IWSVA logs, debug logs, and logs generated by syslogd daemon (if system
                     logs are enabled) 
- 
                  
                  System/network information—Includes the hardware configuration, operating system, build, system resource status,
                     other application installed, and network information 
- 
                  
                  CDT-compliant configuration/plugins information—Includes information about changes made to CDT as a result of IWSVA adding a new
                     component, such as a TMCM or MCP agent. 
- 
                  
                  Verbose Logging - Create verbose logs with IP-filtering. 
Core files are first created in the first directory listed below, and then compressed
               and moved to the second directory listed:
            /var/iwss/coredumps
            /var/iwss/UserDumps
            Use these files when working with Trend Micro technical support to help diagnose the
               cause of your problem. To view the files yourself, use a program like GDB, the GNU
               Project debugger.
            While IWSVA is generating the core and/or system file(s), the application may encounter
               some conditions that prevents it from gathering all the possible diagnostic information.
               For instance, debug may be disabled, a core dump may not exists, or critical commands
               or files may not exist. In this case, IWSVA gathers as much information as possible
               and also records any encountered errors in a log file with comprehensive messages.
            See also