Release Notes for Galaxy VL Firmware 14.4.0

[CDiggin]

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: Radius, Security, Syslog, DNS, Email, EAPoL, UIO, PCNS and Technical Support Debug. NOTE: Notifications by email and trap for audit log events is disabled by default.

Support added for Dell VxRail for PowerChute Network Shutdown v4.5 or higher.

t 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

Issue with email servers using authentication password in previous release (13.18.1) is now addressed. Email notifications will now work as expected.

A reboot is no longer required to update the upsBasicBatteryLastReplaceDate SNMP Object Identifier (OID).

The Modbus register 8227 now displays the correct value, which displayed an incorrect value in the previous release (13.18.1)

Security Updates

The following third-party component has been updated to address cybersecurity vulnerability: OpenSSL: CVE-2022-4304.

Known Issues

Known Issue

The SNMP Object Identifier (OID) upsAdvStateAbnormalConditions will not update after the first alarm has been triggered. To clear the alarm, you need to stop and restart the SNMP feature and then you will get the next alarm.

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.

Traps with more than 200 characters are being truncated.

Newly added logs are not translated in this release.

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.

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”.