- observium - lists.observium.org

Issue with traffic volume graph for asymmetric interfaces.
by T-MONT Administrator 05 Nov '15

05 Nov '15

Hi guys, I have problem with graphing traffic graphs for one of my Observium monitored device; problem occurs when it comes to graph traffic for asymmetric interfaces - ones that only send or receive traffic. The problem is that when such interface is queried on the device for actual traffic values the response is: for only-sending interface: Rx OID -> noSuchInstance, TxOID -> actual bits for only-receiving interface: Rx OID -> actual bits, TxOID -> noSuchInstance Those values as used then to populate corresponding RRD file which results in series of "NaN"s for INOCTETS or OUTOCTETS data stores. The result is that traffic graph plotted from this RRD is corrupted - like this example: http://i66.tinypic.com/7281fo.png Currently my Observium instance is at revision 7167. Could you share with me any ideas how to resole this issue? Thank you & Regards! Pawel

2 5

QNAP IOPS Latency
by Simone Montagnani 05 Nov '15

05 Nov '15

Hi, is there any QNAP support to output graph of volume IOPS and Latency via Observium? Regards, Simone

3 3

F5 and Palo Alto firewall
by George Philip 04 Nov '15

04 Nov '15

Hi,Does Obserium provide support for F5 and Palo alto firewall as I don't see that getting discovered by the application ? Thanks,George

2 1

Observium ports stack
by Σταύρος Κρουστούρης 04 Nov '15

04 Nov '15

Hello, I have noticed that ports stack is missing some entries. As a result i cant find some relations between some physical and aggregated interfaces. Is this a known bug/misbehavior? Do you need some extra details? Thanks -- ----------------------------------------------------------------------- Stavros Kroustouris - staurosk(a)noc.grnet.gr GRNET NOC WEB APPLICATIONS DEVELOPER - http://noc.grnet.gr -----------------------------------------------------------------------

2 2

Re: [Observium] Dropout and graph problems in graphs.............!
by ron＠rjr-services.com 04 Nov '15

04 Nov '15

I'm monitoring a little over 600 devices with my installation. Likewise in a VM, 8x vCPU @3.0GHz, 32GB DRAM, and 32GB of swap. While CPU goes up to 85+% during polls, I don't have any drops whatsoever. Given what you describe, you probably want to add more memory to your VM. Also, what is your average and overall polling time? You may need to add additional polling instances so that everything completes within the 5min window before the next round of polling starts, which again means more memory will be very helpful. Sent from my Verizon Wireless 4G LTE smartphone -------- Original message -------- From: Chaman Rathee <chaman.rathee(a)progression.com> Date: 11/03/2015 9:37 PM (GMT-07:00) To: 'Observium Network Observation System' <observium(a)observium.org> Subject: [Observium] Dropout and graph problems in graphs.............! -- This message has been scanned by E.F.A. Project and is believed to be clean.

1 0

any update for OSPF alert trigger
by Samarasinghe, Sujith 03 Nov '15

03 Nov '15

Hi , This has been discussed in the past but not sure if I have missed updates. Is there a way to trigger OSPF alerts in Observium? Thanks, Sujith. Confidentiality Note: This e-mail and any attachments are confidential and may be protected by legal privilege. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of this e-mail or any attachment is prohibited. If you have received this e-mail in error, please notify us immediately by returning it to the sender and delete this copy from your system. Thank you for your cooperation.

1 0

dropout or gap over all graphs.
by Chaman Rathee 03 Nov '15

03 Nov '15

Hi Team, I got dropouts or gap over all my graphs. But there is no dropouts/gap for my localhost map. I also increase snmpget timeout to check but it doesn't work for me. ......... With Best Regards, Chaman Rathee Mob. No:- +91-9560055816 [Fabrikam] Privileged or confidential information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), please delete this message and kindly notify the sender by an emailed reply. Opinions, conclusions and other information in this message that do not relate to the official business of Progression and its associate entities shall be understood as neither given nor endorsed by them.

3 4

Default new ports to not alert?
by Spencer Ryan 03 Nov '15

03 Nov '15

We are considering adding some of our testbed Cisco devices to Observium, but we'd like all the ports to default to not alert, since they are constantly up and down, and vlans are created dynamically. Any way to do this in the config? *Spencer Ryan* | Senior Systems Administrator | sryan(a)arbor.net *Arbor Networks* +1.734.794.5033 (d) | +1.734.846.2053 (m) www.arbornetworks.com

1 0

P2P-Radio in Jira
by Eduardo Schoedler 03 Nov '15

03 Nov '15

Hi people, Recently I created tickets for our p2p-radios in Jira. I know it's not easy to do, but do you have idea when it will be available in the professional edition? Thank you. Regards, -- Eduardo Schoedler

1 0

Search pages broken?
by Tim Cooper 03 Nov '15

03 Nov '15

A colleague has just noticed that the ports and device search pages no longer search when you click the button? We have just upgraded to 7161 today, but not sure when it broke as it's been a while since anyone actually used the search page... We are working around this quite easily but seemed worth mentioning :) Thanks, Tim C

4 4

General pre-buy questions
by Ryan Milton 03 Nov '15

03 Nov '15

I am thinking of pushing team to purchase the full version, and even for some support. I have a free version now Questions I have are the following for my managers: 1. Can I alert off of bandwidth utilization? What other types of things can I alert off for the enterprise? 2. Can I alert for jitter across an MPLS? This is a biggie, because we have about 40 circuits. 3. We use WUG, which I hate… how is this better? 4. We use Solarwinds, which is expensive, why is this better? 5. (I know this is bad form, but) why these bars in the graph: Thanks for your awesome answers, and please, give me some reasons that I can use to get team to put money into this. Ryan Milton

3 4

CDR 98th accounting
by Niilo Kajander 03 Nov '15

03 Nov '15

Hi, I was wondering if there are any plans to add CDR 98th traffic accounting as an option? — Niilo Kajander nk(a)kajander.fi

2 2

Port () Deleted
by Matt Zillmann 03 Nov '15

03 Nov '15

Hello, When polling devices, all ports are getting deleted: "Port () deleted" Has anyone seen this or know how to fix this? Everything else is being discovered and polled normally. Thank you, Matt

2 2

Portnames instead of ifAlias for Fabric OS devices
by Ole Hansen 03 Nov '15

03 Nov '15

Hello, Observium (as of 0.15.9.6997) displays ifAlias / ifDescr as label for Brocade Fabric OS SAN switches. Brocade, however, uses “portnames”, which can be found at OID 1.3.6.1.4.1.1588.2.1.1.1.6.2.1.36 Is this per design or just because very few have Fabric OS devices in Observium? — Ole Hansen

2 4

Subscription fails
by Svensson Fredrik A 02 Nov '15

02 Nov '15

I get stuck here: [cid:image001.png@01D11559.9F0088A0] Regards Fredrik

2 2

Re: [Observium] EIGRP
by brokerdavelhr 01 Nov '15

01 Nov '15

ISIS is indeed the way to go....imho. Versatile, simple, reliable, and highly supported :-) Sent via the Samsung GALAXY S®4, an AT&T 4G LTE smartphone -------- Original message -------- From: Adam Armstrong <adama(a)memetic.org> Date: 11/01/2015 5:31 PM (GMT-07:00) To: observium(a)observium.org Subject: Re: [Observium] EIGRP IS-IS++ adam. On 02/11/2015 00:29:54, Raphael Maunier <raphael.maunier(a)gmail.com> wrote:The original question and answer was not about the igp itself but about the support of it ! He want to move from OSPF to Eigrp and still get the same support from an opensource software. That was clearly the answer : You can expect to have bad or no support using EIGRPChoosing the path to use a protocol that is clearly not supported by all vendor, will almost 100% of the time lead you to a lack of compatibility from the community. And Yes IS-IS is the way go :) Raphael On 02 Nov 2015, at 01:15, Aaron Finney <aaron.finney(a)openx.com> wrote: I would argue that IS-IS also separates the men from the boys, is an open standard, and also happens to be protocol-neutral. I have my own opinions about IGPs, of course, but I agree with Alex on this one...nobody asked for my opinion on using EIGRP, so I'll save it until they do. :) On Sunday, November 1, 2015, Ron Marosko <ron(a)rjr-services.com> wrote: I probably bleed Cisco more than most on this list, something about that two day test 16 years ago. I’ll just say one thing about routing protocols. BGP. Yes, it *is* as good running as an IGP as it is as an EGP. And separates the men from the boys, so to speak. From: observium [mailto:observium-bounces@observium.org] On Behalf Of Raphael Maunier Sent: Sunday, November 01, 2015 4:47 PM To: Observium Network Observation System Subject: Re: [Observium] EIGRP If you want good support from any software, you should not use "proprietary" protocols and use something supported by more than one or 2 vendor.Another option, use it and buy expensive software from that vendor. Envoyé de mon iPhone Le 1 nov. 2015 à 23:37, Chard, Alex (RET-SYD) <Alex.Chard(a)Reed-Elsevier.com.au> a écrit :Perhaps we would do better not to tell people how to run their network…We do not know anything about the network in question beyond the fact that it is probably monitored with Observium. Also Cisco released basic EIGRP functionality for other vendors to implement in a RFC.http://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/enh… So the real question is not “why?” but “is this supported in Observium?”.. and the real answer is “no”. Regards,Alex Chard Senior Network Engineer<image001.jpg> 475 Victoria Ave, Chatswood, NSW 2067 (: +61 (02) 8007 0709 <image002.gif>: +61 (04) 03 894 614*: alex.chard(a)reed-elsevier.com.au www.reedelsevier.com From: observium [mailto:observium-bounces@observium.org] On Behalf Of Raphael Maunier Sent: Monday, 2 November 2015 4:07 AM To: Observium Network Observation System Subject: Re: [Observium] EIGRP HuH, The real question is Why ? Ospf can be used with all vendor, eigrp .. not compatible unless you have a cisco network and other clone equipment.Ospf is widely supported and even with software like Observium. You can expect to have bad or no support using EIGRP 2015-11-01 17:45 GMT+01:00 Jason Vanlandingham <van.sjason(a)gmail.com>:I've been running OSPF but am changing to EIGRP. EIGRP isn't showing in the routing section when I look at devices. _______________________________________________ observium mailing list observium(a)observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium 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. _______________________________________________ observium mailing list observium(a)observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/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 Facebook LinkedIn _______________________________________________ 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

Graph errors on OS upgrade
by Roland Hill 01 Nov '15

01 Nov '15

Hi list, I'm running CE version 0.15.6.6430, on my non-critical home network. I recently upgraded my server OS from Ubuntu 15.04 to 15.10. This appears to have resulted in some of the graphs in Observium now not drawing. The OS upgraded took rrdtools from version 1.4.8 to 1.5.4, and I suspect this is the root of the issue as I seem to remember this being raised on the list before. I note there was a bugfix committed in August for "Fixed some issues with rrdtool command parsing on newer rrdtool versions". Can you confirm that the draw error's I'm seeing are most likely related to the rrdtool version, and that the next release of CE will probably fix it? An example of the rrdtool error is: RRDTool Output: ERROR: Unused Arguments "" in command : AREA:inbits0#B6D14B:p3p1 Rx: Sorry if this is not enough information. I can provide screenshots if required. -- Regards, Roland PGP Key 0xDA39319B = BCF0 1214 BAE9 5A3D 46FC 21A6 360D 9398 DA39 319B

2 1

Unable to send email from Observium CE
by George Philip 01 Nov '15

01 Nov '15

Hi, I have installed the Observium CE on the centOS and the mail is not working for me.Can someone please in finding the issue ? Below are the mail config info from config.php : // Set up a default alerter (email to a single address) $config['alerts']['alerter']['default']['descr'] = "Network Alert"; $config['alerts']['alerter']['default']['type'] = "mail"; $config['alerts']['alerter']['default']['contact'] = "network1_alert(a)abc.com"; $config['alerts']['alerter']['default']['enable'] = TRUE; $config['email']['enable'] = TRUE; $config['email']['default'] = "network1_alert(a)abc.com"; $config['email']['default_only'] = TRUE; $config['email']['from'] = "Observium<observium(a)abrrad100.abc.com>"; $config['email']['backend'] = 'mail'; $config['email']['smtp_host'] = 'abrsmtp1001.abc.com'; $config['email']['smtp_port'] = 25; $config['email']['smtp_timeout'] = 20; $config['email']['smtp_secure'] = FALSE; $config['email']['smtp_auth'] = FALSE; $config['email']['smtp_username'] = NULL; $config['email']['smtp_password'] = NULL; $config['email']['sendmail_path'] = '/usr/sbin/sendmail'; Also,when I run the below command, I get the following error: [root@abrrad1001 observium]# php test_mail.php -h abcd.tor.fd01.01.01.42PHP Fatal error: Call to undefined function mres() in /opt/observium/test_mail.php on line 41 Thanks,George

2 1

IP SLA Cisco not repoerted
by Federico Olivieri 31 Oct '15

31 Oct '15

Hi All, I have just enabled IP SLA on my cisco router but I don't see any graph in my OBSERVIUM. There is any particular procedure that I have to follow? snmp-server enable traps ipsla Thanks Federico

3 4

NetApp OnTap 8 OIDs
by Daniel Steig 31 Oct '15

31 Oct '15

Hi at all, does anyone by chance came any further by finding the new OIDs to monitor the netapps Disk I/O. I tried my best but can't get the graphs working. Thank you very much in advance and have a nice day, Daniel Daniel Steig System Engineer URL: www.fyber.com -- *Daniel Steig* System Engineer Skype: d.steig-fyber URL: www.fyber.com

1 0

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 28 Oct '15

28 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 28 Oct '15

28 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