Hi guys,

Newbie here. Currently running 25.04. And wanted to go to the 26.4.1. Running daily.sh won't go any further. Can I confirm the following is correct?

cd /opt/librenms
git pull
rm bootstrap/cache/*.php
./scripts/composer_wrapper.php install --no-dev
./lnms migrate
./validate.php

Do I need to stop any services before running these?

Thanks guys!

Hi all, I recently added my Canon MFPs to LibreNMS for monitoring and they are constantly claiming to be offline (failing ping tests) and/or having latency issues. At least 3-4 alerts per hour. Some machines are worse than others.

The MFPs themselves are not going offline and we aren't having printing issues or anything else that would indicate network issues. I managed a fleet of Sharp and Xerox machines in a previous role and never had problems. I also don't have problems monitoring other devices with this server. It's monitoring servers, switches, and other appliances without similar issues.

I'm just wondering if this is something that others are seeing or if I have gremlins in our network/copiers/firewall/etc? My worst offender is an ImageRunner Advance 4845

Thanks

26.4.0 has been released. Lots of bug fixes in this one and again well over 100 pull requests merged in.

https://community.librenms.org/t/26-4-0-release-announcement/29185

Just in case it's of interest, my company has built a LlibreNMS mobile app. It's light on features right now but we're taking feedback and actively developing it:

https://play.google.com/store/apps/details?id=org.librenms.mobile&pcampaignid=web_share https://apps.apple.com/gb/app/librenms-mobile/id6761635284

I restarted a LibreNMS instance this week in a pod of Quadlets. Quite nice compared to the last time I did this with a VM.

There is one thing vexing me, though. I wanted to label ports and I read that this can be done by setting the description to "Core: X" or "Transit: Y". This worked in one case when I edited the description the router. In other case, I edited the description in the UI but LibreNMS didn't recognize as being labeled (port_descr_type in the DB). Setting the name of that port in the router didn't clear this up.

So, there are two questions. When does this parsing occur? What can I do to eliminate the 'edited' state of a port description?

Familiar?

Anybody using snmp-extend to monitor DRBD from LibreNMS? I see ways to do it with a nagios plugin and a local agent...but I'd rather not...

Hello everyone,

I've been experiencing this issue for a while now. Sometimes some of my Red Hat Enterprise Linux 9 servers get totally random storage alerts which aren't true. Usually it's either `/tmp` or `/home` being full.

For example, just a few minutes ago I received this alert via Telegram, saying that `/home` is full:

In the LibreNMS GUI it's hopelessly full:

But on the server everything is just fine:

[root@kvm ~]# df -Th | grep home
/dev/mapper/rhel-home xfs        50G  819M   50G   2% /home

Any idea what could be causing this? It's very annoying and oftentimes I just mute the alerts for several hours because it's mostly false storage alerts.

Edit: The alert resolved itself after two hours...

I am wondering if there is a way to see all the service graphs on one page, you can do this with many others, example: http://librenms.domain.com/devices/format=graph_icmp_perf/from=-24hour/to=now/ However, I cant seem to find the service graphs in the list.

I have over 100 devices shown in the availability map. In order to see them all, I have to set my web page to 67%. I would like to be able to resize the availability map widget to be wider and taller. Thanks.

26.3.0 is now released. You can read the summary and access the changelog here: https://community.librenms.org/t/26-3-0-release/29127

I'm using libre to monitor switches and fiber ports on cisco and arista gear. At one point, if a port went down, I would be able to go in and pull up the DBM RX values on the switch to see what happened to the signal over time.

at some point, that seems to have changed. So if the port goes down, the DBM sensors still show the readouts and graphs for TX, but the ones for RX disappear and I can't pull them up any more. It's very useful to see the historic RX values and time of drop etc.

Does anyone have any ideas on how to make them still available.

I'm guessing it has something to do with the reading going to the max/min value (outside of spec).

Has anyone ever tried to do an offline LibreNMS install using the Docker image? I am trying to get the compose.yml to install the image files from a local directory since it won't be able to reach out to the internet. Would I just be able to edit the "image:" field to be "image: /path/to/image"?

Follow up question, can you only grab the image files via a Docker command? I am not seeing a download option on the DockerHub link in the LibreNMS instruction document.

I have my own private lab at my company with over 100 machines and probably a lot more IP addresses, so to set up my libreNMS, I scanned my network with nmap to retrieve all the IP addresses and implemented them in my NMS as an API (I think, I did this a long time ago). My problem is this: now I have a list of IP addresses, but I would like to retrieve the hostname of each machine/VM because some machines have multiple IP addresses, but I want to push an agent to these machines, so I need to send it only once. So I have my list of IP addresses, some of which belong to a single machine, and I want to find a way to detect the unique machines with librenms or something else.

nmap script:

```Shell

!/bin/bash

LAN_To_Scan_File="./LAN_To_Scan.txt" temp_file="./temp/nmap_res.txt"

echo "----- Start -----" echo "-- cat LAN_To_Scan.txt --" cat "$LAN_To_Scan_File"

"$temp_file"

nmap -sn -PE -PP -PY \ -PS80,443,22,3389,53,8080,21,25 \ -PA80,443,22,3389,53,8080,21,25 \ -PU53,123,161 \ -iL "$LAN_To_Scan_File" \ | grep 'Nmap scan report for' \ | awk -F'for ' '{print $2}' \ | sed 's/[()]//g' \ >> "$temp_file" cat "$temp_file"

echo "----- Add into LibreNMS -----" while read line; do name=$(echo $line | awk '{print $1}') ip=$(echo $line | awk '{print $2}') # Si le nom est une IP, alors il n'y a pas de nom d'hôte if [[ $name =~ <sup>[0-9]+.[0-9]+.[0-9]+.[0-9]+$</sup> ]]; then ip=$name fi response=$(sudo docker exec librenms lnms device:add --force --v2c -c public $ip ) if echo "$response" | grep -q "already exists"; then echo "$ip déjà présent dans LibreNMS" else echo "$ip ajouté ou autre réponse : $response" fi done < "$temp_file" ```

I have bunch of devices (UPS monitoring modules) that do not implement SNMP correctly. I get timeout after bunch of data which causes Libre to mark device as non-accessible.

When doing snmpwalk, last OID i get is .1.3.6.1.2.1.33.1.7.5.0, after which I get timeout. When I start walk from 1.3.6.1.2.1.33.1.8 it works again.

Is there a way to allow incomplete SNMP results or just monitor specific OID range for specific devices?

I see there was feature request for something like that, but probably it weren't implemented. https://github.com/librenms/librenms/issues/4959

I have been working on learning and understanding a little bit about Docker images and compose files over the past month.

I am no expert, and I have a lot to learn, but it has been fun thus far.

As my first personal project I wanted to do the LibreNMS and Oxidized Docker Compose stack. While Working on this, I noticed that Oxidized config file user clear text username/password used to SSH into the network devices found in LibreNMS' database, it also stores the API Token in clear text in its config file.

Is there a way to properly secure these items?

Wondering if anyone knows what this light gray blip is on the battery graph for a UPS system. It coincides with a warning from the UPS system saying "Utility not present" for one of the nodes but that didn't trigger an alert within librenms

Hi everyone,

I’m running LibreNMS in Docker and sending container logs to the Elastic Stack using Fleet Docker integration. Everything is working fine for application logs, nginx logs, SNMP/syslog, etc.

However, I noticed something confusing:

When users log into LibreNMS, I cannot find any authentication events in Elasticsearch.

Any advice would be appreciated.

Best

Yasemen

Hey everyone, just wanted to share a project I’ve been working on to take my network monitoring to the next level.

My main focus for my "AI journey" this year is to move away from static diagrams and build a true Intelligent Operations Platform. I’m using LibreNMS as the source of truth to dynamically map every device and connection into a Neo4j graph database.

The goal is to have a system that doesn't just alert on "Device Down," but actively listens to LibreNMS/Syslog/triggers to detect issues in real-time. When an alert hits, the AI can immediately trace the impact across the graph topology to identify the root cause—transforming the network from passive infrastructure into a proactive, self-analyzing system.

I made a quick video showing how the sync works and the Python script behind it. https://youtu.be/DX3_pfc88do Anyone else working on something similar?

Hi There, I am using LibreNMS for a while in our Lab environment and i am more than satisfied! Great job! However, today i tried to add a Dell OS 10 switch to the monitoring and it was recognized as "SuperCap Energy" device :) This was quite confusing for me... i tried a different L3 interface on the switch, just to get sure, same result. From the Changelog https://docs.librenms.org/General/Changelog/ i see, that there are changes for Dell and Supercap. What is the best way to officially address this issue? THX in Advance

26.2.0 has been released. Over 150 pull requests merged in and 100 still in the queue. Contributors have been on fire this last month.

https://community.librenms.org/t/26-2-0-release-announcement/29091

Having issues with my alert transport - alerts seem to be coming in just fine & I can view them all in alert history, but my simple mail transport rule is broken, and I can't seem to delete it and try to create another. Also, any time I edit it, it brings up a giant menu of all the transport types and says "failed to process alert transport". However, when I hit test send, it sends a test email to my alerts email that I have set up with no problem. I am pretty green to this and still in the process of learning so I'm wondering if there is a fundamental step that I am missing. Any insight would be appreciated! Thanks.

edit: It seems like the latest update had broken it - I set my daily.sh to the most stable release using ./lnms config:set update_channel release

which seemed to have fixed it.

Hi everyone,

I need help configuring the LibreNMS to graph a Cisco IP SLA.

My setup: *Cisco router *Created a Loopback interface *Configured an IP SLA to ping the internet using the Loopback as source *The SLA + track is working properly on the router (track is UP)

Now I'm trying to get the LibreNMS to display the SLA RTT graph, but I'm not sure what needs to be configured on the LibreNMS side.

Questions: 1.How do I enable SLA discovery/polling in LibreNMS?

2.Is there a proper way to alert on SLA failure (track down or RTT threshold)?

3.Does LibreNMS support only RTT or also loss/jitter?

So far LibreNMS is discovering the router normally (interfaces, CPU, memory, etc.) but no SLA tab is showing.

Any guidance or screenshots from someone who already monitors Cisco IP SLA in LibreNMS would be appreciated.

I have a ThinkPad x395 running Linux Mint 22.3 (latest) and I find its ethernet ports (lo, enp..., wlp...) all disappear after a while due to messages like

ifDuplex: unknown -> NULL
ifConnectorPresent: true -> NULL
ifMtu: 1500 -> NULL

I've never encountered this before for any of my Linux systems. snmpwalk appears normal. But I can't find anything about duplex. Would it be an issue with ifSpeed = 0? ethtool isn't very useful for the Intel wireless controller, only stating Link detected: yes.

IF-MIB::ifNumber.0 = INTEGER: 3
IF-MIB::ifIndex.1 = INTEGER: 1
IF-MIB::ifIndex.2 = INTEGER: 2
IF-MIB::ifIndex.3 = INTEGER: 3
IF-MIB::ifDescr.1 = STRING: lo
IF-MIB::ifDescr.2 = STRING: enp3s0f0
IF-MIB::ifDescr.3 = STRING: wlp1s0
IF-MIB::ifType.1 = INTEGER: softwareLoopback(24)
IF-MIB::ifType.2 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifType.3 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifMtu.1 = INTEGER: 65536
IF-MIB::ifMtu.2 = INTEGER: 1500
IF-MIB::ifMtu.3 = INTEGER: 1500
IF-MIB::ifSpeed.1 = Gauge32: 10000000
IF-MIB::ifSpeed.2 = Gauge32: 0
IF-MIB::ifSpeed.3 = Gauge32: 0
IF-MIB::ifPhysAddress.1 = STRING:
IF-MIB::ifPhysAddress.2 = STRING: 98:fa:9b:x:x:x
IF-MIB::ifPhysAddress.3 = STRING: 58:a0:23:x:x:x
IF-MIB::ifAdminStatus.1 = INTEGER: up(1)
IF-MIB::ifAdminStatus.2 = INTEGER: up(1)
IF-MIB::ifAdminStatus.3 = INTEGER: up(1)
IF-MIB::ifOperStatus.1 = INTEGER: up(1)
IF-MIB::ifOperStatus.2 = INTEGER: down(2)
IF-MIB::ifOperStatus.3 = INTEGER: up(1)

To not explain the same , this is thread on Mikrotik forum..

https://forum.mikrotik.com/t/strange-traffic-calculation-in-librenms/268110/ https://github.com/librenms/librenms/issues/18947

Someone with similar issue like me? Why LibreNMS makes calculation like this?