Difference between revisions of "UPS Handling with NUT"
Jump to navigation
Jump to search
| Line 46: | Line 46: | ||
<p class="mwt-heading">See [https://networkupstools.org/docs/man/nut.conf.html the nut.conf documentation] for more details.</p> | <p class="mwt-heading">See [https://networkupstools.org/docs/man/nut.conf.html the nut.conf documentation] for more details.</p> | ||
* [[Using NUT with pfSense]] | |||
* [[Using NUT to gracefully shut down ESXi]] | * [[Using NUT to gracefully shut down ESXi]] | ||
Revision as of 20:16, 16 April 2022
 |
11 (bullseye) |
|
| As always... | |
|---|---|
|
Start with: |
|
Install & Configure NUT
Select your mode
| none | Disable automatic startup of NUT | |
| standalone | This MODE is for local only configuration | Standalone NUT usage |
| netserver | This MODE is open to the network. (A NUT server) | Setting up a NUT Server |
| netclient | This MODE is for client machines that will access a NUT server | Setting up a NUT Client |
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...