Both sides previous revision
Previous revision
Next revision
|
Previous revision
Next revision
Both sides next revision
|
userdoc:tt_ups_monitoring [2014/01/07 18:33] abelbeck [CLI Custom Configuration] |
userdoc:tt_ups_monitoring [2016/01/04 12:29] droemel [General Configuration] |
| |
{{:userdoc:ups-default-config.jpg?nolink|UPS Default Configuration}} | {{:userdoc:ups-default-config.jpg?nolink|UPS Default Configuration}} |
| |
| !!Note ->!! By default the "UPS Password" is: ''astlinux'', the firewall port, if needed, is 3493/TCP. |
| |
\\ | \\ |
{{:userdoc:ups-notify-options.jpg?nolink|UPS Notify Options}} | {{:userdoc:ups-notify-options.jpg?nolink|UPS Notify Options}} |
| |
Finally, the "Kill Power on the UPS after a Powerfail Shutdown" only applies if a "UPS Driver" is defined. When enabled this option will instruct the UPS to cut power if both on battery and a shutdown is in progress. Power will be cut approximately 60 seconds after a shutdown. The idea is when line power is restored the battery will not be totally depleted. | Finally, the "Kill Power on the UPS after a Powerfail Shutdown" only applies if a "UPS Driver" is defined. When enabled this option will instruct the UPS to cut power if both on battery and a shutdown is in progress. Power will be cut approximately 60 seconds after a shutdown. The idea is when line power is restored the battery will not be totally depleted and the UPS connected device will be power cycled off/on. |
==== Display UPS Status ==== | ==== Display UPS Status ==== |
| |
{{:userdoc:ups-diskstation-astlinux.jpg?nolink|Diskstation to AstLinux}} | {{:userdoc:ups-diskstation-astlinux.jpg?nolink|Diskstation to AstLinux}} |
| |
!!Tip ->!! Be sure to test an automatic shutdown in a controlled environment rather than later scratching your head when something did not work as expected while in production. | !!Tip ->!! Be sure to test an automatic shutdown in a controlled environment rather than later scratching your head when something did not work as expected following an actual power loss. |
| |
==== CLI Custom Configuration ==== | ==== CLI Custom Configuration ==== |
/mnt/kd/ups/upsmon.conf | /mnt/kd/ups/upsmon.conf |
| |
Additionally, in very special situations, the following two files can be added. The upssched.conf will also have to reference a upssched-cmd script similar to upsnotify. | Additionally, in very special situations, the following two files can be added. The ''upssched.conf'' will also have to reference a ''upssched-cmd'' script similar to ''upsnotify''. |
| |
/mnt/kd/ups/upssched.conf | /mnt/kd/ups/upssched.conf |
!!Tip ->!! The directory ''/stat/etc/ups/'' contains the sample templates for the above files as reference. | !!Tip ->!! The directory ''/stat/etc/ups/'' contains the sample templates for the above files as reference. |
| |
| The ''[master]'' user's password is auto-generated as a random string, which may be accessed by the ''upsd.users'' and ''upsmon.conf'' configuration files using the token: ''@MASTER_PASS@'' . For example a snippet of a custom ''upsd.users'' could contain: |
| |
| [master] |
| password = @MASTER_PASS@ |
| upsmon master |
| |
| or a snippet of a custom ''upsmon.conf'' could contain: |
| |
| MONITOR ups@localhost 1 master @MASTER_PASS@ master |
| |
| Of course a custom ''upsd.users'' and ''upsmon.conf'' could share a custom ''[master]'' user's password if desired. |
| |