TOCPREVNEXTINDEX


PowerChute

Event Configuration

The Event Configuration screen lists the events that can occur and separates them into three categories - critical (severe), warning, and informational. You cannot change an event's category.

By default, the Informational events are hidden, click the + icon beside Informational to display them. You can also click the - sign to hide any of the three categories.

You can configure events to cause certain actions, named in separate columns:

  • Logging: Records the event in the Event Log when the check box is selected.
  • You can disable all logging, see Log Settings.

  • E-Mail: Sends an e-mail message to users and administrators when an event occurs. The check box must be selected to enable this. E-mail must be configured in PowerChute, see E-Mail Settings.
  • Shutdown: Initiates an operating system shutdown sequence in response to an event when the check box is selected. See Shutdown.
  • Command File: Runs a user-specified command file when an event occurs.
  • Command files are often used to shut down open applications in order to avoid loss of data. They have to be placed in this folder:

    <Installation folder>\APC\PowerChute Business Edition\agent\cmdfiles

    which for example is, by default on Windows, this folder:
    C:\Program Files\APC\PowerChute Business Edition\agent\cmdfiles

    Click on the Command File icon to enable it, and choose a file to run and a duration.

    All command file types are supported.

    When you have enabled a command file for an event, the icon color changes from grey, , to green, .

See also Command file durations and shutdowns and Power Failure Configuration and Shutdown on Event Configuration.

Some events cannot be configured to trigger certain actions and have no check box for that action. For example, most informational events cannot cause a shutdown so the check box is missing in the Shutdown column for those events.

Description of events

For descriptions of individual events, see:

The events that display depend on your UPS, some events described below might not display on your screen.

Critical events

Critical (severe) events can cause the UPS to stop supplying power to its supported equipment. These events require your immediate attention.

Event Name
Description
Communication Lost While On Battery
A problem occurred causing PowerChute to lose communication with the UPS while the UPS was operating on battery power.
Make sure that the proper communications cable is being used and that it is connected correctly.
UPS Internal Temperature Threshold Exceeded
The internal temperature of the UPS has exceeded the user-configured threshold. This causes a shutdown which cannot be cancelled, even if the internal temperature returns to normal.
You can set this threshold in the High Internal Temp Threshold under UPS Settings.
After this event occurs, to prevent it occurring repeatedly, when you log onto the machine with the Agent installed, you must stop the Agent service immediately. You should disconnect your UPS and wait for the temperature to cool down.
See “Starting and Stopping the PowerChute Agent” in the Installation help and the Linuxreadme.txt.
Low Battery
A UPS that is operating on battery power has reached the low runtime threshold.
That is, the Runtime Remaining reported by the UPS is less than the At runtime limit value on the Shutdown Settings screen.
Alternatively, a UPS management accessory (such as a UPS Interface Expander Card) has triggered the Low Battery event in order to request a shutdown.

Warning events

Warning events alert you to situations that should be monitored

Event Name
Description
Power Failed
The UPS has switched to battery operation due to a power outage or poor power quality.
Battery Discharged
An On Line UPS has reached the low runtime threshold. If a power outage occurs, a shutdown will begin immediately.
The low runtime threshold indicates that the Runtime Remaining reported by the UPS is less than the At runtime limit value on the Shutdown Settings screen.
Overload
The UPS cannot support the current load. It is at 105% or more of its maximum capacity. (This percentage varies between UPS devices and can be as high as 110%).
If the overload was not caused by adding new load equipment, do the following:
1. Run a UPS self-test to see if the problem clears.
2. If the problem persists, disconnect all equipment from the UPS and reboot the UPS.
3. If the problem is cleared, reconnect and turn on the load equipment, one piece at a time, to determine which piece of equipment causes the overload.
If the overload still exists, the UPS needs to be repaired or replaced. For further information, see the support services at www.apc.com/support.
Self-Test Failed
The UPS failed its last self-test. It might have a bad battery.
If the system is reporting an Insufficient Runtime Available or an Overload condition, clear the event and test the UPS again.
If the self-test fails again, see the support services at www.apc.com/support.
Communication Lost
Communication between PowerChute and the UPS has been lost while the UPS was On Line. Make sure that the proper communications cable is being used and that it is connected correctly.
Time on Battery Threshold Exceeded
The UPS is on battery and has breached the user-configured threshold.
Specifically, the time that the UPS has been on battery exceeds the After UPS has been on battery for value on the Shutdown Settings screen.
Output Load Threshold Exceeded
The UPS has exceeded the user-defined load threshold. See UPS Output Load Threshold on UPS Settings.
This threshold event can be seen as a warning. The UPS itself determines when the UPS is actually overloaded and this generates another more serious event, see Overload.
Insufficient Runtime Available
The UPS is On Line and is below the low runtime threshold.
That is, the Runtime Remaining reported by the UPS is less than the total turn-off delays for the outlet group supplying power to the Agent.
This outlet group is designated by the PowerChute logo on the Outlet Sequence screen, see Using the graph and common fields.
In a forced shutdown, the UPS might not have enough runtime available to perform a graceful shutdown.
Low Runtime Available
The UPS is on battery and is below the low runtime threshold.
That is, the Runtime Remaining reported by the UPS is less than the total turn-off delays for the outlet group supplying power to the Agent.
This outlet group is designated by the PowerChute logo on the Outlet Sequence screen, see Using the graph and common fields.
In a forced shutdown, the UPS will NOT have enough runtime available to perform a graceful shutdown.
Battery Needs Replacing
One or more UPS batteries need to be replaced.
UPS Internal Temperature Warning
The warning threshold in place for your UPS internal temperature has been exceeded. See High Internal Temp Warning Threshold.
Battery Disconnected
The battery in your UPS has been disconnected or removed.
Reconnect the battery. If this does not clear the problem, see the support services at www.apc.com/support.
Bypass Internal Fault
The UPS has reported an internal hardware problem.
Contactor Stuck In On Position
The bypass failed to put the UPS into bypass mode.
Contactor Stuck In Bypass
This is an abnormal state caused by a UPS hardware problem.
Bypass Relay Malfunction
For further information, see the support services at www.apc.com/support.
Bypass Power Supply Failure
The bypass power supply has failed. For further information, see the support services at www.apc.com/support.
Inverter Fault
The inverter has failed. The UPS cannot supply power during a power outage. For further information, see the support services at www.apc.com/support.
Main Relay Malfunction
The main relay has failed. The UPS cannot supply power during a power outage. For further information, see the support services at www.apc.com/support.
AVR Boost Enabled
The UPS began using AVR Boost to correct a low voltage condition.
AVR Trim Enabled
The UPS began using AVR Trim to correct a high voltage condition.

Informational events

Informational events report data about the UPS device's operation.

Event Name
Description
Online (Green Mode)
Your UPS has begun operating in green mode: it is running normally on AC utility power, and the electrical input is being utilized with high efficiency.
Note: Some UPS devices can incorrectly signal they are in this mode when the internal battery is disconnected.
Power Restored
AC utility power has been restored; the UPS is no longer running on battery power. This event follows Power Failed.
Overload Solved
The overload condition has been corrected. See Overload.
Output Load in Range
The UPS load out-of-range condition has been corrected. See Output Load Threshold Exceeded.
Shutdown Starting
Shutdown Cancelled
Shutdown In Progress
Various stages of the shutdown procedure.
Calibration Started
Calibration Complete
Calibration Cancelled
Various stages of a runtime calibration. A calibration cancellation can be caused by either a user or a power outage. See Diagnostics.
Communication Established
PowerChute has established communication with the UPS.
Monitoring Started
Monitoring Stopped
PowerChute has started or stopped monitoring the UPS.
Sufficient Runtime Available
This event follows Insufficient Runtime Available. Your UPS now has enough runtime available to perform a graceful shutdown.
Administrative Shutdown Scheduled
A shutdown will start after the user-specified delay has expired. An administrative shutdown is caused by a user rather than an event such as a power outage. See Shutdown.
Administrative Shutdown Cancelled
Cancel Server Shutdown was selected by the user and the shutdown process was aborted. An administrative shutdown is caused by a user rather than an event such as a power outage. See Shutdown.
Self-Test Initiated
Self-Test Passed
The UPS has started or passed its internal diagnostic self-test.
See Diagnostics for details of the date and status of the self-test.
AVR Boost No Longer Active
The UPS no longer needs to use AVR Boost to correct a low voltage condition. This event follows AVR Boost Enabled.
AVR Trim No Longer Active
The UPS no longer needs to use AVR Trim to correct a high voltage condition. This event follows AVR Trim Enabled.
Battery Reconnected
The battery in your UPS had previously been disconnected and is now reconnected.
Bypass Maintenance
The UPS has been switched to bypass using the rear-panel switch on the device.
Bypass User-Initiated
A user has initiated a bypass using either the software or the UPS front-panel control.
Bypass Ended
The UPS is no longer on bypass.
Bypass Contactor OK
The bypass contactor fault has been corrected.
Bypass Power Supply Normal
The bypass power supply malfunction has been corrected.
Battery Installed
Battery Removed
Battery Replaced
Various states relating to the battery.
Internal Temperature In Range
The UPS's internal temperature has returned to an acceptable level. This event follows UPS Internal Temperature Threshold Exceeded or UPS Internal Temperature Warning.
Inverter Normal
The inverter malfunction has been corrected. This event follows Inverter Fault.
Main Relay Normal
The main relay malfunction has been corrected. This event follows Main Relay Malfunction.

Command file durations and shutdowns

The Time for other applications to shut down on the Outlet Sequence screen is an important element in a shutdown (see the OFF sequence for more details). The value is read-only on Outlet Sequence.

It represents the longest command file duration configured for any event that has shutdown enabled. Time for other applications to shut down is automatically updated when the longest command file duration is increased by using this Event Configuration screen.

For example if the command file duration for Battery Discharged is the longest duration at 3 minutes, and you increase the Power Failed duration to 4 minutes, Time for other applications to shut down will be updated to 4 minutes.

E-Mail Settings

The E-Mail Settings screen lists the mail addresses of users configured to be notified when an event occurs. In order to receive mailings when an event occurs, the mail address must be set up here. See Event Configuration for information on configuring an event to send an e-mail when it occurs.

The following five fields must be defined to enable PowerChute to send e-mail messages when events occur. (This includes messages to pagers that accept e-mail).

  • SMTP Server (Hostname, IPv4, or IPv6) identifies the SMTP server by one of the three methods mentioned: its name, its IPv4 address, or its IPv6 address. An example hostname is mail.server.com.
  • From E-Mail Address specifies the e-mail address from which the recipient receives the e-mail. It is the e-mail account to be used to send notifications.
  • Port specifies the port number from which e-mail is sent via SMTP. Port numbers can have a maximum of five digits and can be set to 25, 465, 587, or any number ranging from 5000 to 32768. If you do not enter a port number, the default of 25 is used.
  • Use SSL/TLS defines the e-mail encryption protocol that will be used when e-mail is sent. There are three options available:
    • None Selected – if authentication is disabled, no e-mail encryption protocol will be used and e-mail will be sent un-encrypted. If authentication is enabled, e-mail will be encrypted using the SMTPS protocol.
    • SSL – e-mail will be encrypted using the SSL encryption protocol.
    • TLS – e-mail will be encrypted using the TLS encryption protocol.
    • If you are using SSL/TLS and your SMTP Server uses a self-signed certificate, the certificate must be added to the trusted certificate store of the bundled Java JRE.

      On Windows:
      Open a command prompt with Administrator privileges and type in the following command:

      "<PowerChute JRE Path>\bin\keytool.exe" –import –trustcacerts –alias mailserv –file server.crt –keystore
      "<PowerChute JRE Path>\lib\security\cacerts" –storepass changeit

      e.g.

      "C:\Program Files (x86)\APC\PowerChute Business Edition\jre1.8.0_102\bin\keytool.exe" –import –trustcacerts –alias mailserv –file server.crt –keystore
      "C:\Program Files (x86)\APC\PowerChute Business Edition\jre1.8.0_102\lib\security\cacerts" –storepass changeit

      On Unix/Linux:
      As an Administrator, type in the following command:

      <PowerChute JRE Path>/bin/keytool –import –trustcacerts –alias mailserv –file server.crt –keystore
      <PowerChute JRE Path>/lib/security/cacerts –storepass changeit

      e.g.

      /usr/local/bin/java/jre/1.8.0_102/bin/keytool –import –trustcacerts –alias mailserv –file server.crt –keystore
      /usr/local/bin/java/jre/1.8.0_102/lib/security/cacerts –storepass changeit

      Note: In the above examples, mailserv is the alias of the mail server used within the cert file, and server.crt is the self-signed SSL cert of the mail server.


      See also Authenticating e-mail.
  • To E-Mail Address: See Adding and removing e-mails.

The PowerChute Console has a separate e-mail system (available under Configuration Profile there). Any new e-mails added here will not be sent to the Console list.

Adding and removing e-mail recipients

To add an e-mail address, under the Add/Remove E-Mail Recipients section, type an e-mail address and click the Apply button.

To remove an e-mail address, select the check box to the right of the address, and click Apply.

Filling in the Contact Name and System Location under Contact Information is optional. If present, the information is included in e-mails. The name is intended to represent the person responsible for the maintenance of the UPS. The location is the physical location of the server hosting the PowerChute Agent.

See also Authenticating e-mail.

We advise testing your e-mails after you add them. You can do this by selecting an E-Mail check box for an event with Event Configuration and then creating that event.

Authenticating e-mail

Authenticating e-mail is optional. You can enable it by selecting the Basic E-Mail for Authentication check box. Contact your e-mail administrator if you’re not sure about authentication.

If you’re going to use authentication, you can specify a server username and password in the respective fields, but you do not have to do so. If you don’t specify a server username and password, PowerChute uses the SMTP Server (Hostname, IPv4, or IPv6) to obtain a list of IP Addresses that are allowed to send authenticated e-mails.

SNMP Settings

With Simple Network Management Protocol (SNMP) traps, you can get automatically notified of significant UPS events. They are a useful tool for monitoring devices on your network.

SNMP traps are used in combination with a Network Management Systems (NMS) like HP OpenView.

Use this SNMP Settings option to enable or disable access to your system’s devices by SNMP services. SNMP is enabled by default. (This option is displayed even if your system does not have an SNMP service installed).

To learn about trapping SNMP errors, search for “MIB” on the APC website and download the guide.

PowerChute does not support SNMP on Linux, only on Windows.

When SNMP access is enabled, use the Minimum SNMP Trap Severity setting to select what events will cause an SNMP trap to be sent: Informational, Warning, etc.

The list shows the levels in increasing order of severity. See also Using a Master SNMP Agent below.

Using a Master SNMP Agent

You must have a Master SNMP Agent installed and properly configured at the PowerChute Agent’s host PC before you can use SNMP to manage the computer’s UPS.

PowerChute utilizes the Security, Trap, and Agent settings from the Master SNMP Agent (for example, contact and location). For information about how to install and configure the Master SNMP Agent, consult your operating system documentation.


TOCPREVNEXTINDEX
Copyright © 2001-2016 by Schneider Electric
http://www.apc.com
All rights reserved.
v9.0.4, v9.2.1
Last Updated: July 25, 2016
 
Send any comments on this help to:
PCBE_feedback@schneider-electric.com