Version: 2020-09-04
68
Copyright of the European Union is effective (Copyright EU) (c) 2019 GENEREX Systems GmbH, Hamburg, Germany, All rights reserved
TEL +49(40)22692910 - EMAIL generex@generex.de - WEB www.generex.de (This and all other product datasheets are available for download.)
What is the intention of a jobs for an event?
System events are highly dependent on the UPS model to be used and vary in both - designation as well as abundance of possibilities.
Furthermore, administrators will find interesting conceptional issues according to the interplay of events and counter-events:
An event receives an action, a job. This job will be executed when the event occurs. These jobs differ in central role as well as its direct
function:
- Information
These jobs can be executed as often as desired and only fulfill the purpose of the information. Depending on the configuration,
information can be sent once or cyclically as long as an event is pending - the nature of the event does not matter. If the situation
changes and the event does not come to fruition, an according job will not continue.
- Action
These jobs are designed to switch, trigger, start emergency routines, etc. These jobs are triggered as soon as an event occurs.
They differ from information jobs due to the fact administrators have to terminate these jobs by using corresponding counter-
rotating jobs. In some cases, there are counter-events to be used, others need to be configured manually.
Note:
It is important to understand the difference
As long as a power failure occurs, a mail with log files is appendixed to should be sent every 5 minutes. Once the power failure is
eliminated, no more email is written. On the other hand, a job to close potential-free contact as soon as a power failure is detected is
executed. This cannot be reverted - even if the main power comes back,
the contact remains in closed position. If a warning light is switched via this contact, it would light up until this contact is deliberately
opened. A counter-job is needed in case of main power returns.
The following example shows why it is important to understand the difference:
If the temperature sensor measures critical temperatures, the CS141 will send e-mails and simultaneously close the contact of an air
conditioner. As soon as the temperature drops below the critical level, CS141 stops sending e-mails - but the air conditioner needs to
run until the temperature has returned to normal condition. This will not work if the contact automatically opens in case of critical
temperature is no longer given:
You need to use an active job to switch off the air conditioning system as soon as a certain temperature has been reached.
It becomes problematic if a power failure causes two UPS systems running on separated power input circuits to send a server shutdown
command:
As soon as both systems send a valid shutdown command, the server shuts down immediately - even if both UPS systems report a
power failure time-separated. If they do not cancel the shutdown command after their respective individual problems were resolved, the
server will shut down due the fact, both UPS systems seems to report problems.
Event handling: Defining a job
The jobs can be configured at any time.
In order to test a job, two conditions need to be adjusted according to the job:
1. Jobs according to e-mails require valid e-mail account data
2. Jobs based on the TCP / IP settings require a valid network configuration
Before continuing configuration ensure all access data are available for configuration, network settings are correct, and that the CS141
is in the regular operating mode inside your network.
Managing jobs
Under Devices, open the UPS submenu and go to Events.
Please note that both the functions as well as designation will differ by usage of different UPS systems.
These are the icons the CS141 provides:
➔ Open /close tables
➔ Edit an existing job