Created on
03-23-2020
06:05 PM
Edited on
05-12-2025
01:45 AM
By
Jean-Philippe_P
Description
This article provides useful diagnostics commands for troubleshooting NTurbo-related issues.
Scope
FortiGate.
Solution
Debug command:
fnsysctl cat /proc/nturbo/<n>/drv <------ '<n>' is the NTurbo ID.
# fnsysctl cat /proc/nturbo/0/drv
Turbo interface ID: 0
=======================================================================
Driver RX/TX: 0/0
TX hang: No
Free/Used buffers: 48128/8192
Alloc fail: 0, Bad qid: 0
queue ready: 0x0000001f, 0x00000000
RXQ_0(0,374): IN 0 OUT 0 DROP 0 NRDY 0 Fullness 0, Peak 0
TXQ_0(0,374): IN 0 OUT 0 DROP 0 USR_DROP 0 BUFERR 0
RXQ_1(2,375): IN 0 OUT 0 DROP 0 NRDY 0 Fullness 0, Peak 0
TXQ_1(2,375): IN 0 OUT 0 DROP 0 USR_DROP 0 BUFERR 0
RXQ_2(4,373): IN 0 OUT 0 DROP 0 NRDY 0 Fullness 0, Peak 0
TXQ_2(4,373): IN 0 OUT 0 DROP 0 USR_DROP 0 BUFERR 0
……………
'RXQ':
'TXQ':
Note: Running the fnsysctl command requires Super Admin privileges; otherwise, it will return the error message 'Unknown action 0'.
Related documents:
Technical Note: How to troubleshoot NTurbo on a FortiGate
NTurbo offloads flow-based processing
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.