Re: Shutdown for APC Back-UPS 350 CS

2003-01-20 Thread Toomas Aas
Hi!

> DEVICE /dev/ttyd0

I had a quick look at my apcupsd.conf and mine says DEVICE /dev/usv, 
where /dev/usv is symlink to /dev/cuaa0. 
--
Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/
* When an agnostic dies, does he go to the "great perhaps"?


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message



Re: Shutdown for APC Back-UPS 350 CS

2003-01-20 Thread Albertus Magnus
On Monday 20 January 2003 05:42, Mark wrote:
> Apparent, CTS changes state. Dunno what RNG does (alarm?), but CTS
> should suffice. Hmm, that kinda makes me wonder, is there not a
> FreeBSD command I can issue myself, via cron or something, to test
> the state of CTS? Then I may not need apcupsd at all.
>
> Thanks for your continual help,
>
> - Mark

I suggest you look at nut in the ports collection.  It will do just 
about anything you need, though it is a bitch to set up (umpteen 
interrelated config files need to be just right).  But more 
importantly, it has lots of good documentation about cables and such.  
I found, for example, that the supposedly correct APC cable for my APC 
BackUPS (one of the semi-dumb ones) was actually missing a line.  I 
made a custom cable, and walla!  no more problem.

Keep in mind, by the way, that the serial cable is not actually sending 
serial data (like ascii text, for example).  It just raises and lowers 
the levels of various lines to signal various things.  (I know you 
probably already know that, but just for completeness...)

And finally, yes, even the dumb UPS's can sense and communicate the loss 
and return of AC power, at the very least.

HTH
Albert

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message



Re: Shutdown for APC Back-UPS 350 CS

2003-01-20 Thread Jack L. Stone
At 09:15 AM 1.20.2003 -0600, Mike Meyer wrote:
>In <[EMAIL PROTECTED]>, Jack L. Stone
<[EMAIL PROTECTED]> typed:
>> At 02:05 AM 1.20.2003 +0100, Per olof Ljungmark wrote:
>> I have been asking WHY have a cable with a dumb UPS for a long time and yet
>> to get a good answer. I have tested with instruments the pins on those
>> cables and very little to nothing found in a way of a signal. If you go to
>> that apcupsd URL and did down you will find all (most) of the cables and it
>> also explains them. SmartUPSes -- yes -- okay and will work with the cable.
>> The computer may sense the dumb UPS -- BUT, will not communicate about
>> shutdown and other critical info. If I'm wrong, then let me know I
>> spent a lot of time falling for the "cable" bit.
>
>Even a "dumb" UPS communicates with the machine - with the right
>cable. The computer gets three signals: On battery power, off battery
>power, and almost out of battery. The computer can send one signal to
>the UPS, telling it to turn off and stay off. The idea is that you use
>the last signal from the UPS to initiate a shutdown, and the last
>thing you do as you shut down is tell the UPS to go off and stay off.
>
>I have as yet to figure out how to get FreeBSD to signal the UPS to
>shut down in a safe way. Anyone else worked on this one? Maybe in 5.0?
>
>   -- 
>Mike Meyer <[EMAIL PROTECTED]> http://www.mired.org/consulting.html
>Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.
>

Let me clarify that I did not coin the classification "smartUPSes" and
"dumbUPSes", but suffice it to say that anyone who buys a UPS without the
ability to fully communicate as does the ones designated as "SmartUPS" (or
SmartPro... too?) should not expect the results of one. There are two
classes - "smart" and "dumb" as far as I know. So, before buying and one
wants to have full bi-directional functionality, make sure it has the
capability. Don't just go by "it has a cable" and let the cable fool you
otherwise. Unfortunately, I have never seen a box that explained this on
the outside or even the inside of a "dumb" one -- with cable.

Best regards,
Jack L. Stone,
Administrator

SageOne Net
http://www.sage-one.net
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message



Re: Shutdown for APC Back-UPS 350 CS

2003-01-20 Thread Mike Meyer
In <[EMAIL PROTECTED]>, Jack L. Stone 
<[EMAIL PROTECTED]> typed:
> At 02:05 AM 1.20.2003 +0100, Per olof Ljungmark wrote:
> I have been asking WHY have a cable with a dumb UPS for a long time and yet
> to get a good answer. I have tested with instruments the pins on those
> cables and very little to nothing found in a way of a signal. If you go to
> that apcupsd URL and did down you will find all (most) of the cables and it
> also explains them. SmartUPSes -- yes -- okay and will work with the cable.
> The computer may sense the dumb UPS -- BUT, will not communicate about
> shutdown and other critical info. If I'm wrong, then let me know I
> spent a lot of time falling for the "cable" bit.

Even a "dumb" UPS communicates with the machine - with the right
cable. The computer gets three signals: On battery power, off battery
power, and almost out of battery. The computer can send one signal to
the UPS, telling it to turn off and stay off. The idea is that you use
the last signal from the UPS to initiate a shutdown, and the last
thing you do as you shut down is tell the UPS to go off and stay off.

I have as yet to figure out how to get FreeBSD to signal the UPS to
shut down in a safe way. Anyone else worked on this one? Maybe in 5.0?

  http://www.mired.org/consulting.html
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message



Re: Shutdown for APC Back-UPS 350 CS

2003-01-20 Thread Mark
- Original Message -
From: "Jack L. Stone" <[EMAIL PROTECTED]>
To: "Per olof Ljungmark" <[EMAIL PROTECTED]>
Cc: "Mark" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, January 20, 2003 2:22 AM
Subject: Re: Shutdown for APC Back-UPS 350 CS

> At 02:05 AM 1.20.2003 +0100, Per olof Ljungmark wrote:
>
> > 
> >
> >> To do what you want requires a UPS with "SmartUPS" to "talk" to your
> >> system. You have what is referred to as a "dumb UPS". I use SmartUPSes
> >> on "master" machines to tell the "slave" machines when to shut down and
> >> other instructions. The SmartUPSes will carry on an exchange with the
> >> machine, but the dumb ones will not. The slaves are attached to the
> >> dumb UPSes for continuations of power, but the SmartUPS tells each
> >> slave what to do and when to shut down. Each slave must have an apcupsd
> >> daemon installed, running and configured to communicate with the master
> >> over the network for this to work. 
> >
> > But why then supply a cable for use between the 350CS and the computer?
> > I use only SmartUPS and BackUPS Pro so I could not be sure but...
> >
> > Per olof
>
> I have been asking WHY have a cable with a dumb UPS for a long time and
> yet to get a good answer. I have tested with instruments the pins on those
> cables and very little to nothing found in a way of a signal. If you go to
> that apcupsd URL and did down you will find all (most) of the cables and
> it also explains them. SmartUPSes -- yes -- okay and will work with the
> cable. The computer may sense the dumb UPS -- BUT, will not communicate
> about shutdown and other critical info. If I'm wrong, then let me know
> I spent a lot of time falling for the "cable" bit.
>
> Dumb UPSes are useful for keeping the machines going until you or a master
> machine can tell it to shut down gracefully
>
> Best regards,
> Jack L. Stone,
> Administrator


Thanks for the replies, guys; I really appreciate it. :)

The BackUPS 350 CS is not supposed to be truly 'dumb', but allegedly can
report power-failure over its cable. So, I ran "apctest", and a line change
of sorts IS noted:

--
2003-01-20 11:32:31 apctest 3.8.5 (4 January 2002) freebsd
Checking configuration ...

Select test number: 1

2003-01-20 11:21:22 IOCTL GET: 5 LE RTS
2003-01-20 11:21:32 Test 1: normal condition, completed.

Select test number: 3

For the third test, the serial cable should be plugged
back into the UPS, but the AC power plug to the UPS should be DISCONNECTED.

Please enter any character when ready to continue:

2003-01-20 11:23:10 IOCTL GET: a5 LE RTS CTS RNG
2003-01-20 11:23:20 Test 3: no power, completed.
--

Apparent, CTS changes state. Dunno what RNG does (alarm?), but CTS should
suffice. Hmm, that kinda makes me wonder, is there not a FreeBSD command I
can issue myself, via cron or something, to test the state of CTS? Then I
may not need apcupsd at all.

Thanks for your continual help,

- Mark


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message



Re: Shutdown for APC Back-UPS 350 CS

2003-01-19 Thread Jack L. Stone
At 02:05 AM 1.20.2003 +0100, Per olof Ljungmark wrote:
>
>> To do what you want requires a UPS with "SmartUPS" to "talk" to your
>> system. You have what is referred to as a "dumb UPS". I use SmartUPSes on
>> "master" machines to tell the "slave" machines when to shut down and other
>> instructions. The SmartUPSes will carry on an exchange with the machine,
>> but the dumb ones will not. The slaves are attached to the dumb UPSes for
>> continuations of power, but the SmartUPS tells each slave what to do and
>> when to shut down. Each slave must have an apcupsd daemon installed,
>> running and configured to communicate with the master over the network for
>> this to work.
>
>
>But why then supply a cable for use between the 350CS and the computer?
>I use only SmartUPS and BackUPS Pro so I could not be sure but...
>
>Per olof
>

I have been asking WHY have a cable with a dumb UPS for a long time and yet
to get a good answer. I have tested with instruments the pins on those
cables and very little to nothing found in a way of a signal. If you go to
that apcupsd URL and did down you will find all (most) of the cables and it
also explains them. SmartUPSes -- yes -- okay and will work with the cable.
The computer may sense the dumb UPS -- BUT, will not communicate about
shutdown and other critical info. If I'm wrong, then let me know I
spent a lot of time falling for the "cable" bit.

Dumb UPSes are useful for keeping the machines going until you or a master
machine can tell it to shut down gracefully

Best regards,
Jack L. Stone,
Administrator

SageOne Net
http://www.sage-one.net
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message



Re: Shutdown for APC Back-UPS 350 CS

2003-01-19 Thread Per olof Ljungmark


To do what you want requires a UPS with "SmartUPS" to "talk" to your
system. You have what is referred to as a "dumb UPS". I use SmartUPSes on
"master" machines to tell the "slave" machines when to shut down and other
instructions. The SmartUPSes will carry on an exchange with the machine,
but the dumb ones will not. The slaves are attached to the dumb UPSes for
continuations of power, but the SmartUPS tells each slave what to do and
when to shut down. Each slave must have an apcupsd daemon installed,
running and configured to communicate with the master over the network for
this to work.



But why then supply a cable for use between the 350CS and the computer?
I use only SmartUPS and BackUPS Pro so I could not be sure but...

Per olof


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message



Re: Shutdown for APC Back-UPS 350 CS

2003-01-19 Thread Jack L. Stone
At 01:08 AM 1.20.2003 +0100, Mark wrote:
>I know I have asked this before, a month or so ago, but I am still rather
>stuck with this. So, if anyone has a useful suggestion, I would appreciate
>you sharing it with me.
>
>Has anyone ever managed to get the APC Back-UPS 350 CS to shutdown? It runs
>on /dev/ttyd0, with the appropriate cable. But it never sees the power go
>off-line, and, hence, does not go into shutdown mode. :( When I do an
>"apcaccess status", it gives me this:
>
>--
>DATE : Mon Jan 20 01:02:14 CET 2003
>HOSTNAME : asarian-host.net
>RELEASE  : 3.8.5
>UPSNAME  : UPS_IDEN
>CABLE: APC Cable 940-0128A
>MODEL: BackUPS
>UPSMODE  : Stand Alone
>STARTTIME: Sun Jan 19 19:54:05 CET 2003
>LINEFAIL : OK
>BATTSTAT : OK
>STATFLAG : 0x008 Status Flag
>END APC  : Mon Jan 20 01:02:14 CET 2003
>--
>
>It all seems dandy, but it just will not notice the power-loss. :( Has
>anyone ever got this to work on FreeBSD 4.7 (the machine the APC Back-UPS
>350 CS runs on)?
>
>Thanks.
>
>- Mark
>

To do what you want requires a UPS with "SmartUPS" to "talk" to your
system. You have what is referred to as a "dumb UPS". I use SmartUPSes on
"master" machines to tell the "slave" machines when to shut down and other
instructions. The SmartUPSes will carry on an exchange with the machine,
but the dumb ones will not. The slaves are attached to the dumb UPSes for
continuations of power, but the SmartUPS tells each slave what to do and
when to shut down. Each slave must have an apcupsd daemon installed,
running and configured to communicate with the master over the network for
this to work.

Best regards,
Jack L. Stone,
Administrator

SageOne Net
http://www.sage-one.net
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message



Re: Shutdown for APC Back-UPS 350 CS

2003-01-19 Thread Mark
- Original Message -
From: "Per olof Ljungmark" <[EMAIL PROTECTED]>
To: "Mark" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, January 20, 2003 1:31 AM
Subject: Re: Shutdown for APC Back-UPS 350 CS

> Mark wrote:
>
> > I know I have asked this before, a month or so ago, but I am still
> > rather stuck with this. So, if anyone has a useful suggestion, I would
> > appreciate you sharing it with me.
> >
> > Has anyone ever managed to get the APC Back-UPS 350 CS to shutdown? It
> > runs on /dev/ttyd0, with the appropriate cable. But it never sees the
> > power go off-line, and, hence, does not go into shutdown mode. :( When I
> > do an "apcaccess status", it gives me this:
> >
> > --
> >
> > DATE : Mon Jan 20 01:02:14 CET 2003
> > HOSTNAME : asarian-host.net
> > RELEASE  : 3.8.5
> > UPSNAME  : UPS_IDEN
> > CABLE: APC Cable 940-0128A
> > MODEL: BackUPS
> > UPSMODE  : Stand Alone
> > STARTTIME: Sun Jan 19 19:54:05 CET 2003
> > LINEFAIL : OK
> > BATTSTAT : OK
> > STATFLAG : 0x008 Status Flag
> > END APC  : Mon Jan 20 01:02:14 CET 2003
> >
> > --
> >
> > It all seems dandy, but it just will not notice the power-loss. :( Has
> > anyone ever got this to work on FreeBSD 4.7 (the machine the APC
> > Back-UPS 350 CS runs on)?
>
> I don't know specifically about the 350CS, about the only thing I know
> is you have to have exactly the right cable/software combination. Did
> you confirm that there is a 940-0128A between the units? Perhaps trying
> other options as advised at
> http://www.sibbald.com/apcupsd/3.8manual/configure.html#ConfigGeneral
> could give you a hint in the right direction.


Thank you for the quick reply. Yes, I have the correct cable; in fact, APC
specifically sent it to me as I could not get USB to work at all (seems not
yet supported on FreeBSD), and the number is stamped in the cable.

I am familiar with the document you pointed me to, and I believe I set
everything according to how it should be; here is my config (stripped off
comments):

UPSCABLE 940-0128A
UPSTYPE backups
DEVICE /dev/ttyd0
LOCKFILE /var/spool/lock
BATTERYLEVEL 10
MINUTES 3
TIMEOUT 15
ANNOY 10
ANNOYDELAY 5
NOLOGON always
KILLDELAY 0
NETSERVER off
NISPORT 7000
EVENTSFILE /var/log/apcupsd.events
STATTIME 3600
STATFILE /var/log/apcupsd.status
LOGSTATS off
DATATIME 0
UPSNAME UPS_IDEN
BEEPSTATE 0
LOWBATT 2
UPSCLASS standalone
UPSMODE disable
NETACCESS true

Understanding the docs right, the "TIMEOUT 15" should start a forced
shutdown after 15 secs of power loss (set so low for test-purposes). Alas,
nothing happens. :(

Thanks anyway.

- Mark


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message



Re: Shutdown for APC Back-UPS 350 CS

2003-01-19 Thread Per olof Ljungmark
Mark wrote:

I know I have asked this before, a month or so ago, but I am still rather
stuck with this. So, if anyone has a useful suggestion, I would appreciate
you sharing it with me.

Has anyone ever managed to get the APC Back-UPS 350 CS to shutdown? It runs
on /dev/ttyd0, with the appropriate cable. But it never sees the power go
off-line, and, hence, does not go into shutdown mode. :( When I do an
"apcaccess status", it gives me this:

--
DATE : Mon Jan 20 01:02:14 CET 2003
HOSTNAME : asarian-host.net
RELEASE  : 3.8.5
UPSNAME  : UPS_IDEN
CABLE: APC Cable 940-0128A
MODEL: BackUPS
UPSMODE  : Stand Alone
STARTTIME: Sun Jan 19 19:54:05 CET 2003
LINEFAIL : OK
BATTSTAT : OK
STATFLAG : 0x008 Status Flag
END APC  : Mon Jan 20 01:02:14 CET 2003
--

It all seems dandy, but it just will not notice the power-loss. :( Has
anyone ever got this to work on FreeBSD 4.7 (the machine the APC Back-UPS
350 CS runs on)?


I don't know specifically about the 350CS, about the only thing I know 
is you have to have exactly the right cable/software combination. Did 
you confirm that there is a 940-0128A between the units? Perhaps trying 
other options as advised at
http://www.sibbald.com/apcupsd/3.8manual/configure.html#ConfigGeneral
could give you a hint in the right direction.

Cheers,
Per olof


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message