You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
exact device name and related information (manufacturing date, web pointers, ...), Tripp Lite AVRX550U
complete problem description:
When the UPS loses AC power and receives a shutdown command from the server after the server shuts down the UPS powers down but then after two seconds powers back on even though it is still under battery power. When I contacted Tripp Lite about the issue, they pointed out that the AVRX550U uses the 2012 protocol, but the NUT compatibility list has it using the 2010 protocol. If Tripp Lite is correct then the protocol in AVRX550U needs to be corrected to 2012, not 2010.
Second, it's unclear if NUT is issuing the command for the UPS to power back on after powering off, but it should not be issuing that command. I've attached the protocol documentation that Tripp Lite sent me. You probably already have it, but just in case it's helpful, here it is.
objecttothis
changed the title
Tripp Lite AVRX550U using wrong protocol and issuing restart command to UPS after shutdown
Tripp Lite AVRX550U using wrong protocol. Issuing restart command to UPS after shutdown?
Jul 12, 2020
When the UPS loses AC power and receives a shutdown command from the server after the server shuts down the UPS powers down but then after two seconds powers back on even though it is still under battery power. When I contacted Tripp Lite about the issue, they pointed out that the AVRX550U uses the 2012 protocol, but the NUT compatibility list has it using the 2010 protocol. If Tripp Lite is correct then the protocol in AVRX550U needs to be corrected to 2012, not 2010.
Second, it's unclear if NUT is issuing the command for the UPS to power back on after powering off, but it should not be issuing that command. I've attached the protocol documentation that Tripp Lite sent me. You probably already have it, but just in case it's helpful, here it is.
Communication Protocol 2012 for customer.pdf
Here is the upsmon.conf file:
ups.conf
upssched.conf
The text was updated successfully, but these errors were encountered: