Schneider Electric PowerChute Business Edition v9.5.1 Instructions
- June 9, 2024
- Schneider Electric
Table of Contents
Schneider Electric PowerChute Business Edition v9.5.1
Introduction
The PowerChute Business Edition Release Notes have the following sections:
- What’s new in this release
- Known Issues
Additional resources:
- The Product Center page contains links to Power Chute-related Knowledge Base articles
- The Troubleshooting section of the Installation Guide provides additional troubleshooting information
What’s new in this release
The following features are new to PowerChute Business Edition v9.5.1:
- The Server and Console components have been removed.
- A single, unified Agent is used to manage any UPS device less than 5kVA in the Smart-UPS range.
- Multiple Agents can now be managed via SNMP, removing the 5 or 25 node limit.
- Support for SUSE Linux via USB.
- Security Enhancements
- SNMPv3 (in addition to SNMPv1) support for Windows operating systems.
- SNMPv1 and SNMPv3 support for Linux operating systems.
- RSA key size less than 2048 bits are not supported.
- Upgrading the Log4j version to 2.17.1 to address Log4Shell vulnerabilities.
NOTE: PowerChute Business Edition v9.5.1 supports upgrades form PowerChute v9.5.0 only.
Known Issues
Problem/Issue
Initiating a shutdown through the Shutdown Now screen does not shut down the
UPS if an Interface Expander 2 (IE2) card is inserted.
Description
This is an issue with the IE2 card for both Smart and Simple Signaling
configuration with PowerChute Business Edition.
Problem/Issue
Some UPS devices with the SMX and SMC prefix, e.g. SMX3000LVNC, SMX3000HVNC,
SMC1500I, do not allow the values for High and Low Transfer Values to be
edited in the UPS Settings screen.
Description
This issue is specific to these UPS devices. When the values are edited and
saved, the new values do not persist and instead, the previous values remain.
To work around this, you can change these values using a Network Management 2
(NMC2) card.
Problem/Issue
Some UPS devices with the RT prefix, e.g. RT 2200 XL, RT 1000 XL, display some
events in the Event Configuration screen that are not supported by these
models. For example: AVR Boost Enabled, AVR Trim Enabled, AVR Boost Not
Enabled, AVR Trim Not Enabled, Extended Undervoltage, Extended Overvoltage,
Frequent Undervoltage, and Frequent Overvoltage.
Description
This issue is specific to these UPS devices and does not affect any
functionality.
Problem/Issue
No record is logged in the Event Log if you try to put your UPS into bypass
mode, and it is unsuccessful.
Description
This issue is specific to UPS devices that support bypass.
Problem/Issue
If a “Power Failed” or “Low Battery” event is triggered on some UPS devices
with the C postfix, e.g. SMT 750 C, SMC 1500C, the UPS does not shut down.
Description
The outlet group(s) connected to the UPS do shutdown; however, the UPS itself
does not. Manually turn off the UPS until these power-related events are
resolved, i.e. when the power returns.
Problem/Issue
You are unable to create an SNMPv3 profile with SHA1 as the Authentication
Protocol and AES-256 Ex as the Privacy Protocol.
Description
This issue is specific to the SHA1 and AES-256 Ex combination only.
Combinations using SHA-1 and AES-192 or AES-256 allow successful connection.
Problem/Issue
On some UPS devices with the SUA prefix, e.g. SUA3000RM, the “Replace Battery”
event is logged in the Event Log and the UPS status changes to “Replace
Battery” in the Battery Management page after a “Self Test Failed” event.
Description
This issue is specific to this UPS model.
Problem/Issue
On Type B UPS devices, except models with the SRC prefix, e.g. SRC1K1, SRC2KI,
SRC1K1-IN, and SRC1KUXI, a self test can be initiated if the battery
percentage is below 70%.
Description
This issue is specific to Type B UPS devices. Visit Knowledge Base article
FA315835 on the APC website to find out more about UPS model types.
Problem/Issue
Bypass-related events are not shown in the Event Configuration screen for some
UPS devices with the SRC prefix and UXI postfix, e.g. SRC2KUXI, SRC2000UXI,
SRC3000UXI.
Description
This issue is specific to these UPS models only.
Problem/Issue
Some fields in the Predictive Battery Replacement section of the Battery
Management page behave differently for UPS devices with the SRT prefix and LI
postfix, e.g. SRT1500UXI-LI, SRT1000RMXLI.
Description
The “Battery Installation Date” field cannot be modified, and the date might
not reflect the correct factory installation date. The “Predicted Replacement
Date” field shows the manufacture date of the battery pack instead of the
battery replacement date.
Problem/Issue
No events are logged in the Event Log for Runtime Calibration if PowerChute is
configured with Simple Signaling and communicating with a 990-0128D cable.
Description
This issue is specific to using the 990-0128D cable with Simple Signaling.
Problem/Issue
PowerChute reports a failed SNMPv3 connection attempt in the Event Log, though
the SNMPv3 connected has been successful.
Description
Certain MIB browsers attempt initial connections before using the correct
username specified in PowerChute. SNMPv3 connection has been successful, and
Event Log reports indicating a failed connection attempt can be disregarded in
this scenario.
Problem/Issue
The 940-0023 cable does not perform properly with a Back-UPS or a UPS using
Simple Signaling.
Description
PowerChute Business Edition requires the 940-0020 or the 940-0128 cable for
UPS communications using Simple Signaling. If you were using the 940-0023
cable with a previous PowerChute product, you must replace it with the
940-0020 or 940-0128 cable when you use PowerChute Business Edition.
Problem/Issue
PowerChute Business Edition Agent does not install on a system which is using
the SJIS locale.
Description
The SJIS locale is not supported by PowerChute Business Edition. The Japanese
local supported by PowerChute is euc and UTF-8.
Problem/Issue
PowerChute Business Edition Agents running on Linux may not be able to send
broadcast messages to Windows systems. If you are using Japanese-language
systems, messages sent from Linux to Windows may not be readable.
Description
These problems are the result of incompatibilities between Windows and Linux,
and cannot be resolved through PowerChute.
Problem/Issue
During the boot process, the server momentarily pauses and displays messages
similar to below:
modprobe: modprobe: can’t locate module char-major-4
Description
This is an issue that will not affect the performance of PowerChute.
Problem/Issue
RPM uninstaller reports:
Error: cannot remove /opt/APC/PowerChuteBusinessEditionAgent directory not
empty
Description
This is inaccurate. The directory is properly removed during the uninstall.
Problem/Issue
Following a power failure event, UPS devices with the SRC prefix, e.g. SRC1KI,
SRC2KI, do not automatically turn on when power is restored before the UPS
turns off. You can configure power failure events through
the Shutdown Settings screen and select one of the following options:
“Immediately”, “After UPS has been on battery for”, or “At runtime limit”.
Description
Manually turn the UPS on after the power failure event is resolved. If the
power failure was caused by the removal of the power cable, reconnect the
cable after the UPS turns off.
Problem/Issue
An error message is shown after stopping or restarting the PowerChute service
on Windows operating systems:
Windows could not stop the APC PBE Agent service on Local Computer.
Error 1053: The service did not respond to the start or control request in a
timely fashion.
Description
This error message can be ignored. PowerChute continues to operate after the
service is started.
Problem/Issue
On SUSE12SP3 operating systems, “Lost Communications” is shown after upgrading
to JRE v1.8_152 (64-bit).
Description
This issue is specific to this operating system and JRE v1.8_152. PowerChute
operates normally with the bundled JRE (v1.8_u144) and JRE upgrades until JRE
v1.8_151. This issue does not impact Windows or other Linux operating systems.
Problem/Issue
SSL and TLS e-mails do not work with Microsoft Exchange Server.
Description
This issue is specific to SSL and TLS e-mails with Microsoft Exchange Server.
To use SSL and TLS e-mail, use a Postfix e-mail server.
© 2022 Schneider Electric. All Rights Reserved.