Unable to render embedded object: File (books.jpg) not found.
Go to documentation repository
Documentation for Monitoring 10.0. Documentation for other versions of Monitoring is available too.
Previous page Next page
Let us imagine that we are interested in situations when electricity has turned off and the UPS began to work in battery mode (ID Code = 2000), and after a time electrical supply was restored (ID Code = 1003).
- In the list of events, select the event UPS On Battery and, for this event, select the Run Command File check box (Fig. 4.4 – 4.4—14).
Fig. 4.4 – 4.4—14 Configuring UPS On Battery events
- To the right of Run Command File, click the Options... button (see Fig. 4.4 – 4.4—14).
- In the dialog box that opens, indicate the full path to the StateUPS utility that you want to be started when the event occurs (Fig. 4.4 – 4.4—15).
Fig. 4.4 – 4.4—15 Path to the StateUPS utility for the UPS On Battery event
This path should be surrounded by double quotation marks (one at the beginning of the path and one at the end). Leave a space and then indicate the ID code; for the UPS On Battery event, the ID code is 2000 (see Tab. 4.4 – 1).
- Similar actions for the Utility Power Restored event are shown in Fig. 4.4 – 4.4—16 and Fig. 4.4 – 4.4—17.
Fig. 4.4 – 4.4—16 Configuring the Utility Power Restored event
Fig. 4.4 – 4.4—17 Path to the StateUPS utility for the Utility Power Restored event
You should also remember that after utility power is restored, the UPS does not always generate the Utility Power Restored event; sometimes, it generates the UPS Enabling SmartBoost or UPS Enabling SmartTrim events. In order to not "miss" the moment at which utility power is restored, it is advisable to also handle the UPS Enabling SmartBoost and UPS Enabling SmartTrim events.
Each time the StateUPS utility is called, a log file is created in the OS system folder (System32) with a name of the following format:
upslog_<state><date><time>.log