similar to: Availability of the driver for MGE* Network Management Cards (mge-xml)

I'm now doubting if I've made this statement or not, so here it is: newmge-shut is *not* ready for production usage! I've lately found some bugs during the MGE PSP 3.0.4/3.0.5/3.0.6 updates. So for the moment, prefer to keep using mge-shut. 2007/10/25, R?zsa G?bor <mailer.tovis at freemail.hu>: > newmge-shut ??? > Shutdown, switch of ups does not work. Using command >

Hi all, some time ago I bought at discount price a NMC for managing a few computers using the programmable outlets features available on my MGE Evolution, unuseful otherwise (ATM). However, expecially for my server machine, I don't like very much the NSM client provided by MGE/Eaton and I'd rather use only NUT from my distribution. So, looking at the netxml-ups driver, I started adding

One good intro to this is https://github.com/networkupstools/nut/blob/master/docs/snmp-subdrivers.txt although it focuses on adding new subdrivers - but more or less the same workflow applies to extending existing ones. Sometimes it helps to generate a new one for a currently-partially-supported device, and then compare with existing subdriver (using meld or similar GUI helps a lot) to port the

So what would it take me to edit NUT's code for my case to work? My Network Management Card sends its output state using unfortunately only (I guess so) this OID: 1.3.6.1.4.1.318.1.1.1.11.1.1.0 Weirdly the standard way of obtaining Battery Status (drivers/apc-mib.c) 1.3.6.1.4.1.318.1.1.1.2.1.1.0 gives me good results. Unfortunately power status OID's value type differs (my: 64 digits

Well thanks, The solution for my problem was kinda easy (still need some testing though): found out my ups status is a string, so then I changed the way snmp-ups.c gets the status. Had to change *nut_snmp_get_int *to *nut_snmp_get_str *at around line 3470, then grab fourth char out, use *strtol *function to then send it to *su_status_set *function. I created my copy of *apc-mib.c *with my OID at

Dear folks, According to mge-mib.c (NUT 2.6.2) LB condition is gained from variable .1.3.6.1.4.1.705.1.5.14.0 (i.e. upsmgBatteryLowBattery.0). The test device of me does not set this variable to yes(1) even if runtime drops below the preconfigured limit. I complained about this at Schneider Electric. They replied that low battery status is indicated by .1.3.6.1.4.1.705.1.5.14.0

I've got an update on this case Using tkmib I discovered that my UPS (NMC per say) sends its state by OID 1.3.6.1.4.1.318.1.1.1.11.1.1.0 .iso.org.dod.internet.private.enterprises.apc.products.hardware.ups.upsState.upsBasicState.upsBasicStateOutputState.0 = 0001010000000000001000000000000000000000000000000000000000000000 (mib used for this snmpget was powernet441.mib) (I got a description about

Citeren Marco Chiappero <marco op absence.it>: > I managed to get twice connected at the same time from the same > machine to a single UPS using different hostnames, so it's > definitely not an IP based check (at least here with 66102 / EC). Never mind. The alarm messages are not bound to a specific outlet, but are sent to all NSM clients that are connected. Which means

Hello, I'll be back with my MGE Evolution 2200 connected with RS232 I upgrade nut 2.0.1 in nut 2.2 + psp as you ask me PSP autodetect my UPS and autoconfigure NUT. not really diffcult ! So I didn't change anything but I always have in my syslog these event Nov 13 11:09:22 mezenc upsmon[3865]: Poll UPS [mgeups at localhost] failed - Data stale Nov 13 11:09:27 mezenc upsmon[3865]: Poll

Hello, At my workplace I have exact UPS config as stated in the subject (APC MGE Galaxy 5500 + AP9635CH). I have it set up to work with snmp-ups NUT driver. Despite many readings from *upsc* command I am not receiving "On Line Status" (ups.status OL) nor "On Battery Status" (ups.status OB) and therefore I can't get my systems to shutdown during a power outage event.

I finally took some time to lay down a consolidated roadmap to the next major milestone (2.4), and some update on this. 1) new documentation (User and Developer Manuals) -------------------------------------------------------------------------------------- This is the biggest change for 2.4. We will use the new test.networkupstools.org website to create and maintain the content, based upon the

I'll be back one more time perhaps I found the reason of these errors Nov 13 11:09:22 mezenc upsmon[3865]: Poll UPS [mgeups at localhost] failed - Data stale it happens when daemon upsd et upsmon are started after the boot obviously, there isn't any errors when upsd and upsmon are started at boot following later ... -----Message d'origine----- De : goudard sabine Envoy? : mardi

Hello, At my workplace I have exact UPS config as stated in the subject (APC MGE Galaxy 5500 + AP9635CH). I have it set up to work with snmp-ups NUT driver. Despite many readings from *upsc* command I am not receiving "On Line Status" (ups.status OL) nor "On Battery Status" (ups.status OB) and therefore I can't get my systems to shutdown during a power outage event.

Hello all, I wonder if the improvements to a driver called "newmge-shut" which have been mentioned in October 06 got it to the 2.0.5 release? I tried my setup again with this release and still get this "communication lost -> established -> lost -> established" cycle. USB was not working because of the Solaris 8 installation. Regards, Ingo -------------- next part

[the mailing list you want is nut-upsuser.] On Mon, Aug 3, 2009 at 8:05 AM, Blagovest Kolenichev wrote: > Hi, all > > I had fail to find in the supported hardware page > > http://www.networkupstools.org/compat/stable.html > > support for "NOVA AVR 625", but see that "NOVA AVR 600 Serial" > is supported. Can you tell us is there a big difference between

Hello all, I've got an MGE Pulsar Ellipse Premium 800 powering a couple of FreeBSD systems. Driver used is mge-shut, I don't know what the new mge-shut driver offers, but I follow the "if it works, don't fix it" dogma here. :) I also had a nut server installed on the master, with the /usr/local/etc/rc.d/nut script slightly modified to include a couple of upsrw commands

Hi, I've been using NUT for many years to look after the UPS on my home servers. Originally I was using a Compaq R3000 but that was replaced with an MGE Pulsar Evolution 3000 about a couple of years ago because the Compaq one was just too noisy! I'm just setting up a replacement server and would like to connect it using a serial cable as I've found that the USB connection

Hi I have Pulsar 1000 (MGE) and mge-shut 2.0.5-3. By default mge-shut don;t reboot ups after upsmoc -c fsd, only permanent powerdown. After I add ondelay=30 in config, all nice, ups restarted after 10 sec. But according man mge-shut ondelay measured in tens of seconds and by default equal 3. -- Olleg Samoylov

Dear Arjen, Arnaud et al, I've just organized an MGE UPS with Ref. 66074 SNMP/Web Transverse Card for testing purposes. Months ago I found a quite simple bug in the UPS-MIB implementation of this card and Schneider Electric guys seemed not to have intention and/or knowledge to fix it. Now local representative sent me an MGE "Pulsar Extreme 2000 VA" model in order to find an

hello, at first I'm sorry my english isn't perfect but I tried to be clear I work with mandriva 2007 and with nut 2.0.1 installed with urpmi my UPS is a MGE Evolution 2200 connected with RS232 in my ups.conf I try to use mge-utalk driver and also mge-shut both seem to work I don't really known which I add to use It's the first point. As I saw on web site, I add maxage 25 in