Created on 07-17-2024 09:18 PM Edited on 07-18-2024 05:16 AM By Jean-Philippe_P
Description | This article describes the behavior when FortiGate frequently experiences failures for L2 polling. |
Scope | FortiNAC, FortiGate. |
Solution |
SNMP and CLI credentials are working, but the L2 polling for FortiGate frequently fails due to the 'java.net.SocketTimeoutException: Read timed out' error in output.master logs for FortiGate. This means FortiNAC is trying to read data from the request, but it is taking longer than the timeout value for the data to arrive from the FortiGate.
To resolve the issue:
execute enter-shell
> Device -ip <FGT IP addr> -setAttr -name API_CONNECT_TIMEOUT -value <time in milliseconds> > Device -ip <FGT IP addr> -setAttr -name API_READ_TIMEOUT -value <time in milliseconds>
Example:
> Device -ip 10.10.10.1 -setAttr -name API_CONNECT_TIMEOUT -value 180 > Device -ip 10.10.10.1 -setAttr -name API_READ_TIMEOUT -value 45
Note: By default, the API connect timeout value is 120 seconds and the API read timeout value is 30 seconds. |
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 2024 Fortinet, Inc. All Rights Reserved.