Differences

This shows you the differences between two versions of the page.

--- userdoc:tt_ups_monitoring [2014/01/07 18:33]
abelbeck [CLI Custom Configuration]
+++ userdoc:tt_ups_monitoring [2016/01/04 12:33]
droemel [General Configuration]
@@ Line 24: / Line 24: @@
 {{:userdoc:ups-default-config.jpg?nolink|UPS Default Configuration}}
+!!Note ->!! By default the "UPS Password" is: ''astlinux''.
 \\
@@ Line 44: / Line 46: @@
 {{:userdoc:ups-server-config.jpg?nolink|UPS Server Configuration}}
+!!Note ->!! The firewall port on the server, if needed, is 3493/TCP
 \\
@@ Line 61: / Line 65: @@
 {{: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 ====
@@ Line 76: / Line 79: @@
 {{: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 ====
@@ Line 91: / Line 94: @@
   /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
@@ Line 98: / Line 101: @@
 !!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.