| Description | This article describes the 'diagnose sys profile cpumask' command, which can be used in cases where only 1 CPU core shows high utilization in system space. |
| Scope | All supported versions of FortiGate. |
| Solution |
In some cases, all of the CPU cores are in normal utilization and only 1 CPU core is showing high utilization in system space.
To troubleshoot, perform the following steps:
After verifying which CPU core is high and confirming that the cycles are predominantly used in system space (represented by the percentage in 'system', 'irq', 'softirq') , use the command 'diagnose sys profile cpumask' to further focus the kernel profiler to that specific core.
This command helps the kernel profiler target individual CPU cores to troubleshoot.
diagnose sys profile cpumask X <- Replace X with the CPU core number. diagnose sys profile start <- To start the profiling process, wait a minimum of 5-10 seconds before executing the 'profile stop' command below. diagnose sys profile stop <- To stop the process
The following command will generate an output which will consist of all system calls seen during the time the profiler was running. This command will sort the system calls seen by the profiler from highest hit count to lowest
diagnose sys profile show order
The output generated from the kernel profiler can provide some clues as to what is keeping a particular CPU busy when used in conjunction with a CPU mask set. However, the results may need interpretation by support. |
