Troubleshooting Tip: FortiProxy Policy OID Issue

Description

This article describes a technical issue where policy-related OIDs are returned to zero even though there is actual data in FortiProxy's GUI. The user may experience this issue when trying to retrieve policy statistics using SNMP.

Scope

FortiProxy.

Solution

To troubleshoot the FortiProxy policy OID issue, follow these steps:

1. Verify that the SNMP agent is enabled and the community is configured correctly on the FortiProxy device. Make sure the allow host IP is set to the IP address of the SNMP server.
   
   

2. Run the command to enable SNMP debug logging.

diagnose debug reset
diagnose debug enable
diagnose debug application snmpd -1

3. Replicate the issue by running an SNMP walk command, such as:

snmpwalk -v2c -c public 192.168.1.1 1.3.6.1.4.1.12356.101.5.1.2.1.1.1

Example of problematic SNMP result output:

fgFwPolID.1.0 .1.3.6.1.4.1.12356.101.5.1.2.1.1.1.1.0 Integer 0
fgFwPolID.1.1 .1.3.6.1.4.1.12356.101.5.1.2.1.1.1.1.1 Integer 1
fgFwPolPktCount.1.0 .1.3.6.1.4.1.12356.101.5.1.2.1.1.2.1.0 Counter32 0
fgFwPolPktCount.1.1 .1.3.6.1.4.1.12356.101.5.1.2.1.1.2.1.1 Counter32 0
fgFwPolByteCount.1.0 .1.3.6.1.4.1.12356.101.5.1.2.1.1.3.1.0 Counter32 0
fgFwPolByteCount.1.1 .1.3.6.1.4.1.12356.101.5.1.2.1.1.3.1.1 Counter32 0
fgFwPolLastUsed.1.0 .1.3.6.1.4.1.12356.101.5.1.2.1.1.4.1.0 OctetString No Session Data
fgFwPolLastUsed.1.1 .1.3.6.1.4.1.12356.101.5.1.2.1.1.4.1.1 OctetString No Session Data
fgFwPolPktCountHc.1.0 .1.3.6.1.4.1.12356.101.5.1.2.1.1.5.1.0 Counter64 0
fgFwPolPktCountHc.1.1 .1.3.6.1.4.1.12356.101.5.1.2.1.1.5.1.1 Counter64 0
fgFwPolByteCountHc.1.0 .1.3.6.1.4.1.12356.101.5.1.2.1.1.6.1.0 Counter64 0
fgFwPolByteCountHc.1.1 .1.3.6.1.4.1.12356.101.5.1.2.1.1.6.1.1 Counter64 0

This issue has been fixed in the next FortiProxy GA release, versions 7.4.14GA and 7.6.7GA; there is no workaround.