Troubleshooting Tip: SNMP connection failed due to special character

[Hsharma]

Description	This article describe how to troubleshoot the SNMPv2 error message 'failed to match community'
Scope	FortiGate.
Solution	Start Debugging SNMP: diagnose debug reset diagnose debug application snmpd -1 diagnose debug console timestamp enable diagnose debug enable After enabling the above commands, initiate connectivity from the SNMP manager/server. Consider an example where the name of the SNMP community is defined as the following, for example: xHdt@hb#$gsj@0. The error message in SNMP debugging will appear as follows: Sample error message in debug: snmpd: </msg> 0 snmpd: checking if community "xHdt@hb#" is valid snmpd: full name mismatched snmpd: failed to match community " xHdt@hb#" Here, the $ sign in the name is not being processed, which results in a mismatch of the name between FortiGate and the SNMP server: in other words, it is trying to match 'xHdt@hb#' instead of 'xHdt@hb#$gsj@0'. To resolve this, remove the $ sign from the name of community then restart the SNMP demon with the following command: diagnose test application snmpd 99 Related article: Technical Tip: How to troubleshoot on FortiGate when SNMP Is not delivering interface state informat....