- observium - lists.observium.org

Cisco subinterfaces
by Mirditor Kuçaj 28 Sep '16

28 Sep '16

Hello Lost the graphs on subinterfaces and portchannels. We rebooted a 7604 with IOS 15.4(3)S2 and monitored with Observium 0.16.9.8104. Somehow the graphs ID-are changed and doesnt belong to the same subinterface/portchannel. Thx Mirditor Kuçaj Backbone miri(a)abissnet.al <mailto:miri@abissnet.al> Abissnet Sh.a. +355 69 60 91 364 +355 (0)44 300 003 Ext 139 Rr. Ismail Qemali, Pallati Abissnet, Tiranë <http://www.abissnet.al/> www.abissnet.al <https://www.facebook.com/Abissnet> <https://plus.google.com/u/0/+AbissnetalISP> <https://www.linkedin.com/profile/view?id=AAIAABqLWRAB88ljU6t8b67oVm8PAlvPrh mPybE&trk=nav_responsive_tab_profile%20>

2 1

Re: [Observium] Cisco subinterfaces
by ron＠rjr-services.com 28 Sep '16

28 Sep '16

Please review this Cisco document regarding interface persistence. This is likely the issue you are seeing, not a problem with Observium itself. http://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-prot… There is a command you can include in your configuration that will keep interface numbering persistent across reboots. I just don't recall it exactly off the top of my head, or I would include it here. ... Ron Get Outlook for Android On Wed, Sep 28, 2016 at 7:34 AM -0500, "Mirditor Kuçaj" <miri(a)abissnet.al> wrote: -- This message has been scanned by E.F.A. Project and is believed to be clean.

1 0

Trunk Issues
by Talk Jesus 28 Sep '16

28 Sep '16

I've been using Observium for a while and there seems to be some discrepancies between my graphs and the upstream (my data center provides me Ethernet GigE bandwidth). For example, from around 8am to 12pm today it showed overall utilization pretty consistent well above 400Mbps. I have two drops from them: primary and secondary (redundant). Plus, they both show active instead of active/passive. Not sure if that has anything to do with it. >From the tech: "95th percentile is calculated from both ingress and egress traffic. For example, if you used a constant 200Mbps up and down, then you would only be charged your commit of 200Mbps, not double. I do see what you mean that the two handoffs (layer 2) are equaling more than 300Mbps, but when you look at the Aggregate (layer 3) graph at the top, it does not go over 300Mbps. These packets can possibly be queued before going out so you don’t go over your commit. " So, what do you think might be causing this hiccup? I noticed this too: so these switches are actually trunked (2 x 3650 L3 switches). In the graph, it also shows the uplink connectivity calculated with the total utilization. This is definitely not accurate as it shouldn't do that. Example: Drop #1 = 40Mbps Drop #2 = 200Mbps Uplink to Switch #2 = 130Mbps Now as a result VLAN2155 (total utilization) is calculating not only #1 and #2 drops from the upstream, but even the trunk port labeled "Uplink to Switch #2". How can I rectify this with Observium to avoid that and get an accurate output?

5 11

Can't Add Device
by Talk Jesus 28 Sep '16

28 Sep '16

Trying to add my secondary trunked switch, but I get this error "Could not ping switch2.mydomain.com." I ran a DNS lookup on that hostname and it shows the records fine and the switch (#2) accurately. I tried adding the device using the same setup as the original switch that's already there: port 161, udp transport, v2c protocol version, snmp community same as primary. I can ping the hostname too, not sure why Observium cannot.

2 5

False positives on Device Alerts
by Timothy Kaufman 27 Sep '16

27 Sep '16

We have an SE installation with about 260 devices being checked. We have alerting setup for various services or checks. Often we see false positives on the SNMP device down alert, for example devices will report SNMP down when they are not really down. After a second or even third SNMP check we see a recovery and the uptime shows no outage. I also verify this by doing and snmpwalk from observium while the “alert” is active. Is there anything we can check or begin to look to find the cause. The server is not overloaded, with either memory or processor. We are running 25 poller wrappers with a complete polling time of about 300 seconds. Thanks, Tim

4 5

Poll Observium Agent using TLS
by Matthias Gabathuler 27 Sep '16

27 Sep '16

1 0

Observium with smokeping and rrdcached
by Lyndon Labuschagne 27 Sep '16

27 Sep '16

Hi is it possibly to get smokeping integrated with Observium if you are using rrdcached? I get permissions issues, but id I disable rrdcache then I can see the smokeping graphing?

1 0

Re: [Observium] Sensors auto-deleted and re-added.
by Henrik Cednert (Filmlance) 27 Sep '16

27 Sep '16

And now it have started to do it frequently. =( Never had this issue before. Anyone with a clue to why it’s happening? 2016-09-24 06:40:58 netbotz01 Sensor deleted: humidity apc memSensorsHumidity.0.4 Temp/humid 2016-09-24 06:40:58 netbotz01 Sensor deleted: temperature apc memSensorsTemperature.0.4 Temp/humid 2016-09-24 06:40:53 netbotz01 Temp/humid Sensor added: temperature apc emsProbeStatusProbeTemperature.4 Temp/humid 2016-09-24 06:40:53 netbotz01 Temp/humid Sensor added: humidity apc emsProbeStatusProbeHumidity.4 Temp/humid 2016-09-24 00:37:49 netbotz01 Sensor deleted: humidity apc emsProbeStatusProbeHumidity.4 Temp/humid 2016-09-24 00:37:49 netbotz01 Sensor deleted: temperature apc emsProbeStatusProbeTemperature.4 Temp/humid 2016-09-24 00:37:45 netbotz01 Sensor added: humidity apc memSensorsHumidity.0.4 Temp/humid 2016-09-24 00:37:45 netbotz01 Sensor added: temperature apc memSensorsTemperature.0.4 Temp/humid 2016-09-23 18:38:05 netbotz01 Sensor updated (limits): limit_low -> "0" 2016-09-23 12:40:44 netbotz01 Sensor deleted: humidity apc memSensorsHumidity.0.4 Temp/humid 2016-09-23 12:40:44 netbotz01 Sensor deleted: temperature apc memSensorsTemperature.0.4 Temp/humid 2016-09-23 12:40:40 netbotz01 Sensor added: temperature apc emsProbeStatusProbeTemperature.4 Temp/humid 2016-09-23 12:40:40 netbotz01 Sensor added: humidity apc emsProbeStatusProbeHumidity.4 Temp/humid 2016-09-23 06:38:32 netbotz01 Sensor deleted: humidity apc emsProbeStatusProbeHumidity.4 Temp/humid 2016-09-23 06:38:32 netbotz01 Sensor deleted: temperature apc emsProbeStatusProbeTemperature.4 Temp/humid 2016-09-23 06:38:28 netbotz01 Sensor added: humidity apc memSensorsHumidity.0.4 Temp/humid 2016-09-23 06:38:28 netbotz01 Sensor added: temperature apc memSensorsTemperature.0.4 Temp/humid -- Henrik Cednert cto | compositor Filmlance International | www.filmlance.se mobile [ + 46 (0)704 71 89 54 ] skype [ cednert ] On 2016-09-21, 14:05, "observium on behalf of Henrik Cednert (Filmlance)" <observium-bounces(a)observium.org on behalf of henrik.cednert(a)filmlance.se> wrote: Hey Anyone with an idea to why this would happen on its own? 2016-09-21 12:38:54 Sensor deleted: humidity apc emsProbeStatusProbeHumidity.4 Temp/humid 2016-09-21 12:38:54 Sensor deleted: temperature apc emsProbeStatusProbeTemperature.4 Temp/humid 2016-09-21 12:37:58 Temp/humid Sensor added: humidity apc memSensorsHumidity.0.4 Temp/humid 2016-09-21 12:37:58 Temp/humid Sensor added: temperature apc memSensorsTemperature.0.4 Temp/humid An APC/Schneider Netbotz200. Cheers -- Henrik Cednert cto | compositor Filmlance International | www.filmlance.se mobile [ + 46 (0)704 71 89 54 ] skype [ cednert ] _______________________________________________ observium mailing list observium(a)observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

2 2

No devices found
by Skelkelos 25 Sep '16

25 Sep '16

Hi, I am having an issue with latest Observium release 0.16.9.8086 (9th September 2016), after updating to latest revision the discovery/polling is still working fine according to logs, however the web interface shows 'No devices found' and can't access any data. Any hints on how to solve this issue or investigate further ? Resetting the search parameters doesn't help. Best regards, Alessandro

2 5

Disabled devices showing on front page
by Ben Hohnke 25 Sep '16

25 Sep '16

Hi Guys, We updated our observium installation yesterday, and since then we're getting alerts (from the alert module) and front page alerts for devices that are disabled. The version we're running is 0.16.9.8092 (rolling). I really don't want to delete these devices, as the historical data is useful.. [image: pasted1]

3 3