Support for Tripplite SUINT1500LCD2U

[agentpatience]

Hello,

Can you advise if Tripplite SUINT1500LCD2U is supported by NUT?

Thanks!

[clepple]

The SUINT1500LCD2U shares the same Advanced Users Manual as several other supported models (such as the SU2200RTXLCD2U), which means it might be close enough. Are you planning to use the USB interface? If so, what does lsusb -d 09ae: return?

Reference: https://networkupstools.org/stable-hcl.html?manufacturer=Tripp%20Lite

[agentpatience]

Hi Charles. Thanks for your support. I am a bit of a noob with this software, used it long ago for USB mode but I want to setup NUT with SNMP mode now. I will however try that command with the USB cable attached. I have 2-3 servers attached to each UPS. I have installed the nut software via "dnf install nut" in rock linux 8.10. That is as far as I have got. Can you clue me in on the next steps? Thanks!

[clepple]

That sounds like you are looking for something like https://networkupstools.org/docs/user-manual.chunked/Features.html#_advanced_configuration (instructions in the next section: https://networkupstools.org/docs/user-manual.chunked/Configuration_notes.html)

I am aware of the SNMP driver, but the UPSes I use day-to-day only have USB or serial connections. From https://networkupstools.org/docs/man/snmp-ups.html (and the fact that no Tripp Lite UPSes have been marked as tested for "network" in the HCL link I sent earlier) it looks like maybe the SNMP support is still pretty basic.

[jimklimov]

Yes, in fact the "Tripplite MIB" is an alias to standard default fallback IETF mapping at the moment (just uses detection of vendor-specific OID to match).

[jimklimov]

Do you know the settings from UPS side? If SNMP is enabled at all, if it is on standard port (161/udp), if its SNMP v1/v2c community is set and is not default public (R/O) or private (R/W), or if SNMPv3 credentials and crypto are used?..

[agentpatience]

We used tripplite webgui to check that. We wanted to try v1 to try and keep it simple but i'm all ears. They all appear to be "On" Our default configuration on UPS side:

[agentpatience]

We are making some progress. We changed port to 161 and manually added "public" for the community string and "tripplite" for the community string on the tripplite profile.

You can see the snmp query worked with net-scanner and snmpwalk. WE are still a little needy on proceeding to get a working setup. We really just need to be able to detect when the battery goes to 50% or so and shutdown servers gracefully.

[agentpatience]

Here is some output from one of the snmp-ups driver commands says to contact nut developers on one line. Sorry if it is false alarm 🚨

[agentpatience]

Ahh the upsec command is talking to localhost server client duh!

[agentpatience]

Trying to do some sanity testing now, I wonder what we are missing?!

upsdrvctl -t shutdown
Network UPS Tools - UPS driver controller 2.8.2
Network UPS Tools - Generic SNMP UPS driver 1.31 (2.8.2)
Can't open /run/nut/snmp-ups-public: No such file or directory
Detected SUINT1500LCD2U on host 192.168.0.105 (mib: tripplite 1.55)
Initiating UPS shutdown
Shutdown failed!
upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it
Driver failed to start (exit status=1)
Network UPS Tools - Generic SNMP UPS driver 1.31 (2.8.2)
Can't open /run/nut/snmp-ups-tripplite: No such file or directory
Detected SUINT1500LCD2U on host 192.168.0.105 (mib: tripplite 1.55)
Initiating UPS shutdown
Shutdown failed!
upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it
Driver failed to start (exit status=1)

"Create a upsd user for upsmon to use while monitoring this UPS."

Does this user need to be a SNMP user on the UPS side?

[jimklimov]

"Create a upsd user for upsmon to use while monitoring this UPS"

That's from... where? Don't see an exact match above. Anyhow, this is about creating an entry in upsd.users file with the specific upsmon role (primary or secondary). Not related to account/community names in SNMP (may be or not be coincidentally similar; security-wise better not).

Note that on the UPS side, the SNMP public community is read-only, so by design should not be able to handle any variable settings or issue commands to the device.

As for the test itself, can you please retry it with some more debug verbosity, perhaps as upsdrvctl -DDDDDD -d -t shutdown ?

On the one hand, looking into code https://github.com/networkupstools/nut/blob/v2.8.2/drivers/upsdrvctl.c I see that all (hopefully) executions and signal sending are fenced by testmode variable; on the other - I don't see the effects of printf("*** Testing mode: not calling exec/kill/signal\n"); etc. above, and it apparently does try to run the driver programs.

So the drivers did try to power off your UPS despite the testing mode, just by some chance failed to.

First I've suspected a non-capable SNMP community, but then remembered an issue fixed a couple of months ago (part of upcoming NUT v2.8.3 release) to let sdcommands be specified. As of your version, in https://github.com/networkupstools/nut/blob/v2.8.2/drivers/snmp-ups.c the upsdrv_shutdown() method cycles through "shutdown.return", "shutdown.reboot", "load.off.delay" and now I found that the IETF OID mapping (used also for Tripplite as noted above) in https://github.com/networkupstools/nut/blob/v2.8.2/drivers/ietf-mib.c actually defines none of these names. So that is probably why it gets to upslogx(LOG_ERR, "Shutdown failed!");

So I suppose these devices have no way of triggering a shutdown with NUT v2.8.2 or older, and might be able to with custom sdcommands configuration with current master branch, eventually NUT v2.8.3 or newer.

Orthogonally to this, note that nut-driver-enumerator can automatically generate systemd units that wrap your driver instances, see https://github.com/networkupstools/nut/wiki/nut%E2%80%90driver%E2%80%90enumerator-(NDE) - so using directly the driver programs or old upsdrvctl becomes trickier, especially with non-networked UPSes (serial/USB) due to exclusive-link conflicts. A newer executed copy of the driver can try to kill off the older one (so first the one you run manually kills the one under the service, then the unit is revived and kills your manually-spawned copy).

Here socket files like /run/nut/snmp-ups-public were absent, so the respective drivers were not running. Probably :)

[agentpatience]

"Create a upsd user for upsmon to use while monitoring this UPS

That's from... where?

https://networkupstools.org/docs/user-manual.chunked/ar01s06.html under "NUT User Creation"

It seems that we chased some rabbits today one being that in order to start getting ups.status returned we need to run upsd manually via cli. For whatever reason installing from packages does not allow it to startup when the server boots? I cannot seem to find the instructions to have it init at start?

We are going to try a basic shutdown config per the docs. I however, lack experience with this project and please forgive me if it sounds elementary.