Created on
‎11-28-2024
08:55 AM
Edited on
‎08-25-2025
08:46 AM
By
AishAbdu
| Description | This article describes the initial troubleshooting commands when modem detection failed. |
| Scope | FortiGate. |
| Solution |
Modem detection issues might occur due to various factors, which can be resolved through LTE modem's cold reboot ('execute lte-modem cold-reboot') and will not lead to a FortiGate restart. If issues persist, try to enable sim-hot-swap as shown below:
config system lte-modem set sim-hot-swap enable end
The following are the troubleshooting commands that should be sent if the ticket needs to be opened related to modem detection issue:
get system status get system performance status get hardware status execute sensor list fnsysctl ifconfig wwan show full system lte-modem diagnose hardware sysinfo memory diagnose sys session stat diagnose sys lte-modem modem-details diagnose sys lte-modem sim-info diagnose sys lte-modem data-session-info execute lte-modem wireless-profile list diagnose test application lted 5 diagnose test application lted 9 diagnose debug reset diagnose debug enable diagnose debug application lted -1
Wait for at least 5 minutes and reboot the modem.
execute lte-modem cold-reboot
Collect the crashlog as well, disable the debugging, and attach the debug output to the ticket.
diagnose debug crashlog read diagnose debug reset
Enable LTE Debugging. To gather more detailed information for troubleshooting, enable LTE debugging using the following commands:
diagnose debug disable
diagnose debug reset
diagnose debug console time enable
diagnose debug application lted -1
diagnose debug enable
|
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.