Viewing logs

Edit online

Collect the Fortinet agent and plugin logs that IBM Support requires to help resolve issues while troubleshooting Fortinet environments.

Agent logs

The Fortinet SD-WAN collector agent logs are stored in the agent directories under the location /var/log/SDWAN/<device-id>/<latest-build>.

To view the collector agent logs, run commands like these:

# cd /var/log/SDWAN/Cisco-SDWAN<device-id>/
# ls -l

The following example shows the collector agent logs for version 8.2.0-build.3:

[root@SevOn 8.2.0-build.3]# cd /var/log/SDWAN/Cisco-SDWAN 8.2.0-build.3
total 0
drwxr-xr-x.  2 root root  58 Nov 19 12:32 TLocAgent
drwxr-xr-x.  2 root root  45 Nov 19 12:32 main
[root@SevOne8.2.0-build.3]# [8.2.0] $ cd TLocAgent/
[root@SevOne8.2.0-build.3]# [8.2.0] $ ls
Cisco-SDWAN2_TLoc_8.2.0-build.3.log
[root@SevOne8.2.0-build.3]# [8.2.0] $ cd ../main/
Cisco-SDWAN2_main_8.2.0-build.3.log

To enable debug logs for collector agents, complete the following steps:

  1. SSH into the SevOne NMS Host. 
    ssh <nms-user>@<nms-host-ip>
  2. Enter the SevOne NMS Application Container. 
    podman exec -it nms-nms-nms bash
  3. Edit the collector configuration file using the editor of your choice. 
    vi /config/collectors/<collector-type>/<collector-name>/<config-file>.yaml
    Example: 
    vi /config/collectors/sdwan/Fortinet/default-Fortinet.yaml
  4. Locate the log: section and change the log level from info to debug, as shown below. 
     
log:
  level: debug
    Note: After collecting logs, revert debug back to info and restart again.
  5. Save the file and restart the collector.

Plugin logs

You can check the Fortinet SD-WAN container logs to get plugin-related information. The logs show whether the Fortinet SD-WAN plugin fetched the integration devices and whether the devices authenticated with the provided information.

  1. To check the Fortinet SD-WAN container logs, run the following command on the node where the Fortinet SD-WAN collector is running: 
    podman ps --filter name=nms-collections-?????cisco-sdwan-collector
    If the Fortinet SD-WAN collector is not listed, run a command like this to list all containers: 
    podman ps -a
  2. To view the collector plugin logs, run a command like this: 
    podman logs <collector_container_id> or <container_name>

The following example shows the collector plugin logs for nms-collections-cisco-sdwan-collector:

?????
2026-04-05T08:13:28.536780000Z {"level":"info","ts":1775376808.5362322,"msg":"using poll frequency from database","device_id":34,"frequency_seconds":300}
2026-04-05T08:13:28.537674000Z {"level":"info","ts":1775376808.536649,"msg":"skipping the run as last run time is less than poll frequency","skipped:":"Cisco-SDWAN34"}
2026-04-05T08:13:28.537792000Z {"level":"info","ts":1775376808.536702,"msg":"using poll frequency from database","device_id":35,"frequency_seconds":300}
2026-04-05T08:13:28.538879000Z {"level":"info","ts":1775376808.5381172,"msg":"skipping the run as last run time is less than poll frequency","skipped:":"Cisco-SDWAN35"}
2026-04-05T08:13:28.539037000Z {"level":"info","ts":1775376808.5381753,"msg":"using poll frequency from database","device_id":43,"frequency_seconds":300}
2026-04-05T08:13:28.539176000Z {"level":"info","ts":1775376808.5385625,"msg":"skipping the run as last run time is less than poll frequency","skipped:":"Cisco-SDWAN43"}
2026-04-05T08:13:28.539270000Z {"level":"info","ts":1775376808.5385838,"msg":"using poll frequency from database","device_id":51,"frequency_seconds":300}
2026-04-05T08:13:28.539411000Z {"level":"info","ts":1775376808.5389674,"msg":"skipping the run as last run time is less than poll frequency","skipped:":"Cisco-SDWAN51"}
2026-04-05T08:14:28.546475000Z {"level":"info","ts":1775376868.5461133,"msg":"using poll frequency from database","device_id":34,"frequency_seconds":300}
2026-04-05T08:14:28.547607000Z {"level":"info","ts":1775376868.5474281,"msg":"last-run key does not exist in redis"}
2026-04-05T08:14:28.548515000Z {"level":"info","ts":1775376868.5479045,"msg":"Same Data already present in redis "}
2026-04-05T08:14:28.548687000Z {"level":"info","ts":1775376868.5479946,"msg":"Default file exist , using those values "}
2026-04-05T08:14:28.550540000Z {"level":"info","ts":1775376868.5486608,"msg":"successfully loaded client credentials from","path":"/var/lib/mysql-files/client-files/cisco-sdwan-collector_client_credentials.json"}
2026-04-05T08:14:28.550673000Z {"level":"info","ts":1775376868.5492887,"msg":"YAML file created successfully."}
2026-04-05T08:14:28.550765000Z {"level":"info","ts":1775376868.5495198,"msg":"using poll frequency from database","device_id":35,"frequency_seconds":300}
2026-04-05T08:14:28.550866000Z {"level":"info","ts":1775376868.5496428,"msg":"last-run key does not exist in redis"}
2026-04-05T08:14:28.550957000Z {"level":"info","ts":1775376868.5499601,"msg":"Same Data already present in redis "}
2026-04-05T08:14:28.551059000Z {"level":"info","ts":1775376868.550013,"msg":"Default file exist , using those values "}
2026-04-05T08:14:28.551173000Z {"level":"info","ts":1775376868.5504916,"msg":"successfully loaded client credentials from","path":"/var/lib/mysql-files/client-files/cisco-sdwan-collector_client_credentials.json"}
2026-04-05T08:14:28.551324000Z {"level":"info","ts":1775376868.5510106,"msg":"YAML file created successfully."}
2026-04-05T08:14:28.551532000Z {"level":"info","ts":1775376868.5513818,"msg":"using poll frequency from database","device_id":43,"frequency_seconds":300}
2026-04-05T08:14:28.551700000Z {"level":"info","ts":1775376868.5515845,"msg":"last-run key does not exist in redis"}
2026-04-05T08:14:28.551994000Z {"level":"info","ts":1775376868.5518842,"msg":"Same Data already present in redis "}
2026-04-05T08:14:28.552106000Z {"level":"info","ts":1775376868.5519505,"msg":"Default file exist , using those values "}
2026-04-05T08:14:28.553079000Z {"level":"info","ts":1775376868.5525277,"msg":"successfully loaded client credentials from","path":"/var/lib/mysql-files/client-files/cisco-sdwan-collector_client_credentials.json"}
2026-04-05T08:14:28.553307000Z {"level":"info","ts":1775376868.553245,"msg":"YAML file created successfully."}
2026-04-05T08:14:28.553720000Z {"level":"info","ts":1775376868.5536516,"msg":"using poll frequency from database","device_id":51,"frequency_seconds":300}
2026-04-05T08:14:28.554152000Z {"level":"info","ts":1775376868.5540733,"msg":"last-run key does not exist in redis"}
2026-04-05T08:14:28.554776000Z {"level":"info","ts":1775376868.5547185,"msg":"Same Data already present in redis "}
2026-04-05T08:14:28.554863000Z {"level":"info","ts":1775376868.5547905,"msg":"Default file exist , using those values "}
2026-04-05T08:14:28.555327000Z {"level":"info","ts":1775376868.5552754,"msg":"successfully loaded client credentials from","path":"/var/lib/mysql-files/client-files/cisco-sdwan-collector_client_credentials.json"}
2026-04-05T08:14:28.555900000Z {"level":"info","ts":1775376868.555836,"msg":"YAML file created successfully."}
2026-04-05T08:14:28.561252000Z {"level":"info","ts":1775376868.5587263,"msg":"successfully started a collection process for cisco sdwan","Identifier":"Cisco-SDWAN34"}
2026-04-05T08:14:28.561434000Z {"level":"info","ts":1775376868.55881,"msg":"waiting to finish for","identifier:":"Cisco-SDWAN34"}
2026-04-05T08:14:28.561484000Z {"level":"info","ts":1775376868.5588863,"msg":"successfully started a collection process for cisco sdwan","Identifier":"Cisco-SDWAN43"}
2026-04-05T08:14:28.561525000Z {"level":"info","ts":1775376868.5589075,"msg":"waiting to finish for","identifier:":"Cisco-SDWAN43"}
2026-04-05T08:14:28.596520000Z {"level":"info","ts":1775376868.5962305,"msg":"successfully started a collection process for cisco sdwan","Identifier":"Cisco-SDWAN35"}
2026-04-05T08:14:28.607620000Z {"level":"info","ts":1775376868.5968497,"msg":"successfully started a collection process for cisco sdwan","Identifier":"Cisco-SDWAN51"}
2026-04-05T08:14:28.607860000Z {"level":"info","ts":1775376868.596882,"msg":"waiting to finish for","identifier:":"Cisco-SDWAN51"}
2026-04-05T08:14:28.607943000Z {"level":"info","ts":1775376868.5963337,"msg":"waiting to finish for","identifier:":"Cisco-SDWAN35"}
2026-04-05T08:14:29.794097000Z {"level":"info","ts":1775376869.7938466,"msg":"routine:successfully finished a collection process for cisco sdwan","Indentifier:":"Cisco-SDWAN51","pid:":99019,"exitcode:":0}

To collect the plugin logs and attach them to a support case, run a command like this:

podman logs -t nms-collections-cisco-sdwan-collector >> /root/cisco-sdwan-collector-podman-logs 2>&1