Skip Navigation

how's your week going, Beehaw

busy as usual, currently reading Alt-America (David Neiwert)

42

You're viewing a single thread.

42 comments
  • It's going. It's been a very busy couple days already at work. But I talked about work last week, so I'll give an update on something more interesting (to me): My homelab! 🤓

    My UPS arrived like a week ago. I set it up and hooked up devices to it: server, router, and a small switch are on the battery backup. Which gets me about 17min of runtime on the battery if power fails. Pretty good.

    I was able to install the UPS software as an ESXi VM. And I got that to communicate with the ESXi host. Configured some delays to ensure it didn't try to shutdown the server due to a momentary blackout/brownout, and I even got the software to send me email notifications (thank you SMTP2GO).

    Then it was time. I unplugged the UPS from the wall. And waited for it run out of battery. And guess what? It shut down the server! Even before the UPS completely ran out of power. That said, I didn't take a stopwatch to it, or really get a chance to monitor how it was shutting down VMs. It looked like they were all shut down properly after I powered on the VMs again, but I can't say for certain. I could tighten this up. Either way, it basically did what it was supposed to do.

    Next thing I need to figure out is how to get it to boot the server back up once wall power is back. I have some ideas on how to do it manually (if I wasn't home when power was lost), but I think it'd be neat to figure out how to do it automatically.

    • Yay for a UPS! I'm sure you'll find some funky way of getting automagic reboots going.

    • Congrats on your new setup! A UPS is never a bad idea.

      As for the auto power-on, check the BIOS settings. Most have an option that says somehing along the lines of "computer power state after plugging it in" and you can usually set it to on, off or whatever it was before power loss.

      • Good idea. I did check the BIOS and that setting was already enabled. So I unplugged the UPS from the wall to simulate and test. Unfortunately, the server didn't boot automatically after I plugged the UPS back into the wall. And I remembered that in the past, when the power went out due to storms or something, the server did automatically boot on resumption of power.

        I think I know what's going on.

        With the server and a couple small networking devices on the UPS, I get about 16-17min of battery power. After a few minutes on battery power only, the UPS sends the commands to ESXI to start shutting down VMs and then eventually shuts down the server completely. That takes about 10min. That means there's still battery power remaining, and now with the server off, the largest load on the UPS, the remaining battery time increases to like 40min since the total load on the UPS is now much smaller. However, there's still technically power being served to the server; there's even a small light on the back of the server that stayed on the whole time.

        Plugging the UPS back in the wall didn't do anything, which I kinda expected. It's not going to "send" more power to the server to "wake it up." I think the only way the server would turn back on automatically in this situation is if the power outage was long enough to completely drain the UPS and turn the UPS off completely. So at least 40min. Then there would be absolutely no power being given to the server. Once wall power is back, the UPS itself turns back on, which sends a little bit of power to the server, which the server BIOS recognizes as "Hey, I was actually without any power at all, but I have power now! Boot!" I'll test that out next weekend.

        So for outages less than 40min, the best bet would be doing a remote desktop into a computer on my network, accessing the web GUI for IDRAC, the server's out-of-band-management software, and then powering on the server from there. I tried this out and it worked fine.

        Not automatic in all cases, but as long as I have a manual means to restart the server remotely, that'll do.

        Sorry for the long post; I wrote this down mostly for myself to work it all out!

You've viewed 42 comments.