Eaton updated MIB

eaton-warning.diff

Sorry for the late replay, I had a lot of diffrent things i need to focus on, se diff.

Since "Battery over aged (06/01/2020)" is just a arbitreri date, is not alert for immediate action, hence reduce level to warning.

since "xupsBatteryNotPresent" is not present on non UPS devices we can safly sett it to warning.

Torstein, I remember that I have already fixed something additionally for this issue.

What additional question we need to solve here?

'XUPS-MIB::xupsBatteryLastReplacedDate.0' is just a date.

'XUPS-MIB::xupsBatteryAged.0' is the one with the alert.

I.e. for MGE UPS we have complete same status "Battery Replacement Needed":

$type = 'mge-status-state';

$config['mibs'][$mib]['states'][$type][1] = array('name' => 'Yes', 'event' => 'alert');

$config['mibs'][$mib]['states'][$type][2] = array('name' => 'No', 'event' => 'ok');

Please show 'XUPS-MIB::xupsBatteryLastReplacedDate.0' and 'XUPS-MIB::xupsBatteryAged.0' for UPS which you are talking about.

I did make a distinction about warning/alert level, like a battery is old is not a immediate action.
nominally it is exactly alert state, but you can ignore it by self alert rules.

I made the xupsBatteryNotPresent a alert since no battery means i have not working UPS.
currently this status set ignore which mean "alert", but ignored. Probably I can switch this status to "alert" to, but not warning!
this Oid present not only on UPS devices, where not exist battery is not high trouble.

for the status's:

I didn't know about the ng version, so we can probly use that.

I did make a distinction about warning/alert level, like a battery is old is not a immediate action. 

I made the xupsBatteryNotPresent a alert since no battery means i have not working UPS.

for sensors: 

I notices if i played around with the oid part i will break RRD file mapping on other UPS. so it probly need a "rename_rrd" to update the rrd to new.

For current I was thinking of using the same oid, so the RRD file stayed the same.

For current i think it was redundant to have the auto limite enable, duo the change load we have on ours UPS day vs night, and it was creating a lot of false alerts. for overload we have the load and the power that is more accurate.

The reason for not controlling for 

&& $entry['xupsBypassCurrentHighPrecision'] != 0)  

was that Bypass current is only active then UPS is in bypass mode.

is attached.

is attached.

Please make and attach additional information about the device:

• full snmp dump from device:

  snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk

  snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

  If device not support SNMP version 2c, replace -v2c with -v1.

• If you have problems with discovery or poller processes, please do and attach these debugs:

  ./discovery.php -d -h <device>

  ./poller.php -d -h <device>

• additionally attach device and/or vendor specific MIB files

Note, this comment is added automatically.