Closed MatthewHink closed 3 years ago
Nothing to do here. If we don't get the data, we don't get the data.
Wait: There is something to do here. We are getting a completely empty reading like this:
[mhink@ion ~/src/vapor/vem-access/burnin/site_tests (mhink-vem-180-testing)]$ curl --insecure https://synse.c1.ke2.pit.vio.ke/v3/read/93440615-0c8f-5e10-aee1-f56525b13fd0
[
]
We should get a reading with a null value:
[mhink@ion ~/src/vapor/vem-access/burnin/site_tests (mhink-vem-180-testing)]$ curl --insecure https://synse.c1.ke2.pit.vio.ke/v3/read/1524f3fa-fd23-5e2f-a3c6-45024e432a59
[
{
"device": "1524f3fa-fd23-5e2f-a3c6-45024e432a59",
"timestamp": "2021-01-22T19:25:28Z",
"type": "status",
"device_type": "status",
"unit": null,
"value": null,
"context": {
"model": "Galaxy VM 180 kVA"
}
}
]```
snmpget tells us what's up, the plugin is erroring out for some reason:
[mhink@ion ~/src/vapor/edge-ops/sites/pit/ke2-pit (master)]$ snmpget -v3 -l authPriv -u 'apc snmp profile1' -a SHA -A $(sctl read SNMP_UPS_AUTH_PASSPHRASE) -x AES -X $(sctl read SNMP_UPS_PRIVACY_PASSPHRASE) 10.193.12.241 .1.3.6.1.2.1.33.1.1.4.0
SNMPv2-SMI::mib-2.33.1.1.4.0 = No Such Object available on this agent at this OID
Turns out this UPS does not send these data over SNMP. This ticket is just for tracking.
SNMP OIDs with null readings:
upsIdentAgentSoftwareVersion .1.3.6.1.2.1.33.1.1.4.0 upsIdentName .1.3.6.1.2.1.33.1.1.5.0 upsIdentAttachedDevices .1.3.6.1.2.1.33.1.1.6.0 upsBatteryTemperature .1.3.6.1.2.1.33.1.2.7.0
snmpwalk -v3 -l authPriv -u 'apc snmp profile1' -a SHA -A $(sctl read SNMP_UPS_AUTH_PASSPHRASE) -x AES -X $(sctl read SNMP_UPS_PRIVACY_PASSPHRASE) 10.193.12.241 .1.3.6.1.2.1.33