June 2024 - observium - lists.observium.org

Building an Observium appliance
by Serge Caron 16 Dec '24

16 Dec '24

It's time I give something back to the community. This project, GitHub - SergeCaron/observium_appliance: Build and maintain an Observium appliance<https://github.com/SergeCaron/observium_appliance>, is aimed at SMB environments and walks the sysadmin through each phase of creating and maintaining (backup, restore, upgrade) an Observium appliance. It also covers the installation of Let's Encrypt certificates, secure (https) access to the Observium web site, basic email configuration for notifications, and log aggregation. It's basically a recipe with scripts. A small appliance with fault tolerant network configuration is shown to emphasize the standalone nature of the project. Of course, any virtual environment can do ;-) I hope I kept the typos and omissions to a minimum. Regards, Serge Caron

4 4

User access levels
by Tibor Marchyn 06 Dec '24

06 Dec '24

Hi, I have another beginner question please. I have setup Active Directory authentication, but how can I limit users to exact devices? I really do not want for some users to see anything else than they need to and all of them have level 1 access. And I can't see any option to limit them or assign user to device. Also it would be great to assign users to exact device group I have created. Thanks a lot Tibor

2 2

Buy subscription via invoice / bank transfer ?
by anders.jonsson＠norconsult.com 21 Oct '24

21 Oct '24

Hello, Thanks for your excellent software. We are very interested in buying a Professional Subscription subscription (to begin with) but we don't have company issued cards and not allowed to used paypal either. Is there any possibility to do a invoice / bank transfer instead ?

3 2

API Error 500
by Nicolas Korten 18 Sep '24

18 Sep '24

Hello dear Observium Team, I'm trying to add a device using the API and get an error 500 message instead of the expected notice that the device is not respondig to snmp. > curl -u korten:secret https://observium.domain.net/api/v0/devices/ -X POST -d '{"hostname":"pe-lab02.domain.net", "snmp_community":"test", "ping_skip":"on"}' <h1>500 Internal Server Error</h1><h3>flight\Engine::_json(): Argument #2 ($code) must be of type int, string given, called in /opt/observium/libs/flight3/core/Dispatcher.php on line 86 (0)</h3><pre>#0 /opt/observium/libs/flight3/core/Dispatcher.php(86): flight\Engine->_json() #1 /opt/observium/libs/flight3/core/Dispatcher.php(50): flight\core\Dispatcher->runEvent() #2 /opt/observium/libs/flight3/Engine.php(113): flight\core\Dispatcher->run() #3 [internal function]: flight\Engine->__call() #4 /opt/observium/libs/flight3/core/Dispatcher.php(287): call_user_func_array() #5 /opt/observium/libs/flight3/Flight.php(143): flight\core\Dispatcher::invokeMethod() #6 /opt/observium/html/api/v0/includes/devices.inc.php(133): Flight::__callStatic() #7 [internal function]: api_add_device() #8 /opt/observium/libs/flight3/core/Dispatcher.php(250): call_user_func_array() #9 /opt/observium/libs/flight3/core/Dispatcher.php(237): flight\core\Dispatcher::callFunction() #10 /opt/observium/libs/flight3/Engine.php(508): flight\core\Dispatcher::execute() #11 /opt/observium/libs/flight3/core/Dispatcher.php(86): flight\Engine->_start() #12 /opt/observium/libs/flight3/core/Dispatcher.php(50): flight\core\Dispatcher->runEvent() #13 /opt/observium/libs/flight3/Engine.php(113): flight\core\Dispatcher->run() #14 [internal function]: flight\Engine->__call() #15 /opt/observium/libs/flight3/core/Dispatcher.php(287): call_user_func_array() #16 /opt/observium/libs/flight3/Flight.php(143): flight\core\Dispatcher::invokeMethod() #17 /opt/observium/html/api/v0/index.php(66): Flight::__callStatic() #18 {main}</pre> As far as I can see, the error is in: api/v0/includes/devices.inc.php at line 133: >Flight::json($json, '400'); should be: Flight::json($json, 400); Agree? Thank you and have a nice day, Nico -- Nicolas Korten Dipl.-Ing. Systemtechnik und Dienste/EDV komro GmbH Am Innreit 2 DE-83022 Rosenheim Telefon: +49 8031 365 7913 Telefax: +49 8031 365 7699 Mail: korten(a)komro.net / http://www.komro.net __________________________________________________________________________________________________________ Geschäftsführer: Dipl. Ing. Gert Vorwalder Vorsitz im Aufsichtsrat: Oberbürgermeister Andreas März Sitz der Gesellschaft: Rosenheim Registergericht: Traunstein, HRB-Nr. 10689 USt.-IdNr.: DE 188814299 Hinweise zur Verarbeitung Ihrer personenbezogenen Daten gem Art. 13 DSGVO: Verantwortlich für die Verarbeitung Ihrer personenbezogenen Daten im Rahmen des vorliegenden Kontakts ist die komro GmbH Weitere Informationen zur Verarbeitung Ihrer Daten, insbesondere zu den Ihnen zustehenden Rechten, können Sie unserer Homepage unter https://www.komro.net/datenschutz entnehmen oder auf jedem anderen Wege unter den o.g. Kontaktdaten bei uns erfragen.

4 7

How to add a device which only responds to ping/icmp?
by Thomas Stather 23 Aug '24

23 Aug '24

Hi How can i add a device which cannot (!) speak any snmp and only responds to ping/icmp requests? We have an Aruba wlan setup (Mobility Master and two Mobility Controllers) and i want to add the aps to Observium, so that they are monitored but only by ping/icmp. (The MM and the two MCs are already added to Observium, but i cannot see if one AP went offline or came back online again) The aps cannot speak any snmp when managed by the MM or MC, thats why it fails when i try to add one via ./add_device.php I appreciate any help :) Best, Thomas -- Thomas Stather IT Services VCP4, VCP6-DCV, VCP6.5-DCV Tel: +49 6221 486 628 Fax: +49 6221 486 561 Bevor Sie diese Mail ausdrucken, prüfen Sie bitte ob dies wirklich nötig ist. Umweltschutz geht uns alle an!

10 15

Observium doesn't show interfaces within VPRN on Nokia routers
by Tao Zhang 21 Aug '24

21 Aug '24

Hi Observium team, We are using Observium as a main tool to monitor our router interfaces and collect SNMP stats. We recently replaced our Juniper routers with Nokia SR 7750. We noticed that Observium doesn't work very well with Nokia routers. Observium can only show the interfaces in the master instance, not the interfaces within VPRN or VPLS instances (Nokia call those interfaces SAPs). To be able to see interfaces within VPLS or VPRN, we need to enable two other MIBs, TIMETRA-SAP-MIB and TIMETRA-VRTR-MIB. We are not sure how to enable those two MIBs. Do we need to add them manually? This is the MIBs enabled on the Nokia router (default). [cid:ece89bfc-3ae2-4dcd-9c7c-641c3978f803] Any suggestion is greatly appreciated. Thanks, Tao

1 1

Missing some nice stats from Cisco 9800 that I got from Cisco 5520
by andri＠harpa.is 12 Aug '24

12 Aug '24

Hi Our organization recently upgraded from Cisco 5520 WLC to Cisco 9800 WLC. In observium I get really good statistics about wireless client count and wireless ap count on the 5520 but not on the 9800. I am not sure if this is something on observium side or cisco side. But I wanted to ask if anyone has the same issue and if they found a solution. Or maybe this is just something that needs to be added. Please let me know if there is any further information I can submit. Best regards Andri

4 6

Bug report: Broken scaling on some SFP receive power graphs
by Corwin Ziegler Hunts 09 Aug '24

09 Aug '24

Hi Observium team, We're having issues with some of the generated graphs. Some of our devices report the light level received by SFPs using mW (rather than dBm). We are on the latest stable revision (13582). Issue 1: The graphs generated by Observium for these sensors usually show an excessive scale of at least -100 mW to 100 mW when the data in the specified time interval are entirely within the range 100 nW to 1 mW and usually only a small chunk of that. The calculated minimum and maximum values shown below the graph are correct. These graphs worked properly in the past with a prior version of Observium. Issue 2: Selecting and deselecting the Force Autoscale option appears to have no effect on the generated graph or displayed rrd graph command. Manually running the generated rrd graph command after removing the "--alt-autoscale" option results in a good graph. Here is the raw SNMP output for one of the these sensors showing a current value of 0.5560mW: ENTITY-SENSOR-MIB::entPhySensorType.1000004631 = INTEGER: watts(6) ENTITY-SENSOR-MIB::entPhySensorScale.1000004631 = INTEGER: milli(8) ENTITY-SENSOR-MIB::entPhySensorPrecision.1000004631 = INTEGER: 4 ENTITY-SENSOR-MIB::entPhySensorValue.1000004631 = INTEGER: 5560 ENTITY-SENSOR-MIB::entPhySensorOperStatus.1000004631 = INTEGER: ok(1) Corwin

5 12

Oxidized Integration?
by Wiethoff, Helge 05 Aug '24

05 Aug '24

Hi, I am currently testing a replacement for rancid. Rancid has worked for a long time, but adding new device classes feels more and more unwieldy. Oxidized [1] makes a good first impression and I was able to add new device classes without big problems. Then of course I would also like to see an integration with my favorite network management tool :-) There are people who have already worked on this: https://github.com/colin-stubbs/observium-oxidized It looks like this patch doesn't quite work for current observium versions, so I'd like to ask if anyone is working on it and what are the chances that there could be an Observium integration (professional edition)? Thanks Helge [1] https://github.com/ytti/oxidized

3 4

Many devices shown as down(dns)
by Marios.P＠crowe.com.cy 19 Jul '24

19 Jul '24

Hello all, I can see in my observium installation that many devices changed their status to down(dns). This is a new installation and we migrated the configuration yesterday on a new server and devices were working properly. At around the same time (14:20:00) a lot of our machines changed their status to down. The message in the Event log is "Device status changed to Down (dns)". I tried to find what the problem may be but I can see SNMP are correct and dns records exist for the systems. Any ideas? Thank you, Marios

6 7