- observium - lists.observium.org

Cronjobs in polling the devices
by Jerico M. Rubion 26 Mar '15

26 Mar '15

Hi there, I would like to inquire about the desired minimum cron jobs that are accepted in observium. I only have a Quad Core Intel(R) Xeon(R) CPU E5405 @ 2.00GHz CPU resources available currently managing 69 HOSTS/Devices. My current setting in /etc/cron.d/observium is */10 * * * * root /opt/observium/poller-wrapper.py 4 >> /dev/null 2>&1 */10 * * * * root /opt/observium/poller.php -h all >> /dev/null 2>&1 Can I comment out the 2nd line -> */10 * * * * root /opt/observium/poller.php -h all >> /dev/null 2>&1 ?? Best Regards, Jerico M. Rubion | 77GSI IT Services Group SEVEN SEVEN GLOBAL SERVICES INC. | 27th Floor, Orient Square Bldg., F. Ortigas Jr. Ortigas Center, Pasig City, Philippines 1605 Office: +632.915.7747 ext. 1911 | Mobile: +63.9175382740 | Duo: +632.9667501 The Information contained and all attachments to this email are for the named recipient(s) only. It contains legally privileged and confidential information intended solely for the use of the addressee. The addressee undertakes to use such information consistent with its privileged and confidential character, and by the receipt thereof appreciates that any use contrary thereto will subject him to sanctions provided for by law. If the reader of this message is not the intended recipient, please be notified that any reading, dissemination, distribution, copying or other use of this message or its attachments is strictly prohibited. If you have received this transmittal in error, please notify the sender immediately.

2 1

Inquiry increased work load
by Jerico M. Rubion 25 Mar '15

25 Mar '15

Hi, Is there an automatic upgrade/patch that happened last March 24 2015 (1pm) EST Timezone? I'm getting an incremental increase of CPU load starting from the date and time I specified, I didn't change any settings in observium application even in the cronjobs. Output of: ps aux | sort -nrk 3 | head root 12585 8.5 0.0 4612 696 ? R 02:12 0:00 /usr/bin/snmpbulkwalk - xxx -OQUs -m CISCO-IPSEC-FLOW-MONITOR-MIB -M /opt/observium/mibs udp:xxxxxxx:161 cipSecGlobalStats root 12546 7.0 0.0 4748 1540 ? R 02:12 0:00 /usr/bin/snmpwalk -v1 -c -OQUs -m SNMPv2-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp udp:xxxxxxx:161 snmp root 12581 6.5 0.0 4880 1744 ? R 02:12 0:00 /usr/bin/snmpget -v1 -c -Otv -M /opt/observium/mibs udp:xxxxxx:161 sysUpTime.0 root 12579 6.0 0.0 4932 1828 ? R 02:12 0:00 /usr/bin/snmpbulkwalk -r 0 -v2c -c -OqsX -m BRIDGE-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp udp:xxxxxx:161 dot1dTpFdbEntry root 12573 6.0 0.0 0 0 ? R 02:12 0:00 [snmpbulkwalk] root 12571 6.0 0.0 5008 1888 ? R 02:12 0:00 /usr/bin/snmpbulkwalk -v2c -c -OQUn -M /opt/observium/mibs udp:xxxxx:161 .1.3.6.1.4.1.9.9.13.1 root 12569 6.0 0.0 4748 1668 ? R 02:12 0:00 /usr/bin/snmpbulkwalk -r 0 -v2c -c -OqsX -m BRIDGE-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp udp:xxxxxxx:161 dot1dTpFdbEntry root 12582 5.5 0.0 4924 1968 ? R 02:12 0:00 /usr/bin/snmpbulkwalk -v2c -c -OQUs -m IF-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp udp:xxxxx:161 ifEntry root 12539 5.3 0.0 5016 1884 ? R 02:12 0:00 /usr/bin/snmpbulkwalk -v2c -c -OQUs -m CISCO-VLAN-MEMBERSHIP-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp:/opt/observium/mibs/cis co udp:xxxxxx:161 vmVlan root 12557 5.0 0.0 5016 1872 ? R 02:12 0:00 /usr/bin/snmpbulkwalk -v2c -c -OQUs -m CISCO-VLAN-MEMBERSHIP-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp:/opt/observium/mibs/cis co udp:xxxxxx:161 vmVlan Note: xxxxx is used to replaced sensitive information Kindly see attached screenshot for the incremental increase of CPU load that happend last Match 24 1pm (EST Timezone) Best Regards, Jerico M. Rubion | 77GSI IT Services Group SEVEN SEVEN GLOBAL SERVICES INC. | 27th Floor, Orient Square Bldg., F. Ortigas Jr. Ortigas Center, Pasig City, Philippines 1605 Office: +632.915.7747 ext. 1911 | Mobile: +63.9175382740 | Duo: +632.9667501 The Information contained and all attachments to this email are for the named recipient(s) only. It contains legally privileged and confidential information intended solely for the use of the addressee. The addressee undertakes to use such information consistent with its privileged and confidential character, and by the receipt thereof appreciates that any use contrary thereto will subject him to sanctions provided for by law. If the reader of this message is not the intended recipient, please be notified that any reading, dissemination, distribution, copying or other use of this message or its attachments is strictly prohibited. If you have received this transmittal in error, please notify the sender immediately.

1 0

Re: [Observium] howto control ports
by Tom Laermans 25 Mar '15

25 Mar '15

You typo'd your realname in your mail client setup ;) 'Ports' is quite a confusing word to use in this context indeed... Tom On Mar 24, 2015 8:38 PM, Adam Armstronf <adama(a)memetic.org> wrote: > > Well, that was totally not obvious! > > We don't actually do any "port" monitoring at all, the old services code is long since deprecated and probably broken. > > Adam. > > Sent with AquaMail for Android > http://www.aqua-mail.com > > On 24 March 2015 12:17:28 Frank Lahr <logman0u812(a)gmail.com> wrote: >> >> He wants to monitor an applications port(s), up/down and the data going going threw it. >> I was thinking about using Observium to monitor dicom/hl7 ports too, but have not looked into it yet. >> >> Frank >> >> On Tue, Mar 24, 2015 at 2:48 AM, Adam Armstrong <adama(a)memetic.org> wrote: >>> >>> I think you might be using the wrong words :) >>> >>> adam. >>>> >>>> On 24/03/2015 06:25:33, J.P.M.H. Geerets <j.p.geerets(a)amc.uva.nl> wrote: >>>> >>>> Hi folks, >>>> >>>> Bit new here. >>>> >>>> Have an observium (community edition) install in test environment. >>>> Is het possible to creat my own ports to test on? >>>> Want to test for example ports on a cloverleaf (communication) server to check orm messages etc. >>>> Also wanna check dicomports, mostly on 104. >>>> >>>> Any idea how to do this with observium? >>>> >>>> >>>> Met vriendelijke groet, >>>> >>>> Jean-Paul >>>> --- >>>> Jean-Paul Geerets - ICT Radiologie >>>> >>>> ________________________________ >>>> >>>> AMC Disclaimer : http://www.amc.nl/disclaimer >>>> >>>> ________________________________ >>>> _______________________________________________ >>>> observium mailing list >>>> observium(a)observium.org >>>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium >>> >>> >>> _______________________________________________ >>> observium mailing list >>> observium(a)observium.org >>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium >>> >> >> >> >> -- >> Frank >> _______________________________________________ >> observium mailing list >> observium(a)observium.org >> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium >>

3 2

Re: [Observium] (no subject)
by Adam Armstrong 25 Mar '15

25 Mar '15

Either SNMP timeout, SNMP stack bug or vendor bug. Adam. On 25 Mar 2015 02:06, Zach Underwood <zunder1990(a)gmail.com> wrote: > > I get the same thing about the interfaces nulling on some of my HP 1910 switches. > > On Mar 24, 2015 10:02 PM, "Christopher Pole" <chris(a)apexn.com.au> wrote: >> >> Poor choice of terms on my part regarding discovery, let me try again. >> >> Every now and then Observium will go through and mark every interface attribute on this device as NULL and then shortly thereafter re-learn the attributes, for example: >> >> Time: 2015-03-25 00:56:26 >> Port: lag2 >> Message: Interface changed: [ifName] LAG2 -> NULL; [ifAlias] Trunk: sw01 -> NULL; [ifAdminStatus] up -> NULL; [ifOperStatus] up -> NULL; [ifMtu] 9216 -> NULL; [ifSpeed] 2000000000 -> NULL; [ifHighSpeed] 2000 -> NULL; [ifType] ieee8023adLag -> NULL; [ifPhysAddress] 001bed9fa841 -> NULL; [ifPromiscuousMode] true -> NULL; [ifConnectorPresent] false -> NULL >> >> At this point the alert triggers for this interface, as anything over 0bps is triggers the >85% util alarm. >> >> Shortly thereafter observium relearns the interface attributes: >> >> Time: 2015-03-25 01:00:16 >> Port: lag2 >> Message: Interface changed: [ifName] -> LAG2; [ifAlias] -> Trunk: sw01; [ifAdminStatus] -> up; [ifOperStatus] -> up; [ifMtu] -> 9216; [ifSpeed] -> 2000000000; [ifHighSpeed] -> 2000; [ifType] -> ieee8023adLag; [ifPhysAddress] -> 001bed9fa841; [ifPromiscuousMode] -> true; [ifConnectorPresent] -> false >> >> At this point the alert sends a recovery message. >> >> The nullification and re-learning of interface attributes happens periodically but with no fixed schedule. Is this possibly something that can be caused by a bulk-walk failure part way through? Or an SNMP timeout? >> >> Thanks, >> >> Chris >> >> >> On Wed, Mar 25, 2015 at 10:41 AM, Adam Armstrong <adama(a)memetic.org> wrote: >>> >>> Nothing gets rediscovered at any frequency other than the frequency with which you run discovery.php. >>> >>> Almost everything collected by the poller is collected by snmpbulkwalk. >>> >>> It's possible that bulkwalk is failing part way through for this device causing the ifHighSpeed to be set to zero (or set to the value of ifSpeed, which will be just as useless on ports >1Gb) >>> >>> adam. >>>> >>>> On 24/03/2015 22:16:43, Christopher Pole <chris(a)apexn.com.au> wrote: >>>> >>>> Hi folks, >>>> >>>> we have an alert that triggers when certain ports hit >85% utilisation being triggered by a single device on a regular basis as it seems to get rewalked quite often, which briefly sets the speed of the monitored ports to 0 which then triggers the alert as any utilisation over 0 is >85% :). >>>> >>>> The device is a Brocade CES, but it is the only one in our fleet that suffers from this rediscover > trigger alert issue. Though the others also seem to rediscover more often than is necessary. >>>> >>>> Any thoughts on how I might figure out what is going on so I can fix it? >>>> >>>> Thanks, >>>> Chris >>>> _______________________________________________ observium mailing list observium(a)observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium >>> >>> >>> _______________________________________________ >>> observium mailing list >>> observium(a)observium.org >>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium >>> >> >> >> _______________________________________________ >> observium mailing list >> observium(a)observium.org >> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium >>

1 0

(no subject)
by Christopher Pole 25 Mar '15

25 Mar '15

Hi folks, we have an alert that triggers when certain ports hit >85% utilisation being triggered by a single device on a regular basis as it seems to get rewalked quite often, which briefly sets the speed of the monitored ports to 0 which then triggers the alert as any utilisation over 0 is >85% :). The device is a Brocade CES, but it is the only one in our fleet that suffers from this rediscover > trigger alert issue. Though the others also seem to rediscover more often than is necessary. Any thoughts on how I might figure out what is going on so I can fix it? Thanks, Chris

3 3

Alerts not working
by Patrick Marquetecken 25 Mar '15

25 Mar '15

I'm trying to get my alerts working but until now without success. I have put a server down, and i know some systems have a disk that is full about 80% I have followed the http://www.observium.org/wiki/Creating_an_Alert_Checker and created some alert according to the examples, and run the regenerate. Test mails are successfully send from the command line. but no luck, can anyone please advice on this matter?

3 7

howto control ports
by J.P.M.H. Geerets 24 Mar '15

24 Mar '15

Hi folks, Bit new here. Have an observium (community edition) install in test environment. Is het possible to creat my own ports to test on? Want to test for example ports on a cloverleaf (communication) server to check orm messages etc. Also wanna check dicomports, mostly on 104. Any idea how to do this with observium? Met vriendelijke groet, Jean-Paul --- Jean-Paul Geerets - ICT Radiologie ________________________________ AMC Disclaimer : http://www.amc.nl/disclaimer ________________________________

4 6

LDAP changes in the Professional version?
by George Phillips 23 Mar '15

23 Mar '15

Hi folks! I tried searching the list but didn’t see anything promising... I had LDAP auth setup and working great on the Community version, but as soon as I upgraded to Professional (version 0.15.3.6343), it ceased allowing logins. A debug of the login shows: LDAP[Connecting to xxx.xxx.xxx.xxx] LDAP[Connected] LDAP[Referrals][Disabled] LDAP[Version][Set to 3] LDAP[Bind DN called] LDAP[Bind][cn=manager,ou=Internal,dc=example,dc=com] LDAP[Filter][(uid=testuser)][ou=Users,ou=Accounts,dc=example,dc=com] LDAP[Authenticate][User: testuser][Bind user: cn=Test User,ou=Users,ou=Accounts,dc=example,dc=com] LDAP[Authenticate][Comparing: cn=admins,ou=Groups,ou=Accounts,dc=example,dc=com][member=cn=Test User,ou=Users,ou=Accounts,dc=example,dc=com] LDAP[Authenticate][Compare LDAP error: No such object] So this part looked a bit strange to me: LDAP[Authenticate][Comparing: cn=admins,ou=Groups,ou=Accounts,dc=example,dc=com][member=cn=Test User,ou=Users,ou=Accounts,dc=example,dc=com] (notice the strange "member=cn=…" part) My config is: // Begin LDAP Config $config['auth_mechanism'] = "ldap"; $config['auth_ldap_starttls'] = FALSE; $config['auth_ldap_binddn'] = "cn=manager,ou=Internal,dc=example,dc=com"; $config['auth_ldap_bindpw'] = “PASSWORD_HERE"; $config['auth_ldap_attr']['uid'] = "uid"; $config['auth_ldap_attr']['uidNumber'] = "uidNumber"; $config['auth_ldap_attr']['cn'] = "cn"; $config['auth_ldap_objectclass'] = "inetOrgPerson"; $config['auth_ldap_version'] = 3; $config['auth_ldap_server'] = “LDAP_SERVER_IP"; $config['auth_ldap_port'] = 389; $config['auth_ldap_prefix'] = "cn="; $config['auth_ldap_suffix'] = ",ou=Users,ou=Accounts,dc=example,dc=com"; $config['auth_ldap_group'] = array("cn=admins,ou=Groups,ou=Accounts,dc=example,dc=com"); $config['auth_ldap_groupbase'] = "ou=Groups,ou=Accounts,dc=example,dc=com"; $config['auth_ldap_groupmembertype'] = "fulldn"; $config['auth_ldap_groupmemberattr'] = "member"; unset($config['auth_ldap_groups']); $config['auth_ldap_groups']['admins']['level'] = 10; // End LDAP Config Again, this same config works like a champ on the community edition. Did something change with LDAP auth in the professional edition? Am I missing something? Thanks! —George George Phillips www.pfsense.org

2 2

Request for more info from Allied Telesis AW+ switches
by Daniel Olynsma 23 Mar '15

23 Mar '15

Hi All, I use Observium daily to monitor various test networks and have noticed limited support for AlliedwarePlus products. I have done some digging round in the MIBs as well as the Observium php files and found that Observium is only extracting the Software version from AT-SETUP-MIB in the file: /opt/observium/includes/polling/os$ cat alliedwareplus.inc.php I would like to request that this be increased to contain more device information. I have found that the HW, serial No etc.. info is available in the AT-RESOURCE-MIB. I have not attached the MIB file as it is already part of Observium. Please find below some experiments that I have done extracting the info. I have conducted experiments on standalone as well as a 'stacked' product consisting of 8 physical switches (rscBoardName). Each device lists a base board '.3' and stacking module '.4' and a power supply '.5'. I would expect that you would only be interested in the '.3' values. for the switch Type. In my experiments I also found following could be extracted: H/W Rev - rscBoardRevision S/N - rscBoardSerialNumber I do not have PHP experience so do not know how to add this functionality myself. However since I am requesting this I do make myself available to assist in this or other Allied Telesis related tasks Regards, Daniel Experiment results: ------- Get the $Hardware value AT-RESOURCE-MIB rscBoardName Standalone (With stacking hw) danielo@tb105 ~ $ snmpwalk -O n -v 2c -c public 10.37.105.36 1.3.6.1.4.1.207.8.4.4.3.21.1.1.4 .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.1.3 = STRING: "x510-52GTX" danielo@tb105 ~ $ Stacked product (8-stack) danielo@tb105 ~ $ snmpwalk -O n -v 2c -c public 10.37.105.49 1.3.6.1.4.1.207.8.4.4.3.21.1.1.4 .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.1.3 = STRING: "AT-x930-52GTX" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.1.4 = STRING: "AT-StackQS" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.1.5 = STRING: "PWR250" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.2.3 = STRING: "AT-x930-52GPX" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.2.4 = STRING: "AT-StackQS" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.2.5 = STRING: "PWR250" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.3.3 = STRING: "AT-x930-52GTX" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.3.4 = STRING: "AT-StackQS" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.3.5 = STRING: "PWR250" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.4.3 = STRING: "AT-x930-52GPX" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.4.4 = STRING: "AT-StackQS" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.4.5 = STRING: "PWR250" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.5.3 = STRING: "AT-x930-52GTX" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.5.4 = STRING: "AT-StackQS" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.5.5 = STRING: "PWR250" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.6.3 = STRING: "AT-x930-52GPX" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.6.4 = STRING: "AT-StackQS" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.6.5 = STRING: "PWR250" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.7.3 = STRING: "AT-x930-52GTX" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.7.4 = STRING: "AT-StackQS" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.7.5 = STRING: "PWR250" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.8.3 = STRING: "AT-x930-52GPX" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.8.4 = STRING: "AT-StackQS" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.8.5 = STRING: "PWR250" danielo@tb105 ~ $ Standalone (Without stacking hw) danielo@tb105 ~ $ snmpwalk -O n -v 2c -c public 10.37.105.34 1.3.6.1.4.1.207.8.4.4.3.21.1.1.4 .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.1.3 = STRING: "x610-24Ts/X" danielo@tb105 ~ $ danielo@tb105 ~ $ snmpwalk -O n -v 2c -c public 10.37.105.34 1.3.6.1.4.1.207.8.4.4.3.21 .1.3.6.1.4.1.207.8.4.4.3.21.1.1.3.1.3 = STRING: "Base" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.1.3 = STRING: "x610-24Ts/X" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.5.1.3 = Gauge32: 340 .1.3.6.1.4.1.207.8.4.4.3.21.1.1.6.1.3 = STRING: " " .1.3.6.1.4.1.207.8.4.4.3.21.1.1.7.1.3 = STRING: "B-0" .1.3.6.1.4.1.207.8.4.4.3.21.1.1.8.1.3 = STRING: "C1ZQB4107" .1.3.6.1.4.1.207.8.4.4.3.21.2.1.1.1 = STRING: " Total: 511640 kB Free: 379816 kB" .1.3.6.1.4.1.207.8.4.4.3.21.2.1.2.1 = STRING: "63.0MB Used: 25.2MB Available: 37.8MB" .1.3.6.1.4.1.207.8.4.4.3.21.2.1.3.1 = STRING: "0 days 15:25:56" .1.3.6.1.4.1.207.8.4.4.3.21.2.1.4.1 = STRING: "2.0.4" danielo@tb105 ~ $ localadmin@observium:~$ snmpwalk -O n -m ~/.snmp/mibs/AT-RESOURCE-MIB -v 2c -c public 10.37.105.49 rscBoardName .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.1.3 = STRING: AT-x930-52GTX .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.1.4 = STRING: AT-StackQS .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.1.5 = STRING: PWR250 .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.2.3 = STRING: AT-x930-52GPX .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.2.4 = STRING: AT-StackQS .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.2.5 = STRING: PWR250 .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.3.3 = STRING: AT-x930-52GTX .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.3.4 = STRING: AT-StackQS .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.3.5 = STRING: PWR250 .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.4.3 = STRING: AT-x930-52GPX .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.4.4 = STRING: AT-StackQS .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.4.5 = STRING: PWR250 .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.5.3 = STRING: AT-x930-52GTX .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.5.4 = STRING: AT-StackQS .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.5.5 = STRING: PWR250 .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.6.3 = STRING: AT-x930-52GPX .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.6.4 = STRING: AT-StackQS .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.6.5 = STRING: PWR250 .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.7.3 = STRING: AT-x930-52GTX .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.7.4 = STRING: AT-StackQS .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.7.5 = STRING: PWR250 .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.8.3 = STRING: AT-x930-52GPX .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.8.4 = STRING: AT-StackQS .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.8.5 = STRING: PWR250 localadmin@observium:~$ snmpwalk -O n -m ~/.snmp/mibs/AT-RESOURCE-MIB -v 2c -c public 10.37.105.34 rscBoardName .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.1.3 = STRING: x610-24Ts/X localadmin@observium:~$ localadmin@observium:~$ localadmin@observium:~$ snmpwalk -O n -m ~/.snmp/mibs/AT-RESOURCE-MIB -v 2c -c public 10.37.105.36 rscBoardName .1.3.6.1.4.1.207.8.4.4.3.21.1.1.4.1.3 = STRING: x510-52GTX localadmin@observium:~$

2 1

BUG: (and Fix) in poll-billing.php - snmp v1 issue
by Mark Gibbons 23 Mar '15

23 Mar '15

Hi We upgraded to the PRO version last week so that we could look at the billing feature. We did all the needed setup stuff including install of jdgraph etc and added the required cron jobs. We created a few tests bills on a couple of ports We left it for a few hours and got absolutely nothing. We ran poll-billing manually and kept on seeing that it returned "No Data" We searched online and believe that this bug might be referenced here: http://jira.observium.org/browse/OBSERVIUM-711 We enabled OBS_DEBUG in poll-billing.php and immediately could see the problem. The snmpget command was being invoked requesting v2 High Capacity counters against snmp v1 targets. The reason is that the conditional clause when building the snmpget command is wrong. Currently line 86 reads: if ($port['snmp_version'] == "1" || $port['port_64bit'] == "0") { However the snmpv1 string that should be looked for is "v1" not "1". Changing the clause to: if ($port['snmp_version'] == "v1" || $port['port_64bit'] == "0") { Solves all the problems and poll-billing then correctly returns data from snmp v1 devices. Can the please be fixed in an upcoming SVN release so we do not have to reapply the fix if poll-billing.php gets changed for other reasons. KR's Mark

1 0

lighttpd
by tridinebandim 23 Mar '15

23 Mar '15

hi guys, just registered to address a missing info in lighttpd installiation tutorial. "python-mysqldb" package is not in the list of prerequisite packages and what i see is it's required to run the cron "*/5 * * * * root /opt/observium/poller-wrapper.py 2 >> /dev/null 2>&1" if you can edit the tutorial, people who uses lighttpd will be able to see graphs with data. thanks for all your hard work.

1 0

Re: [Observium] MySQL/Apache apps
by Ben Gatewood 23 Mar '15

23 Mar '15

Have you set the “Agent Port” section in your config? Ben On 16/03/2015 09:27, "Asensio Sánchez, Juan" <jasensios(a)indra.es> wrote: >Hi > >We have just installed Observium from SVN, added some hosts, and almost >everything seems to work fine. We have some MySQL servers, and followed >the instructions to get the graphs. Running observium_agent in the MySQL >server, I get the <<<mysql>>> section. Doing telnet to the MySQL server >from the Observium server, to the agent port, I get the same section, >but I don't get any data in the device page. Any advice? The same >happens with the Apache servers. > >Regards. > >Este correo electrónico y, en su caso, cualquier fichero anexo al mismo, >contiene información de carácter confidencial exclusivamente dirigida a >su destinatario o destinatarios. Si no es vd. el destinatario indicado, >queda notificado que la lectura, utilización, divulgación y/o copia sin >autorización está prohibida en virtud de la legislación vigente. En el >caso de haber recibido este correo electrónico por error, se ruega >notificar inmediatamente esta circunstancia mediante reenvío a la >dirección electrónica del remitente. >Evite imprimir este mensaje si no es estrictamente necesario. > >This email and any file attached to it (when applicable) contain(s) >confidential information that is exclusively addressed to its >recipient(s). If you are not the indicated recipient, you are informed >that reading, using, disseminating and/or copying it without >authorisation is forbidden in accordance with the legislation in effect. >If you have received this email by mistake, please immediately notify the >sender of the situation by resending it to their email address. >Avoid printing this message if it is not absolutely necessary. >_______________________________________________ >observium mailing list >observium(a)observium.org >http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

3 2

Re: [Observium] alert after 2 checks
by Tom Laermans 23 Mar '15

23 Mar '15

Yes. Set delay to 2 :) On Mar 23, 2015 6:07 PM, Simon Smith <simonsmith5521(a)gmail.com> wrote: > > Hi All, > > Im just wondering if this is possible, it may not be, or I just may not know how to do it? > > Currently i have a check thats says if bandwidth on a port more than 75%, then alert me… > > BUT i want the alert to only send me an email if after say 15mins its still over 75% ? > > i currently check our kit every 5 mins, so it work out after 3 checks > > Is this possible? > > regards > > Simon - Hestor Ltd > > _______________________________________________ > observium mailing list > observium(a)observium.org > http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

2 1

alert after 2 checks
by Simon Smith 23 Mar '15

23 Mar '15

Hi All, Im just wondering if this is possible, it may not be, or I just may not know how to do it? Currently i have a check thats says if bandwidth on a port more than 75%, then alert me… BUT i want the alert to only send me an email if after say 15mins its still over 75% ? i currently check our kit every 5 mins, so it work out after 3 checks Is this possible? regards Simon - Hestor Ltd

2 1

Duplicate device neighbour entries
by Chard, Alex (RET-SYD) 23 Mar '15

23 Mar '15

HI All, Just wondering is anyone has seen this happening before. We have switches that run LLDP and CDP. On most switches, Observium correctly determines that the neighbour entries for each protocol are identical and ignores the second one from LLDP. However on one switch, it's decided that it represents a separate connection (see attachment) I suspect it has to do with the differing port ID, but Observium seems to be able to reconcile that on other switches. Any ideas? Thanks, Alex This e-mail is for the use of the intended recipient(s) only. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's permission. We have taken precautions to minimise the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this e-mail. We cannot accept liability for any loss or damage caused by software viruses.

1 1

Re: [Observium] Critical alert not matching alerts checker
by Tom Laermans 23 Mar '15

23 Mar '15

Quick reply from my cellphone, you need an alert checker for entity type status instead of sensor since a few weeks... Tom On Mar 22, 2015 7:55 PM, Robert Williams <Robert(a)CustodianDC.com> wrote: > > Hi All, > > > > I have a device a Cisco 2960G with a failed internal PSU that has switched to it’s backup RPS supply. Observium is correctly identifying this as ‘critical’ under the Status Indicators for the device in question (image below): > > > > > > > > There is a “Hardware Fault” event I have created which /should/ have matched this, I believe: > > > > > > (I’ve added the match for value = critical as a test, it wasn’t there originally) > > > > This alert checker correctly matches a who load of devices and status checkers on many devices (1691 in total, all green): > > > > > > However, for this particular type of sensor, it does not see any sensors which match the “Hardware Fault” checker. As you can see, I have already removed all the “Device Match” and “Entity Match” criteria from the checker itself to rule that out. So essentially this checker is matching every type of sensor that there is (except, obviously, the one which I want it to). > > > > When I click the link on the graph for “Sw1, PS1 Critical, RPS Normal” sensor I get this URL http://observium-server/device/device=343/tab=health/metric=status/ which may be of use in helping diagnose this. > > > > After doing some more checking, I’ve found that it is not matching any other kind of sensor with a similar class, for example it does not match the WS-CAC-4000W-IN power supplies in any of the Cat6k chassis either. > > > > In fact, I think it’s actually failing to match sensors which have ‘normal’ and ‘critical’ type statuses, instead of ‘true’ and ‘false’ > > > > So the following sensors highlighted in yellow are also being missed from matching in this generic alerting config: > > > > > > So I believe it’s a wider issue and not just related to this one device. > > > > Can someone confirm what I’m doing wrong and/or maybe check to see if your alerting configurations can match sensors which have an OK state of ‘normal’ instead of ‘true’? > > > > Cheers! > > Robert Williams > Custodian Data Centre > Email: Robert(a)CustodianDC.com > http://www.CustodianDC.com

2 4

Map and Neighbours
by Dudu 23 Mar '15

23 Mar '15

Hi All, For some reason I don’t have the Neighbours and Map tabs under the ports page. It's probably something that I have change but I'm unable to find it. Also the mysql link table is empty. Any idea? Thanks David

1 1

Critical alert not matching alerts checker
by Robert Williams 22 Mar '15

22 Mar '15

Hi All, I have a device a Cisco 2960G with a failed internal PSU that has switched to it’s backup RPS supply. Observium is correctly identifying this as ‘critical’ under the Status Indicators for the device in question (image below): [cid:image001.png@01D064D0.36501EE0] There is a “Hardware Fault” event I have created which /should/ have matched this, I believe: [cid:image002.png@01D064D0.36501EE0] (I’ve added the match for value = critical as a test, it wasn’t there originally) This alert checker correctly matches a who load of devices and status checkers on many devices (1691 in total, all green): [cid:image003.png@01D064D0.36501EE0] However, for this particular type of sensor, it does not see any sensors which match the “Hardware Fault” checker. As you can see, I have already removed all the “Device Match” and “Entity Match” criteria from the checker itself to rule that out. So essentially this checker is matching every type of sensor that there is (except, obviously, the one which I want it to). When I click the link on the graph for “Sw1, PS1 Critical, RPS Normal” sensor I get this URL http://observium-server/device/device=343/tab=health/metric=status/ which may be of use in helping diagnose this. After doing some more checking, I’ve found that it is not matching any other kind of sensor with a similar class, for example it does not match the WS-CAC-4000W-IN power supplies in any of the Cat6k chassis either. In fact, I think it’s actually failing to match sensors which have ‘normal’ and ‘critical’ type statuses, instead of ‘true’ and ‘false’ So the following sensors highlighted in yellow are also being missed from matching in this generic alerting config: [cid:image004.png@01D064D1.B26D89D0] So I believe it’s a wider issue and not just related to this one device. Can someone confirm what I’m doing wrong and/or maybe check to see if your alerting configurations can match sensors which have an OK state of ‘normal’ instead of ‘true’? Cheers! Robert Williams Custodian Data Centre Email: Robert(a)CustodianDC.com http://www.CustodianDC.com

1 0

Down ports but can't see them
by Chard, Alex (RET-SYD) 20 Mar '15

20 Mar '15

Hi All, Got an interesting issue... Observium's dashboard shows 2 down ports [cid:image001.png@01D06344.0CB21DF0] But clicking on "2 down" takes me to a screen that shows no down ports: [cid:image002.png@01D06344.0CB21DF0] If I have any more than 2 down ports, they are displayed correctly. Any idea how I can identify the offending ports? Thanks, Alex This e-mail is for the use of the intended recipient(s) only. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's permission. We have taken precautions to minimise the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this e-mail. We cannot accept liability for any loss or damage caused by software viruses.

1 0

tons of rrd zombie processes + solution
by Gerwin Krist 19 Mar '15

19 Mar '15

Hi, FYI on PHP 5.5 we saw a lot of defunt rrdtool proceeses (1 for every image created in the browser). If you see this there are a couple of fixes/work-around: 1. Fix it in observium, open ./includes/rrdtool.inc.php and change *function rrdtool_pipe_close(&$rrd_process, &$rrd_pipes)* to *function rrdtool_pipe_close($rrd_process, &$rrd_pipes)* 2. downgrade to PHP 5.4 Seems to be caused by https://bugs.php.net/bug.php?id=69014 Regards, Gerwin Krist

2 1

Purchase support
by Dudu 19 Mar '15

19 Mar '15

Hi All. How can i buy support? I would like to finance and improve the product. Thanks David Sent from my Samsung Galaxy smartphone.

1 0

Alert emails not working
by Aurélien PERRODY 18 Mar '15

18 Mar '15

Hi, I recently bought the full version of Observium to get alerts system. So I migrated from the CE version to full version, no problem. I edited the config.php file as well: -------------------- // Enable alerter (not available in CE) $config['poller-wrapper']['alerter'] = TRUE; // Set up a default alerter (email to a single address) $config['alerts']['alerter']['default']['descr'] = "Default Email Alert"; $config['alerts']['alerter']['default']['type'] = "email"; $config['alerts']['alerter']['default']['contact'] = "xxx(a)xxx.com"; $config['alerts']['alerter']['default']['enable'] = TRUE; // Configuration email (APE 2015-03-12) $config['email']['backend']= 'smtp'; $config['email']['enable'] = TRUE; $config['email']['from'] = 'xxx(a)xxx.com'; $config['email']['default'] = 'xxx(a)xxx.com'; $config['email']['default_only'] = TRUE; $config['email']['smtp_host'] = '192.168.1.29'; $config['email']['smtp_port'] = 25; $config['email']['smtp_timeout']= 10; $config['email']['smtp_secure']= NULL; $config['email']['smtp_auth']= NULL; $config['email']['smtp_username'] = NULL; $config['email']['smtp_password'] = NULL; -------------------- When I check my configuration, it works, I received the email test, no problem. ------------------- root@MEDSRV15:/home/logs# /opt/observium/test_mail.php -h MEDHPV01 No log handling enabled - turning on stderr logging /etc/snmp/snmp.conf: line 6: Warning: Unknown token: rocommunity. Observium 0.15.3.6342 Test E-mail Configuration See mail backend options here: http://www.observium.org/wiki/Configuration_Options#Email_backend_settings My Hostname: MEDSRV15.xxxx.xxxxx E-mails ENABLED globally ($config['email']['enable']) E-mails use SMTP backend ($config['email']['backend']) smtp host: [192.168.1.29] smtp port: [25] smtp timeout: [10] smtp auth: [FALSE] E-mails send only to default email ($config['email']['default_only']) E-mails use these default recipient(s) ($config['email']['default']): xxxx(a)xxxxx.com E-mails send from ($config['email']['from']): xxxxx(a)xxxxxx.com E-mails send to recipients based on default recipient from config and/or device sysContact. Try send test notification for medhpv01 to these email(s): xxxxx(a)xxxxx.com EMAILING Notification for medhpv01 SENT. ------------------- Then I created a classic alert checker, when devices are down. -Conditions: device_status eq 0 -Device match * entity match * Alerts on the webpage works correctly, but I did not receive an alert email. So Y U NO WORK OBSERVIUM?? :) I read the wiki but don't see my pb... Many thanks for helping. My version information below: Observium 0.15.3.6342 OS Linux 3.2.0-4-amd64 [amd64] (Debian 7 (wheezy)) Apache 2.2.22 (Debian) PHP 5.4.35-0+deb7u2 MySQL 5.5.40-0+wheezy1 SNMP NET-SNMP 5.4.3 RRDtool 1.4.7 Regards, Aurélien

1 0

SVN error retreving REPORT
by Dash Brousseau 17 Mar '15

17 Mar '15

Can no longer download the full svn of observium ever since I upgrade to Ubuntu 14.10. I even did a fresh install and the same problem After around 70-80% I get svn: E000104:Error retrieving REPORT: connection reset by peer I then try to do svn cleanup I able to get a few more files Then it won’t go any further and I get the same error Anyone come across this? Dash This message contains information which may be confidential and privileged. Unless you are the intended addressee (or authorized to receive for the intended addressee), you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender by e-mail then delete the message immediately. Francais: http://www.fundserv.com/fr/company/disclaimer<http://www.fundserv.com/francais/legal/disclaimer_email_ib.shtml>

1 0

Alerting system patch
by Gert-Jan de Boer 16 Mar '15

16 Mar '15

Hi, A while ago I posted this patch to Jira, after some brief discussion I didn't hear back about it. I would like to add some more notification backends (for example Slack integration), is there any reason why this would not be accepted? The patch is under http://jira.observium.org/browse/OBSERVIUM-1194 Kind regards, GJ

1 0

Description not saved
by Asensio Sánchez, Juan 16 Mar '15

16 Mar '15

Hi We have installed Observium from SVN. When trying to edit a device a change (set) a description, that is not saved, I get a message "Device record unchanged. No update necessary." This happens with all devices. Any advice? Regards. Este correo electrónico y, en su caso, cualquier fichero anexo al mismo, contiene información de carácter confidencial exclusivamente dirigida a su destinatario o destinatarios. Si no es vd. el destinatario indicado, queda notificado que la lectura, utilización, divulgación y/o copia sin autorización está prohibida en virtud de la legislación vigente. En el caso de haber recibido este correo electrónico por error, se ruega notificar inmediatamente esta circunstancia mediante reenvío a la dirección electrónica del remitente. Evite imprimir este mensaje si no es estrictamente necesario. This email and any file attached to it (when applicable) contain(s) confidential information that is exclusively addressed to its recipient(s). If you are not the indicated recipient, you are informed that reading, using, disseminating and/or copying it without authorisation is forbidden in accordance with the legislation in effect. If you have received this email by mistake, please immediately notify the sender of the situation by resending it to their email address. Avoid printing this message if it is not absolutely necessary.

1 0