Open mhaebler opened 4 years ago
That all looks normal to me. What's the problem?
@brian-brazil None of the measurementsOutletSensorValue
related values show up in the snmp_exporter output.
I'd break out tcpdump then, as that all looks fine to me.
@mhaebler I understand the problem you've faced, but I've just tried the same using the same generator.yml
as you shared above, and got the following in smtp.yaml
# WARNING: This file was auto-generated using snmp_exporter generator, manual changes will be lost.
auths:
public_v1:
community: public
security_level: noAuthNoPriv
auth_protocol: MD5
priv_protocol: DES
version: 1
public_v2:
community: public
security_level: noAuthNoPriv
auth_protocol: MD5
priv_protocol: DES
version: 2
modules:
raritan:
walk:
- 1.3.6.1.4.1.13742.6.4.1.2.1.3
- 1.3.6.1.4.1.13742.6.5.4.3.1.4
metrics:
- name: outletSwitchingState
oid: 1.3.6.1.4.1.13742.6.4.1.2.1.3
type: gauge
help: The outlet state at present - 1.3.6.1.4.1.13742.6.4.1.2.1.3
indexes:
- labelname: pduId
type: gauge
- labelname: outletId
type: gauge
enum_values:
-1: unavailable
0: open
1: closed
2: belowLowerCritical
3: belowLowerWarning
4: normal
5: aboveUpperWarning
6: aboveUpperCritical
7: "on"
8: "off"
9: detected
10: notDetected
11: alarmed
12: ok
14: fail
15: "yes"
16: "no"
17: standby
18: one
19: two
20: inSync
21: outOfSync
22: i1OpenFault
23: i1ShortFault
24: i2OpenFault
25: i2ShortFault
26: fault
27: warning
28: critical
29: selfTest
30: nonRedundant
- name: measurementsOutletSensorValue
oid: 1.3.6.1.4.1.13742.6.5.4.3.1.4
type: gauge
help: The sensor reading as an unsigned integer - 1.3.6.1.4.1.13742.6.5.4.3.1.4
indexes:
- labelname: pduId
type: gauge
- labelname: outletId
type: gauge
- labelname: sensorType
type: gauge
enum_values:
1: rmsCurrent
2: peakCurrent
3: unbalancedCurrent
4: rmsVoltage
5: activePower
6: apparentPower
7: powerFactor
8: activeEnergy
9: apparentEnergy
10: temperature
11: humidity
12: airFlow
13: airPressure
14: onOff
15: trip
16: vibration
17: waterDetection
18: smokeDetection
19: binary
20: contact
21: fanSpeed
22: surgeProtectorStatus
23: frequency
24: phaseAngle
25: rmsVoltageLN
26: residualCurrent
27: rcmState
28: absoluteHumidity
29: reactivePower
30: other
31: none
32: powerQuality
33: overloadStatus
34: overheatStatus
35: displacementPowerFactor
36: residualDcCurrent
37: fanStatus
38: inletPhaseSyncAngle
39: inletPhaseSync
40: operatingState
41: activeInlet
42: illuminance
43: doorContact
44: tamperDetection
45: motionDetection
46: i1smpsStatus
47: i2smpsStatus
48: switchStatus
49: doorLockState
50: doorHandleLock
51: crestFactor
52: length
53: distance
54: activePowerDemand
55: residualAcCurrent
56: particleDensity
57: voltageThd
58: currentThd
59: inrushCurrent
60: unbalancedVoltage
61: unbalancedLineLineCurrent
62: unbalancedLineLineVoltage
I've tried with two versions of the PDU2-MIB.txt both with similar results (the only difference being the 2017 version only has 50 enum_values for the measurementsOutletSensorValue
.
raritan MODULE-IDENTITY
LAST-UPDATED "202209210000Z" -- September 21, 2022
raritan MODULE-IDENTITY
LAST-UPDATED "201711130000Z" -- November 13, 2017
Having some generator issues with this Raritan PDU2-MIB.txt
Host operating system: output of
uname -a
WSL2 Debian on Win10
snmp_exporter version: output of
snmp_exporter -version
What device/snmpwalk OID are you using?
Raritan PX3 - see MIB above. Here is the SNMP table I am trying to ingest:
This goes against the usual examples I see in the example
generator.yml
where all MIBs seem to follow a<valuename>.<index>
schema. Can someone provide an example how to handle the above?Current
generator.yml
I tried:This translates to
snmp.yml
as follows:If this is a new device, please link to the MIB(s).
Raritan PDU2-MIB.txt
What did you do that produced an error?
See
generator.yml
above. Does not produce any values formeasurementsOutletSensorValue
What did you expect to see?
Values for everything in the MIB.
What did you see instead?
No values for
measurementsOutletSensorValue
. Are there any examples for how to handle this reversed order?