Nut upsuser - Oct 2015 - APC Back-UPS ES 650 connected to a Synology DS411slim

I found their source code for what appears to be the previous version of
DSM (their OS), the most recent entry in the NUT Changelog is:

2012-05-31  Arnaud Quette <arnaud.quette at free.fr>

        * [r3643] NEWS, UPGRADING, configure.in, docs/website/news.txt:
          Final update for 2.6.4 release

Ah ha. Nevermind the above, I tried just running upsmon and that worked
(with settings taken from upsd.users on the NAS). Somehow I didn't realize
upsd was not required. However, I do have a follow on question. The only
entry in upsd.users on the NAS has 'upsmon master'. Can I run upsmon on
my
desktop as a slave, or do I need to create another user in upsd.users on
the NAS with 'upsmon slave'?

Thanks,
Dan

On Tue, Oct 13, 2015 at 10:58 PM, Charles Lepple <clepple at gmail.com>
wrote:
> [please use reply-all to include the list.]
>
> > On Oct 12, 2015, at 4:52 PM, Daniel Green <ddgreen at gmail.com>
wrote:
> >
> > I recently connected my UPS to my NAS. The NAS detected the UPS, and I
> checked the "Enable network UPS server" option and added relevant
IPs to
> the "Permitted DiskStation devices" option. The NAS is running
DSM 5.2-5592
> Update 4, with a NUT version of SDS5-2-2015Q1branch-5579-15061.
>
> Hmm, that "NUT version" seems to be an internal Git ID for
Synology, not
> an actual NUT version number. Do they post their source code publicly?
> (It's probably at least NUT 2.7.2, but it would be handy to know what
other
> changes were included, in case some of our standard assumptions no longer
> hold true.)
>
> > I then attempted to connect my desktop via SNMP. My desktop is running
> Arch Linux, with a NUT version of 2.7.3. I seem to be able to connect to
> the NAS, but snmp-ups errors out with the following message:
> >
> > No matching MIB found for sysOID '.1.3.6.1.4.1.8072.3.2.10'!
> > Please report it to NUT developers, with an 'upsc' output for
your
> device.
> > Going back to the classic MIB detection method.
> > No supported device detected
>
> Do you specifically need SNMP support, or can you use the NUT protocol for
> monitoring the UPS on the NAS?
>
> Hopefully, the Synology firmware also has options that correspond to the
> upsd.users file in NUT, which would allow upsmon on your desktop box to log
> in directly to the NUT upsd process on the NAS.
>
> It would be possible to extend snmp-ups to talk to the NAS, but that would
> add an extra upsd and snmp-ups driver process on your desktop, and I'm
not
> sure what benefits that would have over connecting directly using the NUT
> protocol.
>
> > Using the exact same configuration options, I can successfully connect
> from Windows XP using WinNUT 2.0.0.4.
>
> WinNUT, to the best of my knowledge, only uses the NUT network protocol.
>
> --
> Charles Lepple
> clepple at gmail
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20151014/559ed34b/attachment.html>

> On Oct 14, 2015, at 12:01 AM, Daniel Green <ddgreen at gmail.com>
wrote:
> 
> I found their source code for what appears to be the previous version of
DSM (their OS), the most recent entry in the NUT Changelog is:
> 
> 2012-05-31  Arnaud Quette <arnaud.quette at free.fr>
> 
>         * [r3643] NEWS, UPGRADING, configure.in, docs/website/news.txt:
>           Final update for 2.6.4 release
I think that "driver.version.internal: 0.38" puts your version a
little later than that (after NUT 2.7.1), but this is more for my own curiosity
at the moment.
> Ah ha. Nevermind the above, I tried just running upsmon and that worked
(with settings taken from upsd.users on the NAS). Somehow I didn't realize
upsd was not required.
Especially given all of the new topologies with NAS systems, we could use a few
more diagrams to clarify this.
> However, I do have a follow on question. The only entry in upsd.users on
the NAS has 'upsmon master'. Can I run upsmon on my desktop as a slave,
or do I need to create another user in upsd.users on the NAS with 'upsmon
slave'?
I would consider this an implementation detail (though not likely to change):
the "upsmon master" permissions are a superset of the "upsmon
slave" permissions. You should be able to set up your desktop as a slave
using the existing upsd.users.

https://github.com/networkupstools/nut/blob/master/server/user.c#L320

-- 
Charles Lepple
clepple at gmail

Thanks for the help, things seem to be working as desired now.

Dan

On Wed, Oct 14, 2015 at 8:38 AM, Charles Lepple <clepple at gmail.com>
wrote:
>
> > On Oct 14, 2015, at 12:01 AM, Daniel Green <ddgreen at
gmail.com> wrote:
> >
> > I found their source code for what appears to be the previous version
of
> DSM (their OS), the most recent entry in the NUT Changelog is:
> >
> > 2012-05-31  Arnaud Quette <arnaud.quette at free.fr>
> >
> >         * [r3643] NEWS, UPGRADING, configure.in,
docs/website/news.txt:
> >           Final update for 2.6.4 release
>
> I think that "driver.version.internal: 0.38" puts your version a
little
> later than that (after NUT 2.7.1), but this is more for my own curiosity at
> the moment.
>
> > Ah ha. Nevermind the above, I tried just running upsmon and that
worked
> (with settings taken from upsd.users on the NAS). Somehow I didn't
realize
> upsd was not required.
>
> Especially given all of the new topologies with NAS systems, we could use
> a few more diagrams to clarify this.
>
> > However, I do have a follow on question. The only entry in upsd.users
on
> the NAS has 'upsmon master'. Can I run upsmon on my desktop as a
slave, or
> do I need to create another user in upsd.users on the NAS with 'upsmon
> slave'?
>
> I would consider this an implementation detail (though not likely to
> change): the "upsmon master" permissions are a superset of the
"upsmon
> slave" permissions. You should be able to set up your desktop as a
slave
> using the existing upsd.users.
>
> https://github.com/networkupstools/nut/blob/master/server/user.c#L320
>
> --
> Charles Lepple
> clepple at gmail
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20151016/8ee172dd/attachment.html>