|
High memory usage may be caused by the snmpd daemon due to too many child processes being forked.
This can be confirmed by running the command 'diagnose sys top-mem 1000' or 'diagnose sys top 1 1000 1' and seeing over 100 snmpd processes.
By using the command 'diagnose test application snmpd 99' the snmpd process can be restarted, killing the child processes and restoring memory usage back to a normal level.
This is a known issue documented in bug ID 1093042 which has been resolved in v 7.6.1. As a workaround, exclude the get-wad-stats OIDs as shown below:
config system snmp mib-view
edit "bypassWAD"
set include "1.3.6"
set exclude "1.3.6.1.4.1.12356.101.8.2" "1.3.6.1.4.1.12356.101.9.2" "1.3.6.1.4.1.12356.101.10"
next
end
config system snmp community – For SNMP v1/v2
edit [ID] <----- The change must be done on each SNMP community on the FortiGate.
set mib-view bypassWAD
next
end
config system snmp user – For SNMP v3
edit [NAME] <----- The change must be done on each SNMP user on the FortiGate.
set mib-view bypassWAD
next
end
|
