I’m using APC Back-UPS BX750MI in my rack and had it attached to RB5009UG+S+ via USB. The Router reads it out well at first, but there are 2 big issues:
All the status information gets stuck/freezed without any warning at some point, everything seems like everything is okay, but when I unplug the UPS from the mains power nothing changes on the router, so it’s useless
After the UPS lost power, it caused the router to reboot with the warning “router was rebooted without proper shutdown, probably kernel failure” and “kernel failure in previous boot”
The Aruba switch and many other equipments connected to the same UPS have not lost power / rebooted, their uptime is over 30 days, I suppose it’s some kind of weird comm issue with UPS or the USB itself? There are no “only surge protection” sockets on the UPS so I suppose it’s not a PEBKAC problem, thank you for assuming so xD
Could be that bug, which “freezes” display of UPS status, contributes to reboot as well. But anyway, I doubt you’ll get any help about your problems on this forum, they don’t seem to be due to configuration error, which is what we, fellow MT users, can help. But this forum is not one of official means of support, you have to get in touch with MT support in other ways (one of them I mentioned in my previous post).
About PEBKAC problem … I had to ask. Some users might assume that USB connection between UPS and router would work as powering connection as well (but it doesn’t).
I’ve updated to 7.16.1, tried unplugging UPS from the mains and plugging it back in and everything works okay… I suppose I have to wait for UPS Status to freeze again. When that happens, I’ll write back here, generate a supout file and send it to the support mail.
Well damn, that would never even occur to me, yeah, I can make silly mistakes but nothing that big. You taught me a funny acronym yesterday and I’m grateful for that
EDIT: I spoke too soon, it has crashed just a bit later, I’m sending supout to the staff
I’ve gotten a response that they’ve been able to reproduce the issue and that it’ll be fixed in one of the future releases.
Thanks for the great support! I’ll mark this as solved once the issue has been fixed.