Can I monitor an SNMP device that blocks ping?

For a device whose SNMP agent is reachable but ICMP replies are intentionally blocked, open its Edit settings, then Misc, and enable Disable ICMP Test. LibreNMS can then attempt SNMP polling without that preliminary check, but an unreachable device may take longer to fail because of SNMP timeouts.

How do I limit automatic device addition to approved networks?

Set the allowed subnets in the nets configuration and exclude any exceptions through autodiscovery.nets-exclude. Review those ranges before enabling automatic addition so neighboring devices are not accepted merely because they are visible.

Can I switch to one-minute polling by changing only the schedule?

No, one-minute polling also requires compatible RRD step and heartbeat settings, plus a matching cron or dispatcher frequency. Existing RRD files need a separate conversion after a backup; the new storage settings do not retroactively change them.

How can I silence maintenance notifications while keeping alert states current?

Choose the Mute alerts behavior for the scheduled maintenance. LibreNMS continues evaluating and updating alerts but suppresses their notifications; Skip alerts instead pauses the rule checks.

Will adding a vendor MIB automatically reveal missing sensors?

Adding a MIB alone does not make LibreNMS discover new sensors. Device support also needs discovery definitions that identify the relevant values and describe how to collect them.

How do I change the address used to poll an existing device?

Open the device's Edit page and change its hostname or address, or use ./renamehost.php OLD_HOST NEW_HOST from the installation directory. Replace both placeholders with the actual old and new values, then check reachability at the new address and verify the next scheduled poll.

Why are some SNMPv3 authentication or encryption options disabled?

LibreNMS disables certain SNMPv3 choices when the server's Net-SNMP or OpenSSL installation lacks the required version or build features. Check the optional-requirements warning before selecting an algorithm; support on the device alone is insufficient.

How can I inspect a poll without writing graph data?

Add --no-data to a manual ./lnms device:poll command to suppress updates to metric datastores. The command still queries the device, so it is not an offline simulation.

Why does an alert appear in LibreNMS without an email?

An alert rule can raise an alert without sending a notification if no notification operation is assigned. Check the operation's recipients and timing, along with its email transport configuration.

Should I use a static or dynamic device group?

Use a static group for a manually selected set of devices, or a dynamic group when membership should follow rules such as hostname patterns. A dynamic group changes as the device data matches or stops matching those rules.

How to Monitor Network Devices with LibreNMS

LibreNMS can discover and poll network devices so you can follow interface traffic, status, and other values the devices expose. Start with one device you administer: validate the installation, add its management address and credentials, and check that scheduled polls produce fresh graph data. A device appearing in the list is only the beginning; it does not prove that the poller is collecting the intended data.

You need a working LibreNMS server, administrator access to its web interface, and permission to configure monitoring on the target device. The examples below use the standard Linux installation directory, /opt/librenms, and its librenms account. Do not scan or add devices outside a network you are authorized to monitor.

Validate the LibreNMS Installation

Finish the LibreNMS web installer before adding devices. The application needs its database connection, PHP dependencies, writable graph storage, and background jobs as well as a working web server. Confirm that the web interface is reachable only through the intended management network or other controlled access path; configure HTTPS before sending credentials through the browser.

From an administrative shell on the LibreNMS server, switch to the application account and run the validation script:

sudo su - librenms
cd /opt/librenms
./validate.php

Use your actual installation directory if it differs. Resolve reported scheduler, database, file permission, and dependency problems before diagnosing the target device. A working web page alone does not prove that background jobs or graph storage work. After correcting a reported problem, run validation again.

Keep the librenms shell open for the later commands, and check that scheduled polling continues after any manual test.

Configure Restricted Device Credentials

On the device, enable a monitoring method appropriate to its capabilities. Prefer a read-only SNMPv3 account using authentication and encryption, the security level commonly labeled authPriv. Restrict SNMP queries to the actual poller addresses with device access rules and the network firewall. Choose the device's actual management interface and confirm the poller can reach it.

Keep authentication and encryption passwords out of shell history, screenshots, and published examples.

Some older devices support only SNMPv2c. SNMPv2c sends its community string and monitoring data without encryption. If v2c is necessary, use a unique nondefault read-only value and a rule allowing only the poller addresses, and treat the community as a secret. Do not reuse a default or publicly shown community string. Avoid enabling broad SNMP access merely to make discovery succeed.

Confirm the path from the poller to the device, including routing, firewall rules, and the SNMP port, normally UDP 161. An SNMP timeout can result from blocked traffic, an unavailable agent, or mismatched credentials or protocol settings. The timeout alone does not identify which cause applies. Testing from your laptop may not represent the poller location, particularly with VLANs or a remote poller.

Add a Device by Its Management Address

In the LibreNMS interface, open Devices and choose Add Device. Enter the device's management IP address in the Hostname field. A literal IP address keeps polling directed at that address without depending on DNS resolution. You can set a friendly display name after adding the device; that label does not change the polling address.

Select the matching SNMP version. For SNMPv3, enter the username, security level, authentication method and password, and encryption method and password configured on the device. For SNMPv2c, enter its community string. Check the port and then select Add Host.

If addition fails, read the returned error and verify the target details before retrying. For command-line administration, ./lnms device:add --help lists the options available in your installed release; use the web form here to avoid putting passwords directly in command history.

After discovery completes, confirm that the displayed address, hardware or operating system identity, and interface list match the intended device. A duplicate management address, stale DNS record, or address reused by another device can produce misleading data. Correct identity issues before creating alerts or dashboards.

Run Discovery and Polling

Discovery determines what the device exposes and what LibreNMS should poll. Polling collects changing values for the discovered items. In the librenms shell, run the following commands for the one device you added. Replace 192.0.2.10, a documentation address, with its exact Hostname field value or numeric LibreNMS device ID:

./lnms device:discover 192.0.2.10
./lnms device:poll 192.0.2.10

Review the discovery result before starting the poll, then inspect the poll result. Keep the command limited to the selected device; all would process the entire inventory.

If discovery succeeds but polling fails, check for a connectivity change, a credential change since discovery, or an error in the failing polling module. Add -vv when you need more diagnostic output. Debug logs can include SNMP responses, interface descriptions, and other sensitive details, so inspect and redact them before sharing.

The standard graphs use round-robin database (RRD) files to store measurements over time. A single poll is insufficient to calculate a traffic rate from a counter. Leave the device under scheduled polling for several intervals, then select a graph time range that includes those polls. An interface traffic graph normally shows a rate derived from counter changes, not the raw cumulative counter value.

Check the Interface Graphs

Open the device page and inspect its interface list and graph labels. Compare the interface name, speed, and status with the real device. Choose an interface carrying traffic you recognize and confirm that its graph extends with fresh samples. Check the units and direction labels before comparing the graph with a device counter or another monitoring system.

A horizontal line at a nonzero rate can simply mean traffic is steady. A line at zero may be correct for an idle interface; a blank region or gap indicates unavailable samples rather than proven zero traffic.

If all graphs stop updating, inspect the poller log, scheduled jobs, and permissions on graph storage. If only one metric is absent, check whether the device exposes it and whether its discovery and polling modules are enabled. A manual poll that succeeds while scheduled polls fail points to the background execution path, so compare the service account and scheduled job configuration before changing device credentials.

Use Ping-Only Monitoring When SNMP Is Unavailable

For a device that cannot provide SNMP data, turn SNMP off in the Add Device form. The equivalent command is ./lnms device:add --ping-only 192.0.2.10, with the example address replaced by the intended device's address. This mode provides an ICMP response graph. It does not provide interface counters, processor readings, or other SNMP-derived metrics.

A successful ping shows that the device answered ICMP from the poller at that time. It does not confirm that a web service, routing function, or other application on the device is working. Choose the monitoring mode according to the information you need, and identify ping-only entries clearly when reviewing the device list.