FortiGate
FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
yloo
Staff
Staff
Article Id 416138
Description This article describes the error code returned by FortiGate as a result of the SNMP server queries for non-existent OIDs.
Scope FortiGate.
Solution

Run these debugging commands in FortiGate's command line interface (CLI) or while connected to FortiGate via SSH:

 

diagnose debug reset

diagnose debug application snmpd -1

diagnose debug enable

 

To stop the debug:

 

diagnose debug reset

diagnose debug disable

 

zabbix.jpg

 

Debug output:

 

snmpd: <msg> 42 bytes 192.168.50.202:63156 -> 192.168.50.252/192.168.50.252:161 (itf 3.3)

snmpd: checking if community "Public" is valid

snmpd: checking against community "Public"

snmpd: request 1(root)/3/192.168.50.202 == comm 1/0/192.168.50.202/255.255.255.255

snmpd: matched community "Public"

snmpd: get     : mib-2.25.1 -> () -> 3

snmpd: snmp_get failed  : 3

snmpd: </msg> 1

 

SNMP error code 3 means noSuchName.

This error indicated that the requested Object Identifier (OID) is not recognized by the FortiGate SNMP agent.

To resolve this issue, verify the OID against the MIB files to ensure its validity and support.

 

Related article:

Technical Tip: Download FortiOS and FortiCore MIB files 

Contributors