PowerChute Network Shutdown | ||
These release notes provide important information about PowerChute Network Shutdown, including known software problems and their solutions (if any). For any additional troubleshooting, see http://swhelp.apcc.com/pcns/help/troubleshootingguide_EN. |
Table of Contents |
Note: After clicking on a link directly below, press the Back button on your Web browser to return to these contents. Alternatively, press the Ctrl + Home keys. |
General Problems On All Operating Systems |
Problem/Issue: Servers shut down and reboot continually when connected to the following Smart-UPS devices: SMT750, SMT1000, SMT1500, SMT2200, SMT3000, SMX750, SMX1000, SMX1500RM2U, SMX1500RM2UNC, SMX2000RMLV2U, SMX2200RMLV2U, SMX3000RMLV2U, SMX3000RMLV2UNC Solution:
Check the APC website for further Network Management Card firmware updates and releases. Problem/Issue:PowerChute Network Shutdown (PCNS) does not shut down when the UPS enters a bypass state that is caused by either a hardware or an internal fault. Solution: Enable Bypass: For Maintenance on the PCNS Configure Events page and configure it to shut down your system. Problem/Issue: PCNS does not support Parallel Smart-UPS VT, prior to firmware v5.0. Solution: Contact APC to obtain the latest UPS firmware for Parallel Smart-UPS VT. Problem/Issue: PCNS does not support Switched Outlet Group functionality. Solution: Some UPS devices have Switched Outlet Group functionality that is configurable using the Network Management Card (NMC). For example, it is possible to shut down, reboot or turn off a specific outlet group using the NMC. However, if the load is connected to that outlet group, PCNS will not shut it down gracefully. The NMC can also configure an outlet group to switch off in response to an On Battery or Overload event. PCNS can detect these events and they can be configured to cause a shutdown but you must enable this in PCNS and the PCNS shutdown delay must be less than the Power Off delay configured for the outlet group. If you intend to use this feature in the NMC you should disable the option "Turn off the UPS after the shutdown finishes" on the Configure Shutdown page in PCNS. Problem/Issue:After a power failure, your PCNS server shuts down repeatedly for no apparent reason. Solution: This only happens with a Multiple-UPS configuration and when using the Network Management Card (NMC) firmware v3.2.x through v3.5.5. Several things can trigger this problem after a power failure. For example, it could start happening after you manually turn off the power to one UPS in a configuration. Or it could start after a UPS has gone on battery and is turned off based on settings chosen on the Advanced Configuration page of the PCNS user interface. To avoid this problem, disable the option to turn off a UPS when it goes on battery on the Advanced Configuration page of the PCNS user interface. In addition, you should not turn off a UPS manually, that is, using the UPS power switch. To resolve this problem once it has started happening, you should reboot the NMC:
Problem/Issue:
Problem/Issue: Remote Authentication Dial In User Service (RADIUS) is not supported by PowerChute Network Shutdown. Solution: None. Problem/Issue: When installing on Windows, Linux, VMware, and Solaris, the most recent update of Java Runtime Environment (JRE) is not installed. Solution: Before installing or upgrading PowerChute Network Shutdown (PCNS), uninstall the current JRE on your system. Otherwise the PCNS installation program installs a JRE version that is valid and closest in number to the version already installed on your system (for example, if you currently have JRE 5.0 Update 11, the installation program would install JRE 5.0 Update 12, not 13). Problem/Issue: PowerChute Network Shutdown does not recognize a temperature or humidity probe on the AP9631 Network Management Card. Solution: Switch the probe from the AP9631 Universal I/O port on the right (labelled 2) to the port on the left (labelled 1). PCNS will then recognize the probe. Problem/Issue: PowerChute Agent machines are shut down following an On Battery event on one UPS in a Parallel configuration: this happens even though the other UPS's can support the load. Solution: This could be caused by a low shutdown delay time of 30 seconds or less if you have configured your system to shut down when the UPS's go on battery. If one UPS goes on battery in a Parallel configuration, it tries to transfer its load to the other UPS's, but a low delay time might not give it enough time to communicate with the PCNS system to accomplish this. Try increasing the shutdown delay time to be greater than 30 seconds; the default is two minutes. |
User Interface on Internet Explorer and Other Web Browsers |
Problem/Issue:
Problem/Issue:
Problem/Issue: |
Network Configuration | ||||||
Problem/Issue:
Problem/Issue: | ||||||
Event Configuration and Logging | ||||||
Problem/Issue:
Problem/Issue:
Problem/Issue: | ||||||
Windows | ||||||
Problem/Issue: 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
Problem/Issue:
Problem/Issue:
Problem/Issue: 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:
Problem/Issue: | ||||||
Mac OS X | ||||||
Problem/Issue:
Problem/Issue: | ||||||
AIX | ||||||
Problem/Issue: | ||||||
SUSE Linux Enterprise Server 10 | ||||||
Problem/Issue:
| ||||||
Red Hat Enterprise Linux 5 server | ||||||
Problem/Issue:
| ||||||
VMware | ||||||
Problem/Issue: | ||||||
Entire contents copyright © 2009 by Schneider Electric. All rights reserved. Reproduction in whole or in part without permission is prohibited. All trademarks, product names, and corporate names are the property of their respective owners and are used for informational purposes only.
|