Buscar Preguntas Frecuentes
Migrate PowerChute Network Shutdown configuration from PowerChute v4.2, v4.3 virtual appliance to v4.4 virtual appliance
Issue:
Migrate PowerChute Network Shutdown configuration from PowerChute v4.2, v4.3 virtual appliance to PowerChute v4.4 virtual appliance.
Product:
PowerChute Network Shutdown v4.4
Environment:
PowerChute v4.2 CentOS 7 virtual appliance, PowerChute v4.3 CentOS 7 virtual appliance, and PowerChute v4.4 CentOS 8.1 virtual appliance.
Solution:
NOTE: Some v4.2 virtual appliances are CentOS 5 based. To verify you're CentOS version, open a terminal and issue a cat /etc/*-release command. The expected output is:
If your v4.2 virtual appliance is CentOS 5 based, the steps below are not applicable.
Follow the steps below to migrate your PowerChute v4.2, v4.3 virtual appliance configuration to the v4.4 virtual appliance:
On the PowerChute v4.4 virtual appliance:
Migrate PowerChute Network Shutdown configuration from PowerChute v4.2, v4.3 virtual appliance to PowerChute v4.4 virtual appliance.
Product:
PowerChute Network Shutdown v4.4
Environment:
PowerChute v4.2 CentOS 7 virtual appliance, PowerChute v4.3 CentOS 7 virtual appliance, and PowerChute v4.4 CentOS 8.1 virtual appliance.
Solution:
NOTE: Some v4.2 virtual appliances are CentOS 5 based. To verify you're CentOS version, open a terminal and issue a cat /etc/*-release command. The expected output is:
NAME="CentOS Linux"
VERSION="5"
If your v4.2 virtual appliance is CentOS 5 based, the steps below are not applicable.
Follow the steps below to migrate your PowerChute v4.2, v4.3 virtual appliance configuration to the v4.4 virtual appliance:
1. Deploy a copy of the PowerChute v4.4 virtual appliance. Complete the initial configuration wizard to enable root access. For information, see the PowerChute Network Shutdown Installation Guide Log in as root and stop the PowerChute service:
2. Log in as root and stop the PowerChute service:
2. Log in as root and stop the PowerChute service:
systemctl stop PowerChute.service
On the PowerChute v4.2/v4.3 virtual appliance:3. Log in and stop the PowerChute service:
/etc/init.d/PowerChute stop
4. Save the below v4.x configuration files locally from the /opt/APC/PowerChute/group1 directory:
- m11.cfg
- m11.bak
- pcnsconfig.ini
- pcnsconfig_backup.ini
On the PowerChute v4.4 virtual appliance:
5. Copy the files saved in step 4 to the PowerChute v4.4 virtual appliance in the /opt/APC/PowerChute/group1 directory, and overwrite the existing files.
6. Run the INI upgrade tool to migrate the configuration between versions, from the group1 directory:
../jre-14.0.2/bin/java -Xms32m -Xmx64m -Dfile.encoding=UTF-8 -DapplicationDirectory=/opt/APC/PowerChute -cp .:lib/*:comp/pcns.jar --add-opens java.xml/com.sun.org.apache.xerces.internal.parsers=ALL-UNNAMED com.apcc.pcns.configservice.UpgradeIniConverter
7. Edit the pcnsconfig.ini file and change the value of localHostAddress in the section [Networking] to match the v4.4 virtual appliance IP address.
8. Delete the keystore firm the group1 directory /opt/APC/PowerChute/group1/keystore
9. Start the PowerChute service:
6. Run the INI upgrade tool to migrate the configuration between versions, from the group1 directory:
../jre-14.0.2/bin/java -Xms32m -Xmx64m -Dfile.encoding=UTF-8 -DapplicationDirectory=/opt/APC/PowerChute -cp .:lib/*:comp/pcns.jar --add-opens java.xml/com.sun.org.apache.xerces.internal.parsers=ALL-UNNAMED com.apcc.pcns.configservice.UpgradeIniConverter
7. Edit the pcnsconfig.ini file and change the value of localHostAddress in the section [Networking] to match the v4.4 virtual appliance IP address.
8. Delete the keystore firm the group1 directory /opt/APC/PowerChute/group1/keystore
9. Start the PowerChute service:
systemctl start PowerChute.service
10. Log into PowerChute using the user interface, and review the configuration settings.
Publicado para:APC Peru
Explora más
Explora más
