PowerChute™ Network Shutdown
v4.2 Release Notes
The release notes provide important information about PowerChute Network Shutdown (PowerChute), including known
software issues and their solutions. For any additional troubleshooting and background help, see the PowerChute
Network Shutdown Product Center. The Product Center contains the most up-to-date troubleshooting and product
information.
What's new in v4.2
SNMP Configuration
• PowerChute can be discovered via SNMP by Network Management Systems, such as StruxureWare Data Center
Expert.
• SNMPv1 and SNMPv3 can be used to query and configure PowerChute Settings.
• PowerChute can generate SNMP traps for UPS critical events and lost communication events.
• PowerChute SNMP settings can be enabled and configured via the Web Interface and Silent Installation
configuration (INI) file.
• SNMP events are logged to the Event Log.
Additional Features
• PowerChute now detects the type of firewall used by Red Hat Linux and CentOS (firewalld) during installation to
automatically open the ports required for NMC communication.
Security Enhancements
• Updated to JRE 8 update 91, and JDK 8 update 91 on Mac OS X.
® ®
• Fix for DLL preloading vulnerability in the PowerChute Installer for Microsoft Windows , detailed in Microsoft
Security Advisory bulletin 2269637.
Issues Resolved in this Release
Visit the Knowledge base to view more detail on the following documented issues that are now resolved in v4.2.
Issue Details
Following installation on certain Solaris SPARC This issue has been resolved in PowerChute Network
systems, the PowerChute Web Server does not start, Shutdown v4.2.
and the Web User Interface is not accessible.
In an Advanced Configuration, PowerChute incorrectly This issue has been resolved in PowerChute Network
reports that there are no suitable hosts for VM Shutdown v4.2.
migration, when there are two hosts available.
The VM inventory on the VM Prioritization page does This issue has been resolved in PowerChute Network
not load successfully and a message displays Shutdown v4.2.
indicating that vCenter is inaccessible.
This issue occurred when there was a large number of
VMs in the inventory.
When vCenter Server is deployed on a VM and ESXi This issue has been resolved in PowerChute Network
hosts have multiple NICs, host shutdown can take Shutdown v4.2.
longer than expected. This occurs when PowerChute
attempts to connect to the IP address of each NIC
configured each ESXi host, and if some NIC IP
addresses are not accessible, PowerChute waits a 75
second delay per NIC to attempt connection before
timing out.
PowerChute redirects to an incorrect IP address when This issue has been resolved in PowerChute Network
redirecting from HTTP (port 3052) to HTTPS (port 6547). Shutdown v4.2.
PowerChute does not correctly redirect to the IP
specified in the pcnsconfig.ini file, under property
localHostAddress.
Known Issues
• General Issues
• Browser Issues
• Network Configuration
• SNMP Configuration
• Event Configuration and Logging
• Windows
• VMware
• Linux
• Mac OS X
General Issues on all Operating Systems
↑ Known Issues
Issue Solution
A PowerChute Network Shutdown (PowerChute) PowerChute should not shut down for critical events when they
Parallel-UPS Configuration is shutting down on only occur on only one UPS in a Parallel Redundant Configuration.
one critical event This is a known issue that occurs when the Configuration
Wizard is run again after the initial configuration for a Parallel
UPS. If you run the Configuration Wizard again after the initial
configuration you should re-start the PowerChute service.
PowerChute does not support Parallel Smart-UPS Contact APC to obtain the latest UPS firmware for Parallel
VT, prior to firmware v5.0. Smart-UPS VT.
After a power outage has been resolved, Upgrade the firmware on the Network Management Card to
PowerChute shuts down the Operating System the latest version, see downloads. To resolve the issue once it
every time it is started. This happens with a has started happening:
Redundant-UPS configuration and when using the 1. Temporarily remove the network cable from the
Network Management Card (NMC) firmware v3.2.x PowerChute machine before powering it on (this will
through v3.5.5. prevent PowerChute from communicating with the
NMC and triggering a shutdown).
2. Power on your PowerChute machine.
3. Upgrade the firmware on the NMC. The upgrade tool
will automatically reboot the NMC during the upgrade
process.
4. Re-attach the network cable to the PowerChute
machine and ensure communication is established with
the NMC.
When several actions are selected for the same Threading issues in Java occasionally cause the actions to
event, and the actions all have the same delay time, interfere with each other. Use different delay times for each
some actions do not occur. action.
PowerChute does not recognize a temperature or Switch the probe from the AP9631 Universal I/O port on the
humidity probe on the AP9631 Network right (labelled 2) to the port on the left (labelled 1). PowerChute
Management Card. will then recognize the probe.
PowerChute does not support an SMX or SMT UPS Disable the SCG option for these devices using the NMC UI.
device that is part of a Synchronized Control Group
(SCG). An SCG is set up using the Network
Management Card (NMC) user interface.
The PowerChute user interface is not available Wait a few minutes.
immediately after restarting a service or daemon.
The delay is caused by PowerChute carrying out
background validations and checks.
PowerChute does not allow you to log on again if If you accidentally close the browser, re-start the PowerChute
you exit the Setup Wizard by closing the Web service or daemon. Open the User Interface and complete the
browser. A message is displayed that another user Setup.
is already logged in.
If you change an existing command file path for an Change the path to the correct value, in the INI file or by using
event in the pcnsconfig.ini file (e.g. the PowerChute web user interface.
event_PowerFailed_commandFilePath) by typing an
invalid path, PowerChute will subsequently log an
error message in relation to an invalid value in the
ini file when it starts. It does not restore the
previous valid path from the pcnsconfig.ini.bak file.
After an initial configuration, if you subsequently For a) no workaround. For b) you need to re-start the service
change the IP address of any NMC using the Setup or daemon.
Wizard:
a. the establishment of communications with the
card is not recorded in the event log, and
b. when the IP address is for a different UPS
model type, the PowerChute list of events
does not automatically update.
When the PowerChute service or daemon starts, it Run the Setup Wizard again to set the correct PowerChute IP
validates the Pcnsconfig.ini value named address.
localHostAddress. (This is the PowerChute IP
address that is registered with the NMC). If
PowerChute has not already acquired an IP address
when this check occurs, PowerChute will report an
invalid value. PowerChute will report this as an
invalid value in the ini file.
In a Parallel Redundant UPS configuration, No workaround.
PowerChute might incorrectly report Lost
communications while on Battery when
communications are lost and only one UPS has
been on battery. The event log does not record the
On Battery event prior to this.
Following silent installation using IPv6, the Network 1. Use the full format address when entering IPv6 address
Management Card shows two entries for the e.g.:
PowerChute client unicast address. This occurs if a UNICAST_ADDRESS=fe80:0:0:0:80e9:7d49:2793:361
short format IPv6 address is entered in 6 before running the silent install.
silentInstall.ini for UNICAST_ADDRESS e.g.
2. If installation is already completed, the short format
UNICAST_ADDRESS=fe80::80e9:7d49:2793:3616 IPv6 address can be removed from the Network
Management Card via Configuration > PowerChute
This can result in the NMC sending unnecessary clients.
packets.
When PowerChute is installed on an IPv6 only Replace the Self-Signed SSL cert using the steps outlined in
machine the CN (Container Name) value in the self- Kbase FA176886.
signed SSL Certificate is set to 127.0.0.1. 1. Re-enable IPv4 on the machine and stop the
PowerChute Service.
2. Delete PowerChute-Keystore file from group1 folder
where PowerChute is installed.
3. Re-start the service.
On Linux/Unix/Mac OSX:
1. Stop the PowerChute service.
2. Add the IPv6 addresses and the Fully Qualified Domain
Name of the machine to /etc/hosts file.
3. Re-start the Service.
IPv6 support for PowerChute is only available for Upgrade the NMC firmware to v6.0.X or higher for IPv6
NMC Firmware v6.0.X or higher support.
User Interface Web Browser Issues
↑ Known Issues
Issue Solution
If the browser window remains open during an upgrade Close and re-open the affected web browser and access
to PowerChute v4.2 the PowerChute user interface the PowerChute user interface. The user interface will
does not display correctly following the upgrade, and a display correctly.
notification to delete the log file appears.
Mozilla Firefox does not load the PowerChute web Use the short hostname in Mozilla Firefox to load
interface when the Fully Qualified Domain Name is PowerChute the web interface. View the Mozilla Firefox
used. Support - Server Not Found issue for more information.
A security warning is displayed when launching the There are two possible solutions:
PowerChute User Interface in a browser stating that the 1. You can choose to add the PowerChute self-signed
Web Server SSL cert is not trusted. This occurs SSL cert as a trusted cert and ignore the warning.
because PowerChute uses a self-signed SSL cert by
default. 2. You can replace the default self-signed SSL cert
with a trusted SSL cert. See the Product Center.
PowerChute is not compatible with IE 10 Metro Use the desktop version of IE 10 to access the PowerChute
Version. UI on Windows 2012 and Windows 8. The start menu item
for PowerChute will launch using the desktop version of IE
for these operating systems .
Network Configuration
↑ Known Issues
Issue Solution
PowerChute Network Shutdown web interface will not On a private network using a static IP address, use
load using the Fully Qualified Domain Name in a http://localhost:6547 to load the PowerChute web interface.
private network using a static IP address - FQDN
cannot be resolved. This issue only occurs if there is
no DNS server configured for the network card.
After you uninstall PowerChute Network Shutdown, the Delete the IP address from the list of PowerChute agents in
Network Management Card (NMC) still lists the IP the NMC User Interface.
address on the PowerChute agents page.
On a machine with multiple network cards, when None. There is no functional impact caused by this issue.
PowerChute issues a UPS/Outlet Turn off command,
the Network Management Card (NMC) may show the IP
address of one of the other network cards instead of
the IP address that was used to register with the NMC.
SNMP Configuration
Issue Solution
PowerChute reports a failed SNMPv3 connection SNMPv3 connection has been successful, and Event Log
attempt in the Event Log, though the SNMPv3 reports indicating a failed connection attempt can be
connection has been successful. disregarded in this scenario.
Certain MIB browsers attempt initial connections
before using the correct user name specified in
PowerChute.
Event Configuration and Logging
↑ Known Issues
Issue Solution
PowerChute reports Communications established There is no loss of communications with the NMC and this
with the NMC, and then reports that PowerChute issue does impact the functionality of the vMA in any way.
cannot connect to the NMC. This issue occurs when
PowerChute is configured to use IPv6, when
PowerChute is installed on a vMA and the vMA is
restarted following configuration.
A UPS Critical event is reported twice with a delay There is no workaround to this issue. This issue may cause a
between each event logged. This issue can occur in slight delay in starting the shutdown sequence, as
the following scenarios: PowerChute checks if the target ESXi hosts are available in
the inventory.
• When a host has been removed from the Host
Protection page in any UPS configuration, or
• When a host has been linked to a different
UPS/Outlet group on the Host Protection page,
or
• When ESXi hosts have Multiple Kernel
Adapters with multiple IPs associated for each
Kernel Adapter.
Hostlist key is not removed from HostConfigSettings Restart the PowerChute Service.
section in the pcnsconfig.ini file when switching
from Single to Advanced UPS Configuration, and the
following event appears in the Event log:
WARNING: The invalid key hostlist should be
deleted from section HostConfigSettings in the ini
file
The Multiple Critical Events Occurred event is You can ignore the second instance of "On Battery" in this
logged with "On Battery" displaying twice: "Multiple logged event.
Critical Events occurred: On Battery, On Battery,
UPS Turn Off Initiated".
Clicking on the Export button on the Event Log page Click on Tools - Internet Options in Internet Explorer and click
does not save a copy of the Event Log on the local on the Advanced tab. Disable the option "Do not save
machine. encrypted pages to disk". For more information see
http://support.microsoft.com/kb/2549423.
When you switch PowerChute to connect to a Restart the PowerChute service to display the correct list of
different type of UPS device the list of configurable events.
events is not updated in the UI. (Different UPS
devices can have different configurable events).
On MGE Galaxy 300/ 7000 UPS devices: sometimes With the MGE Galaxy 300/ 7000 devices, on the NMC user
the Runtime: Exceeded event is incorrectly cleared interface ensure that the Maximum Required Delay is always
in the event log. equal to or greater than the Maximum Negotiated Delay.
After the PowerChute service or daemon start, No workaround.
PowerChute does not log the communications
established event for a Parallel system until all of the
NMCs are in communication with PowerChute. It
should report communication established when at
least one NMC is communicating with PowerChute.
Windows
↑ Known Issues
Issue Solution
Command files do not run properly when called by The command file must use the @START command to run
PowerChute. The command file stops before all of the executable programs, and use the full path name of the
statements have executed. program. Path names that include spaces must be
enclosed in quotes. Arguments for the executable must be
outside the quotes.
For example, if you must run HyperTerminal and Backup in
your command file, use the syntax:
@START "c:\Program Files\Windows NT\hypertrm.exe"
arguments
@START c:\Winnt\system32\backup arguments
A PowerChute client that acquires its IP address Each system using PowerChute must have a permanent IP
through DHCP will lose communications with the address. Reserve IP addresses in DHCP by using the MAC
Network Management Card when the client renews its address, so that they never change for specified machines.
DHCP address lease and acquires a different IP
address.
After a graceful shutdown by PowerChute, the server At this time, there are no updates available for this issue.
does not turn on when utility power is restored. Check Windows Update for the latest updates and service
packs for your operating system.
Due to changes in the power management feature in
Windows XP SP1 and Windows 2003, some servers
with an ACPI (Advanced Configuration and Power
Interface) BIOS will not turn on when utility power is
restored after an outage.
The following is an example of what may occur:
• A server is attached to a UPS and running
PowerChute. PowerChute is configured to shut
down the operating system when the UPS has
been on battery for a specific time.
• With a utility power outage, causing the on-
battery event, PowerChute commands the
operating system to shut down gracefully.
• Because ACPI power management is controlled
by the operating system rather than by the BIOS,
when the operating system completes its
graceful shutdown, it commands the server to
turn off.
• The UPS remains on battery until its shutdown
delay time has expired. When utility power is
restored, the UPS provides power; the server
does not turn on.
On Windows 2003 (without SP1 installed), when a "Low Install the SP1 update for Windows 2003.
Battery" event occurs or any event with "Shut Down
System" enabled, the operating system should shut
down but it does not.
The UDP and TCP exceptions for PowerChute are only See Microsoft TechNet.
applied to the active profile in the Windows Firewall
(and only one profile can be active at a time). If the
active profile is changed you will need to manually add
exceptions for TCP ports 3052 and 6547 and UDP port
3052.
VMware
↑ Known Issues
Issue Solution
If VM shutdown is enabled but the duration value is set Set a non-zero value for VM shutdown duration.
to 0 seconds the shutdown sequence will not proceed.
In an Advanced UPS configuration, if the vCenter Re-start the PowerChute service and associate the
Server IP address is changed on the Communication VMware hosts in the new vCenter Server Inventory with the
Settings page, the VMware hosts that were previously UPS's.
associated with UPS's are not removed from the target
host list.
When there are multiple vApps in different clusters, None. PowerChute does not perform any operations on
PowerChute may log events for vApps that are not these vApps.
running on the VMware Hosts being protected.
If the ESXi Host running vCenter Server VM is not Run the Setup Wizard again, ensure that the vCenter
added on the Host Protection page during the Setup Server VM Host is added to the Host Protection page and
Wizard, or if the Setup Wizard is exited without complete the Setup Wizard.
applying the vCenter Server VM Shutdown duration on
the Virtualization Settings page, the vCenter Server VM
shutdown duration is not applied correctly when the
Host is added on the Host Protection page and
Virtualization Settings are updated in the Main UI.
PowerChute Web UI is inaccessible via vSphere Web In the information bar select the option to display blocked
Client plug-in on first launch. The following error content or install the PowerChute SSL certificate to the
message is displayed: Trusted Root Certification Authority Store, or replaced the
"Content was blocked because it was not signed by a default self-signed SSL cert with a trusted cert per the
valid security certificate." instructions in FA176886.
Following a service re-start on a vMA or PowerChute No workaround
Virtual Appliance, VMs which contain High ASCII or
DBCS characters in their name may be stored in
pcnsconfig.ini file using a different encoding. This can
cause issues for VM Prioritization and VM startup, as
the name stored in the INI file will not match what
appears in the vCenter Server inventory.
Linux
↑ Known Issues
Issue Solution
HP-UX
PowerChute fails to shutdown HP-UX machine Do not install or restart the PowerChute daemon using the
when installed via iLO/MP Console. This can also iLO/MP Console. Either log on directly or use SSH/rlogin to
occur if the PowerChute daemon is restarted via connect remotely.
iLO/MP Console.
Solaris
When configuring the "Notify User" option in Specify All Users when configuring the "Notify User" option.
PowerChute, if a Single User is chosen, the user
does not receive the notification.
Ubuntu
On Ubuntu with KDE 4.8.5, clicking the Close Update to KDE 4.9.0.
button in the PowerChute About box will crash the
Rekonq browser.
Red Hat Enterprise Linux (RHEL)
PowerChute fails to install on 32-bit RHEL 5.x. A This occurs due to a bug in SELinux.
permission-denied error message for the file 1. Temporarily disable SELinux to complete the
libjvm.so is displayed. installation:
/usr/sbin/setenforce 0
2. Run the following command after completing the
installation:
chcon -t textrel_shlib_t
'/opt/APC/PowerChute/jre1.7.0_45/lib/i386/client/libjvm.s
o'
3. Re-enable SELinux:
/usr/sbin/setenforce 1
Mac OS X Issues
↑ Known Issues
Issue Solution
In SilentInstall.ini add the IPv6 address of the PowerChute
Following silent installation using IPv6 on MAC machine to the key:
OSX the event log reports the following error: "LOCAL_IP_ADDRESS=000.000.000.000" and remove the
"ERROR: The ini contains an invalid value for comment symbol: #.
localHostAddress in section Networking." This needs to be done in addition to specifying the IPv6
address in the #UNICAST_ADDRESS= key.
Copyright © 1999-2016 Schneider Electric.
All rights reserved.
http://www.apc.com
990-2468K-001
08-2016
