Re: [Observium] SNMP Device without sysObjectId.0

28 Jun 2017

      Hi Chris,
This is definitely a bug you need to pick up with JTAC. Sounds weird though.
Tom
On 06/27/2017 08:20 PM, Chris Laffin wrote:
...
I noticed QFX stops reporting this value after upgrading to newer 
junos and changed to Generic os from junos. Has anyone else seen this 
behaviour on QFX on JUNOS16.1R3 ? MX seems ok. I've added a local mod 
for now to use sysDescr of '/^Juniper Networks/' which has restored 
the ability to detect it. Maybe it's a junos bug or a new feature to 
hide the SysObjectId, or maybe worth adding sysDescr junos detection 
incase of SysObjectId failing?
On Thu, May 4, 2017 at 3:10 AM, Oberreiter Andreas 
<a.oberreiter@nadlinger.at mailto:a.oberreiter@nadlinger.at> wrote:
I've noticed a typing error

Snmpget -v 1 -c public portal.nadlinger.at
<http://portal.nadlinger.at> .1.3.6.1.4.1.14848.2.1.1.1.0

-----Ursprüngliche Nachricht-----
Von: observium [mailto:observium-bounces@observium.org
<mailto:observium-bounces@observium.org>] Im Auftrag von
Oberreiter Andreas
Gesendet: Donnerstag, 4. Mai 2017 10:53
An: Observium Public Support <observium@observium.org
<mailto:observium@observium.org>>
Betreff: Re: [Observium] SNMP Device without sysObjectId.0

Snmpget -v 1 -c public portail.nadlinger.at
<http://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
<mailto:observium-bounces@observium.org>] Im Auftrag von Mike Stupalov
Gesendet: Donnerstag, 4. Mai 2017 10:00
An: Observium Public Support <observium@observium.org
<mailto:observium@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
<mailto:observium-bounces@observium.org>] Im Auftrag von
> Mike Stupalov
> Gesendet: Mittwoch, 3. Mai 2017 17:21
> An: Observium Public Support <observium@observium.org
<mailto:observium@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
<mailto:observium-bounces@observium.org>] Im Auftrag
>> von Mike Stupalov
>> Gesendet: Freitag, 28. April 2017 15:02
>> An: Observium Public Support <observium@observium.org
<mailto:observium@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@observium.org <mailto:observium@observium.org>
>>> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
<http://postman.memetic.org/cgi-bin/mailman/listinfo/observium>
>
> --
> Mike Stupalov
> Observium Limited, http://observium.org
> _______________________________________________
> observium mailing list
> observium@observium.org <mailto:observium@observium.org>
> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
<http://postman.memetic.org/cgi-bin/mailman/listinfo/observium>
>
> _______________________________________________
> observium mailing list
> observium@observium.org <mailto:observium@observium.org>
> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
<http://postman.memetic.org/cgi-bin/mailman/listinfo/observium>

--
Mike Stupalov
Observium Limited, http://observium.org

_______________________________________________
observium mailing list
observium@observium.org <mailto:observium@observium.org>
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
<http://postman.memetic.org/cgi-bin/mailman/listinfo/observium>

_______________________________________________
observium mailing list
observium@observium.org <mailto:observium@observium.org>
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
<http://postman.memetic.org/cgi-bin/mailman/listinfo/observium>

_______________________________________________
observium mailing list
observium@observium.org <mailto:observium@observium.org>
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
<http://postman.memetic.org/cgi-bin/mailman/listinfo/observium>

observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

Re: [Observium] SNMP Device without sysObjectId.0

Tom Laermans