[nut-Bugs][312364] Improvements for netvision mips (snmp-ups)
nut-bugs at alioth.debian.org
nut-bugs at alioth.debian.org
Tue Feb 23 19:49:25 UTC 2010
Bugs item #312364, was changed at 2010-02-23 18:06 by Arjen de Korte
You can respond by visiting:
https://alioth.debian.org/tracker/?func=detail&atid=411542&aid=312364&group_id=30602
Status: Open
Priority: 3
Submitted By: Andrea Soster (sghebuz-guest)
Assigned to: Nobody (None)
Summary: Improvements for netvision mips (snmp-ups)
Category: Driver
Group: None
Resolution: None
Initial Comment:
Dear,
I'm testing a new ups (Sicom/Socomec MASTERSYS BC 15 KVA), and it works
with nut 2.4.1
After upgrading to 2.4.2/3 it's not working anymore: it's unable to see
the status.
I fixed the driver making it work again with 2.4.3 and made some
improvements:
1. The order of "netvision_output_info" is incorrect: fields with
null value come before the "OL" one, excluding it from the
lookup. For that reason nut was returning a blank status (and
upsmon wasn't very happy)
2. NETVISION_OID_BATTERYSTATUS was checked for
"netvision_batt_info" and "netvision_output_info". Now
"netvision_output_info" is checked on
NETVISION_OID_OUTPUT_SOURCE
3. If you start the shutdown procedure on the UPS, nut is not
receiving anything (as the ups is still online) -> Now it checks
alarm 50 - "UPS imminent stop" and send a FSD signal when
present
best regards
Andrea Soster
----------------------------------------------------------------------
>Comment By: Arjen de Korte (adkorte-guest)
Date: 2010-02-23 20:49
Message:
1. Close, but no cigar. The order of the items is supposed to be irrelevant. Usually we choose ascending order, but that's only because that is easier on our eyes. What's really wrong here, is that only the last entry in the list should be "NULL", since this is treated as the terminating entry.
2, Good to know. Thanks for the report.
3. We'll have to discuss this on the development mailing list. The procedure for now would be to issue 'upsmon -c fsd' to initiate a shutdown sequence before (manually) starting the shutdown sequence. This doesn't rely on the cooperation of the UPS and won't require us to track down all the possible flags and alarms that indicate the UPS is about to shutdown. I'm not to thrilled to add this.
----------------------------------------------------------------------
You can respond by visiting:
https://alioth.debian.org/tracker/?func=detail&atid=411542&aid=312364&group_id=30602
More information about the NUT-tracker
mailing list