The Galaxy VS application firmware version 6.130.0 release notes apply to the following NMC cards and products: AP9644 Network Management Card 4 (NMC4) See Knowledge Base article FAQ000265832 for the list of applicable SKUs. New Features   For a list of features available in the NMC 4, refer to the Network Management Card 4 Feature List.   New Feature Added support for the following OID: upsDiagnosticRelativeHumidityPct (1.3.6.1.4.1.318.1.1.1.13.13.1) The relative humidity in percentage. If not available, this variable is set to (-1). Additional logging has been added for the battery self-test feature. NOTE: Notifications by email and trap for audit log events is disabled by default.   Fixed Issues   Fixed Issue The NMC discovery issue on EcoStruxure™ IT Data Center Expert in the previous release 6.123.x is now resolved. An error message is now displayed when an invalid EAPoL certificate is uploaded through the Web Interface. A warning sign is no longer displayed when the user uploads a valid EAPOL certificate.   Known Issues   Known Issue When users enter invalid values for IP address, priority, and port number on the firewall configuration page, the error message appears briefly and then disappears, making it difficult for users to identify the cause of the validation failure Recommendation: Please check input values carefully before submission. Commands are displaying twice on the CLI. Following a reset of all configuration changes, except for the TCP/IP settings, NMC Modbus TCP remains in the enabled state and allows new connections. To resolve this issue, disable Modbus from the Web UI and apply the settings. The Modbus TCP feature will then be disabled and will not allow new connections. Email notifications routed through Gmail are not being received by end users. Where feasible, consider using an alternative email service for critical communications. Changes made to the date and time on the Network Management Card through the Web Interface are not always applied the first time. If this happens, try to hit the apply button again, refresh the page, or navigate away to another page for the change to be applied.   Email notifications are not working when the SMTP server is configured to use an IPv6 address.  Syslog notifications are not working when the Syslog server is configured to use an IPv6 address.   SNMP Traps are not working with Global, Static and Link-Local IPv6 addresses. When a reset is performed or self-signed TLS certificates are generated from the Web UI or the CLI on the Network Management Card on the 29th of February, HTTPS may become unavailable as an invalid TLS certificate will be created. We recommend you wait until the 1st of March on a leap year to run the gencert      command on the Network Management Card CLI. If browsing over the Web UI is essential, the Network Management Card can be accessed over HTTP, however for cybersecurity reasons, we at Schneider Electric do not recommend this unless absolutely necessary. Traps with more than 200 characters are being truncated. Configuration changes for Vendor Cookie sections are not reported in emails. Due to security enhancements, downgrading to a previous firmware version may result in some features not working as expected. If a downgrade to a previous firmware version is required, the email authentication password will need to be reset manually. Some DER format certificates cannot be uploaded to the NMC using SCP. It is recommended that PEM format certificates are used As user SSL certificates are removed, and self-signed certificates are regenerated during a reset of all NMC settings, when you are logged out after initializing a reset of all NMC settings, you must refresh the page before the browser can connect to the NMC over HTTPS using the new SSL certificates. After a reset of all NMC settings, you may be presented with the error “Maximum number of sessions exceeded” when attempting to login to the NMC Web UI. The NMC should be accessible once again after 3 minutes. Configurable events related to the temperature and humidity probe connected to the Network Management Card are not displayed in PowerChute Network Shutdown if the probe is connected after registration is complete. To prevent this issue from occurring, connect the temperature and humidity probe to the Network Management Card before completing the registration in PowerChute Network Shutdown. Alternatively, connect the probe after registration is complete and restart the PCNS service. When you attempt to login to the NMC Web UI following a soft reset, you will be immediately logged out following a successful login. This can be resolved by closing and restarting the web browser. When using a custom email server for a configured email recipient, if a recipient authentication password is set for the email recipient, the settings for the recipient can no longer be changed using the email CLI command, unless the password (-p) and confirm password (-d) arguments are included. Note that the settings can be changed without any problems from the Web UI. On very rare occasions following a soft reset, when SNMP is configured, the NMC does not communicate over SNMP. On these occasions, a reboot of the NMC is required to resolve the issue. With some browsers, due to auto-refresh functionalities, an inactive user may not be automatically logged out if the configured session timeout is greater than 15 minutes. It is recommended that the session timeout for a user is no greater than 15 minutes. The default is set to 3 minutes. SSH and HTTPS connections will be unsuccessful if the private key is not generated in PEM. It is not possible to register a PowerChute client that is using IPv6 with the NMC. Disabling Syslog on a per-event basis does not work as expected. You can only disable Syslog using the event action per-group option in the Web UI. No event is logged when an SSL certificate is removed via the SSL Certificate Configuration page in the Web UI. The “New self-signed certificate loaded” event will be logged if a new certificate is manually added or auto generated if the old certificate is deleted or out of date. You may be logged out unexpectedly from the Web UI if multiple Web UI tabs are open. This issue only occurs on Google Chrome. When a user’s password is changed via the user command in the CLI and does not meet the password requirements, a parameter error is displayed instead of “Password did not meet the requirements for a strong password.” There are discrepancies between the current time displayed in the Web UI and the CLI. The date command in the CLI will report the current time in real-time, whereas the Web UI will display the browser’s current time with respect to the UTC value set. NOTE: The UPS HMI will also display the current time in real-time. The Configure Events screen in PowerChute Network Shutdown v4.3 displays the “Communication Established with EMC” and “Communication Lost with EMC” events. These events can be ignored as they are not supported. When the optional NMC (AP9644) is inserted, some alarms and events are not logged on all the configured interfaces (traps, emails, Syslog, Event Log). For example, the “Lost Communication” alarm is not logged as an active alarm or sent as a trap/email. When the Web UI is locally accessed via an internal IP address (169.254.251.1 / 169.254.252.1) and HTTP/HTTPS is disabled, you can no longer access the UI using the disabled protocol. For example, if HTTP is disabled, you cannot access the Web UI at http://169.254.252.1 When adding a rule via the Firewall Configuration page in the Web UI, the table incorrectly includes the Range/Subnet column, which is not currently supported. The Notification Delay and Repeat Interval features for event actions do not behave as expected. For example, you may receive multiple notifications for an active event. You cannot connect to SNMPv1 using an IPv6 address. Use SNMPv3 as an alternative. File Transfer Protocol (FTP) is not available over IPv6. The NMC Web UI does not load beyond the Schneider Electric logo screen when accessed via EcoStruxure™ IT Data Center Expert. To resolve this, open the NMC Web UI directly in a browser using its IP address or DNS name (if configured). When Auto Configuration is disabled in the IPv6 Settings page in the Web UI, the NMC still displays the card’s IPv6 address, and the card is accessible using a DHCP IPv6 address. No browser warning message is displayed in the Web UI when navigating without saving your changes. When viewing the Event Details page in the Web UI for an event, you cannot disable the logging of an event to the Event Log. When accessing the Web UI using a smartphone, the Rule Configuration table on the Firewall Configuration page is not responsive. When an SNMPv3 profile is enabled with a valid NMS IP/Host Name, you can connect to a MIB browser of another system and not the configured SNMP profile. NOTE: The only supported value for NMS IP/Host Name for SNMPv3 is “0.0.0.0”.

The Galaxy VS application firmware version 6.123.0 release notes apply to the following NMC cards and products: AP9644 Network Management Card 4 (NMC4) See Knowledge Base article FAQ000265832 for the list of applicable SKUs.   New Features   For a list of features available in the NMC 4, refer to the Network Management Card 4 Feature List.   New Feature No new feature in this release.   Fixed Issues   Fixed Issue An issue has been fixed that addressed a potential NMC reboot when using SNMP for an extended period. The loading icon no longer continuously displays on the EAPoL Configuration page when an existing CA certificate is removed. Self-signed certificate generation on the Web UI will no longer fail if the page is refreshed, or you navigate to a different page while the regeneration process is in progress. Previously users may have experienced an issue following an NMC soft reset via the Web UI where a certificate failed to be generated, preventing access to the Web UI. This issue has now been addressed. Security Update The following third-party component (open source or proprietary) has been updated to address a cybersecurity vulnerability: Unauthenticated Remote Code Execution in Erlang/OTP SSH - CVE-2025-32433 Erlang OTP library has been updated to a patched version to mitigate this issue.   Known Issues   Known Issue Commands are displaying twice on the CLI. Following a reset of all configuration changes, except for the TCP/IP settings, NMC Modbus TCP remains in the enabled state and allows new connections. To resolve this issue, disable Modbus from the Web UI and apply the settings. The Modbus TCP feature will then be disabled and will not allow new connections. Email notifications routed through Gmail are not being received by end users. Where feasible, consider using an alternative email service for critical communications. Changes made to the date and time on the Network Management Card through the Web Interface are not always applied the first time. If this happens, try to hit the apply button again, refresh the page, or navigate away to another page for the change to be applied.   An error message is not displayed when an invalid certificate is uploaded through the Web Interface. A warning icon appears but there is no error message or event logged. Warning sign is displayed when the user uploads a valid EAPOL certificate. The certificate is however uploaded successfully. Email notifications are not working when the SMTP server is configured to use an IPv6 address.  Syslog notifications are not working when the Syslog server is configured to use an IPv6 address.   SNMP Traps are not working with Global, Static and Link-Local IPv6 addresses. When a reset is performed or self-signed TLS certificates are generated from the Web UI or the CLI on the Network Management Card on the 29th of February, HTTPS may become unavailable as an invalid TLS certificate will be created. We recommend you wait until the 1st of March on a leap year to run the gencert      command on the Network Management Card CLI. If browsing over the Web UI is essential, the Network Management Card can be accessed over HTTP, however for cybersecurity reasons, we at Schneider Electric do not recommend this unless absolutely necessary. Traps with more than 200 characters are being truncated. Configuration changes for Vendor Cookie sections are not reported in emails. Due to security enhancements, downgrading to a previous firmware version may result in some features not working as expected. If a downgrade to a previous firmware version is required, the email authentication password will need to be reset manually. Some DER format certificates cannot be uploaded to the NMC using SCP. It is recommended that PEM format certificates are used As user SSL certificates are removed, and self-signed certificates are regenerated during a reset of all NMC settings, when you are logged out after initializing a reset of all NMC settings, you must refresh the page before the browser can connect to the NMC over HTTPS using the new SSL certificates. After a reset of all NMC settings, you may be presented with the error “Maximum number of sessions exceeded” when attempting to login to the NMC Web UI. The NMC should be accessible once again after 3 minutes. Configurable events related to the temperature and humidity probe connected to the Network Management Card are not displayed in PowerChute Network Shutdown if the probe is connected after registration is complete. To prevent this issue from occurring, connect the temperature and humidity probe to the Network Management Card before completing the registration in PowerChute Network Shutdown. Alternatively, connect the probe after registration is complete and restart the PCNS service. When you attempt to login to the NMC Web UI following a soft reset, you will be immediately logged out following a successful login. This can be resolved by closing and restarting the web browser. When using a custom email server for a configured email recipient, if a recipient authentication password is set for the email recipient, the settings for the recipient can no longer be changed using the email CLI command, unless the password (-p) and confirm password (-d) arguments are included. Note that the settings can be changed without any problems from the Web UI. On very rare occasions following a soft reset, when SNMP is configured, the NMC does not communicate over SNMP. On these occasions, a reboot of the NMC is required to resolve the issue. With some browsers, due to auto-refresh functionalities, an inactive user may not be automatically logged out if the configured session timeout is greater than 15 minutes. It is recommended that the session timeout for a user is no greater than 15 minutes. The default is set to 3 minutes. SSH and HTTPS connections will be unsuccessful if the private key is not generated in PEM. It is not possible to register a PowerChute client that is using IPv6 with the NMC. Disabling Syslog on a per-event basis does not work as expected. You can only disable Syslog using the event action per-group option in the Web UI. No event is logged when an SSL certificate is removed via the SSL Certificate Configuration page in the Web UI. The “New self-signed certificate loaded” event will be logged if a new certificate is manually added or auto generated if the old certificate is deleted or out of date. You may be logged out unexpectedly from the Web UI if multiple Web UI tabs are open. This issue only occurs on Google Chrome. When a user’s password is changed via the user command in the CLI and does not meet the password requirements, a parameter error is displayed instead of “Password did not meet the requirements for a strong password.” There are discrepancies between the current time displayed in the Web UI and the CLI. The date command in the CLI will report the current time in real-time, whereas the Web UI will display the browser’s current time with respect to the UTC value set. NOTE: The UPS HMI will also display the current time in real-time. The Configure Events screen in PowerChute Network Shutdown v4.3 displays the “Communication Established with EMC” and “Communication Lost with EMC” events. These events can be ignored as they are not supported. When the optional NMC (AP9644) is inserted, some alarms and events are not logged on all the configured interfaces (traps, emails, Syslog, Event Log). For example, the “Lost Communication” alarm is not logged as an active alarm or sent as a trap/email. When the Web UI is locally accessed via an internal IP address (169.254.251.1 / 169.254.252.1) and HTTP/HTTPS is disabled, you can no longer access the UI using the disabled protocol. For example, if HTTP is disabled, you cannot access the Web UI at http://169.254.252.1 When adding a rule via the Firewall Configuration page in the Web UI, the table incorrectly includes the Range/Subnet column, which is not currently supported. The Notification Delay and Repeat Interval features for event actions do not behave as expected. For example, you may receive multiple notifications for an active event. You cannot connect to SNMPv1 using an IPv6 address. Use SNMPv3 as an alternative. File Transfer Protocol (FTP) is not available over IPv6. When credentials are provided in EcoStruxure IT Data Center Expert after adding the NMC via SNMP, the NMC still requires login credentials when attempting to access the Web UI. When Auto Configuration is disabled in the IPv6 Settings page in the Web UI, the NMC still displays the card’s IPv6 address, and the card is accessible using a DHCP IPv6 address. No browser warning message is displayed in the Web UI when navigating without saving your changes. When viewing the Event Details page in the Web UI for an event, you cannot disable the logging of an event to the Event Log. When accessing the Web UI using a smartphone, the Rule Configuration table on the Firewall Configuration page is not responsive. When an SNMPv3 profile is enabled with a valid NMS IP/Host Name, you can connect to a MIB browser of another system and not the configured SNMP profile. NOTE: The only supported value for NMS IP/Host Name for SNMPv3 is “0.0.0.0”.

The Galaxy VS application firmware version 6.118.0 release notes apply to the following NMC cards and products: AP9644 Network Management Card 4 (NMC4) See Knowledge Base article FAQ000265832 for the list of applicable SKUs.   New Features For a list of features available in the NMC 4, refer to the Network Management Card 4 Feature List.   New Features Remote battery self-test via Web UI and SNMP.  Validity period for the self-signed certificate is now 10 years from date of creation. Previously the validity period was set to 1 year. Added support for the following OIDs: upsDiagPMAverageFanSpeed (1.3.6.1.4.1.819.1.1.1.13.2.2.1.10) The average fan speed of the working fans in the Power Module in revolutions per minute (RPM). Returns (-1) if not supported. upsDiagPMAmbientTemperature (1.3.6.1.4.1.318.1.1.1.13.2.2.1.11) The ambient temperature inside the Power Module in tenths of degrees celsius. If not available this variable is set to (-1999).   upsDiagSubSysIntBypFanSpeed (1.3.6.1.14.1.318.1.1.1.13.4.4.1.9) The average fan speed of the working fans in the Internal Bypass Switch in revolutions per minute (RPM). Returns (-1) if not supported. upsDiagSubSysIntBypAmbientTemperature (1.3.6.1.4.1.13.4.4.1.10)  The ambient temperature in tenths of degrees Celsius inside the Internal Bypass Switch. If not available, this variable is set to (-1999).   Fixed Issues Fixed Issues NMC communication stability enhancements.  Issue with email servers using authentication password in previous release (6.101) is now addressed. Email notifications will now work as expected. When an alarm is reported in  UPSAdvStateAbnormalCondition  SNMP OID changes state, only the first state change is being updated.  UPSAdvStateAbnormalCondition  SNMP OID is now fixed to always reflect the relevant alarm states.   SSH can sometimes stop working following an upgrade to a newer version of the Network Management Card 4 firmware. A fix has been introduced in the 6.102 release to re-generate the SSH self-generated keys if the issue persists, it will re-enable the SSH functionality.    Known Issues Known Issues Changes made to the date and time on the Network Management Card through the Web Interface are not always applied the first time. If this happens, try to hit the apply button again, refresh the page, or navigate away to another page for the change to be applied.   An error message is not displayed when an invalid certificate is uploaded through the Web Interface. A warning icon appears but there is no error message or event logged. Warning sign is displayed when the user uploads a valid EAPOL certificate. The certificate is however uploaded successfully. Email notifications are not working when the SMTP server is configured to use an IPv6 address.  Syslog notifications are not working when the Syslog server is configured to use an IPv6 address.   When an existing CA certificate is removed on the EAPoL Certificate Configuration page, the loading icon displays continuously. Refreshing the page clears the loading icon.   SNMP Traps are not working with Global, Static and Link-Local IPv6 addresses. When a reset is performed or self-signed TLS certificates are generated from the Web UI or the CLI on the Network Management Card on the 29th of February, HTTPS may become unavailable as an invalid TLS certificate will be created. We recommend you wait until the 1st of March on a leap year to run the gencert      command on the Network Management Card CLI. If browsing over the Web UI is essential, the Network Management Card can be accessed over HTTP, however for cybersecurity reasons, we at Schneider Electric do not recommend this unless absolutely necessary. Traps with more than 200 characters are being truncated. Configuration changes for Vendor Cookie sections are not reported in emails. Due to security enhancements, downgrading to a previous firmware version may result in some features not working as expected. If a downgrade to a previous firmware version is required, the email authentication password will need to be reset manually. Some DER format certificates cannot be uploaded to the NMC using SCP. It is recommended that PEM format certificates are used As user SSL certificates are removed, and self-signed certificates are regenerated during a reset of all NMC settings, when you are logged out after initializing a reset of all NMC settings, you must refresh the page before the browser can connect to the NMC over HTTPS using the new SSL certificates. After a reset of all NMC settings, you may be presented with the error “Maximum number of sessions exceeded” when attempting to login to the NMC Web UI. The NMC should be accessible once again after 3 minutes. Configurable events related to the temperature and humidity probe connected to the Network Management Card are not displayed in PowerChute Network Shutdown if the probe is connected after registration is complete. To prevent this issue from occurring, connect the temperature and humidity probe to the Network Management Card before completing the registration in PowerChute Network Shutdown. Alternatively, connect the probe after registration is complete and restart the PCNS service. When you attempt to login to the NMC Web UI following a soft reset, you will be immediately logged out following a successful login. This can be resolved by closing and restarting the web browser. When using a custom email server for a configured email recipient, if a recipient authentication password is set for the email recipient, the settings for the recipient can no longer be changed using the email CLI command, unless the password (-p) and confirm password (-d) arguments are included. Note that the settings can be changed without any problems from the Web UI. On very rare occasions following a soft reset, when SNMP is configured, the NMC does not communicate over SNMP. On these occasions, a reboot of the NMC is required to resolve the issue. With some browsers, due to auto-refresh functionalities, an inactive user may not be automatically logged out if the configured session timeout is greater than 15 minutes. It is recommended that the session timeout for a user is no greater than 15 minutes. The default is set to 3 minutes. SSH and HTTPS connections will be unsuccessful if the private key is not generated in PEM. It is not possible to register a PowerChute client that is using IPv6 with the NMC. Disabling Syslog on a per-event basis does not work as expected. You can only disable Syslog using the event action per-group option in the Web UI. No event is logged when an SSL certificate is removed via the SSL Certificate Configuration page in the Web UI. The “New self-signed certificate loaded” event will be logged if a new certificate is manually added or auto generated if the old certificate is deleted or out of date. You may be logged out unexpectedly from the Web UI if multiple Web UI tabs are open. This issue only occurs on Google Chrome. When a user’s password is changed via the user command in the CLI and does not meet the password requirements, a parameter error is displayed instead of “Password did not meet the requirements for a strong password.” There are discrepancies between the current time displayed in the Web UI and the CLI. The date command in the CLI will report the current time in real-time, whereas the Web UI will display the browser’s current time with respect to the UTC value set. NOTE: The UPS HMI will also display the current time in real-time. The Configure Events screen in PowerChute Network Shutdown v4.3 displays the “Communication Established with EMC” and “Communication Lost with EMC” events. These events can be ignored as they are not supported. When the optional NMC (AP9644) is inserted, some alarms and events are not logged on all the configured interfaces (traps, emails, Syslog, Event Log). For example, the “Lost Communication” alarm is not logged as an active alarm or sent as a trap/email. When the Web UI is locally accessed via an internal IP address (169.254.251.1 / 169.254.252.1) and HTTP/HTTPS is disabled, you can no longer access the UI using the disabled protocol. For example, if HTTP is disabled, you cannot access the Web UI at http://169.254.252.1 When adding a rule via the Firewall Configuration page in the Web UI, the table incorrectly includes the Range/Subnet column, which is not currently supported. The Notification Delay and Repeat Interval features for event actions do not behave as expected. For example, you may receive multiple notifications for an active event. You cannot connect to SNMPv1 using an IPv6 address. Use SNMPv3 as an alternative. File Transfer Protocol (FTP) is not available over IPv6. When credentials are provided in EcoStruxure IT Data Center Expert after adding the NMC via SNMP, the NMC still requires login credentials when attempting to access the Web UI. When Auto Configuration is disabled in the IPv6 Settings page in the Web UI, the NMC still displays the card’s IPv6 address, and the card is accessible using a DHCP IPv6 address. No browser warning message is displayed in the Web UI when navigating without saving your changes. When viewing the Event Details page in the Web UI for an event, you cannot disable the logging of an event to the Event Log. When accessing the Web UI using a smartphone, the Rule Configuration table on the Firewall Configuration page is not responsive. When an SNMPv3 profile is enabled with a valid NMS IP/Host Name, you can connect to a MIB browser of another system and not the configured SNMP profile. NOTE: The only supported value for NMS IP/Host Name for SNMPv3 is “0.0.0.0”.

The Galaxy VS application firmware version 6.101.0 release notes apply to the following NMC cards and products: AP9644 Network Management Card 4 (NMC4) See Knowledge Base article FAQ000265832 for the list of applicable SKUs.   New Features For a list of features available in the NMC 4, refer to the Network Management Card 4 Feature List.   New Feature Additional logging has been added for the following features: TCP/IP, EventActions, SSH, Web, FTP, System, SNMP, Modbus and PCNS. NOTE: Notifications by email and trap for audit log events is disabled by default. All user types can now change their own password via the Web UI and CLI. NOTE: Admin users can no longer change their own password without first entering their current password on the Web UI and CLI. It will however be possible for an Admin user to change another users password without entering the current password. UPS ambient temperature is now readable from an NMC over Modbus. Support added for Dell VxRail for PowerChute Network Shutdown v4.5 or higher. It is now possible to configure the SNMP port for SNMP v1 and SNMP v3 trap receivers. This can be set through the Web UI, CLI or the config.ini.   Fixed Issues   Fixed Issue It is now possible to generate a Technical Support debug file if you are logged into the NMC via RADIUS. You no longer need to log in as a local user to generate this file. The Battery Type is now correctly reported as “Lithium Ion” on the UPS Battery Measurements page in the Web UI when a Lithium-ion battery is used. The Update using NTP option works as expected on both the initial and subsequent requests now. Security Updates The following security vulnerabilities have been addressed in this release: CVE-2023-6032: Improper Limitation of a Pathname to a Restricted Directory (Path Traversal) vulnerability. CWE-269: Improper Privilege Management vulnerability exists that could cause a low privileged user to escalate their privilege when that user logs in to the web application. CWE-1236: Improper Neutralization of Formula Elements in a CSV File vulnerability exists that could lead to saved user provided information, that is not neutralized correctly, being interpreted as a command when the file is opened by a spreadsheet product. CWE-400: Uncontrolled Resource Consumption vulnerability exists that could cause a reboot of the Network Management Card (NMC4) when an attacker sends partial HTTP connections to the web server. The following third-party component has been updated to address cybersecurity vulnerability: OpenSSL: CVE-2022-4304.   Known Issues   Known Issue When a reset is performed or self-signed TLS certificates are generated from the Web UI or the CLI on the Network Management Card on the 29th of February, HTTPS may become unavailable as an invalid TLS certificate will be created. We recommend you wait until the 1st of March on a leap year to run the gencert command on the Network Management Card CLI. If browsing over the Web UI is essential, the Network Management Card can be accessed over HTTP, however for cybersecurity reasons, we at Schneider Electric do not recommend this unless absolutely necessary. Traps with more than 200 characters are being truncated. Configuration changes for Vendor Cookie sections are not reported in emails. Due to security enhancements, downgrading to a previous firmware version may result in some features not working as expected. If a downgrade to a previous firmware version is required, the email authentication password will need to be reset manually. Some DER format certificates cannot be uploaded to the NMC using SCP. It is recommended that PEM format certificates are used. As user SSL certificates are removed, and self-signed certificates are regenerated during a reset of all NMC settings, when you are logged out after initializing a reset of all NMC settings, you must refresh the page before the browser can connect to the NMC over HTTPS using the new SSL certificates. After a reset of all NMC settings, you may be presented with the error “Maximum number of sessions exceeded” when attempting to login to the NMC Web UI. The NMC should be accessible once again after 3 minutes. Events related to the temperature and humidity probe connected to the Network Management Card are not displayed in PowerChute Network Shutdown if the probe is connected after registration is complete. To prevent this issue from occurring, connect the temperature and humidity probe to the Network Management Card before completing the registration in PowerChute Network Shutdown. Alternatively, connect the probe after registration is complete and restart the PCNS service. When you attempt to login to the NMC Web UI following a soft reset, you will be immediately logged out following a successful login. This can be resolved by closing and restarting the web browser. When using a custom email server for a configured email recipient, if a recipient authentication password is set for the email recipient, the settings for the recipient can no longer be changed using the email CLI command, unless the password (-p) and confirm password (-d) arguments are included. Note that the settings can be changed without any problems from the Web UI. On very rare occasions following a soft reset, when SNMP is configured, the NMC does not communicate over SNMP. On these occasions, a reboot of the NMC is required to resolve the issue. With some browsers, due to auto-refresh functionalities, an inactive user may not be automatically logged out if the configured session timeout is greater than 15 minutes. It is recommended that the session timeout for a user is no greater than 15 minutes. The default is set to 3 minutes. SSH and HTTPS connections will be unsuccessful if the private key is not generated in PEM. It is not possible to register a PowerChute client that is using IPv6 with the NMC. Disabling Syslog on a per-event basis does not work as expected. You can only disable Syslog using the event action per-group option in the Web UI. No event is logged when an SSL certificate is removed via the SSL Certificate Configuration page in the Web UI. The “New self-signed certificate loaded” event will be logged if a new certificate is manually added or auto generated if the old certificate is deleted or out of date. You may be logged out unexpectedly from the Web UI if multiple Web UI tabs are open. This issue only occurs on Google Chrome. When a user’s password is changed via the user command in the CLI and does not meet the password requirements, a parameter error is displayed instead of “Password did not meet the requirements for a strong password.” There are discrepancies between the current time displayed in the Web UI and the CLI. The date command in theCLI will report the current time in real-time, whereas the Web UI will display the browser’s current time with respect to the UTC value set. NOTE: The UPS HMI will also display the current time in real-time. The Configure Events screen in PowerChute Network Shutdown v4.3 displays the “Communication Established with EMC” and “Communication Lost with EMC” events. These events can be ignored as they are not supported. When the optional NMC (AP9644) is inserted, some alarms and events are not logged on all the configured interfaces (traps, emails, Syslog, Event Log). For example, the “Lost Communication” alarm is not logged as an active alarm or sent as a trap/email. When the Web UI is locally accessed via an internal IP address (169.254.251.1 / 169.254.252.1) and HTTP/HTTPS is disabled, you can no longer access the UI using the disabled protocol. For example, if HTTP is disabled, you cannot access the Web UI at http://169.254.252.1 When adding a rule via the Firewall Configuration page in the Web UI, the table incorrectly includes the Range/Subnet column, which is not currently supported. The Notification Delay and Repeat Interval features for event actions do not behave as expected. For example, you may receive multiple notifications for an active event. You cannot connect to SNMPv1 using an IPv6 address. Use SNMPv3 as an alternative. When you log out from the NMC serial console interface, the Current Sessions page in the Web UI still shows the session as active. File Transfer Protocol (FTP) is not available over IPv6. When credentials are provided in StruxureWare Data Center Expert after adding the NMC via SNMP, the NMC still requires login credentials when attempting to access the Web UI. When Auto Configuration is disabled in the IPv6 Settings page in the Web UI, the NMC still displays the card’s IPv6 address, and the card is accessible using a DHCP IPv6 address. No browser warning message is displayed in the Web UI when navigating without saving your changes. When viewing the Event Details page in the Web UI for an event, you cannot disable the logging of an event to the Event Log. When accessing the Web UI using a smartphone, the Rule Configuration table on the Firewall Configuration page is not responsive. When an SNMPv3 profile is enabled with a valid NMS IP/Host Name, you can connect to a MIB browser of another system and not the configured SNMP profile.   NOTE: The only supported value for NMS IP/Host Name for SNMPv3 is “0.0.0.0”.

New Features For a list of features available in the NMC 4, refer to the NMC4 Feature List.   New Feature Support added for RADIUS. NOTE: RADIUS configuration supports Password Authentication Protocol (PAP) and Challenge Handshake Authentication Protocol (CHAP). You can now upload and download a user configuration file. NOTE: The upload and application of the configuration file, under certain circumstances, can take over 15 minutes to complete. During this time, the Upload/Download Capabilities on the User Config page in the Web UI will be disabled until the settings are uploaded and applied, or the timer expires. Support added for 802.1x (EAPoL) Protocol. Supported EAP methods: EAP-TLS Supported TLS versions: v1.0, v1.1, and v1.2. It is recommended to configure the minimum and maximum as v1.2 on the RADUIS server side. Support added for Secure Syslog. Secure Syslog behaves the same way as Standard Syslog, except the messages are encrypted using Transport Layer Security (TLS) before being transmitted. The NMC supports both one-way and two-way authentication between the client (the NMC) and your external Syslog server. Secure Syslog can only be used with TCP. Reset NMC settings from Web UI and CLI. You now have an option to perform a reset of the NMC settings via the Web UI and the CLI. You can perform a full reset to defaults of all the NMC settings, or a partial reset where the TCP/IP network settings will not be reset but all other NMC setting will be reset. You can now generate and download a debug dump for Technical Support. You can now upload and download files to and from the NMC using SCP. You can now upload files with a size limit of 500 KB.The default for Bad Login Attempts is now set to 5. This had previously been set to 0.   Fixed Issues   Fixed Issue Email notifications will no longer be sent to the old recipient when notifications are modified for an active alarm. When the mode is set to “DHCP Only” in the IPv4 Settings page in the Web UI, the DHCP IP settings are now correctly populated in the “Manual” mode section. When the boot mode is changed from DHCP to manual in the CLI (using the boot command), the previously used static IP address is no longer incorrectly assigned.   Known Issues   Known Issue The Battery Type may incorrectly be reported as “Value-regulated lead-acid, or maintenance-free” on the UPS Battery Measurements page in the Web UI when a Lithium-ion battery is used. The correct battery configuration can be confirmed in the Battery view on the UPS HMI display. In the unlikely event that the violation alarms do not trigger on the NMC, reconfiguring the threshold values or removing and plugging the sensor back into the NMC, will resolve this issue. It is not possible to generate a Technical Support debug file if you are logged into the NMC via RADIUS. You must log in as a local user to generate this file. Security Notification: There were cyber security fixes in this release resolving vulnerabilities with vertical privilege escalation, File Enumeration, and HTTP Denial of Service. Schneider Electric is aware of a directory transversal vulnerability in the Galaxy VS Firmware 6.82.0 which may allow system files to be downloaded in compromised networks. The product team is actively working on a remediation in accordance with our Product Vulnerability Management Policy.   Until then, we strongly recommend to consult the Firewall section of the NMC4 Security Handbook. In addition, please refer to Schneider Electric’s Recommended Cybersecurity Best Practices document. Due to security enhancements, downgrading to a previous firmware version may result in some features not working as expected. If a downgrade to a previous firmware version is required, the email authentication password will need to be reset manually. After a reset of all NMC settings, you may be presented with the error “Maximum number of sessions exceeded” when attempting to login to the NMC Web UI. The NMC should be accessible once again after 3 minutes. Events related to the temperature and humidity probe connected to the Network Management Card are not displayed in PowerChute Network Shutdown if the probe is connected after registration is complete. To prevent this issue from occurring, connect the temperature and humidity probe to the Network Management Card before completing the registration in PowerChute Network Shutdown. Alternatively, connect the probe after registration is complete and restart the PCNS service. When you attempt to login to the NMC Web UI following a soft reset, you will be immediately logged out following a successful login. This can be resolved by closing and restarting the web browser. When using a custom email server for a configured email recipient, if a recipient authentication password is set for the email recipient, the settings for the recipient can no longer be changed using the email CLI command, unless the password (-p) and confirm password (-d) arguments are included. Note that the settings can be changed without any problems from the Web UI. On very rare occasions following a soft reset, when SNMP is configured, the NMC does not communicate over SNMP. On these occasions, a reboot of the NMC is required to resolve the issue. With some browsers, due to auto-refresh functionalities, an inactive user may not be automatically logged out if the configured session timeout is greater than 15 minutes. It is recommended that the session timeout for a user is no greater than 15 minutes. The default is set to 3 minutes. SSH and HTTPS connections will be unsuccessful if the private key is not generated in PEM. It is not possible to register a PowerChute client that is using IPv6 with the NMC. Disabling Syslog on a per-event basis does not work as expected. You can only disable Syslog using the event action per-group option in the Web UI. No event is logged when an SSL certificate is removed via the SSL Certificate Configuration page in the Web UI. The “New self-signed certificate loaded” event will be logged if a new certificate is manually added or auto generated if the old certificate is deleted or out of date. You may be logged out unexpectedly from the Web UI if multiple Web UI tabs are open. This issue only occurs on Google Chrome. When a user’s password is changed via the user command in the CLI and does not meet the password requirements, a parameter error is displayed instead of “Password did not meet the requirements for a strong password.” There are discrepancies between the current time displayed in the Web UI and the CLI. The date command in the CLI will report the current time in real-time, whereas the Web UI will display the browser’s current time with respect to the UTC value set. NOTE: The UPS HMI will also display the current time in real-time. The Configure Events screen in PowerChute Network Shutdown v4.3 displays the “Communication Established with EMC” and “Communication Lost with EMC” events. These events can be ignored as they are not supported. When the optional NMC (AP9644) is inserted, some alarms and events are not logged on all the configured interfaces (traps, emails, Syslog, Event Log). For example, the “Lost Communication” alarm is not logged as an active alarm or sent as a trap/email. When the Web UI is locally accessed via an internal IP address (169.254.251.1 / 169.254.252.1) and HTTP/HTTPS is disabled, you can no longer access the UI using the disabled protocol. For example, if HTTP is disabled, you cannot access the Web UI at http://169.254.252.1 When adding a rule via the Firewall Configuration page in the Web UI, the table incorrectly includes the Range/Subnet column, which is not currently supported. The Notification Delay and Repeat Interval features for event actions do not behave as expected. For example, you may receive multiple notifications for an active event. You cannot connect to SNMPv1 using an IPv6 address. Use SNMPv3 as an alternative. When you log out from the NMC serial console interface, the Current Sessions page in the Web UI still shows the session as active. File Transfer Protocol (FTP) is not available over IPv6. When credentials are provided in StruxureWare Data Center Expert after adding the NMC via SNMP, the NMC still requires login credentials when attempting to access the Web UI. When Auto Configuration is disabled in the IPv6 Settings page in the Web UI, the NMC still displays the card’s IPv6 address and the card is accessible using a DHCP IPv6 address. No browser warning message is displayed in the Web UI when navigating without saving your changes. When viewing the Event Details page in the Web UI for an event, you cannot disable the logging of an event to the Event Log. When accessing the Web UI using a smartphone, the Rule Configuration table on the Firewall Configuration page is not responsive. When an SNMPv3 profile is enabled with a valid NMS IP/Host Name, you can connect to a MIB browser of another system and not the configured SNMP profile. NOTE: The only supported value for NMS IP/Host Name for SNMPv3 is “0.0.0.0”.