Unser Kollege Thomas Gelf hat ein neues Plugin für die AKCP sensorProbe Hardware entwickelt. Das Plugin kann einfach mit der IP des Geräts und der SNMP get Community aufgerufen werden:
./check_akcp_sensorprobe.pl -H 10.10.40.10 -C netdemo OK sensorProbe2: Sensor reports that everything is fine OK Temperature sensor "Temperatur": 19.00C (15.0:25.0/5.0:30.0) OK Humidity sensor "Feuchtigkeit": 43.00% (15.0:60.0/10.0:80.0) OK Switch sensor "Bewegungsmelder" is normally closed |Humidity_1=43.00%;15.0:60.0;10.0:80.0 Temperature_1=19.00C;15.0:25.0;5.0:30.0
Die Schwellwerte und die angeschlossenen Sensoren werden aus den Einstellungen des Geräts übernommen. Man kann „check_akcp_sensorprobe.pl“ unter netways.org herunter laden.
Martin Krodel
Head of Sales
When I use this plugin I get this message:
[root@testmachinelibexec]# ./check_akcp_sensorprobe.pl -H 10.10.10.8 -C read-trans
CRITICAL: Failed to query device 10.10.10.8: Received noSuchName(2) error-status at error-index 4
What could cause this error?
It seems that either your device doesn’t support the OIDs I’m using in the plugin – or that the plugin „missunderstands“ your specific device/model. Please send an snmpwalk output (snmpwalk -v1 -c public 10.10.10.8) to support@netways.de, I’ll have an immediate look at it.
[root@testmachine libexec]# snmpwalk -v1 -c netdemo 10.10.10.8
SNMPv2-MIB::sysDescr.0 = STRING: sensorProbe8 SP8389 210708
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.3854.1
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (2700629576) 312 days, 13:44:55.76
SNMPv2-MIB::sysContact.0 = STRING: ICT
SNMPv2-MIB::sysName.0 = STRING: akcp-manager
SNMPv2-MIB::sysLocation.0 = STRING: Room 2
SNMPv2-MIB::sysServices.0 = INTEGER: 10
IF-MIB::ifNumber.0 = INTEGER: 1
IF-MIB::ifIndex.1 = INTEGER: 1
IF-MIB::ifDescr.1 = STRING: AKCP
IF-MIB::ifType.1 = INTEGER: ethernetCsmacd(6)
IF-MIB::ifMtu.1 = INTEGER: 1500
IF-MIB::ifSpeed.1 = Gauge32: 10000000
IF-MIB::ifPhysAddress.1 = STRING: 0:b:dc:0:8d:7d
IF-MIB::ifAdminStatus.1 = INTEGER: up(1)
IF-MIB::ifOperStatus.1 = INTEGER: up(1)
IF-MIB::ifLastChange.1 = Timeticks: (0) 0:00:00.00
IF-MIB::ifInOctets.1 = Counter32: 3651257853
IF-MIB::ifInUcastPkts.1 = Counter32: 0
IF-MIB::ifInNUcastPkts.1 = Counter32: 0
IF-MIB::ifInDiscards.1 = Counter32: 0
IF-MIB::ifInErrors.1 = Counter32: 0
IF-MIB::ifInUnknownProtos.1 = Counter32: 0
IF-MIB::ifOutOctets.1 = Counter32: 1993778028
IF-MIB::ifOutUcastPkts.1 = Counter32: 0
IF-MIB::ifOutNUcastPkts.1 = Counter32: 0
IF-MIB::ifOutDiscards.1 = Counter32: 0
IF-MIB::ifOutErrors.1 = Counter32: 0
IF-MIB::ifOutQLen.1 = Gauge32: 0
IF-MIB::ifSpecific.1 = OID: SNMPv2-SMI::zeroDotZero
IP-MIB::ipForwarding.0 = INTEGER: notForwarding(2)
IP-MIB::ipAdEntAddr.10.9.108.5 = IpAddress: 10.10.10.8
IP-MIB::ipAdEntIfIndex.10.10.10.8 = INTEGER: 1
IP-MIB::ipAdEntNetMask.10.10.10.8 = IpAddress: 255.255.240.0
IP-MIB::ipAdEntBcastAddr.10.10.10.8 = INTEGER: 1
Seems that it doesn’t walk through the whole tree. Please try again as follows:
snmpwalk -v1 -c public 10.10.10.8 .1.3.6.1.4.1.3854
Output will be much longer than the former one.
Indeed this is a big file 😉 I will mail it to support address.
Mailed it to support@netways.de .
Thank you in advance.
Didn’t you receive my response to your mail at 15:25:38 +0100? I attached a modified version of the plugin…
Tried this modified version and send you email. Didnt receive your answer yet. Still some issues with dry contacts. (see email).
Hallo Thomas I have a Problem whit this Plugin. We have 10 of this devices (sensorProbe2 v2.0), but one whit a new sensor. This needs a new firmware. The output show no (0,00C) temperature.
./check_akcp_sensorprobe.pl -H de-hro-temp-002
WARNING sensorProbe2 v2.0: Sensor reports one or more non-critical problems
OK Temperature sensor „Temperatur – Technikraum 2 HRO“: 0.00C (15.0:25.0/10.0:30.0)
The SNMP-Output but show the right Temperature:
snmpwalk -v1 -c „public“ 10.120.144.82 .1.3.6.1.4.1.3854.1.2.2.1.16
iso.3.6.1.4.1.3854.1.2.2.1.16.1.1.0 = STRING: „Temperatur – Technikraum 2 HRO“
iso.3.6.1.4.1.3854.1.2.2.1.16.1.1.1 = STRING: „Temperature2 Description“
iso.3.6.1.4.1.3854.1.2.2.1.16.1.3.0 = INTEGER: 19
iso.3.6.1.4.1.3854.1.2.2.1.16.1.4.0 = INTEGER: 2
iso.3.6.1.4.1.3854.1.2.2.1.16.1.4.1 = INTEGER: 0
iso.3.6.1.4.1.3854.1.2.2.1.16.1.5.0 = INTEGER: 1
iso.3.6.1.4.1.3854.1.2.2.1.16.1.5.1 = INTEGER: 2
iso.3.6.1.4.1.3854.1.2.2.1.16.1.6.0 = INTEGER: 1
iso.3.6.1.4.1.3854.1.2.2.1.16.1.6.1 = INTEGER: 2
iso.3.6.1.4.1.3854.1.2.2.1.16.1.7.0 = INTEGER: 23
iso.3.6.1.4.1.3854.1.2.2.1.16.1.7.1 = INTEGER: 40
iso.3.6.1.4.1.3854.1.2.2.1.16.1.8.0 = INTEGER: 25
iso.3.6.1.4.1.3854.1.2.2.1.16.1.8.1 = INTEGER: 55
I have compared the output between the „old“ and „new“ devices, no difference.
Can You help me ? How can I resolve the problem?