Skip to main content
VinayHM
Staff
Aug 18, 2023 7:39 AM UTC

Troubleshooting Tip: High CPU and MEMORY usage problem

  • Apr 16, 2026 1:39 PM UTC
  • 0 replies
  • 19559 views
  • Translate All
Description This article provides CLI commands to correct the High CPU and MEMORY usage Problem in the short term.
Scope High CPU and Memory cause of IPS engine.
Solution

IPS Engine using high memory and high CPU cases are different types of cases. Each of them has its own troubleshooting methods.

 

The command shown below might help to collect some detailed information about the IPS Engine and restart/start/stop/bypass it to decrease the usage temporarily.

 

Use the following CLI command:

 

diagnose test application ipsmonitor

 

IPS Engine Test Usage:

1: Display IPS engine information
2: Toggle IPS engine enable/disable status <----- Enable and disable the IPS Engine. Do not apply this command in production hours.
3: Display restart log
4: Clear restart log
5: Toggle bypass status                    <----- It bypasses the IPS Engine.
6: Submit attack characteristics now
10: IPS queue length
11: Clear IPS queue length
12: IPS L7 socket statistics
13: IPS session list
14: IPS NTurbo statistics
15: IPSA statistics
18: Display session info cache
19: Clear session info cache
21: Reload FSA malicious URL database
22: Reload allowlist URL database
24: Display Flow AV statistics
25: Reset Flow AV statistics
32: Reload certificate blocklist database
40: Display packet log statistics
41: Reset packet log statistics
42: IoT device notification statistics
44: Dump IPS stack backtrace
96: Toggle IPS engines watchdog timer
97: Start all IPS engines <----- It starts all IPS Engines after they stopped with the command below.
98: Stop all IPS engines <----- It stops all IPS Engines and needs the command above to start all IPS Engines again.
99: Restart all IPS engines and monitor <----- It restarts all IPS Engines.

 

For high CPU usage by IPS Engine cases, it is recommended to bypass the engine before restarting or stopping it.

 

diagnose test application ipsmonitor 5
bypass: enable

 

The most common command used to deal with the IPS Engine consuming high resources is the following, which restarts the IPS process:


diagnose test application ipsmonitor 99

 

If the CPU usage decreases after bypass, that is a strong indication that the volume of traffic inspected is too much for the FortiGate model that is in use.
If the CPU usage does not change after bypass, it is a strong indication that the problem is not related to the IPS engine itself.

 

Command to disable bypass IPS Engine shown below:

 

diagnose test application ipsmonitor 5
bypass: disable

 

Collect the output below multiple times:

 

diagnose test application ipsmonitor 44

diagnose sys process pidof ipsengine

diagnose sys process pstack <----- PID of IPS Engine from the last command.

 

Example:

 

diagnose sys process pidof engine 

18012

18013

 

diagnose sys process pstack 18021

process pstack 18021

Attaching to the target process

 

To investigate high memory related issues, steps in the following articles can be useful:

 

Note: Do not run the restart or stop commands during production hours, as it will affect the ongoing sessions. Make sure to run them in the maintenance window.

 

Related articles:

Technical Tip: Basic Troubleshooting for high memory or high CPU usage 

Technical Tip: Debugs for troubleshooting high CPU issues 

Technical Tip: IPS engine consumes high CPU after upgrade to FortiOS v7.2.9 and v7.2.10 

Risk and Resilience in the Age of AI. An OT Thought Leadership Summit for Houston's Critical Infrastructure Leaders. Date: Thursday, December 3, 2026. Time: 8:30 am - 1:30 pm (CT). Location: The Westin Houston, Memorial City | 945 Gessner Road, Houston, TX 77024