can any body help with this ?
I’m struggling with this - is this effectively a UPS?
The OID unfortunately on its own is ‘just another embedded linux device’ .1.3.6.1.4.1.8072.3.2.10
There is a UPS and an SMU definition in LibreNMS already, and both cite GSE200M in some form - the SMU one has the exact match to
.1.3.6.1.2.1.1.5.0 = STRING: "GSE200M"
Can you walk this OID and see what you get? .1.3.6.1.4.1.2011
Can you also specifically walk .1.3.6.1.4.1.2011.6.164
I’ve been unable to translate any OIDs out of the MIB from various errors, I’m not practiced enough with snmptranslate to have enough success there.
Hi,
Both OID jumps to this oid .1.3.6.1.4.1.2011.6.178.1.1.1.1.1.0
walk is saved here
I’m out of my depth on this one sorry - I can’t make any sense of it. Maybe someone else can.
When I compile that MIB along with HUAWEI-MIB OID view shows it like this with invalid OIDs:
Best I can find is it’s effectively like a Smart UPS Management module that connects in to power, AC and environment sensing.
There is a relationship to it - if you look at this for example:
The part from .6.178 onwards:
hwECCSysAIDI3SensorName,5.2.336.1.5.6.178.1.1.1.1.52, HUAWEI-ECC-MIB, OBJECT-TYPE
Matches from the last walk:
iso.3.6.1.4.1.2011.6.178.1.1.1.1.52.0 = STRING: “leak sensor”
How you go any further with that, I have no idea.
Hi,
I tried creating the YAML file for specific sensors, but I ran into an issue—my other devices (Huawei devices) were also detected as GSE200M. Haha! I think I’m missing the PHP file, but I’m not sure where to start.
Hi @Rogelio_Cantos
Seems that the snmpwalk is incomplete. Not much we can do with that.
Please provide us this :
snmpbulkwalk -OUneb <deviceIP> -c <community> -v 2c .
Beware that all snmp tree should be in this (so if the device is productive, you may disclose data).
Hi @PipoCanaja
snmpbulkwalk here
Bump…
any help is appreciated
Hi @Rogelio_Cantos
Still not complete. No OID from Huawei specific MIBs are included here. So we can’t simulate your device. Do you have a timeout ? is the device far (latency speaking) from the server you are running snmpwalk ?