Hi,
confusion between MGE/Eaton, because Eaton acquired MGE in 2007 year.
About "Inverter Off" sensor - I walked multiple such devices, and confirm I see on some devices it set as "yes", on some as "no". But I not see any param/way for detect if ups line-interactive or online (by snmp). If someone know - show me.
On 04.08.16 11:32, Robert Williams wrote:
Ahhh… yes that makes perfect sense thanks!
So yes the question now becomes – is there a way to set this in Observium?
Doing it by model would be painful, maybe you could set the state during a discovery to be the ‘good’ state? As the chances of a power fail being present at the exact moment of discovery are relatively small…
Robert Williams Custodian Data Centre Email: Robert@CustodianDC.com http://www.CustodianDC.com
*From:*observium [mailto:observium-bounces@observium.org] *On Behalf Of *Gumilar Siegfried *Sent:* 04 August 2016 09:21 *To:* Observium Network Observation System observium@observium.org *Subject:* Re: [Observium] Eaton 5130 'Inverter Off' Flipped
Hi,
we are using some MGE UPS that are similar to your Eaton UPS and we have the same issue.
I recently talked to an Eaton Engineer and he explained to me that our UPS are line-interactive and therefore the inverter has to be off in normal operation.
For the bigger “online UPS” on the other hand the inverter has to be on.
It seems like Observium is configured to treat all the Eaton and MGE UPS as online UPS.
Maybe there is a way for Observium to detect whether it is an online or line-interactive UPS and handle the inverter Alert accordingly.
Regards,
Siegfried
*Von:*observium [mailto:observium-bounces@observium.org] *Im Auftrag von *Robert Williams *Gesendet:* Donnerstag, 04. August 2016 09:58 *An:* Observium Network Observation System (observium@observium.org mailto:observium@observium.org) *Betreff:* [Observium] Eaton 5130 'Inverter Off' Flipped
Hi,
We’ve got several Eaton 5130 RT 3000 (with extended battery packs) being deployed to some remote locations. One of my guys has been setting them up overnight but has noticed that Observium reports one of the metrics incorrectly for all of the new units.
Ironically the inverter status is, well, inverted.
*The platform is detected as:*
Hardware 5130 RT 3000
Operating system MGE UPS 6006AC (Firmware: JI)
*A debug of the status module, shows:*
SQL[UPDATE `status-state` set `status_value` ='2',`status_name` ='No',`status_event` ='ok',`status_last_change` ='1470278633',`status_polled` ='1470295701' WHERE `status_id` = '1289']
SQL RUNTIME[0.00013590s]
Checking (snmp) Inverter Off
CMD[/usr/bin/snmpget -v1 -c *** -Pu -OUqnv -m SNMPv2-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'ups-41.thn.oob.local':'161' .1.3.6.1.4.1.705.1.7.9.0]
CMD EXITCODE[0]
CMD RUNTIME[0.0414s]
STDOUT[
1
]
SNMP STATUS[TRUE]
RRD CMD[update /opt/observium/rrd/ups-41.thn.oob.local/status-mge-status-state-upsmgOutputInverterOff.1.0.rrd N:1 --daemon unix:/var/run/rrdcached.sock]
RRD RUNTIME[0.0011s]
RRD STDOUT[OK u:0.00 s:0.00 r:0.65]
RRD_STATUS[TRUE]
- /opt/observium/includes/polling/status.inc.php:45
/opt/observium/includes/alerts.inc.php:61
================================================
array(
[status_value] => int(1)
[status_name] => string(3) "Yes"
[status_name_uptime] => int(17068)
[status_event] => string(5) "alert"
))
Reading the standards for that OID, that does seem to be the wrong way around.
After a simulated power failure, you can see it goes to ‘2’ when the power is failed and the inverter is (actually) off.
As a side note, I noticed that Observium is polling the OIDs for a *Merlin Gerin* unit (.1.3.6.1.4.1.*705*.x) for when the unit is actually *Eaton*.
Should it maybe be looking here instead?
iso.3.6.1.4.1.*534*.1.1.1.0 = STRING: "EATON"
iso.3.6.1.4.1.534.1.1.2.0 = STRING: "5130 RT 3000"
iso.3.6.1.4.1.534.1.1.3.0 = STRING: "INV: 6006AC"
iso.3.6.1.4.1.534.1.1.4.0 = INTEGER: 0
iso.3.6.1.4.1.534.1.2.1.0 = INTEGER: 350
iso.3.6.1.4.1.534.1.2.2.0 = INTEGER: 78
iso.3.6.1.4.1.534.1.2.3.0 = INTEGER: 0
iso.3.6.1.4.1.534.1.2.4.0 = INTEGER: 23
iso.3.6.1.4.1.534.1.2.5.0 = INTEGER: 1
iso.3.6.1.4.1.534.1.2.6.0 = ""
iso.3.6.1.4.1.534.1.3.1.0 = INTEGER: 490
iso.3.6.1.4.1.534.1.3.2.0 = Counter32: 0
iso.3.6.1.4.1.534.1.3.3.0 = INTEGER: 1
iso.3.6.1.4.1.534.1.3.4.1.1.1 = INTEGER: 1
iso.3.6.1.4.1.534.1.3.4.1.2.1 = INTEGER: 226
iso.3.6.1.4.1.534.1.3.4.1.3.1 = INTEGER: 0
iso.3.6.1.4.1.534.1.3.4.1.4.1 = INTEGER: 0
iso.3.6.1.4.1.534.1.3.4.1.5.1 = INTEGER: 1
iso.3.6.1.4.1.534.1.3.5.0 = INTEGER: 3
iso.3.6.1.4.1.534.1.4.1.0 = INTEGER: 67
iso.3.6.1.4.1.534.1.4.2.0 = INTEGER: 490
iso.3.6.1.4.1.534.1.4.3.0 = INTEGER: 1
iso.3.6.1.4.1.534.1.4.4.1.1.1 = INTEGER: 1
iso.3.6.1.4.1.534.1.4.4.1.2.1 = INTEGER: 226
iso.3.6.1.4.1.534.1.4.4.1.3.1 = INTEGER: 8
iso.3.6.1.4.1.534.1.4.4.1.4.1 = INTEGER: 1809
iso.3.6.1.4.1.534.1.4.4.1.5.1 = INTEGER: 1
iso.3.6.1.4.1.534.1.4.5.0 = INTEGER: 3
iso.3.6.1.4.1.534.1.4.6.0 = INTEGER: 0
iso.3.6.1.4.1.534.1.4.7.0 = INTEGER: 0
iso.3.6.1.4.1.534.1.4.8.0 = Counter32: 0
iso.3.6.1.4.1.534.1.5.1.0 = INTEGER: 0
iso.3.6.1.4.1.534.1.5.2.0 = INTEGER: 0
iso.3.6.1.4.1.534.1.6.1.0 = INTEGER: 0
iso.3.6.1.4.1.534.1.6.2.0 = INTEGER: 0
iso.3.6.1.4.1.534.1.6.3.0 = INTEGER: 40
iso.3.6.1.4.1.534.1.6.7.0 = INTEGER: 0
iso.3.6.1.4.1.534.1.7.1.0 = Gauge32: 0
iso.3.6.1.4.1.534.1.7.18.0 = Gauge32: 0
iso.3.6.1.4.1.534.1.8.1.0 = INTEGER: 1
iso.3.6.1.4.1.534.1.8.2.0 = INTEGER: 2
iso.3.6.1.4.1.534.1.9.1.0 = INTEGER: 0
iso.3.6.1.4.1.534.1.9.2.0 = INTEGER: 0
iso.3.6.1.4.1.534.1.9.3.0 = INTEGER: 0
iso.3.6.1.4.1.534.1.9.4.0 = INTEGER: 0
iso.3.6.1.4.1.534.1.9.5.0 = INTEGER: 0
iso.3.6.1.4.1.534.1.9.6.0 = INTEGER: 0
iso.3.6.1.4.1.534.1.9.7.0 = INTEGER: 0
iso.3.6.1.4.1.534.1.10.1.0 = INTEGER: 230
iso.3.6.1.4.1.534.1.10.2.0 = INTEGER: 230
iso.3.6.1.4.1.534.1.10.3.0 = INTEGER: 2700
iso.3.6.1.4.1.534.1.10.4.0 = INTEGER: 500
iso.3.6.1.4.1.534.1.10.5.0 = STRING: "08/04/2016 08:34:38"
iso.3.6.1.4.1.534.1.10.6.0 = INTEGER: 160
iso.3.6.1.4.1.534.1.10.7.0 = INTEGER: 294
iso.3.6.1.4.1.534.1.10.8.0 = ""
iso.3.6.1.4.1.534.1.11.1.0 = INTEGER: 5
iso.3.6.1.4.1.534.1.11.2.0 = INTEGER: 2
iso.3.6.1.4.1.534.1.11.3.0 = ""
iso.3.6.1.4.1.534.1.12.1.0 = INTEGER: 2
iso.3.6.1.4.1.534.1.12.2.1.1.1 = INTEGER: 1
iso.3.6.1.4.1.534.1.12.2.1.1.2 = INTEGER: 2
iso.3.6.1.4.1.534.1.12.2.1.2.1 = INTEGER: 1
iso.3.6.1.4.1.534.1.12.2.1.2.2 = INTEGER: 1
iso.3.6.1.4.1.534.1.12.2.1.3.1 = INTEGER: -1
iso.3.6.1.4.1.534.1.12.2.1.3.2 = INTEGER: -1
iso.3.6.1.4.1.534.1.12.2.1.4.1 = INTEGER: -1
iso.3.6.1.4.1.534.1.12.2.1.4.2 = INTEGER: -1
iso.3.6.1.4.1.534.1.12.2.1.5.1 = INTEGER: -1
iso.3.6.1.4.1.534.1.12.2.1.5.2 = INTEGER: -1
iso.3.6.1.4.1.534.1.12.2.1.6.1 = INTEGER: 3
iso.3.6.1.4.1.534.1.12.2.1.6.2 = INTEGER: 6
iso.3.6.1.4.1.534.1.12.2.1.7.1 = INTEGER: 0
iso.3.6.1.4.1.534.1.12.2.1.7.2 = INTEGER: 0
iso.3.6.1.4.1.534.1.12.2.1.8.1 = INTEGER: 0
iso.3.6.1.4.1.534.1.12.2.1.8.2 = INTEGER: 0
iso.3.6.1.4.1.534.1.12.2.1.9.1 = INTEGER: 0
iso.3.6.1.4.1.534.1.12.2.1.9.2 = INTEGER: 0
iso.3.6.1.4.1.534.1.12.2.1.10.1 = Counter32: 0
iso.3.6.1.4.1.534.1.12.2.1.10.2 = Counter32: 0
iso.3.6.1.4.1.534.1.13.1.0 = INTEGER: 32
iso.3.6.1.4.1.534.1.13.2.0 = INTEGER: 0
iso.3.6.1.4.1.534.1.13.3.0 = INTEGER: 0
I could be very wrong, maybe there is a valid reason to us the Merlin Gerin instead (I know they merged, but I thought I’d mention it in light of the odd issue).
Any ideas anyone? Cheers!
Robert Williams
Custodian Data Centre
Email: Robert@CustodianDC.com mailto:Robert@CustodianDC.com
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
