Fortinet FortiGate-FortiWiFi - LTE Modem Daemon Debugging; Data Usage and Wireless Module Debugging

Syslog
LTEmodem daemon debugging
You can use the diagnose debug application lted <level> command to enable or disable LTE modem
daemon debugging. We recommend at least using baud rate 115200 on the console port or, if possible, Telnet or
SSHbecause there might be a flood of debug outputs depending on the debug level.
Level 0 disables debugging, Level 1 prints out warning messages, and Levels 2, 4, 8, and 16 print out low volume
debugging messages. In most cases, setting the level to 31 to output all the low volume and warning messages is
sufficient. Levels 32 and 128 are used to dump QMI-related messages. We recommend using a Tenet client to capture
debug messages. Level 64 is for QDL message dumping. which is discussed in the modem firmware Upgrade Guide.
Data usage tracking
You can use the diagnose debug application qbilld <level> command to debug the billing daemon.
Because this is a low volume debug option, you can always set the level to -1.
Wireless module debugging
This operation requires the debug version of FortiOS image.
You can debug the wireless module if you have the debug version of the FortiOSimage installed on your FortiGate.
There’s a utility /bin/swi-dm and a few DM port filters under /etc/swi-dm.
Before starting to capture the DM log, do the following:
1.
Use the /bin/swi-dm /etc/swi-dm/<filter-name> /dev/ttyusb0 command to enable output on
the DM port.
2.
Use the cat /dev/ttyusb0 > /tmp/<DM log file> command to redirect the output to a file.
3.
When finished, use Ctrl+C to end debugging and transfer the DM log file to a computer.
FortiGate-FortiWiFi 5.0 3G4G LTE Modem Operator's Manual 58
Fortinet Technologies Inc.