Schneider Electric PowerChute User Manual
User Guide
PowerChute™ Network Shutdown v4.4.1
Standard
990-4595H-001
01/2021
Schneider Electric Legal Disclaimer
The information presented in this manual is not warranted by Schneider Electric to be authoritative, error free,
or complete. This publication is not meant to be a substitute for a detailed operational and site specific
development plan. Therefore, Schneider Electric assumes no liability for damages, violations of codes,
improper installation, system failures, or any other problems that could arise based on the use of this
Publication.
The information contained in this Publication is provided as is and has been prepared solely for the purpose of
evaluating data center design and construction. This Publication has been compiled in good faith by Schneider
Electric. However, no representation is made or warranty given, either express or implied, as to the
completeness or accuracy of the information this Publication contains.
IN NO EVENT SHALL SCHNEIDER ELECTRIC, OR ANY PARENT, AFFILIATE OR SUBSIDIARY COMPANY
OF SCHNEIDER ELECTRIC OR THEIR RESPECTIVE OFFICERS, DIRECTORS, OR EMPLOYEES BE
LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL, OR INCIDENTAL
DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS, CONTRACT,
REVENUE, DATA, INFORMATION, OR BUSINESS INTERRUPTION) RESULTING FROM, ARISING OUT,
OR IN CONNECTION WITH THE USE OF, OR INABILITY TO USE THIS PUBLICATION OR THE CONTENT,
EVEN IF SCHNEIDER ELECTRIC HAS BEEN EXPRESSLY ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES. SCHNEIDER ELECTRIC RESERVES THE RIGHT TO MAKE CHANGES OR UPDATES WITH
RESPECT TO OR IN THE CONTENT OF THE PUBLICATION OR THE FORMAT THEREOF AT ANY TIME
WITHOUT NOTICE.
Copyright, intellectual, and all other proprietary rights in the content (including but not limited to software, audio,
video, text, and photographs) rests with Schneider Electric or its licensors. All rights in the content not expressly
granted herein are reserved. No rights of any kind are licensed or assigned or shall otherwise pass to persons
accessing this information.
This Publication shall not be for resale in whole or in part.
Table of Contents
Introduction ................................................................................................................................................................... 1
UPS Configuration ........................................................................................................................................................ 2
Network Configuration ............................................................................................................................................... 3
UPS Configuration Options ....................................................................................................................................... 4
Network Management Card Connection ................................................................................................................... 6
Advanced UPS Setups .............................................................................................................................................. 8
Outlet Group Registration ....................................................................................................................................... 10
Network Management Card Settings ...................................................................................................................... 11
Shutdown Settings ...................................................................................................................................................... 12
UPS Shutdown ........................................................................................................................................................ 13
Shutdown Command Files ...................................................................................................................................... 14
Shutdown Settings for Advanced UPS Configurations ........................................................................................... 15
SSH Settings ............................................................................................................................................................... 17
SNMP Configuration ................................................................................................................................................... 20
SNMPv1 Configuration ............................................................................................................................................ 21
SNMPv3 Configuration ............................................................................................................................................ 22
SNMP Trap Configuration ....................................................................................................................................... 23
SNMP Data Points .................................................................................................................................................. 25
Event Configuration .................................................................................................................................................... 32
Notifications ............................................................................................................................................................. 33
Event-Driven Command Files ................................................................................................................................. 34
Shutdown Actions ................................................................................................................................................... 35
Sequenced Server Shutdown ..................................................................................................................................... 36
Sample Shutdown Scenarios ...................................................................................................................................... 37
UPS without Outlet Groups ..................................................................................................................................... 38
UPS with Outlet Groups .......................................................................................................................................... 40
PowerChute Events and Logging ............................................................................................................................... 44
Configurable Events ................................................................................................................................................ 45
Configurable Environmental Events ........................................................................................................................ 49
Non-Configurable Events ........................................................................................................................................ 50
Configuration (INI) File Events ................................................................................................................................ 54
SSH Action Events .................................................................................................................................................. 56
Java Update Events ................................................................................................................................................ 57
Critical Events in a Redundant-UPS Configuration ................................................................................................. 58
Critical Events in a Parallel-UPS Configuration ...................................................................................................... 59
General ....................................................................................................................................................................... 60
Communications Settings ....................................................................................................................................... 61
i
Table of Contents
PowerChute Agents ................................................................................................................................................ 62
PowerChute Configuration File ............................................................................................................................... 63
Java Update ............................................................................................................................................................ 64
User Interface Session Timeout .............................................................................................................................. 65
Check for Updates .................................................................................................................................................. 66
Customer Support ................................................................................................................................................... 67
Customer Experience Improvement Program (CEIP)............................................................................................... 68
Troubleshooting .......................................................................................................................................................... 69
Network
Browser Troubleshooting ........................................................................................................................................ 71
SSH Ac
SNMP Troubles
General Troubleshooting ......................................................................................................................................... 74
Management Card Troubleshooting ......................................................................................................... 70
tions Troubleshooting ................................................................................................................................. 72
hooting ........................................................................................................................................... 73
ii
Introduction
After installation, it is essential to configure t he software using the PowerChute Setup wizard. This
ensures that PowerChute is aware of UPS critical events in order to protect
PowerChute
(NMC) to provide network-based s hutdown of multiple computer systems.
In the case of a UPS critical event, the software performs a graceful, unattended system shutdown before the UPS
battery is exhausted. The number of protected sy st ems is limited only by the capacity of the UPS.
View these Application Notes for detailed information on using PowerChute in specific environments.
TM
Network Shutdown (PowerChute) works in conjunction with the UPS Network Management Card
your system.
1
UPS Configuration
This section contains information on the topics below:
• Network Configuration
• U
PS Configuration Options
• N
etwork Management Card Connection
• A
dvanced UPS Setups
• O
utlet Group Registration
etwork Management Card Settings
• N
2
PowerChute Network Shutdown: Standard User Guide
Network Configuration
PowerChute can use IPv4 or IPv6 to communicate wi th the Network Management Card(s).
IPv6 support is available only for Network Management Card 2 firmware 6.0.X or higher, and Network
Management Card 3.
Select IP
If your computer has more than one IPv4 address you wil l need to select one of the available addresses. The IP
address you select will be registered with the NMC a nd di splayed in the NMC user interface under Configuration PowerChute Clients.
IPv6 Configuration
If you are using IPv6 to communicate with the NMC(s), each network adapter on your machine will typically have
several IP addresses assigned to it. Each adapter will have at least one link-local address and one global unicast
address assigned to it.
Use the Unicast IP Address drop-down box to specify which address to use. The address type selected in this
drop-down box must match the address type that you enter for the NMC(s) on the Network Management Card
Connection page. This unicast address will be re gi stered on the NMC(s) and displayed on the PowerChute
Network Shutdown Clients page of the NMC.
f
e80::88c8:3d95:bc02:74cc is an example of a li nk-local address.
2001:112:1:0:88c8:3d95:bc02:74cc is an example of a global unicast address.
Multicast Option
The NMC supports sending communication packets to an IPv6 Multicast address instead of sending unicast
packets to each PowerChute agent. To use this, enable the Multicast check box and enter an IPv6 Multicast
address.
The multicast address that is entered here will be re gi stered on the NMC(s) instead of the unicast address and
displayed on the PowerChute Network Shutdown Clients page of the NMC. The NMC(s) will send communication
packets to that multicast address.
FF0
2::1 is an example of a multicast address with link-l o cal scope so that only nodes on the same
physical network segment will receive it. I f using a link-local unicast address, you must use a multicast
address with link-local scope.
FF0E::1 is an example of a multicast address with global scope and the NMC will use its global unicast
address to send the packet. If using a global unicast address you must use a multicast address with global
scope.
For detailed information, please view "The Com m unications Process of PowerChute Network Shutdown" here.
3
UPS Configuration
UPS Configuration Options
For a detailed overview of which UPS’s support each confi guration, please view the “PowerChute Network
Shutdown Operating Modes and supported UPS Conf i gurat i ons” Application Note here.
Single-UPS Configuration
Redundant-UPS Configuration
Redundant-UPS Configuration: Two or more UPS's of the same model protect each server. Each UPS
can support the server load on its own. All UPS Network Management Cards communicate with each
server that has PowerChute installed.
For detailed information, please view “Using PowerChute Network Shutdown in a Redundant-UPS
Configuration” Application Note here.
Parallel-UPS Configuration
Parallel-UPS Configuration: Two or more UPS's of the same model protect the load and provide redundancy or
increased capacity depending on the load. The UPS outputs are tied together so a single output goes to the load. All
UPS Network Management Cards communicate with each server that has PowerChute installed.
4
PowerChute Network Shutdown: Standard User Guide
Note: To use the Parallel-UPS configuration, your UPS devices must already be configured to operate in parallel
mode.
For detailed information, please view “Using PowerChute Network Shutdown in a Parallel-UPS Configuration”
Application Note here.
Advanced UPS Configuration
For detailed information, please view the “Using P owerChute Network Shutdown in an Advanced Redundant
Setup” Application Note here.
5
UPS Configuration
The NMC uses a self
enable "Accept Untrusted SSL
the NMC if a self
Network Management Card Connection
Network Management Card 2 firmware v6.8.0 and higher, and Network Management Card 3 firmware v1.1.0.16
and higher uses the HTTPS protocol by default. T he default protocol for PowerChute is HTTPS which can be
changed to HTTP, although it is not recommended.
The default port is 80 for HTTP, and 443 for HTTPS. Do not change this number unless you changed the port being
used by your NMC.
-signed SSL certificate by default when HTTP S is enabled. You need to
Certificates" to allow PowerChute to establish communication with
-signed certificate is being used by the NMC.
For Redundant and Parallel configurations, you need to enter more than one IP address to enable
communications with all the relevant NMCs.
For more information on UPS configurations and supported UPS models, view the Application Note "PowerChute
Network Shutdown Operating Modes and supported UPS Configurations" here.
Add each IP address using the + Add IP Address butt on. Enter the IP address of the NMC in the UPS. Click OK.
To edit an
IP address, click the icon. To delete an IP address, click the icon.
Adding a Trusted Certificate to PowerChute for NMC communication
When using the HTTPS protocol to communicate with the NMC, you must select the Accept Untrusted SSL
Certificates check box. However, it is possible to create a Trusted Certificate file and add it to the PowerChute
truststore.
Your NMC Security Handbook has details on the Security Wizard used to create the Trusted Certificate file with an
extension .CRT. This file is then used to create com ponents that can be uploaded to the NMC to replace the default
self-signed certificate.
In order to facilitate the trusted SSL communication of PowerChute with the NMC, this Trusted Certificate file must
then be added to the system Java cacerts keystore or to the PowerChutekeystore file. (You can do this using the
Java keytool.exe; for details see the Java help documentation). Adding it to the cacerts keystore means it is
available to all your applications as distinct from just PowerChute.
By default the PowerChute-keystore file is located in APC\PowerChute\group1. If you add the Trusted Certificate
and you subsequently get a connection error with the NMC, then it could be because a) the certificate has expired,
b) it is not yet valid, or c) it has been revoked. In any of these cases, you need to add a new Trusted Certificate to
the PowerChute server or to upload a new valid SSL certificate to the NMC.
6
PowerChute Network Shutdown: Standard User Guide
For more information, see the PowerChute Network Shutdown Security Handbook.
The PowerChute-keystore file only exists after the f irst attempt is made to communicate with the
NMC using HTTPS (by using the configuration wizard for example). For this reason, for a silent
installation you must add the Trusted Certificate to the Java cacerts keystore.
PowerChute only checks the keystore when it s se rv i ce starts. After you add the Trusted
Certificate, you will need to re-start the PowerChute service if it ’s already running.
NMC PowerChute Support
In NMC 2 firmware v6.8.0 and higher and NMC 3 firmware v1.1.0.16 and higher, PowerChute support is disabled
by default. This may result in an error while PowerChute registers with the NMC(s). If an error is displayed, log in to
the NMC UI and ensure PowerChute support is enabled.
In the NMC Web UI, you must specify a user name and aut hentication phrase before PowerChute can be enabled.
You must also choose the protocol used to communicate with PowerChute (HTTP/HTTPS). NOTE: The chosen
protocol must be enabled on the NMC before PowerChute communications can be established. For more
information, refer to the NMC User Guide available on the APC website.
7
UPS Configuration
Advanced UPS Setups
Add UPS Setup
In an Advanced UPS configuration, a single instan ce of PowerChute Network Shutdown can monitor multiple UPS
setups and initiate graceful shutdown of equipment based on different redundancy levels. Each setup can be a
single UPS or a UPS group. A single UPS setup is represented by the icon. A UPS group is represented by the
icon.
For example, one setup may be a group of UPS's that are conf i gured with N+2 redundancy. Another setup may be
a single UPS.
On the UPS Details page of the Setup Wizard, click the + Add UPS(s) button to create a new setup.
To create a setup with a single UPS, on the Configure UP S Setup dialog choose Single UPS:
1. Enter a UPS Setup Name (with a maximum of 20 ASCII characters)
2. Click the + Add IP Address button and enter the IP address of the Netw ork Management card in the UPS.
Click OK.
3. Click OK to complete Single UPS Setup.
8
PowerChute Network Shutdown: Standard User Guide
PowerChute has been tested with a total of 16 NMC s in an advanced configurat
possible to configure for more than 16 NMCs in this conf iguration.
To create a setup with a group of UPS devices, choose UPS Group:
1. Enter a UPS Setup Name (with a maximum of 20 ASCII characters)
2. Click the + Add IP Address button and enter the IP address of the Netw ork Management card in the UPS.
Click OK.
3. Repeat for each of the UPS devices to be added to the UPS group. A minimum of 2 IP addresses is
required to set up a UPS Group.
4. Click OK to complete Group UPS Setup.
Repeat for each UPS setup required.
To edit a UPS Setup, click the icon. To delete a UPS setup, click the icon.
Click the Next button to go to the next step of the Setup Wizard.
ion. However it is
For detailed information, please view the “Using P owerChute Network Shutdown in an Advanced Redundant
Setup” Application Note here.
9
UPS Configuration
Outlet Group Registration
If your UPS supports outlet groups you must specif y which one the server is being powered by so that PowerChute
can monitor it for shutdown events and also issue turn-off commands to that outlet group.
UPS Shutdown Behavior in Mixed UPS Environments
If your servers are being powered by a mix of outlet-aware UPS’s (e.g. SMX/ SMT) and non-outlet-aware UP S’ s
(e.g. SU/ SUA) in a Redundant UPS Configuration, P owerChute only provides the option to turn off the UPS and
not the outlet group.
Your servers are still protected if there is a UPS critical event or if the outlet group is commanded to shut down e.g.
via the NMC User Interface.
10
PowerChute Network Shutdown: Standard User Guide
Network Management Card Settings
For Single, Redundant and Parallel UPS configurat i ons, the IP address of each NMC that PowerChute is
communicating with is displayed under the UPS Configuration menu option.
For Advanced UPS configuration, each UPS Setup is displayed as a menu item and the IP address of the NMC(s)
with which PowerChute is communicating is displayed under each UPS setup.
Click on the IP address to view the UPS information specific to that NMC.
UPS information displayed includes:
• NMC IP Address
• UPS model name
• UPS configuration
The NMC Host Name from the NMC's DNS settings page under Network - DNS - Configuration is also displayed.
This is not the same as the UPS name that can be set under Configuration - UPS General on the NMC.
Clicking the Launch button opens the NMC user interface.
11
Shutdown Settings
The Shutdown Settings page enables you to config ure UPS turnoff and the shutdown command files.
• UPS Shutdown
• Shutdown Command Files
• Shutdown Settings for Advanced UPS Configurati ons
12
PowerChute Network Shutdown: Standard User Guide
The default behavior for most UPS’s if they are turne d off following an on
they will turn on again once input power is restored.
The
Shutdown where you can change the behavior to Turn off and Stay off if required.
This is not available for an Advanced UPS Configuration that contains UPS Setups with
Redundant UPS devices.
If one UPS is on battery and anoth
Single UPS turn off has elapsed, then the first UPS will not be turned off.
UPS Shutdown
The default setting is Do not turn off the UPS.
You can select Turn off the UPS if you want to preserve battery power. Some U PS’s do not support UPS turnoff
through PowerChute or the NMC. For these models, i t can only be done at the UPS itself. Please check your UPS
documentation to ensure your model supports UPS turnoff.
If your UPS has Switched Outlet Groups, then t he Turn off the UPS Outlet Group option enables you to turn off
the outlet group that supplies power to the PowerChute protected server after a critical event occurs.
-battery shutdown is that
On-Battery Shutdown Behavior setting can be found in the NMC under Configuration –
Turn Off Single UPS On Battery in a Redundant-UPS Configuration
In a Redundant UPS configuration you have the option to turn off one of the UPS’s after it has switched to battery
power. This is designed to prolong the battery li fe and preserve the battery power of the UPS. If using this feature
on a UPS that supports outlet groups the option "Turn off the UPS" should be enabled.
The load is still protected by the other UPS in t he configuration.
After the specified delay, PowerChute will is sue a command to gracefully turn off the UPS.
er UPS switches to battery before the configur ed delay for
If the shutdown action is enabled for the On Battery event, a Multiple Critical event condition will
occur if a second UPS switches to battery power (aft er the first UPS has been commanded to
turn off by PowerChute). When this occurs the shutdown sequence will start after 10 seconds.
13
Shutdown Settings
Shutdown Command Files
A Shutdown Command File can be configured to run if a UPS critical event is triggered.
Full path to command file: You must specify the full path name of the command file, including the disk drive
or volume name. For Linux and Unix systems, the file should execute permissions of chmod +x [command file
name].
The command file must be located in the user_files folder, or a sub-folder, in the PowerChute
installation directory. If the default installation directory was chosen during installation, this location will
be:
• C:\Program Files\APC\PowerChute\user_files for Windows systems
• /opt/APC/PowerChute/user_files/ for Linux systems
NOTE: If you are upgrading to PowerChute v4.4, any command files used in a previous version of
PowerChute must be manually added to the user_files folder. If the command files are not added to the
directory, you will see the below errors/warnings for the ShutdownStarting event, and all events
configured to run a command file, in the Event Log:
ERROR: Event ShutdownStarting is enabled for command file execution, but an
invalid value for shutdownCommandFile is specified.
WARNING:
bad parameters. Please validate the configuration.
It is strongly recommended you validate your configuration after an upgrade.
Duration: Enter the number of seconds that the shutdown command file requires to execute.
NOTE: For Advanced UPS Configurations, if there are different command files configured for each
UPS Setup, PowerChute may need to wait for all command files to finish executing before
proceeding with the final steps in the shutdown se quence. This is dependent on the timing that
UPS critical events occur on each UPS Setup. PowerChute will automatically increase the Outlet
Group Power Off delay or Maximum Required delay (non -outlet aware UPS) to include the
combined total of the shutdown command file durat ions for each UPS Setup. This can impact the
runtime available on the UPSs during a shutdown. To accommodate this, set the low battery
duration on the UPSs accordingly.
You must determine the time required for your comm and file to execute. PowerChute cannot
determine whether the command file has complet ed, so it will wait only the amount of time entered
before triggering an operating system shutdown.
Disabling command file execution for event ShutdownStarting due to
The command file runs using the local system account . For Linux/Unix the command file must be executed with
root privileges. PowerChute cannot execut e programs that require interaction with the desktop; only command li ne
enabled programs are supported.
14
PowerChute Network Shutdown: Standard User Guide
Shutdown Settings for Advanced UPS Configurations
With Advanced UPS configurations, PowerChute can monitor multiple UPS setups, including single UPS devices
and groups of redundant UPS devices that you have created (see “Advanced UPS Setups”).
For each setup, you need to specify the following:
Field Description
Number of UPS’s required to
power load
Number of additional (redundant)
UPS’s
Set this value to the minimum number of UPS’s that must be
available to support the equipment that is being powered by the
UPS’s in the setup.
The value set here will be subtracted from the total number of
UPS’s in the setup and used to calculate the numbe r of additional
(redundant) UPS’s.
In redundancy terminology, this is the N in N+x.
This setting is not displayed for UPS Setups with a Singl e UP S
device.
This will appear in a setup with more than one UPS. It represents
the number of extra UPS’s in the setup. This option is associated
with the number of UPS critical events required to trigger
shutdown:
Redundancy level No. of critical events that
will trigger a shutdown
sequence
N+1 2
N+2 3
N+3 4
Multiple critical events occurring on the same UPS does not
impact the above table values.
In redundancy terminology, this is the x in N+x.
This setting is not displayed for UPS Setups with a Si ngle UPS
device.
Total number of UPS’s in Setup This is the total of the above two rows and is calculated
automatically.
15
Shutdown Settings
See Shutdown Command Files.
Run Command When a shutdown sequence is triggered you can co nfigure
PowerChute to execute a command file.
Note: If the same command file is configured for each setup and
a shutdown sequence is triggered for more than one setup at the
same time, the command file is only executed once.
Shut down PowerChute Server This is enabled by default and is used to gracefully shut down the
physical machine running PowerChute.
This option should be disabled if the PowerChute machine is not
being powered by the UPS’s in a particular setup, and i f it is
being used to remotely shut down other servers/ equipment.
Shut down if Redundancy lost If this option is enabled, when the number of UPS crit i cal events
is the same as the number of additional (redundant) U PS’s, a
shutdown sequence will be triggered.
This option is associated with the number of UPS critical events
required to trigger shutdown:
UPS Shutdown
Redundancy level No. of critical events that
will trigger a shutdown
sequence
N+1 1
N+2 2
N+3 3
Multiple critical events occurring on the same UPS does not
impact the above table values.
This option is not shown if there are no additional (redundant)
UPS’s. For example, this option will not appear if the number of
UPS’s required to power the load is the same as the total number
of UPS’s in the group.
Use this option to set the required UPS behavior after connected
equipment or servers are gracefully shut down. For more
information see UPS Shutdown.
16
SSH Settings
PowerChute Network Shutdown can be config ured to execute commands on a remote host via an SSH connection.
To create an SSH action, click Add Action and configure the following:
1. Name: A unique name for each SSH action of a length less than or equal to 255 ASCII characters.
2. Configure one of the following authentication methods:
• User Name and Password: Enter the user name and password to connect to the remote host.
• User Name, SSH Key File Path and SSH Key File Password: Specify the path to a shared SSH
key. This option requires you to generate an SSH key and c
SSH Command File Location.
3. IP Addresses/FQDN and Port: The IP address or Fully Qualified Domain Name (FQDN) and port of the
target SSH component.
4. Path to SSH command file: You must specify the full path name of the command file, including the disk
drive or volume number. See SSH Command File Location.
5. SSH Action Delay: Enter the amount of time, in seconds, that PowerChute will wait before connecting to
the remote host and begin sending commands. The default value is 0.
6. SSH Action Duration: Enter the amount of time, in seconds, for the SSH action to complete before
proceeding with the rest of the shutdown sequence.
opy it to your target systems. See
Using the SSH Action Duration fi eld, you must allow sufficient time for all your SSH
actions to complete.
7. Execute SSH Action:
• On Startup: Execute the SSH command file when the PowerChute service re-starts. In an
advanced configuration, the SSH command file is executed when the critical UPS event is
resolved.
• Before Host Shutdown: Execute the SSH command file before host shutdown.
• After Host Shutdown: Execute the SSH command file after host shutdown.
8. Enable SSH Action: Allows you to enable or disable the configured SSH action. This checkbox is enabled
by default when a new SSH action is created.
17
SSH Settings
NOTES:
• PowerChute takes the command file provided and passes it line-by-line to the remote host
over an SSH connection. As a result, incomplete lines may be interpreted incorrectly by
the remote host. You must ensure that your SSH command file contains complete lines
and commands so the remote host can interpret the file correctly.
• The line ending style of the command file must match that of the PowerChute target host
operating system. For example, a command file configured on PowerChute running on a
Windows host must contain Windows style text line endings.
• Recognized command prompts are:
• $ (Linux)
• # (Linux admin/root)
• > (Windows, or RPDU)
• Custom command prompts can be added via the PowerChute configuration file
(pcnsconfig.ini) by adding the "ssh_prompt_regex" setting to the [SSHAction]
section. For example: to add a custom command prompt of "~", add
"ssh_prompt_regex = \~\s".
• The PowerChute Event Log only displays that an SSH action has completed. The Event
Log does not show if the SSH action has completed successfully or not.
• If a value is specified in the SSH Action Delay field, the Event Log does not log that an
SSH action is running with a configured delay.
18
PowerChute Network Shutdown: Standard User Guide
SH Command File Location
S
The
PowerChute installation directory. If the default installation directory was chosen during installation, this location will
be:
• C:\Program Files\APC\PowerChute\user_files for Windows systems
• /opt/APC/PowerChute/user_files/ for Linux systems
key
SSH
NOTE: If you are upgrading to PowerChute v4.4, any key files and/or command files used in a
previous version of PowerChute must be manually added to the user_files folder. If the files
are not added to the directory, you will see the below errors in the Event Log:
ERROR: The ini contains an invalid value for ssh_command_file_path in
section SSHAction0.
ERROR: The ini contains an invalid value for ssh_keyfile_path in
section SSHAction0.
It is strongly recommended you validate your configuration after an upgrade.
file,
if
configured,
and
command
file
must be located in the user_files folder, or a sub-folder, in the
SSH Settings in an Advanced UPS Configuration
In an Advanced UPS configuration, SSH actions can be enabled and disabled for each UPS setup.
The symbol indicates that an SSH action is enabled in the main SSH Settings screen. To run an SSH action for
a particular UPS setup, enable the checkbox next to the
SSH actions that
enabled for a UPS setup.
are not enabled do not display the
symbol.
symbol. These disabled actions will not be executed if
19
SNMP Configuration
PowerChute Network Shutdown can be config ured to communicate via Simple Network Management Protocol
(SNMP), and can be discovered via SNMP by Networ k Management tools, such as StruxureWare Data Center
Expert. Using SNMP, you can query and configure P owerChute settings, and generate SNMP traps for UPS critical
events and lost communication events.
SNMPv1 and SNMPv3 are supported by PowerChut e Net work Shutdown. IPv4 and IPv6 are both supported. Go to
SNMP Settings in the web user interface to complete the configuration and make PowerChute accessible via
SNMP. It is not necessary to re-start the PowerChute service when enabling SNMP or making SNMP configuration
changes via the web user interface. PowerChute c onfiguration changes via SNMP are logged to the Event Log.
Enter the SNMP Discovery Port. The default value of 161 is automatically populated, but this can be edited if this
port is already in use. The Port number availabili ty is automatically checked, and if it is not available, a new port
number must be entered.
See:
• SNMPv1 Configuration
NMPv3 Configuration
• S
• SN
• SN
• S
MP Trap Configuration
MP Data Points
NMP Troubleshooting
20
Loading...