Description
This article describes the general steps necessary to collect logs for debugging issues as requested by support. This process requires CLI access to the appliance. Contact support if assistance is required.
Note: These are general instructions. For the specific debug outputs required during troubleshooting prior to collecting logs, use the commands provided by support or in the applicable integration reference manual in the Document Library.
Scope
FortiNAC v8.x , v9.x, vF 7.x.
Solution
- Log in to the appliance CLI.
On a CentOS appliance, log in as root.
On a FortiNAC-OS appliance, log in as admin.
-
Enable debugging. Use the commands provided by support or in the applicable integration reference manual in the Document Library.
Example debugging Microsoft InTune:
CentOS appliance:
nacdebug –name MSInTuneServer true
nacdebug –name MdmManager true
FortiNAC-OS appliance:
diagnose debug plugin enable –name MSInTuneServer true
diagnose debug plugin enable –name MdmManager true
-
Reproduce the behavior.
-
Disable debugging.
Example:
CentOS appliance:
nacdebug –name MSInTuneServer false
nacdebug –name MdmManager false
FortiNAC-OS appliance:
diagnose debug plugin disable MSInTuneServer
diagnose debug plugin disable MdmManager
-
Collect the grab-log-snapshot log file. For instructions, see the following article: Technical Tip: How to get a debug log report from FortiNAC-CA or FortiNAC-Manager.
-
Attach the following information to the support ticket:
- The log file.
- The FortiNAC software version (x.x.x.x) is listed in the System Summary Dashboard widget and User drop-down menu.
- The steps used to reproduce the behavior.
