Re: [Nut-upsuser] Multi UPS Monitoring

[Julian H. Stacey]

> > I've read through as many relevant mailing list posts and public blog =
> posts as I could, but I can't seem to find an answer to my issue.
> >=20
> > I currently have 2x Tripp Lite SMART1500LCDXLs, and I am attempting to =
> monitor both of them with the same Raspberry Pi using NUT.

Rasp. Pi, x86 or amd is irrelevant as Pi runs Linux & BSD etc.
Relevant is: What OS ?

If you connect a USB device (mem stick, triplite ups or disc whatevere)
to a FreeBSD computer (PC, rasp. i386 amd64 whatever) the
computer will show serial numbers with all of;
dmesg
vi /var/log/messages
kill -9 `cat /var/run/devd.pid` ; /sbin/devd -d

Cheers,
-- 
Julian Stacey, Consultant Sys. Eng. BSD Linux Unix, Munich & Aachen
http://berklix.com/jhs/cv/  
Crash Brexit in 12 weeks, compounded by PM's refusal to extend despite corona.
UK stole 3,700,000 British votes abroad, 700,000 in EU  http://stolenvotes.uk

___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Multi UPS Monitoring

[Julian H. Stacey]

Hi, Reference:
> From: "Julian H. Stacey" 
> Date: Sun, 11 Oct 2020 01:57:16 +0200

"Julian H. Stacey" wrote:
> > > I've read through as many relevant mailing list posts and public blog =
> > posts as I could, but I can't seem to find an answer to my issue.
> > >=20
> > > I currently have 2x Tripp Lite SMART1500LCDXLs, and I am attempting to =
> > monitor both of them with the same Raspberry Pi using NUT.
> 
> Rasp. Pi, x86 or amd is irrelevant as Pi runs Linux & BSD etc.
> Relevant is: What OS ?
> 
> If you connect a USB device (mem stick, triplite ups or disc whatevere)
> to a FreeBSD computer (PC, rasp. i386 amd64 whatever) the
> computer will show serial numbers with all of;
>   dmesg
>   vi /var/log/messages
>   kill -9 `cat /var/run/devd.pid` ; /sbin/devd -d

PS a few rare old devs don't announce a sernum, so you may be partly
out of luck esp. in light of post from David Zomaya, Tripp Lite.
However newest releases of FreeBSD offer more hub & port no. info
than older releases, & presumably smilar on other OS's, so you may be 
able to extract some differentiating info. Good luck.

Cheers,
-- 
Julian Stacey, Consultant Sys. Eng. BSD Linux Unix, Munich & Aachen
http://berklix.com/jhs/cv/  
Crash Brexit in 12 weeks, compounded by PM's refusal to extend despite corona.
UK stole 3,700,000 British votes abroad, 700,000 in EU  http://stolenvotes.uk

___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Multi UPS Monitoring

[Charles Lepple]

On Oct 9, 2020, at 8:07 PM, Rusty Bower wrote:
> 
> Hey all,
> 
> I've read through as many relevant mailing list posts and public blog posts 
> as I could, but I can't seem to find an answer to my issue.
> 
> I currently have 2x Tripp Lite SMART1500LCDXLs, and I am attempting to 
> monitor both of them with the same Raspberry Pi using NUT. The problem I have 
> is there doesn't seem to be any way in the nut.conf to differentiate between 
> the two UPS via USB other than Vendor/Product/Serial. Unfortunately, I cannot 
> leverage Vendor/Product filtering, because they are the exact same model, and 
> the serial number is returning "unknown"

The unknown serial number does seem to be the case for other 2012 protocol 
models, yes.

(I'm 99% certain this isn't going to yield different results in your case, but 
if you ever want to rule out NUT as part of the problem in retrieving the 
serial number, you can run "lsusb -vvv" as root, or check dmesg/journalctl to 
see if other parts of the system were able to retrieve a serial number.)

> 
> Does anyone know how to get these Tripp Lite models to return an actual 
> serial number? Or is there a way to differentiate between the two devices on 
> the same USB bus?

I forget if adding a USB hub ends up creating a second logical bus as far as 
the kernel is concerned, but if you have a spare hub on hand, it's an easy 
thing to try.

It is possible that a future version of NUT could use the kernel's USB topology 
information: 
http://libusb.sourceforge.net/api-1.0/group__libusb__dev.html#ga14879a0ea7daccdcddb68852d86c00c4
 


but we are still working out issues in the libusb-0.1/1.0 transition: 
https://github.com/networkupstools/nut/issues/300 


If it were me, I'd probably just find a spare Raspberry Pi and have a 1:1 
UPS-to-Pi mapping, just to hedge against the Pi and its power supply being a 
single point of failure in the monitoring system.

> 
> Raspbian GNU/Linux 10
> Nut Version 2.7.4-8

Thanks for the NUT and OS version info!
> 
>0.056938 Checking device (09AE/2012) (001/113)
>0.062961 - VendorID: 09ae
>0.063011 - ProductID: 2012
>0.063055 - Manufacturer: Tripp Lite
>0.063094 - Product: Tripp Lite UPS
>0.063136 - Serial Number: unknown
>0.063189 - Bus: 001
>0.063259 - Device release number: 0009
> 
> Rusty
> ___
> Nut-upsuser mailing list
> Nut-upsuser@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser