- observium - lists.observium.org

Does observium support F5 and Palo Alto firewall
by George Philip 30 Oct '15

30 Oct '15

Hi,Does observium monitor (or have mibs) for Palo Alto firewall and F5's ? Thanks,George

1 0

LLDP issues
by Mark Martinec 30 Oct '15

30 Oct '15

Spent some time trying to get Observium to deal with MIBs as produced by LLDP (Link Layer Discovery Protocol) on a couple of diverse network equipment types. Running the latest CE edition 0.15.6.6430. After initial meager success (only two boxes recognized and several L2 neighbours reported with wrong interfaces), a couple of changes in includes/discovery/discovery-protocols/lldp-mib.inc.php brought some sense into results. There are essentially two problems there: - some lldpRemoteSystemsData OIDs could not be correlated with an interface on the other side (for various reasons, see below); - a fallback mechanism which tries to find a match on an interface's MAC address produces a wrong match, because typically all ports on larger switches have the same MAC address and the heuristics just picks the first match, which is almost always wrong. In case of multiple matches the matching on MAC should just fail, which at least would not produce a senseless match causing operators to scratch their heads and wonder who crossed the cables. The comment in lldp-mib.inc.php : // Find the device by MAC address, still matches multiple ports sometimes, we use the first one and hope we're lucky if very much misguided, as all port MAC addresses on a switch are typically the same, at least on all device types that I checked. The first issue above needs more explanation. I found a couple of different reasons for a failed match, as follows. Case 1: $ snmpbulkwalk -v2c -c ... -M mibs -m LLDP-MIB ... lldpRemoteSystemsData LLDP-MIB::lldpRemChassisIdSubtype.5360466.52.2 = INTEGER: macAddress(4) LLDP-MIB::lldpRemChassisId.5360466.52.2 = Hex-STRING: C4 54 44 1E 71 4E LLDP-MIB::lldpRemPortIdSubtype.5360466.52.2 = INTEGER: local(7) LLDP-MIB::lldpRemPortId.5360466.52.2 = Hex-STRING: 30 2F 34 37 00 LLDP-MIB::lldpRemPortDesc.5360466.52.2 = STRING: "Slot: 0 Port: 47 10G - Level" LLDP-MIB::lldpRemSysName.5360466.52.2 = STRING: "<hidden>" LLDP-MIB::lldpRemSysDesc.5360466.52.2 = STRING: "T3048-LY2R L2/L3 Switch" LLDP-MIB::lldpRemSysCapSupported.5360466.52.2 = BITS: 28 00 bridge(2) router(4) LLDP-MIB::lldpRemSysCapEnabled.5360466.52.2 = BITS: 20 00 bridge(2) LLDP-MIB::lldpRemManAddrIfSubtype.5360466.52.2.6.6.196.84.68.30.113.78 = INTEGER: ifIndex(2) LLDP-MIB::lldpRemManAddrIfId.5360466.52.2.6.6.196.84.68.30.113.78 = INTEGER: 69 LLDP-MIB::lldpRemManAddrOID.5360466.52.2.6.6.196.84.68.30.113.78 = OID: iso.3.6.1.4.1.7244 LLDP-MIB::lldpRemOrgDefInfo.5360466.52.2.0.18.15.1.1 = Hex-STRING: 01 00 00 00 24 LLDP-MIB::lldpRemOrgDefInfo.5360466.52.2.0.18.15.2.1 = Hex-STRING: 00 00 00 LLDP-MIB::lldpRemOrgDefInfo.5360466.52.2.0.18.15.3.1 = Hex-STRING: 01 00 00 00 00 LLDP-MIB::lldpRemOrgDefInfo.5360466.52.2.0.18.15.4.1 = Hex-STRING: 23 F2 LLDP-MIB::lldpRemOrgDefInfo.5360466.52.2.0.128.194.1.1 = Hex-STRING: 00 01 LLDP-MIB::lldpRemOrgDefInfo.5360466.52.2.0.128.194.2.1 = Hex-STRING: 02 00 00 LLDP-MIB::lldpRemOrgDefInfo.5360466.52.2.0.128.194.3.1 = Hex-STRING: 00 01 00 Case 2: LLDP-MIB::lldpRemChassisIdSubtype.9511080.4.5 = INTEGER: macAddress(4) LLDP-MIB::lldpRemChassisIdSubtype.9511149.2.6 = INTEGER: macAddress(4) LLDP-MIB::lldpRemChassisIdSubtype.9511174.3.7 = INTEGER: macAddress(4) LLDP-MIB::lldpRemChassisIdSubtype.9511209.26.8 = INTEGER: macAddress(4) LLDP-MIB::lldpRemChassisIdSubtype.9587238.48.9 = INTEGER: macAddress(4) LLDP-MIB::lldpRemChassisIdSubtype.9588774.27.10 = INTEGER: macAddress(4) LLDP-MIB::lldpRemChassisIdSubtype.9588907.28.11 = INTEGER: macAddress(4) LLDP-MIB::lldpRemChassisIdSubtype.9592381.42.12 = INTEGER: macAddress(4) LLDP-MIB::lldpRemChassisIdSubtype.9827133.8.14 = INTEGER: macAddress(4) LLDP-MIB::lldpRemChassisIdSubtype.9843364.9.16 = INTEGER: macAddress(4) LLDP-MIB::lldpRemChassisId.9511080.4.5 = Hex-STRING: 00 04 96 34 CB 7D LLDP-MIB::lldpRemChassisId.9511149.2.6 = Hex-STRING: 00 04 96 34 CB 78 LLDP-MIB::lldpRemChassisId.9511174.3.7 = Hex-STRING: 00 04 96 34 CB 8D LLDP-MIB::lldpRemChassisId.9511209.26.8 = Hex-STRING: 00 04 96 34 CB 93 LLDP-MIB::lldpRemChassisId.9587238.48.9 = Hex-STRING: A4 8C DB 0C 4B 00 LLDP-MIB::lldpRemChassisId.9588774.27.10 = Hex-STRING: 00 04 96 34 CB 7F LLDP-MIB::lldpRemChassisId.9588907.28.11 = Hex-STRING: 00 04 96 34 CB 8B LLDP-MIB::lldpRemChassisId.9592381.42.12 = Hex-STRING: 44 AD D9 6C 2D 80 LLDP-MIB::lldpRemChassisId.9827133.8.14 = Hex-STRING: C4 54 44 1E 71 4E LLDP-MIB::lldpRemChassisId.9843364.9.16 = Hex-STRING: 2C 60 0C 33 8F FF LLDP-MIB::lldpRemPortIdSubtype.9511080.4.5 = INTEGER: interfaceName(5) LLDP-MIB::lldpRemPortIdSubtype.9511149.2.6 = INTEGER: interfaceName(5) LLDP-MIB::lldpRemPortIdSubtype.9511174.3.7 = INTEGER: interfaceName(5) LLDP-MIB::lldpRemPortIdSubtype.9511209.26.8 = INTEGER: interfaceName(5) LLDP-MIB::lldpRemPortIdSubtype.9587238.48.9 = INTEGER: local(7) LLDP-MIB::lldpRemPortIdSubtype.9588774.27.10 = INTEGER: interfaceName(5) LLDP-MIB::lldpRemPortIdSubtype.9588907.28.11 = INTEGER: interfaceName(5) LLDP-MIB::lldpRemPortIdSubtype.9592381.42.12 = INTEGER: interfaceName(5) LLDP-MIB::lldpRemPortIdSubtype.9827133.8.14 = INTEGER: interfaceAlias(1) LLDP-MIB::lldpRemPortIdSubtype.9843364.9.16 = INTEGER: interfaceAlias(1) LLDP-MIB::lldpRemPortId.9511080.4.5 = STRING: "25" LLDP-MIB::lldpRemPortId.9511149.2.6 = STRING: "25" LLDP-MIB::lldpRemPortId.9511174.3.7 = STRING: "25" LLDP-MIB::lldpRemPortId.9511209.26.8 = STRING: "25" LLDP-MIB::lldpRemPortId.9587238.48.9 = STRING: "50" LLDP-MIB::lldpRemPortId.9588774.27.10 = STRING: "26" LLDP-MIB::lldpRemPortId.9588907.28.11 = STRING: "26" LLDP-MIB::lldpRemPortId.9592381.42.12 = STRING: "Te1/1/2" LLDP-MIB::lldpRemPortId.9827133.8.14 = Hex-STRING: 4C 69 6E 6B 20 74 6F 20 43 4D 49 2C 20 6E 65 75 68 75 62 00 LLDP-MIB::lldpRemPortId.9843364.9.16 = Hex-STRING: 55 70 6C 69 6E 6B 20 74 6F 20 49 4A 53 2D 4E 45 54 00 LLDP-MIB::lldpRemPortDesc.9511080.4.5 = STRING: LLDP-MIB::lldpRemPortDesc.9511149.2.6 = STRING: LLDP-MIB::lldpRemPortDesc.9511174.3.7 = STRING: LLDP-MIB::lldpRemPortDesc.9511209.26.8 = STRING: LLDP-MIB::lldpRemPortDesc.9587238.48.9 = STRING: XGE2 LLDP-MIB::lldpRemPortDesc.9588774.27.10 = STRING: LLDP-MIB::lldpRemPortDesc.9588907.28.11 = STRING: LLDP-MIB::lldpRemPortDesc.9592381.42.12 = STRING: TenGigabitEthernet1/1/2 LLDP-MIB::lldpRemPortDesc.9827133.8.14 = STRING: Slot: 0 Port: 48 10G - Level LLDP-MIB::lldpRemPortDesc.9843364.9.16 = STRING: Slot: 0 Port: 48 10G - Level LLDP-MIB::lldpRemSysName.9511080.4.5 = STRING: <hidden1>.ijs.si LLDP-MIB::lldpRemSysName.9511149.2.6 = STRING: <hidden2>.ijs.si LLDP-MIB::lldpRemSysName.9511174.3.7 = STRING: <hidden3>.ijs.si LLDP-MIB::lldpRemSysName.9511209.26.8 = STRING: <hidden4>.ijs.si LLDP-MIB::lldpRemSysName.9587238.48.9 = STRING: <hidden5> LLDP-MIB::lldpRemSysName.9588774.27.10 = STRING: <hidden6> LLDP-MIB::lldpRemSysName.9588907.28.11 = STRING: <hidden7> LLDP-MIB::lldpRemSysName.9592381.42.12 = STRING: <hidden8> LLDP-MIB::lldpRemSysName.9827133.8.14 = STRING: <hidden9> LLDP-MIB::lldpRemSysName.9843364.9.16 = STRING: <hidden10> LLDP-MIB::lldpRemSysDesc.9511080.4.5 = STRING: ExtremeXOS (X450a-24t) ... LLDP-MIB::lldpRemSysDesc.9511149.2.6 = STRING: ExtremeXOS (X450a-24t) ... LLDP-MIB::lldpRemSysDesc.9511174.3.7 = STRING: ExtremeXOS (X450a-24t) ... LLDP-MIB::lldpRemSysDesc.9511209.26.8 = STRING: ExtremeXOS (X450a-24t) ... LLDP-MIB::lldpRemSysDesc.9587238.48.9 = STRING: Networking Operating System RackSwitch G7052, IBM Networking OS: version 7.6.5, Boot image: version 7.6.5 LLDP-MIB::lldpRemSysDesc.9588774.27.10 = STRING: ExtremeXOS (X450a-24t) ... LLDP-MIB::lldpRemSysDesc.9588907.28.11 = STRING: ExtremeXOS (X450a-24t) ... LLDP-MIB::lldpRemSysDesc.9592381.42.12 = STRING: Cisco IOS Software, Catalyst L3 Switch Software... LLDP-MIB::lldpRemSysDesc.9827133.8.14 = STRING: T3048-LY2R L2/L3 Switch LLDP-MIB::lldpRemSysDesc.9843364.9.16 = STRING: T3048-LY2R L2/L3 Switch [...] In both cases 1 & 2 the lldpRemPortIdSubtype of 'interfaceAlias' and 'local' fell under the "default:" branch of a "switch ($lldp['lldpRemPortIdSubtype'])", instead of being treated just like a "case 'interfaceName':" branch. So my solution was to add "case 'interfaceAlias':" and "case 'local':" there; switch ($lldp['lldpRemPortIdSubtype']) { case 'interfaceName': + case 'interfaceAlias': + case 'local': A Case 3 is a bit nastier and is specific to our Summit Extreme X450a switches. The problem there is that the interface name (i.e. a port number) as reported in the LLDP MIB does not use the same naming/numbering convention as the IF-MIB and SQL: the LLDP MIB just uses a port number (1 .. 26), while the SQL field ports.ifName prefixes a port number with a chassis number, which is always a 1 in a non-stackable switch. Moreover the ifIndex uses a formula 1000*chassis + port number. On top of it the PortDesc in LLDP MIB is an empty string, so cannot be used to correlate with IF-MIB::ifDescr. To illustrate: IF-MIB::ifIndex.1001 = INTEGER: 1001 IF-MIB::ifIndex.1002 = INTEGER: 1002 IF-MIB::ifIndex.1003 = INTEGER: 1003 [...] IF-MIB::ifIndex.1026 = INTEGER: 1026 IF-MIB::ifDescr.1001 = STRING: X450a-24t Port 1 IF-MIB::ifDescr.1002 = STRING: X450a-24t Port 2 IF-MIB::ifDescr.1003 = STRING: X450a-24t Port 3 [...] IF-MIB::ifDescr.1026 = STRING: X450a-24t Port 26 LLDP-MIB::lldpLocPortIdSubtype.1 = INTEGER: interfaceName(5) LLDP-MIB::lldpLocPortIdSubtype.2 = INTEGER: interfaceName(5) LLDP-MIB::lldpLocPortIdSubtype.3 = INTEGER: interfaceName(5) [...] LLDP-MIB::lldpLocPortId.1 = STRING: "1" LLDP-MIB::lldpLocPortId.2 = STRING: "2" LLDP-MIB::lldpLocPortId.3 = STRING: "3" [...] LLDP-MIB::lldpLocPortId.26 = STRING: "26" LLDP-MIB::lldpLocPortDesc.1 = STRING: LLDP-MIB::lldpLocPortDesc.2 = STRING: LLDP-MIB::lldpLocPortDesc.3 = STRING: [...] LLDP-MIB::lldpLocPortDesc.26 = STRING: The corresponding SQL field ports.ifName looks like "1:26", i.e. the port number is prefixed by a chassis number and a colon. So neither the SQL query on ifDescr ("") OR ifName ("26") can succeed, nor the query on ifIndex ("1026"). I ended up with a hackish workaround kludge in lldp-mib.inc.php : case 'interfaceName': $remote_port_id = dbFetchCell("SELECT `port_id` FROM `ports` WHERE (`ifDescr`= ? OR `ifName`= ?) AND `device_id` = ?",array($if, $id, $remote_device_id)); + if (!$remote_port_id && is_numeric($id) && $id < 1000) { + $remote_port_id = dbFetchCell("SELECT `port_id` FROM `ports` WHERE (`ifIndex`= ? OR `ifName`= ?) AND `device_id` = ?", array(1000+$id, "1:$id", $remote_device_id)); + } Actually there is also a Case 4, where lldpRemSysName shows a string "(none).(none)" instead of an empty string, when the (optional) system name is not configured. To fix: - if (empty($lldp['lldpRemSysName']) && $lldp['lldpRemChassisIdSubtype'] == 'macAddress') + if ((empty($lldp['lldpRemSysName']) || $lldp['lldpRemSysName'] == '(none).(none)') && $lldp['lldpRemChassisIdSubtype'] == 'macAddress') The affected devices were: Summit Extreme X450 switches (Case #3), a Quanta LY2R switch (the 'interfaceAlias' Case #2), and a Networking Operating System RackSwitch G7052 (the 'local', Case #1). Not sure what switch was connected there in Case 4, possibly a smaller Quanta, identifies as "armv5tejl/Linux 2.6.17.WB_WPCM450.1.3". The full patch is attached (I hope it survives the mailing list). If more information is needed I'd be gladly providing. Regards Mark

3 5

Support for these devices ?
by Jesper Frank Nemholt 29 Oct '15

29 Oct '15

Hi! Has anyone a status regarding support for these devices ? - Liebert MPX PDUs - ServerTech Sentry PDUs - Raritan PX2 PDUs In version 0.15.10.7107 they are just seen as generic devices, so no power specific information. /Jesper

3 5

Baytech PDU patch
by Aaron Finney 29 Oct '15

29 Oct '15

Hi all, Attached is a diff and related files to include support for Baytech PDUs. It was just an archaeology job on some of the other existing PDU discover/sensor files modified for the Baytechs, but it's working well for us. It'd be great to have it merged, or at least Baytech support added, so I can update without worrying about support for them being lost. :) Thanks, Aaron [someguy@observium-poc observium]# svn status ? html/images/os/baytech.png M includes/definitions/os.inc.php ? includes/discovery/os/baytech.inc.php ? includes/discovery/sensors/baytech-mib.inc.php ? includes/polling/os/baytech-pdu.inc.php ? mibs/baytech [someguy@observium-poc observium]# svn diff Index: includes/definitions/os.inc.php =================================================================== --- includes/definitions/os.inc.php (revision 6977) +++ includes/definitions/os.inc.php (working copy) @@ -3385,6 +3385,19 @@ $config['os'][$os]['mib_dirs'][] = "fiberroad"; $config['os'][$os]['mibs'][] = "XXX-MIB"; +// Baytech + +$os = "baytech-pdu"; +$config['os'][$os]['text'] = "Baytech PDU"; +$config['os'][$os]['type'] = "power"; +$config['os'][$os]['vendor'] = "Baytech"; +$config['os'][$os]['graphs'][] = "device_current"; +$config['os'][$os]['graphs'][] = "device_power"; +$config['os'][$os]['discovery_os'] = "baytech"; +$config['os'][$os]['mib_dirs'][] = "baytech"; +$config['os'][$os]['mibs'][] = "Baytech-MIB"; + + foreach ($config['os'] as $this_os => $blah) { if (isset($config['os'][$this_os]['group'])) [someguy@observium-poc observium]# -- *Aaron Finney | **Network Engineer* 888 East Walnut Street, 2nd Floor | Pasadena, CA 91101 office: +1 (626) 466-1141 x6035 Watch how we make online advertising simple: http://bit.ly/Ent_vid www.openx.com | follow us on: Twitter <http://www.twitter.com/> Facebook <http://www.facebook.com/> LinkedIn <http://www.linkedin.com/>

2 2

Fwd: Custom Email Alerts
by consultancy＠lenstewart.com 28 Oct '15

28 Oct '15

Begin forwarded message: > From: "consultancy(a)lenstewart.com" <consultancy(a)lenstewart.com> > Date: 28 October 2015 at 15:55:57 GMT+1 > To: observium(a)observium.net > Subject: Custom Email Alerts > > Hello community. > > I am looking to customize the email alerts to contain specific detail that are not there by default. > > Specifically regarding BGP alerting, I need the system to push out additional peer info such as a peer name (not only an IP). Is there a way to support this either directly or via a script with a lookup? > > Thanks.

1 0

Observium Alert to Nagios
by consultancy＠lenstewart.com 28 Oct '15

28 Oct '15

Hello Community. Can alerts be somehow integrated with Nagios? Either by SNMP or script? Our NOCs primary interface is Nagios/CheckMK. Thanks.

1 0

Flush process causing slow performace
by Johnson, Edward A. 27 Oct '15

27 Oct '15

Since upgrading PHP to 5.4, Observium has loaded very slowly at times. Most of the time just a refresh of the homepage will take .150 seconds but occasionally it can take up to a minute to load. Running iotop shows the Flush process running taking up 99.99% IO which directly correlates to the slow page loads. Can anyone shed some light on a way to resolve this?

3 7

Log Names of non discoverable Host in autodiscover
by Serge Müller 26 Oct '15

26 Oct '15

Hi, is there any way to find out which host have been found through autodiscovery but could not be queried by snmp or aren't reachable via ICMP? Since we have lots of people working on our network, i do not always know if someone plugs in new switches or routers, especially not if they forget to configure the acls or snmp. The Observium log only shows "added x Hosts to ..." but no failures, running discovery.php -d -h all is a bit too loud and takes quite to long. Any suggestions? regards Serge

2 1

SNMP extensions : distro ... and others ?
by Massimo.Sala＠asl.bergamo.it 24 Oct '15

24 Oct '15

hi ! On the linux guests, you can tweak the snmpd.conf as extend .1.3.6.1.4.1.2021.7890.1 distro "/bin/cat /etc/debian_version" so Observium detects the host OS. Is it possible to set other "devices" values, like purpose and serial, via SNMP extensions ? It seems these columns aren't used. best regards, Sala

2 1

BGP Alert Checks
by Aaron Hite 23 Oct '15

23 Oct '15

Team, I need some guidance. I have spent some time on the web trying to find examples of how to configure a alert checker to tell me when a BGP peer is Admin up but not working. We have quite a few peers in our environment that are Admin down and I just want to ignore those. I have tried many variations of the checker, but must be missing something. Here is a screenshot of the latest attempt. My device and entity match are set to “*”. If I change the condition or any instead of all, I seem to get alerts that are not correct as they are including peer states that are admin down. Any guidance would be appreciated. Thanks, Aaron

3 6