Will do that on next shipment….

MIB’s is not the only thing they fuck up. Something simple as HTTPS is an issue for them.

 

But hey, like the product so I can live with the retarded shit J

 

Met vriendelijke groet,

 

David

 

Van: observium [mailto:observium-bounces@observium.org] Namens Adam Armstrong
Verzonden: maandag 23 januari 2017 13:09
Aan: Observium Network Observation System <observium@observium.org>
Onderwerp: Re: [Observium] MIB Sensorgateway

 

Someone email this vendor and demand non-retarded firware and mibs.

God.

Adam.

Sent from BlueMail

On 23 Jan 2017, at 11:37, Mike Stupalov <mike@observium.org> wrote:

Hi Tomas and Alessandro and other,
 
 I tested output for which you have given me access.

everything is bad :)

there is no way to understand exactly what kind of sensors.
the data do not correspond to MIBs..

FW3 walk:
RFC1213-MIB::sysDescr.0 = STRING: "3.13"
RFC1213-MIB::sysObjectID.0 = OID: LAN-MODULE::lan-module
RFC1213-MIB::sysUpTime.0 = Timeticks: (145433837) 16 days, 19:58:58.37
RFC1213-MIB::sysContact.0 = STRING: "LAN_SWITCH-HOME"
LAN-MODULE::trapReceiverNumber.1 = INTEGER: 1
LAN-MODULE::trapEnabled.1 = INTEGER: No(0)
LAN-MODULE::trapReceiverIPAddress.1 = IpAddress: 10.58.252.2
LAN-MODULE::trapCommunity.1 = Hex-STRING: 00
LAN-MODULE::out0.0 = INTEGER: OFF(1)
LAN-MODULE::out1.0 = INTEGER: OFF(1)
LAN-MODULE::out2.0 = INTEGER: OFF(1)
LAN-MODULE::out3.0 = INTEGER: OFF(1)
LAN-MODULE::out4.0 = INTEGER: OFF(1)
LAN-MODULE::out5.0 = INTEGER: ON(0)
LAN-MODULE::outall.0 = Wrong Type (should be INTEGER): NULL
LAN-MODULE::temp.0 = Wrong Type (should be OCTET STRING): INTEGER: 219
LAN-MODULE::vcc.0 = Wrong Type (should be OCTET STRING): INTEGER: 122
LAN-MODULE::inp1.0 = Wrong Type (should be OCTET STRING): INTEGER: 0
LAN-MODULE::inp2.0 = Wrong Type (should be OCTET STRING): INTEGER: 3
LAN-MODULE::inp3.0 = Wrong Type (should be OCTET STRING): INTEGER: 4326
LAN-MODULE::inp4.0 = Wrong Type (should be OCTET STRING): INTEGER: 575
LAN-MODULE::inp5.0 = Wrong Type (should be OCTET STRING): INTEGER: 25
LAN-MODULE::inp6.0 = Wrong Type (should be OCTET STRING): INTEGER: 219
LAN-MODULE::inp7.0 = Wrong Type (should be OCTET STRING): INTEGER: 215
LAN-MODULE::inp8.0 = Wrong Type (should be OCTET STRING): INTEGER: 236
LAN-MODULE::inp9.0 = Wrong Type (should be OCTET STRING): INTEGER: 231
LAN-MODULE::inp10.0 = Wrong Type (should be OCTET STRING): INTEGER: -600
LAN-MODULE::inp11.0 = Wrong Type (should be OCTET STRING): INTEGER: -600
LAN-MODULE::DTH22-1.0 = Wrong Type (should be OCTET STRING): INTEGER: 0
LAN-MODULE::DTH22-2.0 = Wrong Type (should be OCTET STRING): INTEGER: 0
LAN-MODULE::esense.3.0 = INTEGER: 0
LAN-MODULE::i3xi5.0 = Wrong Type (should be OCTET STRING): INTEGER: 14550
LAN-MODULE::Pxt.0 = Wrong Type (should be OCTET STRING): INTEGER: 0
LAN-MODULE::Pinp4D.0 = Wrong Type (should be OCTET STRING): INTEGER: 0
LAN-MODULE::Pinp4D-24H.0 = Wrong Type (should be OCTET STRING): INTEGER: 0
LAN-MODULE::inp1Digital.0 = INTEGER: HIGH(1)
LAN-MODULE::inp2Digital.0 = INTEGER: HIGH(1)
LAN-MODULE::inp3Digital.0 = INTEGER: HIGH(1)
LAN-MODULE::inp4Digital.0 = INTEGER: HIGH(1)
End of MIB

For Alessandro, your device used complete other oid tree, for which I not have any MIBs:
.1.3.6.1.4.1.7616:

SNMPv2-SMI::enterprises.7616.3.1.0.0 = INTEGER: 0
SNMPv2-SMI::enterprises.7616.3.1.1.0 = INTEGER: 0
SNMPv2-SMI::enterprises.7616.3.1.2.0 = INTEGER: 0
SNMPv2-SMI::enterprises.7616.3.1.3.0 = INTEGER: 0
SNMPv2-SMI::enterprises.7616.3.1.4.0 = INTEGER: 0
SNMPv2-SMI::enterprises.7616.3.1.5.0 = INTEGER: 0
SNMPv2-SMI::enterprises.7616.3.1.6.0 = INTEGER: 1
SNMPv2-SMI::enterprises.7616.3.1.7.0 = INTEGER: 1
SNMPv2-SMI::enterprises.7616.3.1.8.0 = INTEGER: 1
SNMPv2-SMI::enterprises.7616.3.1.9.0 = INTEGER: 1
SNMPv2-SMI::enterprises.7616.3.2.1.0 = INTEGER: 1
SNMPv2-SMI::enterprises.7616.3.2.2.0 = INTEGER: 1
SNMPv2-SMI::enterprises.7616.3.2.3.0 = INTEGER: 1
SNMPv2-SMI::enterprises.7616.3.2.4.0 = INTEGER: 1
SNMPv2-SMI::enterprises.7616.3.3.1.0 = INTEGER: 2
SNMPv2-SMI::enterprises.7616.3.3.2.0 = INTEGER: 2
SNMPv2-SMI::enterprises.7616.3.3.3.0 = INTEGER: 2
SNMPv2-SMI::enterprises.7616.3.3.4.0 = INTEGER: 2
SNMPv2-SMI::enterprises.7616.3.3.5.0 = INTEGER: 0
SNMPv2-SMI::enterprises.7616.3.3.6.0 = INTEGER: 0
SNMPv2-SMI::enterprises.7616.3.3.7.0 = INTEGER: 2495
SNMPv2-SMI::enterprises.7616.3.3.8.0 = INTEGER: 3400
SNMPv2-SMI::enterprises.7616.3.4.1.0 = INTEGER: -600
SNMPv2-SMI::enterprises.7616.3.4.2.0 = INTEGER: -600
SNMPv2-SMI::enterprises.7616.3.4.3.0 = INTEGER: -600
SNMPv2-SMI::enterprises.7616.3.4.4.0 = INTEGER: 220
SNMPv2-SMI::enterprises.7616.3.4.5.0 = INTEGER: -600
SNMPv2-SMI::enterprises.7616.3.4.6.0 = INTEGER: -600
SNMPv2-SMI::enterprises.7616.3.4.7.0 = INTEGER: -600
SNMPv2-SMI::enterprises.7616.3.4.8.0 = INTEGER: -600
SNMPv2-SMI::enterprises.7616.3.4.9.0 = INTEGER: 0
SNMPv2-SMI::enterprises.7616.3.4.10.0 = INTEGER: 0
SNMPv2-SMI::enterprises.7616.3.5.1.0 = INTEGER: 0
SNMPv2-SMI::enterprises.7616.3.5.2.0 = INTEGER: 0
SNMPv2-SMI::enterprises.7616.3.5.3.0 = INTEGER: 0
SNMPv2-SMI::enterprises.7616.3.5.4.0 = INTEGER: 0
SNMPv2-SMI::enterprises.7616.3.5.5.0 = INTEGER: 0
SNMPv2-SMI::enterprises.7616.3.5.6.0 = INTEGER: 0
SNMPv2-SMI::enterprises.7616.3.5.7.0 = INTEGER: 0
SNMPv2-SMI::enterprises.7616.3.5.8.0 = INTEGER: 0
End of MIB


On 19.01.17 12:27, chott@praha1.net wrote:

MIB attached for LAN Controller

 

 

Tomas Chott
technický ředitel

chott@praha1.net
Phone: +420 245 004 005
Mobile: +420 733 123 135

Metropolitní síť Praha 1 z.s.p.o.
Jindrisska 18
110 00 Praha 1
Czech Republic
www.praha1.net

It is possible add support for LAN Controller?

 

Tom

 

Hello team

we have lot of device LAN Controllertr http://www.tinycontrol.pl/tinycontrol/en/lan/lan_kontroler.php

in this case there is old MIB https://github.com/pgmillon/observium/blob/master/mibs/SENSORGATEWAY-MIB.mib

Probably coresponding with OIDs down, is it possible add support for this LAN Controller?

Tom


 

 

 



-- 
Mike Stupalov
http://observium.org


observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Disclaimer ( http://www.avans.nl/over-avans/e-mail-disclaimer )