- observium - lists.observium.org

Deleting device problems!
by Svensson Fredrik A 07 Nov '16

07 Nov '16

Hi there! When we are deleting a device we struggle with the time it takes, I have done a debug and this seems to be the problem: SQL[DELETE FROM `devices_perftimes` WHERE `device_id` = '593'] ROWS[-1] SQL RUNTIME[97.04324698s] ERROR[Error in query: (The total number of locks exceeds the lock table size) 1206] Can you help me with what I can do to fix this problem? This also take some time: SQL[DELETE FROM `alert_log` WHERE `device_id` = '593'] ROWS[11480] SQL RUNTIME[15.23252392s] Regards Fredrik -----Ursprungligt meddelande----- Från: observium [mailto:observium-bounces@observium.org] För greg lambert Skickat: den 25 oktober 2016 09:41 Till: Observium Network Observation System <observium(a)observium.org> Ämne: [Observium] Acme Packet SBC 3820 Good Day, I just loaded my SBC into observium - it doesn not graph the voice utilization. I was hoping to use it to graph voice channel useage etc. Is there any suggested way to get this graphed? Regards, Greg _______________________________________________ observium mailing list observium(a)observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

5 12

Add New Mibs for Huawei Storage
by Jean CARUSO 07 Nov '16

07 Nov '16

Hi, What is the process to integrate the MIBs manufacturer Huawei in Observium? I have the mib files Thank you for your help Regards Jean Caruso Ce message peut contenir des informations confidentielles, couvertes par le secret professionnel ou réservées exclusivement à leur destinataire. Toute lecture, utilisation, diffusion ou divulgation sans autorisation expresse est rigoureusement interdite. Si vous n'en êtes pas le destinataire, merci de prendre contact avec l'expéditeur et de détruire ce message. This email may contain material that is confidential, privileged and/or attorney work product for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

2 3

Re: [Observium] CheckPoint alert creation problem
by Moerman, Maarten 07 Nov '16

07 Nov '16

Have you selected the right entity type when adding an alert-checker? It needs to be of type “sensor” , it doesn’t work when you leave it on “device” Maarten From: observium <observium-bounces(a)observium.org> on behalf of Laszlo Nemeth <laszlo.nemeth(a)emarsys.com> Reply-To: Observium Network Observation System <observium(a)observium.org> Date: Friday, October 28, 2016 at 3:37 PM To: Observium Network Observation System <observium(a)observium.org> Subject: [Observium] CheckPoint alert creation problem Hello, I have a CheckPoint 2205 device. It is supported by Observium, so we love it :D I would like to create an alert for it’s fan speed. I do a normal alert like our other looks like: Device: hostname match *cpfw01* Entity match: sensor_class equals fanspeed Test condition: sensor_value greater 3000 With this settings if i push a Rebuild, it shows 0 entities. How can i check what is wrong? I tried to change the fanspeed to temperature, but the problem is similar, 0 entities after rebuild. I attached a picture about the graphs of the device. Hmm... if i run a „rebuild” there are see lot of devices but there is no any „FW” devices however we have more whit this FW prefix. May be this is the problem? It looks like this list doesn’t show all of our devices. Thanks Br Laszlo

4 8

Changing the name of a device
by Youssef BENGELLOUN - ZAHR 07 Nov '16

07 Nov '16

2 2

Re: [Observium] Check IPsec tunnel status on Juniper SRX firewalls
by Youssef BENGELLOUN - ZAHR 07 Nov '16

07 Nov '16

1 1

Force disable 'Neighbours discovery: LLDP-MIB', ['xdp'] = FLASE; not working
by Andy Lemin 06 Nov '16

06 Nov '16

Hi, How can we _Force_ the disablement of discovering hosts via LLDP/XDP? Normally when running poller.php, with '$config['autodiscovery']['xdp'] = FLASE;' set in config.php, everything is fine. However when running '/opt/observium/discovery.php', it finds a switch, and we have LLDP enabled on our servers and switches for other processes related to the management of servers. However this means that Observium takes over an hour to discover a single Virtual Cassis which has 192 ports, with over 100 active servers (all showing up in the LLDP on the switch). Obviously this is a waste of time, and unnecessarily stressful for the servers being scanned and the Observium server. Why is discovery.php not honouring '$config['autodiscovery']['xdp'] = FLASE;' as set in config.php? Cheers, Andy.

3 3

Device Properties - Ports - Toggle Not Working
by Iwanski, Ed 06 Nov '16

06 Nov '16

I tried looking for mailing list archives but didn't find them online, please let me know where to look if I am mistaken. We are on Observium Professional 0.16.10.8181, stable svn update rev 8201 shown so looks up to date. We are having problems using the toggle or disable for an entire column on the device properties port page. I thought it might be a browser issue but I have tried Chrome, Firefox and IE from different computers with no luck. Currently the button just behaves like the save button and submits the form instead of changing the status on the existing page. Any thoughts on what else I could check would be appreciated.

1 0

SSH versus Ping for device_status
by Dano, Leo 03 Nov '16

03 Nov '16

Hi all, I remember back that ssh wasn't supported, in the later versions has this been implemented? We want Observium to notify is a node loses it's ssh capabilities, versus just icmp Thanks, ----------------------- Leo Dano

1 0

Device Down false positive
by Sebastian Klute 03 Nov '16

03 Nov '16

Hi Tom, well it cannot really be that the device is marked as down by alert. Test conditions are as follows: device_status_type ping device_status equals 0 If I understand it correctly, even if snmp is not reachable the device should NOT be marked as down, because it is pingable. Therefore I do not understand why it is still marked as down. Message: 5 Date: Wed, 2 Nov 2016 20:36:19 +0100 From: Tom Laermans <tom.laermans(a)powersource.cx> To: Observium Network Observation System <observium(a)observium.org> Subject: Re: [Observium] Device Down False positive and snmpget Message-ID: <eff1c872-a32b-fe5f-ecb5-eafe35712ff4(a)powersource.cx> Content-Type: text/plain; charset="utf-8"; Format="flowed" Sebastian, The device was likely down due to ping, first... then, as it became pingable but not snmp-able, there was no change logged in device status (down = down). As to why snmpget is telling you 2 is > 128, I'm not sure... Tom On 02/11/2016 20:05, Sebastian Klute wrote: > Hello folks, > > today I got kinda strange problem. I got a Server up and running fine > but it is still shown as device down. "Device status changed to Down > (ping)" > After some debugging and digging into the workflow of polling and > checking egc. I tried to redo the different checks that could lead to > a device down. > First of all: Is it pingable ? > > root@om:/tmp# /usr/bin/fping -t1000 -t 500 -c 20 -q 84.200.41.226 > 84.2xx.xxx.xxx : xmt/rcv/%loss = 20/20/0%, min/avg/max = > 0.20/0.30/0.43 > > seems good to me - no idea why it should be down by ping. > Is the hostname resolvable? Yes it is. Standart ping with hostname is > working fine. > > So I'll dig further into debug logs and found this > > CMD[/usr/bin/snmpget -v2c -c *** -Pu -OQUst -m SNMPv2-MIB -M > /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp > 'udp':'hostname.example':'161' sysObjectID.0 sysUpTime.0] > > CMD EXITCODE[1] > CMD RUNTIME[6.0283s] > STDOUT[ > > ] > STDERR[ > Timeout: No Response from udp:hostname.example:161. > ] > SNMP STATUS[FALSE] > > I wondered why and did it manualy. > The error is as followed: > > Too many object identifiers specified. Only 128 allowed in one > request. > > > The question is now, what can I do to solve this issue? What about the > false positive device down by ping alert? > > > Additional Info: > > > $data - /opt/observium/poller.php:170 > /opt/observium/includes/alerts.inc.php:61 > ========================================= > array( > [device_status] => string(1) "0" > [device_status_type] => string(4) "snmp" > [device_ping] => string(4) "7.34" > [device_snmp] => int(0) > ) > > Thanks for the help and best regards > Sebastian Klute > > -- > Accelerated IT Services GmbH > Kruppstraße 105 - 60388 Frankfurt - Germany > sk(a)accelerated.de -http://www.accelerated.de/ > Phone: +49 69 - 900 180 41 - Fax: +49 69 - 900 180 90 > > HRB: 60665 - Amtsgericht Ludwigshafen - VatID: DE253684415 > Managing Directors: Nicolaj Kamensek & Ole Krieger > > > _______________________________________________ > observium mailing list > observium(a)observium.org > http://postman.memetic.org/cgi-bin/mailman/listinfo/observium -- Accelerated IT Services GmbH Kruppstraße 105 - 60388 Frankfurt - Germany sk(a)accelerated.de - http://www.accelerated.de/ Phone: +49 69 - 900 180 41 - Fax: +49 69 - 900 180 90 HRB: 60665 - Amtsgericht Ludwigshafen - VatID: DE253684415 Managing Directors: Nicolaj Kamensek & Ole Krieger

2 1

Squash the Hamster!
by Marc Elvery 03 Nov '16

03 Nov '16

No, let's not stand on the hamster, put the PNG could be a lot smaller. Using observium on a site with a slow line, during the login, the hamster takes longer to load than needed. When I throw the PNG into https://tinypng.com/ It shrinks from 359KB -> 67KB. Seems worthwile. Maybe some other PNG's can be shrunken aswell? Greetings, Marc

1 0