Troubleshooting

FortiPAM operation requires multiple components to work together. Generally, a browser and FortiClient are necessary on the client side to connect to the FortiPAM GUI. Secrets on FortiPAM can then be used to connect to the target host.

If the FortiPAM system runs abnormally, pinpointing the failed component can be challenging. This chapter presents the usage of built-in debug tools to speed up finding errors.

You must have system administrator and CLI permissions to use the debug features including debug trace files. See Role.

To use FortiPAM debug feature, debug category and level must be set.

In the CLI console, enter the following commands to set debug category and level:

diagnose wad debug enable category <category>

diagnose wad debug enable level <level>

For example:

diagnose wad debug enable category session #The category is session

diagnose wad debug enable level info #The level is set to info

For debug level settings, all the higher level traces are included, e.g., when the debug level is set to info, error and warn levels are displayed too, but verbose is hidden.

Once the category and level variables are set up in the CLI, traces are displayed in the CLI.

For more troubleshooting information and a Q&A section, check out the FortiPAM Community page: https://community.fortinet.com/t5/FortiPAM/tkb-p/TKB52.