Monitor network devices with SNMP in Pulse
Store an SNMP credential, create an SNMP monitor on a device, and see exactly what Pulse polls today and what it does not support.
Pulse polls switches, routers, firewalls and other SNMP devices from a TOS agent that has Pulse Collector turned on. The agent reads the device over SNMP on your network and sends the readings to the platform. Nothing needs to be opened to the internet.
Before you start#
- Turn on Pulse Collector on an agent at the site and confirm its scan scope. See Pulse network monitoring and device discovery.
- Adopt the device you want to monitor so it appears under Network, then Devices.
- Make sure the device answers SNMP from the collector's network, and note its community string (SNMP v2c) or SNMP v3 user.
What the collector polls#
The collector only reads. It sends SNMP GET and GETBULK requests and never sets a value.
| Monitor type | What it reads |
|---|---|
| SNMP CPU | Average processor load across the device's CPUs. |
| SNMP Walk | Every numeric value under an OID you enter (up to 500 per poll). For example, enter the interface status OID (1.3.6.1.2.1.2.2.1.8) to read the status of every interface. |
| SNMP Interface | Offered on New monitor. Use it when you want an interface reading rather than a walk of an OID you type. |
| SNMP Memory | Offered on New monitor. |
| WAN Speedtest | Offered on New monitor. |
| Config Backup | Offered on New monitor. This is a monitor type. It is not Run CLI, which is not available. |
What is supported#
- SNMP version 2c, with a community string.
- SNMP version 3, with a user name and the three security levels: no authentication, authentication only, and authentication with privacy. Privacy requires authentication, and each password must be at least 8 characters.
- SNMP v3 authentication with MD5, SHA, SHA-256 or SHA-512, and privacy with DES, AES, AES-192 or AES-256. These are the choices the credential form offers.
- The standard SNMP port, UDP 161, unless the credential says otherwise.
What is not supported#
- SNMP version 1 is not offered. Use v2c.
- SNMP traps and informs. Pulse polls on a schedule. It does not receive traps.
- Writing to devices. The collector cannot SET any value.
- Polling outside the collector's scan scope. A monitor whose device address is outside the subnets you confirmed for that collector is not polled, even if you created it.
- IPv6 targets are not polled. Scan scopes are IPv4.
- Ping, TCP port, HTTP and DNS monitors. The TOS agent collector runs SNMP monitors, so the monitor form does not offer these types. A ping, TCP port, HTTP or DNS monitor created earlier is not checked by the agent.
- Time-series charts. The Network section has no page that charts SNMP readings. Readings are stored and feed network alert rules.
Step 1: Store an SNMP credential#
- Open the Settings gear in RMM, then Network Credentials.
- Choose Add credential, pick the Site (the location) and the Type: SNMPv2c or SNMPv3.
- Enter the community string, or the v3 user name with the authentication and privacy protocols and passwords.
- Save. If you are asked to re-authenticate, do so and save again. Credentials are encrypted at rest and are never shown back in full.
A new credential applies to every device at that location. To limit it to one device, open the credential and set Used by to that device. When a device has its own credential, it is used before the location's default. If a device has both a v3 and a v2c credential, the v3 credential is used.
The agent receives a credential only for devices it monitors, and keeps it in memory only.
Step 2: Create the monitor#
- Open Network, then Monitors, and choose New monitor.
- Choose the Location and the Device. Only adopted devices at that location are listed.
- Choose the Monitor type, for example SNMP CPU or SNMP Walk. SNMP Walk needs an OID. The form offers a shortcut for the interface status OID.
- Choose the Check interval and leave Enabled on.
- Choose Create monitor.
The location, device and type cannot be changed after creation. To change them, delete the monitor and create a new one. You can change the interval and pause or resume a monitor at any time.
The form does not ask which credential to use. The collector picks the device's own credential, then the location default.
How often it polls#
The agent refreshes its list of monitors every 5 minutes, so a new monitor can take that long to start. It checks which monitors are due every 30 seconds. No monitor polls more often than every 60 seconds, even if you choose a shorter interval. Each request waits 3 seconds and is retried once.
Alert on SNMP data#
Under Network Alert Rules, the SNMP not answering condition uses SNMP data. When a device stops answering, its monitors turn to fail and one alert opens. If the rule's channels include the PSA, a ticket is created too. When the device answers again, the monitors return to ok and the alert resolves by itself.
| Condition | Needs |
|---|---|
| SNMP not answering | Any SNMP monitor on the device. Fires after a chosen number of missed polls (2 to 20, default 3). |
Only devices marked Managed are evaluated by alert rules.
Troubleshooting#
No data arrives. Check, in order: the collector is Active on Collectors; the device address is inside the collector's confirmed scan scope; a credential exists for the device or its location; the device allows SNMP from the collector's address; the community string or v3 settings match.
The Monitors page shows pending. A new monitor stays pending until its first reading arrives, which can take several minutes (the agent refreshes its monitor list every 5 minutes). The Status then turns to ok, Last value shows the latest CPU or memory reading, and Last run shows when the last reading arrived. If a monitor gets no reading for three intervals (at least 3 minutes) while its collector is still checking in, the status changes to fail. A fail means the device is not answering: check the points under "No data arrives". If the collector itself has stopped checking in, the status is left as it was, because a silent collector is not a failing device.
SNMP v3 credential is refused. Passwords shorter than 8 characters are rejected, and privacy needs an authentication password.
Related#
Was this article helpful?