How to solve the problem of a large number of Received SNMP packet (s) from UDP after Linux turns on snmp monitoring
This article mainly introduces "how to solve the problem of a large number of Received SNMP packet (s) from UDP after Linux turns on snmp monitoring". In daily operation, it is believed that many people have doubts about how to solve the problem of a large number of Received SNMP packet (s) from UDP after Linux turns on snmp monitoring. The editor consulted all kinds of materials and sorted out simple and useful operation methods. I hope it will be helpful to answer the question of "how to solve the problem of a large number of Received SNMP packet (s) from UDP after Linux turned on snmp monitoring"! Next, please follow the editor to study!
Jan 9 11:54:08 i snmpd [2193]: Connection from UDP: [60.195.249.83]: 37412
Jan 9 11:54:08 I snmpd [2193]: Received SNMP packet (s) from UDP: [60.195.249.83]: 37412
Jan 9 11:54:08 i snmpd [2193]: Connection from UDP: [60.195.249.83]: 18749
Jan 9 11:54:09 i snmpd [2193]: Connection from UDP: [60.195.249.83]: 37412
Jan 9 11:54:09 i snmpd [2193]: Connection from UDP: [60.195.249.83]: 18749
Jan 9 11:54:09 i snmpd [2193]: Connection from UDP: [60.195.249.83]: 51089
Jan 9 11:54:09 I snmpd [2193]: Received SNMP packet (s) from UDP: [60.195.249.83]: 51089
Jan 9 11:54:09 i snmpd [2193]: Connection from UDP: [60.195.249.83]: 18749
Jan 9 11:54:09 i snmpd [2193]: Connection from UDP: [60.195.249.83]: 51089
Jan 9 11:54:09 i snmpd [2193]: Connection from UDP: [60.195.249.83]: 18749
There is too much useless information.
If you don't want to see this multi-link information, you can adjust the debug level of snmpd:
# echo "OPTIONS=\"-LS3d-Lf / dev/null-p / var/run/snmpd.pid\ "> > / etc/sysconfig/snmpd.options
Or change the startup script directly
Vi / etc/init.d/snmpd
Find this item.
OPTIONS= "- Lsd-Lf / dev/null-p / var/run/snmpd.pid-a"
Change to
OPTIONS= "- LS3d-Lf / dev/null-p / var/run/snmpd.pid"
Definition of snmpd log level:
0 or!-- LOG_EMERG
1 or a-- LOG_ALERT
2 or c-- LOG_CRIT
3 or e-- LOG_ERR
4 or w-- LOG_WARNING
5 or n-- LOG_NOTICE
6 or I-- LOG_INFO
7 or d-- LOG_DEBUG
Finally, don't forget to restart the service.
# service snmpd restart
At this point, the study on "how to solve the problem of a large number of Received SNMP packet (s) from UDP after Linux turns on snmp monitoring" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!
