TrevorX
Explorer
- Joined
- Mar 10, 2015
- Messages
- 77
Hello,
I have an Eaton 9130 1500VA UPS protecting my servers and network hardware. I have a switch, modem, router, NAS and Hyper-V server running off it, which amounts to a 12% load. The UPS is monitored and communicates over USB to the Hyper-V server using the Eaton Intelligent Power Manager (IPM) software. I've installed the Intelligent Power Protector (IPP) module on important VMs to control elegant shutdown. That all works swimmingly.
What doesn't is the lack of communication with the FreeNAS server. During a power outage the UPS powers down after 10 minutes, which is plenty of time for me to gracefully shut down the FreeNAS box if I'm present, but is a bit difficult to do when I'm not home. It is possible for me to respond to an alert from the UPS, remote into my gateway RDP VM and then run the command on the NAS manually, but such manual intervention is far from elegant.
Is there something I can run on the FreeNAS box to get it to trigger a shutdown from the UPS agent? For example, I can run command line commands from the Hyper-V server based on events like 'Runtime Threshold Reached' and 'Power Restored', but while the 'shutdown' command can remotely shut down a Microsoft box easily, would a Windows command line command be able to trigger a shutdown on a FreeNAS box? Alternatively, my NAS is built on an Asrock Rack C2750D4I with IPMI BMC - most BMC's can be controlled by the command line, but would require an SSH connection to respond to remote commands, which sounds like I'd be making things a lot more difficult than necessary, but might have to be explored if I run out of alternative options.
I've been meaning to devote some time to this for at least a year, but about a month ago a power failure resulted in the UPS powering down and when everything came back up the FreeNAS box had somehow got its domain (and thus permissions) configuration all messed up and none of the shares were accessible - it took me about six hours to get it back online, and I really don't want to have to go through that (or worse) again.
Suggestions much appreciated.
Cheers,
Trevor
I have an Eaton 9130 1500VA UPS protecting my servers and network hardware. I have a switch, modem, router, NAS and Hyper-V server running off it, which amounts to a 12% load. The UPS is monitored and communicates over USB to the Hyper-V server using the Eaton Intelligent Power Manager (IPM) software. I've installed the Intelligent Power Protector (IPP) module on important VMs to control elegant shutdown. That all works swimmingly.
What doesn't is the lack of communication with the FreeNAS server. During a power outage the UPS powers down after 10 minutes, which is plenty of time for me to gracefully shut down the FreeNAS box if I'm present, but is a bit difficult to do when I'm not home. It is possible for me to respond to an alert from the UPS, remote into my gateway RDP VM and then run the command on the NAS manually, but such manual intervention is far from elegant.
Is there something I can run on the FreeNAS box to get it to trigger a shutdown from the UPS agent? For example, I can run command line commands from the Hyper-V server based on events like 'Runtime Threshold Reached' and 'Power Restored', but while the 'shutdown' command can remotely shut down a Microsoft box easily, would a Windows command line command be able to trigger a shutdown on a FreeNAS box? Alternatively, my NAS is built on an Asrock Rack C2750D4I with IPMI BMC - most BMC's can be controlled by the command line, but would require an SSH connection to respond to remote commands, which sounds like I'd be making things a lot more difficult than necessary, but might have to be explored if I run out of alternative options.
I've been meaning to devote some time to this for at least a year, but about a month ago a power failure resulted in the UPS powering down and when everything came back up the FreeNAS box had somehow got its domain (and thus permissions) configuration all messed up and none of the shares were accessible - it took me about six hours to get it back online, and I really don't want to have to go through that (or worse) again.
Suggestions much appreciated.
Cheers,
Trevor