I’ve been doing a lot with cryptocurrency mining lately, so there’s been a lot of activity here on rsts11 about it as well. For this post, a lot of the concepts can apply to a home lab in general, although it was inspired by several conversations on mining channels on Telegram and Discord over the past month.
In the late 1980s, actor Colin Quinn was an announcer on a game show called Remote Control. It’s not terribly remarkable in context, but as I’ve had a few people of differing technical levels ask about remote control for their mining rigs, it seemed relevant.
Whether you’re managing a single server, a home lab, a mining rig, or an entire farm, it’s likely that your gear will not be in your home office or possibly not even in your home at all, but you won’t want to travel to where the gear is everytime something needs to be power cycled. In the case of one of the people I consulted for recently, he was going to deploy mining rigs at a friend’s house in another country, and would not be able to be hands-on with the gear more than 2-3 times a year.
So the considerations I’m making here are tuned for a relatively small number of systems that may not have IPMI console access, and may not have convenient access or remote hands services available. In a datacenter or similar environment, you may have contracted services to send someone to hit the reset button or look for issues. For many of my readers, this is not a luxury you’ll enjoy.
My own remote access adventure happened when my oldest mining rig was a few miles from home. Thanks to my Meraki networks, I did have direct VPN access, but the rig would occasionally crash and require a physical power cycle. It was only 5-10 minutes each way, and I did have 24/7 access to the facility, but it got very inconvenient at times.
The considerations I’ll layout here fall into a couple of categories.
- Network access (usually via VPN of some sort)
- Console access (remote KVM)
- Power control (remote power controller over Ethernet, via #1 above)
Disclosure: Neither Robert M Persig, Colin Quinn, nor Ken Ober have any association or endorsement or even awareness of this blog post.