|
When querying BGP peer status by SNMP (OID 1.3.6.1.2.1.15.3.1.2), sometimes BGP status is returned properly, but there can be random failures where FortiGate returns 'No Such Instance currently exists at this OID' for some VDOMs.
[hgss-pql-gesture-tiger-inf ~]$ snmpwalk -v3 -l authPriv -u snmpv3user -a SHA -A "$auth_pass" -x AES -X "$priv_pass" 10.10.21.37 .1.3.6.1.2.1.15.3.1.2.10.101.5.206
SNMPv2-SMI::mib-2.15.3.1.2.10.101.5.206 = INTEGER: 6
[hgss-pql-gesture-tiger-inf ~]$ snmpwalk -v3 -l authPriv -u snmpv3user -a SHA -A "$auth_pass" -x AES -X "$priv_pass" 10.10.21.37 .1.3.6.1.2.1.15.3.1.2.10.101.5.206
SNMPv2-SMI::mib-2.15.3.1.2.10.101.5.206 = INTEGER: 6
[hgss-pql-gesture-tiger-inf ~]$
[hgss-pql-gesture-tiger-inf ~]$ snmpwalk -v3 -l authPriv -u snmpv3user -a SHA -A "$auth_pass" -x AES -X "$priv_pass" 10.10.21.37 .1.3.6.1.2.1.15.3.1.2.10.101.5.206
SNMPv2-SMI::mib-2.15.3.1.2.10.101.5.206 = No Such Instance currently exists at this OID
[hgss-pql-gesture-tiger-inf ~]$
[hgss-pql-gesture-tiger-inf ~]$ snmpwalk -v3 -l authPriv -u snmpv3user -a SHA -A "$auth_pass" -x AES -X "$priv_pass" 10.10.21.37 .1.3.6.1.2.1.15.3.1.2.10.101.5.206
SNMPv2-SMI::mib-2.15.3.1.2.10.101.5.206 = No Such Instance currently exists at this OID
[hgss-pql-gesture-tiger-inf ~]$ snmpwalk -v3 -l authPriv -u snmpv3user -a SHA -A "$auth_pass" -x AES -X "$priv_pass" 10.10.21.37 .1.3.6.1.2.1.15.3.1.2.10.101.5.206
SNMPv2-SMI::mib-2.15.3.1.2.10.101.5.206 = No Such Instance currently exists at this OID
Debug:
Check the actual BGP peer status in CLI with the command 'get router bgp summary' and verify if the BGP peer is up and stable.
Run SNMP debugs with the following commands:
diagnose debug application snmpd -1
diagnose debug enable
The debug output shows the failure details:
2025-02-07 13:40:28 snmpd: <msg> 70 bytes 10.0.0.1:60363 -> 10.4.0.254/10.4.0.254:161 (itf 477.477)
2025-02-07 13:40:28 snmpd: checking if community "Uqueeg3X79N5Si8YlgW-AEUL21-MCL-1" is valid
2025-02-07 13:40:28 snmpd: matched community "Uqueeg3X79N5Si8YlgW-AEUL21-MCL-1"
2025-02-07 13:40:28 snmpd: get : bgpPeerEntry.2 -> () -> 4
2025-02-07 13:40:28 snmpd: snmp_get failed : 4
2025-02-07 13:40:28 snmpd: </msg> 1
Solution:
Enable the 'append-index' setting in the SNMP system configuration:
config system snmp sysinfo
set append-index enable
end
Related article:
Technical Tip: Enable SNMP index extension
|
