Nut upsuser - Jan 2020 - [EXTERNAL] Re: Tripp Lite SMART1500LCD will not stay shut down when power is disconnected

Thanks Ken.
I'll plan to sit down and look up the protocol information over the next
week or so and follow up.
________________________________
From: Ken Olum <kdo at cosmos.phy.tufts.edu>
Sent: Tuesday, January 14, 2020 1:35:10 PM
To: David Zomaya
Cc: kdo at cosmos.phy.tufts.edu; layne.fowler at gmail.com; nut-upsuser at
alioth-lists.debian.net
Subject: [EXTERNAL] Re: [Nut-upsuser] Tripp Lite SMART1500LCD will not stay shut
down when power is disconnected

This is an EXTERNAL email.  Please take a moment and think before clicking any
links or opening any attachments from this email.  If suspicious, please forward
to ishelpdesk at tripplite.com for review.

______________________________________________________________________
Hi, David.  Thanks for the offer of help.  I have BCPERS450 serial
number 2701DVHBC809300177.  Unfortunately I'm about to go on a trip and
will be away until the end of the month, so I don't have much time to
discuss these things at the moment, but maybe Layne will have something
to say.

My understanding from when I was working on this a couple years ago is
that the main problem in getting NUT working right with Tripp-Lite
equipment is to understand the mappings of the various controls.  For
example, we have ReportID: 0x15, which maps to
UPS.OutletSystem.Outlet.DelayBeforeShutdown.  I think this mapping is
given by the UPS.  NUT than maps this control to load.off.delay.  Is
that mapping correct, i.e., does setting the control in the UPS do the
function that NUT expects?

More importantly, is there anything in the UPS that NUT should be
mapping to load.on.delay?  It does not find such an object, so
load.on.delay is not mapped, which was the original source of the
problem.

Incidentally, according to my old notes, when I ask my UPS to shut
down in ten seconds by setting UPS.OutletSystem.Outlet.DelayBeforeShutdown,
it shuts down even if the power comes back on during those ten seconds.
This is the right behavior because once I send the command I shut down
my system and it needs the power cycle to restart.  My understanding is
that Layne's system does not do this, so there is some difference in
configuration or between the different models.

The only corner case affecting my system that I am aware of is this:
suppose the line power comes back at the same time that my system has
decided to shut down.  The UPS tries to notify the system that the power
is back on, but it's too late and the system is already in the process of
sending the UPS.OutletSystem.Outlet.DelayBeforeShutdown.  Having done
so, the system thinks the UPS will shut off and so shuts down.  However,
because the power was on by the time that UPS actually received the
command, it does not in fact shut off.  Thus the system is shut down and
never reboots.  I don't know how this case is supposed to be handled.

Thanks again.

                                        Ken




________________________________
This message is for the addressee's use only. It may contain confidential
information. If you receive this message in error, please delete it and notify
the sender. Tripp Lite disclaims all warranties and liabilities, and assumes no
responsibility for viruses which may infect an email sent to you from Tripp Lite
and which damage your electronic systems or information. It is your
responsibility to maintain virus detection systems to prevent damage to your
electronic systems and information.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200115/731b9055/attachment-0001.html>

My serial # is 2835BY0SM886900639, model # SMART1500LCD.

Using stock nut, my UPS will turn back on after load off, even with no
power connected. Servers boot up and fail when the UPS finally dies.

Using my patched nut, the UPS will fail to turn on if the power returns
after the shutdown command but before actual load off.

It seems like this UPS is missing the "load.on" and/or
"load.on.delay"
instant commands.

Thanks again David for offering your help. Let me know if I can give you
any other information you need.

On Tue, Jan 14, 2020 at 7:48 PM David Zomaya <David_Zomaya at
tripplite.com>
wrote:
> Thanks Ken.
> I'll plan to sit down and look up the protocol information over the
next
> week or so and follow up.
> ------------------------------
> *From:* Ken Olum <kdo at cosmos.phy.tufts.edu>
> *Sent:* Tuesday, January 14, 2020 1:35:10 PM
> *To:* David Zomaya
> *Cc:* kdo at cosmos.phy.tufts.edu; layne.fowler at gmail.com;
> nut-upsuser at alioth-lists.debian.net
> *Subject:* [EXTERNAL] Re: [Nut-upsuser] Tripp Lite SMART1500LCD will not
> stay shut down when power is disconnected
>
> This is an EXTERNAL email.  Please take a moment and think before clicking
> any links or opening any attachments from this email.  If suspicious,
> please forward to ishelpdesk at tripplite.com for review.
>
> ______________________________________________________________________
> Hi, David.  Thanks for the offer of help.  I have BCPERS450 serial
> number 2701DVHBC809300177.  Unfortunately I'm about to go on a trip and
> will be away until the end of the month, so I don't have much time to
> discuss these things at the moment, but maybe Layne will have something
> to say.
>
> My understanding from when I was working on this a couple years ago is
> that the main problem in getting NUT working right with Tripp-Lite
> equipment is to understand the mappings of the various controls.  For
> example, we have ReportID: 0x15, which maps to
> UPS.OutletSystem.Outlet.DelayBeforeShutdown.  I think this mapping is
> given by the UPS.  NUT than maps this control to load.off.delay.  Is
> that mapping correct, i.e., does setting the control in the UPS do the
> function that NUT expects?
>
> More importantly, is there anything in the UPS that NUT should be
> mapping to load.on.delay?  It does not find such an object, so
> load.on.delay is not mapped, which was the original source of the
> problem.
>
> Incidentally, according to my old notes, when I ask my UPS to shut
> down in ten seconds by setting UPS.OutletSystem.Outlet.DelayBeforeShutdown,
> it shuts down even if the power comes back on during those ten seconds.
> This is the right behavior because once I send the command I shut down
> my system and it needs the power cycle to restart.  My understanding is
> that Layne's system does not do this, so there is some difference in
> configuration or between the different models.
>
> The only corner case affecting my system that I am aware of is this:
> suppose the line power comes back at the same time that my system has
> decided to shut down.  The UPS tries to notify the system that the power
> is back on, but it's too late and the system is already in the process
of
> sending the UPS.OutletSystem.Outlet.DelayBeforeShutdown.  Having done
> so, the system thinks the UPS will shut off and so shuts down.  However,
> because the power was on by the time that UPS actually received the
> command, it does not in fact shut off.  Thus the system is shut down and
> never reboots.  I don't know how this case is supposed to be handled.
>
> Thanks again.
>
>                                         Ken
>
>
>
>
> ------------------------------
> This message is for the addressee's use only. It may contain
confidential
> information. If you receive this message in error, please delete it and
> notify the sender. Tripp Lite disclaims all warranties and liabilities, and
> assumes no responsibility for viruses which may infect an email sent to you
> from Tripp Lite and which damage your electronic systems or information. It
> is your responsibility to maintain virus detection systems to prevent
> damage to your electronic systems and information.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200115/1d829a8d/attachment.html>

Thanks Layne.
Ball is in my court to get back to both of you.

Feel free to nudge me if I don't update in a week or so.

________________________________
From: Layne Fowler <layne.fowler at gmail.com>
Sent: Tuesday, January 14, 2020 11:47:01 PM
To: David Zomaya
Cc: Ken Olum; nut-upsuser at alioth-lists.debian.net
Subject: Re: [EXTERNAL] Re: [Nut-upsuser] Tripp Lite SMART1500LCD will not stay
shut down when power is disconnected

My serial # is 2835BY0SM886900639, model # SMART1500LCD.

Using stock nut, my UPS will turn back on after load off, even with no power
connected. Servers boot up and fail when the UPS finally dies.

Using my patched nut, the UPS will fail to turn on if the power returns after
the shutdown command but before actual load off.

It seems like this UPS is missing the "load.on" and/or
"load.on.delay" instant commands.

Thanks again David for offering your help. Let me know if I can give you any
other information you need.

On Tue, Jan 14, 2020 at 7:48 PM David Zomaya <David_Zomaya at
tripplite.com<mailto:David_Zomaya at tripplite.com>> wrote:
Thanks Ken.
I'll plan to sit down and look up the protocol information over the next
week or so and follow up.
________________________________
From: Ken Olum <kdo at cosmos.phy.tufts.edu<mailto:kdo at
cosmos.phy.tufts.edu>>
Sent: Tuesday, January 14, 2020 1:35:10 PM
To: David Zomaya
Cc: kdo at cosmos.phy.tufts.edu<mailto:kdo at cosmos.phy.tufts.edu>;
layne.fowler at gmail.com<mailto:layne.fowler at gmail.com>; nut-upsuser
at alioth-lists.debian.net<mailto:nut-upsuser at alioth-lists.debian.net>
Subject: [EXTERNAL] Re: [Nut-upsuser] Tripp Lite SMART1500LCD will not stay shut
down when power is disconnected

This is an EXTERNAL email.  Please take a moment and think before clicking any
links or opening any attachments from this email.  If suspicious, please forward
to ishelpdesk at tripplite.com<mailto:ishelpdesk at tripplite.com> for
review.

______________________________________________________________________
Hi, David.  Thanks for the offer of help.  I have BCPERS450 serial
number 2701DVHBC809300177.  Unfortunately I'm about to go on a trip and
will be away until the end of the month, so I don't have much time to
discuss these things at the moment, but maybe Layne will have something
to say.

My understanding from when I was working on this a couple years ago is
that the main problem in getting NUT working right with Tripp-Lite
equipment is to understand the mappings of the various controls.  For
example, we have ReportID: 0x15, which maps to
UPS.OutletSystem.Outlet.DelayBeforeShutdown.  I think this mapping is
given by the UPS.  NUT than maps this control to load.off.delay.  Is
that mapping correct, i.e., does setting the control in the UPS do the
function that NUT expects?

More importantly, is there anything in the UPS that NUT should be
mapping to load.on.delay?  It does not find such an object, so
load.on.delay is not mapped, which was the original source of the
problem.

Incidentally, according to my old notes, when I ask my UPS to shut
down in ten seconds by setting UPS.OutletSystem.Outlet.DelayBeforeShutdown,
it shuts down even if the power comes back on during those ten seconds.
This is the right behavior because once I send the command I shut down
my system and it needs the power cycle to restart.  My understanding is
that Layne's system does not do this, so there is some difference in
configuration or between the different models.

The only corner case affecting my system that I am aware of is this:
suppose the line power comes back at the same time that my system has
decided to shut down.  The UPS tries to notify the system that the power
is back on, but it's too late and the system is already in the process of
sending the UPS.OutletSystem.Outlet.DelayBeforeShutdown.  Having done
so, the system thinks the UPS will shut off and so shuts down.  However,
because the power was on by the time that UPS actually received the
command, it does not in fact shut off.  Thus the system is shut down and
never reboots.  I don't know how this case is supposed to be handled.

Thanks again.

                                        Ken




________________________________
This message is for the addressee's use only. It may contain confidential
information. If you receive this message in error, please delete it and notify
the sender. Tripp Lite disclaims all warranties and liabilities, and assumes no
responsibility for viruses which may infect an email sent to you from Tripp Lite
and which damage your electronic systems or information. It is your
responsibility to maintain virus detection systems to prevent damage to your
electronic systems and information.
________________________________
This message is for the addressee's use only. It may contain confidential
information. If you receive this message in error, please delete it and notify
the sender. Tripp Lite disclaims all warranties and liabilities, and assumes no
responsibility for viruses which may infect an email sent to you from Tripp Lite
and which damage your electronic systems or information. It is your
responsibility to maintain virus detection systems to prevent damage to your
electronic systems and information.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200115/95234389/attachment-0001.html>