- observium - lists.observium.org

Stuck alerts for sensors and statuses
by Robert Williams 12 May '17

12 May '17

Hi, Following a series of device upgrades and reloads over the last couple of days; we now have some 'invisible' stuck alerts: I cannot seem to find them anywhere, clicking them produces a blank list and even if you click the "Total" column. In this example I clicked the number "605" under Statuses but I get a page which only shows 595 items - so 10 missing, which equals the number of phantom alerts exactly. We had this once before and it was to do with devices, which are set to 'Ignore' for their alerts. We have 42 devices like this (a mixture of Lab and workstations) which unfortunately, would be a very large amount of manual checking. So I'm hoping there is a better way and I'm just missing it? :) So - any idea how I can find/reset/clear these items? Cheers! Robert Williams Custodian Data Centre Email: Robert(a)CustodianDC.com http://www.CustodianDC.com

1 0

Re: [Observium] SNMP Device without sysObjectId.0
by Oberreiter Andreas 04 May '17

04 May '17

Snmpget -v 1 -c public portail.nadlinger.at .1.3.6.1.4.1.14848.2.1.1.1.0 Should answer SNMPv2-SMI::enterprises.14848.2.1.1.1.0 = STRING: "Version 1.62" -----Ursprüngliche Nachricht----- Von: observium [mailto:observium-bounces@observium.org] Im Auftrag von Mike Stupalov Gesendet: Donnerstag, 4. Mai 2017 10:00 An: Observium Public Support <observium(a)observium.org> Betreff: Re: [Observium] SNMP Device without sysObjectId.0 Hi, can you privide temporary snmp access to this device? I will do this faster :) Oberreiter Andreas wrote: > I've added print_message lines to see if my code is called. > > When I try another device e.g. a zyxel device I can see my code is executed. > > But when I try the device in question the discovery code isn't executed. > > > -----Ursprüngliche Nachricht----- > Von: observium [mailto:observium-bounces@observium.org] Im Auftrag von > Mike Stupalov > Gesendet: Mittwoch, 3. Mai 2017 17:21 > An: Observium Public Support <observium(a)observium.org> > Betreff: Re: [Observium] SNMP Device without sysObjectId.0 > > This device also not have sysDescr.0 too? > > You also should add os detecting file (from > $config['os'][$os]['discovery_os']): > includes/discovery/os/messpc.inc.php > > with content like this: > > <?php > > if (!$os) > { > // SNMPv2-SMI::enterprises.14848.2.1.1.1.0 = STRING: "Version 1.62" > $data = snmp_get($device, '.1.3.6.1.4.1.14848.2.1.1.1.0', '-Osqnv'); > if (strlen($data)) > { > $os = 'messpc'; > } > } > > // EOF > > And better os name: messpc-env > > Oberreiter Andreas wrote: >> Hi, >> >> The Device is from http://www.messpc.de >> >> I've tried to add the following lines to >> includes/definitions/os.inc.php // MessPC $os = "messpc"; >> $config['os'][$os]['text'] = "MessPC Etherbox"; >> $config['os'][$os]['vendor'] = "MessPC"; >> $config['os'][$os]['type'] = "environment"; >> $config['os'][$os]['discovery_os'] = "messpc"; >> $config['os'][$os]['snmpable'][] = ".1.3.6.1.4.1.14848.2.1.1.1.0"; >> $config['os'][$os]['mibs'][] = "ETHERBOX-MIB"; >> >> I've put the ETHERBIX-MIB file in mibs/messpc/ETHERBOX-MIB >> >> and restarted the Webserver. Then I tried to add the device again no change. >> >> I can do a snmpwalk -v 1 -c public IP .1.3.6.1.4.1.14848 >> >> The result of >> snmpget -v 1 -c public 172.30.7.2 .1.3.6.1.4.1.14848.2.1.1.1.0 is >> SNMPv2-SMI::enterprises.14848.2.1.1.1.0 = STRING: "Version 1.62" >> >> What did I wrong? >> I'm on the latest commercial Version 17.4.8476 >> >> Kind Regards >> Andreas >> >> -----Ursprüngliche Nachricht----- >> Von: observium [mailto:observium-bounces@observium.org] Im Auftrag >> von Mike Stupalov >> Gesendet: Freitag, 28. April 2017 15:02 >> An: Observium Public Support <observium(a)observium.org> >> Betreff: Re: [Observium] SNMP Device without sysObjectId.0 >> >> Hi, >> >> seems as another china/indian device? ;) >> >> For valid device adding required one of this OIDs to be exist on device: >> sysObjectID.0 or sysUpTime.0 >> >> If both OIDs not exist for device, use 'snmpable' os param. >> See example for os 'hikvision-cam': >> >> $os = "hikvision-cam"; >> $config['os'][$os]['text'] = "Hikvision Network Camera"; >> $config['os'][$os]['type'] = "video"; >> $config['os'][$os]['vendor'] = "Hikvision"; >> $config['os'][$os]['discovery_os'] = "hikvision"; >> $config['os'][$os]['snmpable'][] = >> ".1.3.6.1.4.1.39165.1.1.0"; // This device complete not have >> sysObjectID.0 or sysUpTime.0 >> $config['os'][$os]['mibs'][] = "HIK-DEVICE-MIB"; >> >> >> Oberreiter Andreas wrote: >>> Hi All, >>> >>> I have a device which doesn't provide the SysObjectId.0. >>> It start right away with the Enterprise entry's: >>> SNMPv2-SMI::enterprises.14848.2.1.1.1.0 = STRING: "Version 1.62" >>> >>> Is there a way to add such an device? The values I'm interested in are in the enterprise part of the mib and could be easily retreated by a custom OID. >>> >>> But without an SysObjectId it seems impossible to add a device. >>> >>> Any Suggestions? >>> >>> Kind regards >>> Andras >>> >>> >>> _______________________________________________ >>> observium mailing list >>> observium(a)observium.org >>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium > > -- > Mike Stupalov > Observium Limited, http://observium.org > _______________________________________________ > 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 -- Mike Stupalov Observium Limited, http://observium.org _______________________________________________ observium mailing list observium(a)observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

1 0

Re: [Observium] SNMP Device without sysObjectId.0
by Oberreiter Andreas 04 May '17

04 May '17

I've added print_message lines to see if my code is called. When I try another device e.g. a zyxel device I can see my code is executed. But when I try the device in question the discovery code isn't executed. -----Ursprüngliche Nachricht----- Von: observium [mailto:observium-bounces@observium.org] Im Auftrag von Mike Stupalov Gesendet: Mittwoch, 3. Mai 2017 17:21 An: Observium Public Support <observium(a)observium.org> Betreff: Re: [Observium] SNMP Device without sysObjectId.0 This device also not have sysDescr.0 too? You also should add os detecting file (from $config['os'][$os]['discovery_os']): includes/discovery/os/messpc.inc.php with content like this: <?php if (!$os) { // SNMPv2-SMI::enterprises.14848.2.1.1.1.0 = STRING: "Version 1.62" $data = snmp_get($device, '.1.3.6.1.4.1.14848.2.1.1.1.0', '-Osqnv'); if (strlen($data)) { $os = 'messpc'; } } // EOF And better os name: messpc-env Oberreiter Andreas wrote: > Hi, > > The Device is from http://www.messpc.de > > I've tried to add the following lines to > includes/definitions/os.inc.php // MessPC $os = "messpc"; > $config['os'][$os]['text'] = "MessPC Etherbox"; > $config['os'][$os]['vendor'] = "MessPC"; > $config['os'][$os]['type'] = "environment"; > $config['os'][$os]['discovery_os'] = "messpc"; > $config['os'][$os]['snmpable'][] = ".1.3.6.1.4.1.14848.2.1.1.1.0"; > $config['os'][$os]['mibs'][] = "ETHERBOX-MIB"; > > I've put the ETHERBIX-MIB file in mibs/messpc/ETHERBOX-MIB > > and restarted the Webserver. Then I tried to add the device again no change. > > I can do a snmpwalk -v 1 -c public IP .1.3.6.1.4.1.14848 > > The result of > snmpget -v 1 -c public 172.30.7.2 .1.3.6.1.4.1.14848.2.1.1.1.0 is > SNMPv2-SMI::enterprises.14848.2.1.1.1.0 = STRING: "Version 1.62" > > What did I wrong? > I'm on the latest commercial Version 17.4.8476 > > Kind Regards > Andreas > > -----Ursprüngliche Nachricht----- > Von: observium [mailto:observium-bounces@observium.org] Im Auftrag von > Mike Stupalov > Gesendet: Freitag, 28. April 2017 15:02 > An: Observium Public Support <observium(a)observium.org> > Betreff: Re: [Observium] SNMP Device without sysObjectId.0 > > Hi, > > seems as another china/indian device? ;) > > For valid device adding required one of this OIDs to be exist on device: > sysObjectID.0 or sysUpTime.0 > > If both OIDs not exist for device, use 'snmpable' os param. > See example for os 'hikvision-cam': > > $os = "hikvision-cam"; > $config['os'][$os]['text'] = "Hikvision Network Camera"; > $config['os'][$os]['type'] = "video"; > $config['os'][$os]['vendor'] = "Hikvision"; > $config['os'][$os]['discovery_os'] = "hikvision"; > $config['os'][$os]['snmpable'][] = > ".1.3.6.1.4.1.39165.1.1.0"; // This device complete not have > sysObjectID.0 or sysUpTime.0 > $config['os'][$os]['mibs'][] = "HIK-DEVICE-MIB"; > > > Oberreiter Andreas wrote: >> Hi All, >> >> I have a device which doesn't provide the SysObjectId.0. >> It start right away with the Enterprise entry's: >> SNMPv2-SMI::enterprises.14848.2.1.1.1.0 = STRING: "Version 1.62" >> >> Is there a way to add such an device? The values I'm interested in are in the enterprise part of the mib and could be easily retreated by a custom OID. >> >> But without an SysObjectId it seems impossible to add a device. >> >> Any Suggestions? >> >> Kind regards >> Andras >> >> >> _______________________________________________ >> observium mailing list >> observium(a)observium.org >> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium > -- Mike Stupalov Observium Limited, http://observium.org _______________________________________________ observium mailing list observium(a)observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

2 1

session problems with centos 7, php 70, and latest stable Observium
by Darrell Budic 03 May '17

03 May '17

I’ve recently upgraded a commercial observium install to PHP 7 (from IUS) on Centos 7. Ever since, it’s been dropping my session and requiring a fresh login very very often. Sometimes as soon as I login, the links on the home page are telling me my session has expired, and sometimes everything works fine for hours. More often then not, I’m logged out within an hour though. This happens with basic mysql auth and ldap auth. I don’t see anything in the log files to indicate why the sessions are dropping, is there a debugging setting that can help me figure out what is going wrong? Any known gotchas under php 7.0 for the sessions? Looks like r7476 on the stable tree. Thanks, -Darrell

1 0

SNMP Device without sysObjectId.0
by Oberreiter Andreas 03 May '17

03 May '17

Hi All, I have a device which doesn't provide the SysObjectId.0. It start right away with the Enterprise entry's: SNMPv2-SMI::enterprises.14848.2.1.1.1.0 = STRING: "Version 1.62" Is there a way to add such an device? The values I'm interested in are in the enterprise part of the mib and could be easily retreated by a custom OID. But without an SysObjectId it seems impossible to add a device. Any Suggestions? Kind regards Andras

3 4

RFE - Number of prefixes advertised / received per BGP sessions
by Youssef BENGELLOUN - ZAHR 02 May '17

02 May '17

4 11

Dell M1000e - passthrough port statistics support
by Youssef BENGELLOUN - ZAHR 02 May '17

02 May '17

2 3

Observium doesn't discover Juniper MX properly?
by Marcin Kurek 28 Apr '17

28 Apr '17

Hello all, Today I added first Juniper MX480 to our Observium (Subscription Edition), but for some reason it doesn't discover physical interfaces. Loopbacks are properly discovered. What is interesting, when I look into "Inventory" I can see chassis, PEMs and FPCs. I've seen in the docs that MX960 is supported, so should be MX480. Are there any special knobs I should use to get this working please? Kind regards, Marcin Kurek

2 2

Weathermap in Observium PRO (rolling)
by Serghei Golipad 27 Apr '17

27 Apr '17

Hi All, Anyone else has problem with map-poller not updating traffic map? Stopped working after SVN upgrade on 18th of April :( /opt/observium/html/weathermap# ./map-poller.php PHP Fatal error: Call to undefined function external_exec() in /opt/observium/includes/definitions/version.inc.php on line 50 Thank you. PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL. CDW Limited is a Company registered in England and Wales. This email is sent for and on behalf of CDW Finance Holdings Limited. CDW Finance Holdings Limited is the UK holding company for CDW Limited trading as CDW. The registered office for CDW Finance Holdings Limited (Company Number 05872067) and its UK group undertakings is 10 Fleet Place, London, EC4M 7RB. VAT Registration 902 1949 39. Confidentiality: This e-mail contains proprietary information, some or all of which may be confidential and/or legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to this e-mail and then delete the original. If you are not the intended recipient you may not use, disclose, distribute, copy, print or rely on any information contained in this e-mail. You must not inform any other person other than CDW or the sender of its existence. For more information about CDW please visit www.uk.cdw.com

2 1

Cisco switches showing wrong Packet Size
by Jim Glassford 26 Apr '17

26 Apr '17

Hi, No luck trying to review the Observium Archives see if this was asked before, getting a Not Found off the web link. Running Observium 17.3.8438 (stable), question on MTU size on Cisco interfaces. On our HP ProCurve switches with Jumbo enabled, all displays correctly, see MTU as 9216 on the interfaces as expected. On our Cisco models with Jumbo enabled, MTU shows 1500 on Average Packet Size graph. I believe this is due to Cisco interfaces showing the MTU as 1500 even when Jumbo frames are enabled and are passing Jumbo on the switch interfaces. Seeing this on both Cisco models 2960s and 3K the Average Packet Size found to be 1500. Any chance someone have a work around for this Cisco problem, able to set the MTU up to 9216 for the interfaces? Appreciated! Jim

4 6