Difference between revisions of "UPS Handling with NUT"
Jump to navigation
Jump to search
| Line 49: | Line 49: | ||
* [[Setting up a NUT Client]] | * [[Setting up a NUT Client]] | ||
* [[Using NUT to gracefully shut down ESXi]] | * [[Using NUT to gracefully shut down ESXi]] | ||
= Managing NUT = | = Managing NUT = | ||
Revision as of 21:41, 9 April 2022
 |
11 (bullseye) |
|
| As always... | |
|---|---|
|
Start with: |
|
Install NUT
sudo apt install nut
Configure NUT
Select your mode
| none |
Disable automatic startup of NUT |
| standalone | This MODE is for local only configuration |
| netserver | This MODE is open to the network. (A NUT server) |
| netclient | This MODE is for client machines that will access a NUT server |
See the nut.conf documentation for more details.
Managing NUT
The usual:
sudo service nut-server [start|stop|restart|status]
Client commands:
upsc cyberpowerupscmd -l cyberpowerupsrw cyberpowernut-scanner
further Usage Concepts
NUT gives lots of options.
Things like:
- Cleanly shutting down all of the VMs on a server & the server itself too.
- Sending notifications about power issues.
- Managing redundant UPSs on your system.
- etc...