Topic: UPS Comments please !

[Graham]

Hi !

I wonder if anyone can comment here ?

I have purchased an APC Back-UPS CS 350 for a client.

Details here :-

Type UPS            Uninterruptable PSUs        Mfr APC
Description                           Availability        Price(exc/inc)
BackUPS 350EI 350VA         25 1-3 days                   £55.00 £64.62
Mfr code: BK350EI    Quicklinx: 11X1WS      www.dabs.com


The UPS is described in the APCUPSD manual "Apcupsd Post Installation
Configuration" as being supported and using 'simple' signaling as below


Apcupsd UPSTYPE | APC Model UPS | Signaling | Cables Supported | Status
Keyword
 
backups | BackUPS CS (serial mode) | Simple | 940-0128A | Supported


I have installed dmc-mitel-apcupsd-3.8.5-3.noarch.rpm and associated
RH daemon

My cable [940-0128A] does not appear in the drop down list nor is
described in the 'Cables' section of the documentation - although
it is shown as an example in the testing section for dumb ups ?

I set the manager for 940-0020B type cable and the system is shutdown
after a TIMEOUT which seems to work ok.

What I am not sure of is wether the UPS should come out of mains
faiure mode and stop beeping ?

If I re-apply mains I seem to get into some kind of fibrillation
mode with the UPS rapidly switching back and forth between mains
and battery. Holding the button on the front of the UPS with the
mains off seems to cure this ? Is there some kind of reset time?
The manual (piece of paper) witht the UPS doesnt describe re-starts.

Also, when the power is re-applyed the system power button needs to
be activated to boot the system back up [Isnt this just a function
of ATX PSU's anyway ?]

Another thing I have noticed is that the --killpower part of the
script didnt look like it worked although I cant trace this as I
cant find any log file where this is being recorded (it possibly isnt ?)

Any help / comments very much appreciated !


[root@server /]#
Broadcast message from root Mon Dec  2 22:58:27 2002...

Warning power loss detected with UPS UPS_IDEN

Broadcast message from root Mon Dec  2 22:58:32 2002...

Power failure on UPS UPS_IDEN. Running on batteries.

Broadcast message from root Mon Dec  2 22:59:07 2002...

Battery time limit exceded on UPS UPS_IDEN. Doing shutdown.

Broadcast message from root Mon Dec  2 22:59:07 2002...

UPS UPS_IDEN initiated Shutdown Sequence

Broadcast message from root Mon Dec  2 22:59:07 2002...

apcupsd UPS UPS_IDEN initiated shutdown
The system is going down for system halt NOW !!

[Ray Mitchell]

Graham

> My cable [940-0128A] does not appear in the drop down list nor is
> described in the 'Cables' section of the documentation - although
> it is shown as an example in the testing section for dumb ups ?

It is probably OK to select another "simple dumb" cable type
Check the APCUPSD manual for setup details, it gives an extensive list of compatible cable types.

> Also, when the power is re-applyed the system power button needs to
> be activated to boot the system back up [Isnt this just a function
> of ATX PSU's anyway ?]

You need to go into the servers bios to enable "boot up when AC power returns". Then the server will automatically resart without needing to push the power switch.

Regards
Ray Mitchell

[Graham]

Thanks for reply Ray !

I tried the simple type - it didnt shutdown properly at all - the UPS just dropped mains !! FS didnt like that at all !

I will try APC tech and see which cable numbers are equivelant to which !!

The BIOS - I havent seen that feature . . .

Will check it out though  . . .


Thanks !

[Kelvin]

Hi Graham,

I can share my own experience with the BackUPS series (as I have used quite a few - mostly the 650VA model).

Here are my comments (as I have experienced them myself)

1. They are 'dumb' UPSes - call it no frills if you must
2. Like you, I set the cable type to the 020B cable (closest match)
3. The killpower switch will NOT power down the UPS
4. The UPS does not know how to reboot the Server after the mains power is restored (nothing to do with the BIOS setting) because if you actually tested, you will find that the UPS continues to supply power out of the power receptacles even though the server has shut down. Therefore, the BIOS NEVER knows that power was lost and restored unless you manually turned off the UPS after the server shutdown and manually restarted the UPS again.
5. Because the UPS continues to operate after the server shutdown, it continues to beep as long as the power has not come back - yes I've had sites that totally drained the batteries this way due to an extended blackout and the staff did not bother to switch off the annoying beeping thingamajig !

However, I did not encounter the problem of the relays switching between battery and mains after reapplying power.

I have not tried the BackUPS Pro range yet (as they cost more) and for a little more than the Pro range you could get the Smart series which can make use of all the features of APCUPSD. However, APC actually have a Linux based software as well. If I ever find the opportuity to do so, I will try it to see if it gives better control over the BackUPS series than apcupsd.

Kelvin

[Graham]

Kelvin,

That answers most of my questions and confirms my suspicions !

I would like to test the APC Linux software - I will look at their site now !

Many Thanks Kelvin !

[Graham]

Hi !

Checked the APC stuff - There is a small simple signalling demon that requires compiling - from the docs it looks fairly old and as I havent got gcc etc on board
I didnt bother making it.

After that there is a full blown X - App for RH or SuSE - looks nice but obvioulsy SME doesnt have nor need X - so - think I will stick with the recommended solution.

Thanks for reading this !

[Ray Mitchell]

Graham

I have setup an APC Back-UPS 650  UPS (which as far as I can determine is a dumb UPS) with powstatd and it works quite good. The cable type I used was as supplied with the unit, a 940-0020C, green plug on one end grey plug on the other. I did purchase another cable which was supposedly for Linux boxes (as advised by APC tech support), a 940-0023A, but that did not work properly so it was a waste.

I did try APCUPSD with this UPS but had problems shutting it down and restarting it etc, so they do not seem compatible.

Powstatd is perhaps not as fancy as APCUPSD but it does the job OK.
It will shut down the server and UPS and restart them when power returns (as long as the BIOS startup option is set). You can delay the shut down time after mains fails and if the battery nears exhaustion it will signal the server to shutdown immediately.

Powstad may be worth trying, it does not have the nice server manager interface but is quite easy to set up, and it is configurable for different UPS's, and possibly also caters for different cables which have different signals on different pins. Read the new HOWTO mentioned below and you will understand what I mean.
I think the 350 you mentioned is similar to a 650, ie both are dumb, but it does not smooth out the mains as nicely.

The current contrib HOWTO is outdated and the old rpms it refers to only work on e-smith v4.1.2, but I have just recently put together an updated HOWTO for powstatd on v5.5. It is about to be put on the web site but is not there yet. If you want a copy I can email it to you. Please let me know.

Regards
Ray Mitchell

[Graham]

Thanks Ray,

I got apcupsd / server manager to work ok for just basic shutdown.

I of course would be interested in any developments for the future !

Thanks

Graham

ps I also used the other UPS outlets for :-

ISDN Telephone System and ISDN TA

It holds out on batteries for 20 mins, easily enough time to get
the admin email and for me to ring the office !!!

I amazed that people are still ploughing lots of cash into W2KServer
or Back Office SBE when SME does most of what you want !!!

[Lightman]

Hi Ray Mitchell.

I was reading the thread and since I have sme 5.5 and the same UPS
to setup with APC backup 650 , I would like to receive, if you can
and have the time, the Updated HOWTO , could you send it to me by
the mail showed here?.

Sorry to bother you, but I really need it

TIA (A lot !)

see you

Lightman

[Ray Mitchell]

Dear Lightman
The Powstatd HOWTO is at
http://www.e-smith.org/docs/howto/contrib/powstatdUPSHOWTOv5.5v5.6.txt

Regards
Ray Mitchell

[Lightman]

Hi Ray Mitchell

Downloaded & reading it right now.

Thanks a lot

see you

Lightman

[lightman]

Hi!

I downloaded the powstatdHOWTOv5_5v5_6.txt and also a cables
howto, so I can build the correct cable and configure powstatd and
have some errors, I didn't understand very good what causes it, since
I couldn't find enough documentation of how powstatd works (I will
keep looking but in the meantime maybe some of you knows about
it).

I'm runing now SME 5.5 , My UPS is APC Backup 650 the cable
was wired as follows:

RS232                                 UPS
DTR --/\/\/\/\/\/\---*
                         |
CTS -----------------*------------ 5 Low battery
GND ------------------------------4 Ground
DCD -------------------------------2 On Battery
RTS -------------------------------1 Kill UPS

So,I follow the instructions in the howto to configure the UPS and
test powstatd status, so I did:

in /sbin/e-smith
./db configuration set powstatd service \
watch ttyS0 init0 rts init1 dtr fail dcd,0 kill rts,1 low cts,0

all ok, no problems so far, then powstatd -t and....... powstatd says:

powstatd: ignoring unrecognized configuration line watch
powstatd: ignoring unreconigzed configuration line fail
powstatd: ignoring unrecognized configuration line low

powstatd: no UPS to watch; quitting.



serial port is COM1 , tested with a mouse and serial terminal
so I'm sure about that, is not the wrong one.

I'm lost.

any ideas?.
my SME is configured as server only .

TIA !

see you

Lightman

[lightman]

Hi, It's me again
I reply to myself, the errors commented before was due to
a incomplete /etc/powstatd.conf

so I use the template in /usr/share/doc/powstatd-1.4.1/
to create one that reflects my current cable settings, those where

watch ttyS0
init rts 0   (Because it was 1 by default and turn off my UPS )
kill rts 1
init dtr 1
fail dcd 1
low cts 0

then replace the /etc/powstatd.conf by this one and then powstatd -t
and I'm testing the signals right now while I'm typing this post, fail
signal it's OK, now waiting for LOW BATT signal, since the UPS is
650 and I have a PII CPU with no HD just as dummy load, it would
take a while to get the LOW batt I think

now, Did I do something wrong editing /etc/powstatd.conf ?, since
it says that I shouldn't touch it, instead edit the templates, but
the templates didn't allow me to test powstatd -t

should I do the "db configuration set powstatd service...." stuff
anyway??.

thanks in advance

see you

Lightman

[brian kirk]

Hi Lightman - I too am wrestling with this. I had to add a conf file /etc/powstatd.conf to get powstatd -t to work. Also some useful stuff here http://www.apcupsd.com/manual/apctest.html. Let me know if you get it working.
Regards
Brian

[Ray Mitchell]

I think you need to read the HOWTO again and follow the directions carefully.

From the HOWTO the "stuff"
/sbin/e-smith/db configuration set powstatd service \
watch ttyS0 init0 rts init1 dtr fail dsr,0 kill rts,1 low cts,0
/sbin/e-smith/signal-event console-save

is what you do at the beginning and this should create a suitable powstatd.conf. If the values are not correct for your particular UPS, this will become apparent during testing, and you can then make changes as required.

To quote "If it is (ie your UPS is listed) you're in luck and can run the command in the README as configured to modify the e-smith database for your UPS configuration - if it's
not use a config that is close for testing."

If changes are needed then you redo the "stuff"
To quote "You would update the config:
/sbin/e-smith/db configuration set powstatd service \
watch ttyS0 init0 rts init1 dtr fail dcd,0 kill rts,1 low cts,0
with the obviously different values you determined during testing.

Please also note the omission of one command in the section towards the end of the HOWTO which enables powstatd at startup (this is nothing to do with your problems re powstatd.conf).

then do

/sbin/e-smith/db configuration setprop powstatd status enabled
/sbin/e-smith/signal-event console-save
/etc/rc.d/init.d/powstatd start

shutdown and connect your e-smith box to the UPS and reboot.
That's it.


Hope this helps
Regards
Ray Mitchell