Schneider Electric PowerChute Network Shutdown v4.4.3 User Manual – Manuals+
IssueSolutionFollowing an upgrade from v4.3 to v4.4, PowerChute does not retain the Java version used if it was changed via the Java Upgrade feature; for example, to OpenJDK 15. After the upgrade to v4.4, PowerChute will use OpenJDK 14.Use the Java Upgrade feature in the PowerChute UI to manually upgrade the Java version again.Removing and disabling the shutdown
command file on the Shutdown Settings page In the PowerChute UI results in errors being displayed in the pcnsconfigini file after a service re-start.Manually add “shutdownCommandFile =” to the [ Shutdown) section of the pcnsconfigini file.PowerChute accepts usernames with more than 10 ASCII characters and displays the below event In the Event Log:
“Security information for [IP Address] Is Incorrect. Please check that the PowerChute User Name and Authentication Phrase match the Network Management Card.”No workaround.PowerChute does not start the web server until all the configured NMCs are contacted. This may result In a 3-4 minute delay in accessing the PowerChute UI if the NMCs are offline following a restart or an upgrade.No workaround.Following an upgrade from a previous version. the old powernet.mlb file is not removed from the groupl directory.Delete the old powemet.mib file after upgrade.A PowerChute Network Shutdown (PowerChute) Parallel-UPS Configuration Is shutting down on only one critical event.PowerChute should not shut down for critical events when they occur on only one UPS in a Parallel Redundant Configuration. 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 VT. prior to firmware v5.0.Contact APC to obtain the latest UPS firmware for Parallel Smoot-UPS VT.After a power outage has been resolved. PowerChute shuts down the Operating System every time it is started. This happens with a Redundant-UPS configuration and when using the Network Management Card (NMC) firmware v3.2.x through v3.5.5.Upgrade the firmware on the Network Management Card to the Latest version. see downloads. To resolve the issue once it has started happening:
1 Temporarily remove the network cable from the
PowerChute machine before powering it on (this will 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 event, and the actions all have the same delay time, some actions do not occur.Threading issues in Java occasionally cause the actions to interfere with each other. Use different delay times for each action.PowerChute does not recognize a temperature or humidity probe on the AP0631 Network Management Card.Switch the probe from the AP9631 Universal I/O port on the right (labelled 2) to the port on the left (labelled 1). PowerChute veil then recognize the probe.PowerChute does not support an SMX or SMT UPS device that is part of a Synchronized Control Group (SCG). An SCG is set up using the Network Management Card (NMC) user interface.Disable the SCG option for these devices using the NMC UI.The PowerChute user interface is not available immediately after restarting a service or daemon. The delay is caused by PowerChute carrying out background validations and checks.Wait a few minutes.PowerChute does not allow you to log on again if you exit the Setup Wizard by closing the Web browser. A message is displayed that another user is already logged in.If you accidentally close the browser, re-start the PowerChute service or daemon. Open the User Interface and complete the Setup.If you change an existing command file path for an event in the pcnsconfig.ini file (e.g. 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.Change the path to the correct value. in the INI file or by using the PowerChute web user interface.After an Initial configuration, if you
subsequently change the IP address of any NMC using the Setup 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.For a) no workaround. For b) you need to re-start the service or daemon.When the PowerChute service or daemon starts, It validates the Pcnsconfigini value named IocalHostAddress. (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 in’ file.Run the Setup Wizard again to set the correct PowerChute IP addressIn a Parallel Redundant UPS configuration. 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.No workaround.Following silent Installation using IPv6, the Network Management Card shows two entries for the PowerChute client unicast address. This occurs If a short format IPv6 address Is entered In silentInstallini for UNICAST_ADDRESS e.g.
UNICAST_ADDRESS=fe80::80e9:7d49:2793:3616
This can result in the NMC sending unnecessary packets.1.Use the full format address when entering IPv6 address e.g.: UNICAST_ADDRESS=fe80:0:0:0:80e9:7d49:2793:3616 before running the silent install.
2.If installation is already completed, the short format IPv6 address can be removed from the Network Management Card via Configuration > PowerChute clients.When PowerChute is installed on an IPv6 only
machine the CN (Container Name) value in the
self-signed SSL Certificate is set to 127.0.0.1.Replace the Self-Signed SSL cert using the steps outlined in Kbase FA176886.
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:
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 NMC Firmware v6.0.X or higherUpgrade the NMC firmware to v6.0.X or higher for IPv6 support.
command file on the Shutdown Settings page In the PowerChute UI results in errors being displayed in the pcnsconfigini file after a service re-start.Manually add “shutdownCommandFile =” to the [ Shutdown) section of the pcnsconfigini file.PowerChute accepts usernames with more than 10 ASCII characters and displays the below event In the Event Log:
“Security information for [IP Address] Is Incorrect. Please check that the PowerChute User Name and Authentication Phrase match the Network Management Card.”No workaround.PowerChute does not start the web server until all the configured NMCs are contacted. This may result In a 3-4 minute delay in accessing the PowerChute UI if the NMCs are offline following a restart or an upgrade.No workaround.Following an upgrade from a previous version. the old powernet.mlb file is not removed from the groupl directory.Delete the old powemet.mib file after upgrade.A PowerChute Network Shutdown (PowerChute) Parallel-UPS Configuration Is shutting down on only one critical event.PowerChute should not shut down for critical events when they occur on only one UPS in a Parallel Redundant Configuration. 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 VT. prior to firmware v5.0.Contact APC to obtain the latest UPS firmware for Parallel Smoot-UPS VT.After a power outage has been resolved. PowerChute shuts down the Operating System every time it is started. This happens with a Redundant-UPS configuration and when using the Network Management Card (NMC) firmware v3.2.x through v3.5.5.Upgrade the firmware on the Network Management Card to the Latest version. see downloads. To resolve the issue once it has started happening:
1 Temporarily remove the network cable from the
PowerChute machine before powering it on (this will 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 event, and the actions all have the same delay time, some actions do not occur.Threading issues in Java occasionally cause the actions to interfere with each other. Use different delay times for each action.PowerChute does not recognize a temperature or humidity probe on the AP0631 Network Management Card.Switch the probe from the AP9631 Universal I/O port on the right (labelled 2) to the port on the left (labelled 1). PowerChute veil then recognize the probe.PowerChute does not support an SMX or SMT UPS device that is part of a Synchronized Control Group (SCG). An SCG is set up using the Network Management Card (NMC) user interface.Disable the SCG option for these devices using the NMC UI.The PowerChute user interface is not available immediately after restarting a service or daemon. The delay is caused by PowerChute carrying out background validations and checks.Wait a few minutes.PowerChute does not allow you to log on again if you exit the Setup Wizard by closing the Web browser. A message is displayed that another user is already logged in.If you accidentally close the browser, re-start the PowerChute service or daemon. Open the User Interface and complete the Setup.If you change an existing command file path for an event in the pcnsconfig.ini file (e.g. 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.Change the path to the correct value. in the INI file or by using the PowerChute web user interface.After an Initial configuration, if you
subsequently change the IP address of any NMC using the Setup 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.For a) no workaround. For b) you need to re-start the service or daemon.When the PowerChute service or daemon starts, It validates the Pcnsconfigini value named IocalHostAddress. (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 in’ file.Run the Setup Wizard again to set the correct PowerChute IP addressIn a Parallel Redundant UPS configuration. 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.No workaround.Following silent Installation using IPv6, the Network Management Card shows two entries for the PowerChute client unicast address. This occurs If a short format IPv6 address Is entered In silentInstallini for UNICAST_ADDRESS e.g.
UNICAST_ADDRESS=fe80::80e9:7d49:2793:3616
This can result in the NMC sending unnecessary packets.1.Use the full format address when entering IPv6 address e.g.: UNICAST_ADDRESS=fe80:0:0:0:80e9:7d49:2793:3616 before running the silent install.
2.If installation is already completed, the short format IPv6 address can be removed from the Network Management Card via Configuration > PowerChute clients.When PowerChute is installed on an IPv6 only
machine the CN (Container Name) value in the
self-signed SSL Certificate is set to 127.0.0.1.Replace the Self-Signed SSL cert using the steps outlined in Kbase FA176886.
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:
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 NMC Firmware v6.0.X or higherUpgrade the NMC firmware to v6.0.X or higher for IPv6 support.
![Toni Kroos là ai? [ sự thật về tiểu sử đầy đủ Toni Kroos ]](https://evbn.org/wp-content/uploads/New-Project-6635-1671934592.jpg)
