Академический Документы
Профессиональный Документы
Культура Документы
Monitoring via Simple Network Management Protocol (SNMP) is the most basic method
of gathering bandwidth and network usage data.
You can use SNMP to monitor the bandwidth usage of routers and switches on a port-
by-port basis, as well as device readings such as memory and CPU load. The target
devices must support SNMP. Most devices with enabled SNMP require the same
configuration like SNMP version and community string. To find out how to set up SNMP
on a specific device, search in the internet for your device name or model and SNMP
configuration. You will likely get plenty of information on how to configure SNMP.
Keep in mind that SNMP V1 and V2c are not secure protocols so you should not use
them across the internet or insecure data connections. Only SNMP version 3 supports
encryption.
However, SNMP V3 has performance limitations due to the SSL encryption. The main
limiting factor is CPU power (as well as the other general limits for PRTG). Because of this
limitation, you can monitor only a limited number of sensors per second using SNMP V3. Currently,
PRTG is able to handle about 40 requests per second and computer core, depending on your system.
This means that, on a common 1.x GHz computer with two cores, you can run about 5,000 SNMP v3
sensors with a 60 seconds scanning interval; on a system with four cores, you can monitor around
10,000 sensors with 60 seconds interval. The CPU load is at about 50% then. We do not recommend
more.
Furthermore, the PRTG core server and probes should run on different computers. If you
experience increased values in the Interval Delay SNMP or Open Requests channels of the Probe
Health Sensor (values above 0 % indicate that the SNMP requests cannot be performed at
the desired interval), you need to distribute the load over multiple probes. SNMP V1 and V2 do not
have this limitation.
If you run into SNMP overload problems, you have three options:
Increase the monitoring interval of the SNMP V3 sensors.
Distribute the SNMP V3 sensors over two or more probes.
Switch to SNMP V1 or V2 if you can go without encryption.
What is the SNMP Community String?
The SNMP Community String is similar to a user ID or password that allows access to the
statistics of a router or another device. PRTG Network Monitor sends the community
string along with all SNMP requests. If the correct community string is provided, the
device responds with the requested information. If the community string is incorrect,
the device simply discards the request and does not respond.
SNMP community strings are only used by devices that support SNMP V1 and SNMP
V2c protocols. SNMP V3 uses safer username/password authentication, along with an
encryption key.
By convention, most SNMP V1/V2c equipment ships with a read-only community string
set to the value public. It is standard practice for network managers to change all the
community strings to customized values during device setup.
More
Tools: Paessler MIB Importer and SNMP Tester
https://www.paessler.com/tools/
Knowledge Base: How do SNMP, MIBs and OIDs work?
https://kb.paessler.com/en/topic/653
Paessler White Papers: Introducing SNMP and Putting SNMP into Practice
https://www.paessler.com/press/whitepapers/introducing_snmp
German: Paessler White Paper: Einführung in SNMP und SNMP praktisch anwenden
http://www.de.paessler.com/press/whitepapers/introducing_snmp
Video Tutorial: SNMP Basics
https://www.paessler.com/support/videos/prtg-basics/snmp-basics
Video Tutorial: Debugging SNMP
https://www.paessler.com/support/videos/prtg-basics/snmp-debugging
Knowledge Base: My SNMP sensors don't work. What can I do?
https://kb.paessler.com/en/topic/46863
Knowledge Base: The interface numbers on my switch keep changing. What can I do?
https://kb.paessler.com/en/topic/62217
Knowledge Base: What can I check if SNMP and SSH sensors throw timeout and auth
errors?
https://kb.paessler.com/en/topic/63794
Knowledge Base: What can I monitor with the SNMP Custom Table sensor?
https://kb.paessler.com/en/topic/68539