Smart-UPS & 1-Phase Symmetra

Affected Revision Levels   Component  File Details   APC Operating System  apc_hw05_aos_718.bin Network Management Card Operating System & TCP/IP Stack for Hardware Platform  Smart-UPS Application  apc_hw05_sumx_718.bin UPS Application for Smart-UPS, Smart-UPS XL, Smart-UPS RT, Smart-UPS VT, Smart-UPS DP, Smart-UPS OL, MGE Galaxy 3500   Symmetra Application   apc_hw05_sy_718.bin UPS Application for Single-Phase Symmetra, Symmetra LX, Symmetra RM   For details on upgrading the UPS Network Management Card 2 (NMC 2) firmware, see the User Guide on the APC website. New Features   New Feature UPS Family Smart-UPS Single-Phase Symmetra Support added for modifying an existing user via the configuration file (ModifyUser keyword). ♦ ♦ Added the UPS SKU number in the PowerChute Network Shutdown communication exchange. ♦       Fixed Issues   Fixed Issue UPS Family Smart-UPS Single-Phase Symmetra Resolved the SNMPv3 communication issue which earlier impacted the EcoStruxure Data Center Expert monitoring and some third-party MIB browsers. ♦ ♦ The modbus -rDef and userdflt-d CLI commands work as expected. ♦ ♦ The value of the apcDiscoveryDeviceInfoTable SNMP OID now updates as expected if additional devices are added/removed. ♦ ♦ The resetNetworkLeaveModeAndRestart SNMP OID option resetNetworkLeaveModeAndRestart (6) works as expected. ♦ ♦ Emails are now sent, and events are now logged as expected when an unsuccessful login attempt occurs over SSH/Telnet. ♦ ♦ The Super User account can now be disabled via EcoStruxure™ IT Data Center Expert CLI commands. ♦ ♦ SNMPv3 traps are now received as expected on non-default ports when a Trap Receiver is edited. ♦ ♦ An override parameter in the [NetworkTCP/IP] section of the configuration file is no longer missing after a firmware upgrade. ♦ ♦ Trap receiver ports configured via the [NetworkSNMP] section of the configuration file now accepts values over 32768. ♦ ♦ The OutputRelay1Hold, OutputRelay2Hold, OutputRelay2Delay and OutputRelay2Delay settings in the configuration file now accepts the correct values. The range of values accepted by the config.ini for these OutputRelay1Delay setting does not match the range specified and accepted in the web. The web takes 0-65536. The config.ini takes 32767-32767. ♦ ♦ "Confirm password has been entered incorrectly" error message is no longer displayed when logging into the Web UI, when the password is entered correctly. ♦ ♦ EaPOL accepts .pem files as expected. ♦ ♦ NMC Web UI help pages have been updated. ♦ ♦ The SNMPv1 Access Control configuration values are retained after an SNMP walk. ♦ ♦ Application error messages are no longer displayed when navigating to some Web UI pages as a Network-Only user. ♦ ♦ The detbat -id CLI command works as expected. ♦   The upsAdvTestCalibrationDate SNMP OID is now properly supported for UPS devices that support Runtime Calibration. ♦   The NMC will no longer show the UPS firmware update configuration option on the Web UI and the CLI if the UPS is configured to prevent UPS firmware update from the NMC. ♦   Security Update The following security vulnerability has been addressed in this release: CWE-326: Inadequate encryption strength. secp192r1 has been removed. secp192r1 is an out-of-date cipher that does not meet modern cryptographic needs and contains weaknesses that may be exploited by the attackers. ♦ ♦ The following security vulnerability has been addressed in this release: CWE-79: Improper Neutralization of Input During Web Page Generation (Cross-site Scripting). Specified output encoding via HTTP header. ♦ ♦ The following security vulnerability has been addressed in this release: CWE-425: Direct Request (Forced Browsing). Appropriate access controls were added to the web resources that could previously be accessed without authorization. ♦ ♦ The following security vulnerability has been addressed in this release: CWE-319: Cleartext Transmission of Sensitive Information. The configuration of HSTS is now independent from HTTP or HTTPS configuration. ♦ ♦ The following security vulnerability has been addressed in this release: CWE-79 Improper Neutralization of Input During Web Page Generation (Cross-site Scripting). URLs were properly cleared, terminated, and sanitized. ♦ ♦     Known Issues Known Issue UPS Family Smart-UPS Single-Phase Symmetra When you configure the NMC2 to use IPV4 and IPV6, the SSH connections to the NMC will be unsuccessful. ♦ ♦ When upgrading the NMC’s firmware via the NMC Firmware Update Utility using SCP as the protocol, the update may be unsuccessful. If you click the Start Update button again, the following error messages may appear: Resume not supported for SCP transfers. Could not retrieve configuration file via this method, please recheck the settings. Workaround: Use FTP as the protocol. ♦ ♦ If SCP is chosen and the Backup log files prior to update checkbox is selected when upgrading the NMC’s firmware via the NMC Firmware Upgrade Utility, the upgrade will freeze at the “Download Event Log” stage. Workaround: Use FTP as the protocol, or back up your files before initiating the update and unselect the Backup log files prior to update checkbox. ♦ ♦ Modbus TCP cannot be enabled via the CLI on AP9630 and AP9631 NMCs. Workaround: Use the Web UI to enable Modbus TCP. ♦ ♦ The NMC management interface (e.g. the Web UI, CLI) may restart if large groups of event actions ordered by severity are modified. ♦ ♦ SNMPv3 communication and monitoring on some third-party SNMP management tools may not work correctly. ♦ ♦ If a firewall rule is created with a subnet value without the correct CIDR notation, no error is displayed, and the policy can be created with an incorrect subnet value. ♦ ♦ If a firewall rule is created with a subnet and port range defined, connections are not correctly limited to the ports defined in the rule. ♦ ♦ If a firewall rule is created with the option to Log set to ‘No’, the rule is incorrectly logged to the Firewall Policy Log. ♦ ♦ If a firewall rule is created with Protocol set to ICMP and Action set to Discard, ICMP messages such as ping are not stopped as expected. ♦ ♦ If a firewall rule is created with the source host set to the IP address of the NMC, the NMC will not be accessible when the firewall policy is enabled. ♦ ♦ "System: Detected an unauthorized user attempting to access the FTP interface" and "System: Password Changed" events do not send SNMP Traps. ♦ ♦ Device level user privileges in the Command Line Interface (CLI) are not consistent with the device user privileges in the Web interface. ♦ ♦ In the Config.ini, the SystemDateTime primary and secondary server keywords return strange values when long strings are applied. ♦ ♦ The DNS Domain Name validation doesn't conform to RFC1035 Standards for formatting. ♦ ♦ "System: Email: Could not mail, queue full." event log message is repeatedly recorded in the event log when a fourth email recipient is configured, even though the recipient is receiving the notification. ♦ ♦ Some column headers in the data.txt download file are not displayed correctly in Russian. ♦ ♦ File transfers using SCP do not work properly with WinSCP GUI client. ♦ ♦ NMC interface may restart when multiple alarms are logged simultaneously. ♦ ♦ Authenticated/secure email server settings could be potentially altered during an upgrade from an AOS prior to 6.1.8. ♦ ♦ Files do not successfully upload to the NMC via a TFTP server when used with DHCP options 66 and 67. ♦ ♦ When a firewall policy is created through the web UI with a name longer than 16 characters, it cannot be successfully edited, or updated with new rules. ♦ ♦ The NMC may enter a reboot loop when downloading the config.ini file over FTP, when DHCP with options 66 and 67 are enabled.   This reboot loop can be fixed by disabling DHCP or by closing the FTP server. ♦ ♦ When using the "Test Settings" option to test a RADIUS server configuration, the web UI will not accept a username or password longer than 16 characters. ♦ ♦ When configuring the SMTP server of an email recipient in the web UI, if the server is set to 'recipient', the 'From:' address field is incorrectly populated with the 'To:' address. When an email is then sent to the recipient, it incorrectly appears that the email has been sent from the recipient’s own email address. ♦ ♦ When connecting to the command line interface of the NMC via SSH, after a period the NMC management interface may reboot. ♦ ♦ If the maximum number of SMTP Traps and Email Recipients are configured, the maximum number of Web UI sessions, Command Line Interface sessions, Telnet sessions, and FTP sessions are created, and the maximum number of alarms is generated at once, the NMC user interface will become unresponsive, and the NMC will reboot. ♦ ♦ A UPS that has been deliberately put into sleep mode can behave inconsistently. For example, a UPS can turn off after only a few seconds of being in the "Graceful shutdown initiated" state or can turn on after only a few seconds of being in the "Turned off for a defined period" state. ♦ ♦ When a scheduled shutdown is configured with a long interval (e.g. 2 weeks), the UPS shuts down on schedule, but if a power outage occurs before the UPS restarts, the UPS will not shut down at the next scheduled date, and the next scheduled shutdown will be moved forward by one week. ♦ ♦ USB drives of a capacity greater than 32GB are often formatted using an NTFS or ExFAT file system. The NMC is compatible with FAT, FAT16 or FAT32 file systems only. For UPS firmware upgrades via USB, or NMC card firmware upgrade via USB, the NMC does not support USB drives with a capacity greater than 32GB. ♦ ♦ The configuration of the Universal I/O relay state (open/closed) is not persisted if the NMC is removed and then reinserted into the SmartSlot of the UPS. ♦ ♦ The BACnet Device Communication Control Password is displayed in plain text in the config.ini file. It is recommended that you use high security to access your NMC. A fix to this issue is planned for a future release. ♦ ♦ An NMC that never establishes communication with UPS does not give an alarm. ♦   You cannot update the UPS device’s firmware via the Web UI (Configuration > Firmware Update) using Microsoft Edge. Workaround: Use an alternative browser: Google Chrome, Mozilla Firefox, Internet Explorer etc. ♦   When universal I/O sensors* are connected to the NMC and UPS output relay and input contact alarms are triggered, the alarms do not display in the StruxureWare Data Center Expert UI. * Temperature sensor (AP9335T), temperature/humidity sensor (AP9335TH), Dry Contact I/O Accessory (AP9810). NOTE: This issue is only applicable to XU2K0LLXXRCC UPS devices. Workaround: disconnect the universal I/O sensors to see the UPS output relay and input contact alarms in the StruxureWare Data Center Expert UI. ♦   UPS devices with the XU prefix (for example, XU1K3LLXXRCC and XU2K0LLXXRCC) do not turn off power to the connected load. When regulated and protected input power is not available, these UPS devices provide unregulated grid power to the connected load. As a result, you may experience intermittent issues in the NMC web UI. ♦   For some UPS models, the “The output power is turned off” and “The output power is now turned on” events are logged multiple times in the event log when the NMC management interface reboots after the UPS or its outlet groups are manually turned off. ♦   If the NMC is installed in a low-priority slot in the Triple Expansion Chassis, and a Graceful Shutdown event is initiated by a card with higher priority, the UPS: Graceful Shutdown event is recorded twice in the event log of the low-priority NMC and is not recorded in the event log of the high-priority card. ♦   If the AP9617, AP9618, or AP9619 NMC is installed in a high- priority slot in the Triple Expansion Chassis, and a Graceful Shutdown event is initiated by a AP9630/AP9631/AP9635 NMC with lower priority, the Graceful Shutdown alarm does not clear on the AP9617, AP9618, or AP9619 Management Card. ♦   Device Sensors for StruxureWare Data Center Expert and NetBotz appliances detect critical Internal Battery Temperature Violation events, but do not generate an alert. ♦   When the outlet group control commands are configured to perform turn on and turn off actions within less than 3 seconds of each other, the commands may be delayed or canceled. ♦   For some UPS models, bypass alarms do not clear if a graceful off, reboot, or sleep command is initiated while the UPS is in bypass. ♦   If a UPS Control command is in progress and another UPS Control command is initiated, the original command is canceled and the most recent command succeeds. ♦   SNMP does not support the UPS or Switched Outlet Group sequencing delay commands. ♦   For Smart-UPS VT, the Web Redundancy Alarm can only be configured at the display interface. ♦   On "UPS - Outlet Group - Control", selecting Turn Off UPS immediately sometimes logs the turn off and turn on many times.♦ ♦   For SNMPv1, upsAdvConfigRatedOutputVoltage SNMP OID can be set but the new value only displays correctly after you refresh two or three times (using an SNMP Walk). ♦   MGE Galaxy 3500 UPS: upsAdvInputMinLineVoltage SNMP OID does not return the correct value. ♦   MGE Galaxy 3500 UPS: NMC Web UI-> Diagnostics: Calibration test result shows Pass while aborting the test in UPS power view. ♦   MGE Galaxy 3500 UPS: NMC Status for external battery cabinet rating is not matching with the same in Powerview status data. ♦   MGE Galaxy 3500 UPS: Uploading Invalid sleep time values through config.ini causes sleep time to be reset to 0. ♦   Smart-UPS models excluding those with prefix SMT, SMX, SURTD or SRT have limited event list filtering, and may display events not relevant to the UPS model on the Event List and Control Policy web interface pages. ♦   For certain UPS models, some output frequency settings do not display properly on the NMC interfaces. ♦   The web interface page Configuration > Firmware Upgrade is not available to a Device User. ♦   For certain Smart-UPS RT models, attempting to change the output voltage with the output powered on will cause the lower and upper bypass voltage settings to be reported incorrectly. ♦   An SNMP trap is not sent when the NMC initiates a self-test.   ♦ A Graceful Shutdown is logged twice in the event log when initiated from an upstream device. In this context, an upstream device is closer to the UPS on the UPS-Link communication bus than a downstream device (the UPS being the source of the data).   ♦ The "Graceful Shutdown Initiated" alarm does not clear on an NMC device if the reboot is initiated by a downstream NMC. In this context, a downstream device is further away from the UPS on the UPS-Link comm bus than an upstream device (the UPS being the source of the data).   ♦ Certain characters are not allowed in the Name field for the UPS (Administration - General) but no error message displays. Avoid using non-alphabetic symbols like !, #, -.   ♦     Hash Signatures Signatures apc_hw05_aos718_sumx718_bootmon109.exe MD5 0edec2b263db73bce88129e31db5bced SHA-1 f774cda0b8283be78602d7a20dfb52e4f0826c50 SHA-256 a96e08716ae28adf4066a1025bf5ada719482a62fad506562bd07ce88125d440   Signatures  apc_hw05_aos718_sy718_bootmon109.exe MD5 b7faf099db76658cff8920c9ac396312 SHA-1 fc6b05d3ac03d42d11460d680a23f6269d969f84 SHA-256 02a3a2af6596a4574749a89fd4752a030dd64759bdba2161acc099ecfa5971cd  

Affected Revision Levels   Component  File Details   APC Operating System  apc_hw05_aos_720.bin Network Management Card Operating System & TCP/IP Stack for Hardware Platform  Smart-UPS Application  apc_hw05_sumx_720.bin UPS Application for Smart-UPS, Smart-UPS XL, Smart-UPS RT, Smart-UPS VT, Smart-UPS DP, Smart-UPS OL, MGE Galaxy 3500   Symmetra Application   apc_hw05_sy_720.bin UPS Application for Single-Phase Symmetra, Symmetra LX, Symmetra RM   For details on upgrading the UPS Network Management Card 2 (NMC 2) firmware, see the User Guide on the Schneider Electric website.   New Features   New Feature There is no new feature in this release.     Fixed Issues   Fixed Issue UPS Family Smart-UPS Single-Phase Symmetra The SNMPv1 community name now accepts up to 16 characters. ♦ ♦ The Super User is no longer asked to enter and confirm a new password when navigating to the next page in the User Management Configuration page in the Web UI. ♦ ♦ The Web UI now displays correctly when a non-English language is selected. ♦ ♦ SNMPv3 works as expected when authentication/privacy is enabled. ♦ ♦ The BACnet device communication control passphrase is no longer stored in the configuration file (config.ini). ♦ ♦ Security Update The following third-party components (open source or proprietary) have been updated to address cybersecurity vulnerabilities: RADIUS Protocol under RFC 2865 - CVE-2024-3596 Implemented support for the Message-Authenticator attribute.   ♦ ♦ The following security vulnerabilities have been addressed in this release: CWE-200: Information Exposure CWE-203: Information Exposure Through Discrepancy RSA key exchange is disabled by default. ♦ ♦ The following security vulnerabilities have been addressed in this release: CWE-523: Unprotected Transport of Credentials. Login pages do not use adequate measures to protect the username and password while they are in transit from the client to the server. CWE-319: Cleartext Transmission of Sensitive Information. The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors. The user is now referenced as an index rather than the username NMC/KrtUvuh39YtQmHbyua297g/usercfg.htm?user=2 ♦ ♦ The following security vulnerability has been addressed in this release:   CWE-521: Weak Password Requirements The old password is no longer accepted when changing a password. ♦ ♦ The following security vulnerability has been addressed in this release: CWE-79 Improper Neutralization of Input During Web Page Generation (Cross-site Scripting). URLs were properly cleared, terminated, and sanitized. ♦ ♦     Known Issues Known Issue UPS Family Smart-UPS Single-Phase Symmetra When you configure the NMC2 to use IPV4 and IPV6, the SSH connections to the NMC will be unsuccessful. ♦ ♦ When upgrading the NMC’s firmware via the NMC Firmware Update Utility using SCP as the protocol, the update may be unsuccessful. If you click the Start Update button again, the following error messages may appear: Resume not supported for SCP transfers. Could not retrieve configuration file via this method, please recheck the settings. Workaround: Use FTP as the protocol. ♦ ♦ If SCP is chosen and the Backup log files prior to update checkbox is selected when upgrading the NMC’s firmware via the NMC Firmware Upgrade Utility, the upgrade will freeze at the “Download Event Log” stage. Workaround: Use FTP as the protocol, or back up your files before initiating the update and unselect the Backup log files prior to update checkbox. ♦ ♦ Modbus TCP cannot be enabled via the CLI on AP9630 and AP9631 NMCs. Workaround: Use the Web UI to enable Modbus TCP. ♦ ♦ The NMC management interface (e.g. the Web UI, CLI) may restart if large groups of event actions ordered by severity are modified. ♦ ♦ SNMPv3 communication and monitoring on some third-party SNMP management tools may not work correctly. ♦ ♦ If a firewall rule is created with a subnet value without the correct CIDR notation, no error is displayed, and the policy can be created with an incorrect subnet value. ♦ ♦ If a firewall rule is created with a subnet and port range defined, connections are not correctly limited to the ports defined in the rule. ♦ ♦ If a firewall rule is created with the option to Log set to ‘No’, the rule is incorrectly logged to the Firewall Policy Log. ♦ ♦ If a firewall rule is created with Protocol set to ICMP and Action set to Discard, ICMP messages such as ping are not stopped as expected. ♦ ♦ If a firewall rule is created with the source host set to the IP address of the NMC, the NMC will not be accessible when the firewall policy is enabled. ♦ ♦ "System: Detected an unauthorized user attempting to access the FTP interface" and "System: Password Changed" events do not send SNMP Traps. ♦ ♦ Device level user privileges in the Command Line Interface (CLI) are not consistent with the device user privileges in the Web interface. ♦ ♦ In the Config.ini, the SystemDateTime primary and secondary server keywords return strange values when long strings are applied. ♦ ♦ The DNS Domain Name validation doesn't conform to RFC1035 Standards for formatting. ♦ ♦ "System: Email: Could not mail, queue full." event log message is repeatedly recorded in the event log when a fourth email recipient is configured, even though the recipient is receiving the notification. ♦ ♦ Some column headers in the data.txt download file are not displayed correctly in Russian. ♦ ♦ File transfers using SCP do not work properly with WinSCP GUI client. ♦ ♦ NMC interface may restart when multiple alarms are logged simultaneously. ♦ ♦ Authenticated/secure email server settings could be potentially altered during an upgrade from an AOS prior to 6.1.8. ♦ ♦ Files do not successfully upload to the NMC via a TFTP server when used with DHCP options 66 and 67. ♦ ♦ When a firewall policy is created through the web UI with a name longer than 16 characters, it cannot be successfully edited, or updated with new rules. ♦ ♦ The NMC may enter a reboot loop when downloading the config.ini file over FTP, when DHCP with options 66 and 67 are enabled.   This reboot loop can be fixed by disabling DHCP or by closing the FTP server. ♦ ♦ When using the "Test Settings" option to test a RADIUS server configuration, the web UI will not accept a username or password longer than 16 characters. ♦ ♦ When configuring the SMTP server of an email recipient in the web UI, if the server is set to 'recipient', the 'From:' address field is incorrectly populated with the 'To:' address. When an email is then sent to the recipient, it incorrectly appears that the email has been sent from the recipient’s own email address. ♦ ♦ When connecting to the command line interface of the NMC via SSH, after a period the NMC management interface may reboot. ♦ ♦ If the maximum number of SMTP Traps and Email Recipients are configured, the maximum number of Web UI sessions, Command Line Interface sessions, Telnet sessions, and FTP sessions are created, and the maximum number of alarms is generated at once, the NMC user interface will become unresponsive, and the NMC will reboot. ♦ ♦ A UPS that has been deliberately put into sleep mode can behave inconsistently. For example, a UPS can turn off after only a few seconds of being in the "Graceful shutdown initiated" state or can turn on after only a few seconds of being in the "Turned off for a defined period" state. ♦ ♦ When a scheduled shutdown is configured with a long interval (e.g. 2 weeks), the UPS shuts down on schedule, but if a power outage occurs before the UPS restarts, the UPS will not shut down at the next scheduled date, and the next scheduled shutdown will be moved forward by one week. ♦ ♦ USB drives of a capacity greater than 32GB are often formatted using an NTFS or ExFAT file system. The NMC is compatible with FAT, FAT16 or FAT32 file systems only. For UPS firmware upgrades via USB, or NMC card firmware upgrade via USB, the NMC does not support USB drives with a capacity greater than 32GB. ♦ ♦ The configuration of the Universal I/O relay state (open/closed) is not persisted if the NMC is removed and then reinserted into the SmartSlot of the UPS. ♦ ♦ An NMC that never establishes communication with UPS does not give an alarm. ♦ ♦ You cannot update the UPS device’s firmware via the Web UI (Configuration > Firmware Update) using Microsoft Edge. Workaround: Use an alternative browser: Google Chrome, Mozilla Firefox, Internet Explorer etc. ♦   When universal I/O sensors* are connected to the NMC and UPS output relay and input contact alarms are triggered, the alarms do not display in the StruxureWare Data Center Expert UI. * Temperature sensor (AP9335T), temperature/humidity sensor (AP9335TH), Dry Contact I/O Accessory (AP9810). NOTE: This issue is only applicable to XU2K0LLXXRCC UPS devices. Workaround: disconnect the universal I/O sensors to see the UPS output relay and input contact alarms in the StruxureWare Data Center Expert UI. ♦   UPS devices with the XU prefix (for example, XU1K3LLXXRCC and XU2K0LLXXRCC) do not turn off power to the connected load. When regulated and protected input power is not available, these UPS devices provide unregulated grid power to the connected load. As a result, you may experience intermittent issues in the NMC web UI. ♦   For some UPS models, the “The output power is turned off” and “The output power is now turned on” events are logged multiple times in the event log when the NMC management interface reboots after the UPS or its outlet groups are manually turned off. ♦   If the NMC is installed in a low-priority slot in the Triple Expansion Chassis, and a Graceful Shutdown event is initiated by a card with higher priority, the UPS: Graceful Shutdown event is recorded twice in the event log of the low-priority NMC and is not recorded in the event log of the high-priority card. ♦   If the AP9617, AP9618, or AP9619 NMC is installed in a high- priority slot in the Triple Expansion Chassis, and a Graceful Shutdown event is initiated by a AP9630/AP9631/AP9635 NMC with lower priority, the Graceful Shutdown alarm does not clear on the AP9617, AP9618, or AP9619 Management Card. ♦   Device Sensors for StruxureWare Data Center Expert and NetBotz appliances detect critical Internal Battery Temperature Violation events, but do not generate an alert. ♦   When the outlet group control commands are configured to perform turn on and turn off actions within less than 3 seconds of each other, the commands may be delayed or canceled. ♦   For some UPS models, bypass alarms do not clear if a graceful off, reboot, or sleep command is initiated while the UPS is in bypass. ♦   If a UPS Control command is in progress and another UPS Control command is initiated, the original command is canceled and the most recent command succeeds. ♦   SNMP does not support the UPS or Switched Outlet Group sequencing delay commands. ♦   For Smart-UPS VT, the Web Redundancy Alarm can only be configured at the display interface. ♦   On "UPS - Outlet Group - Control", selecting Turn Off UPS immediately sometimes logs the turn off and turn on many times. ♦   For SNMPv1, upsAdvConfigRatedOutputVoltage SNMP OID can be set but the new value only displays correctly after you refresh two or three times (using an SNMP Walk). ♦   MGE Galaxy 3500 UPS: upsAdvInputMinLineVoltage SNMP OID does not return the correct value. ♦   MGE Galaxy 3500 UPS: NMC Web UI-> Diagnostics: Calibration test result shows Pass while aborting the test in UPS power view. ♦   MGE Galaxy 3500 UPS: NMC Status for external battery cabinet rating is not matching with the same in Powerview status data. ♦   MGE Galaxy 3500 UPS: Uploading Invalid sleep time values through config.ini causes sleep time to be reset to 0. ♦   Smart-UPS models excluding those with prefix SMT, SMX, SURTD or SRT have limited event list filtering, and may display events not relevant to the UPS model on the Event List and Control Policy web interface pages. ♦   For certain UPS models, some output frequency settings do not display properly on the NMC interfaces. ♦   The web interface page Configuration > Firmware Upgrade is not available to a Device User. ♦   For certain Smart-UPS RT models, attempting to change the output voltage with the output powered on will cause the lower and upper bypass voltage settings to be reported incorrectly. ♦   An SNMP trap is not sent when the NMC initiates a self-test.   ♦ A Graceful Shutdown is logged twice in the event log when initiated from an upstream device. In this context, an upstream device is closer to the UPS on the UPS-Link communication bus than a downstream device (the UPS being the source of the data).   ♦ The "Graceful Shutdown Initiated" alarm does not clear on an NMC device if the reboot is initiated by a downstream NMC. In this context, a downstream device is further away from the UPS on the UPS-Link comm bus than an upstream device (the UPS being the source of the data).   ♦ Certain characters are not allowed in the Name field for the UPS (Administration - General) but no error message displays. Avoid using non-alphabetic symbols like !, #, -.   ♦     Hash Signatures Signatures apc_hw05_aos720_sumx720_bootmon109.exe MD5 b5dcf67e61287e533ee080a4d9ef87ba SHA-1 4c5b81345027d02a38fdb71924c3c659457763b3 SHA-256 373d4486c62a43f6e7205952fc5b031c80de16598ba382889caa458288d12b29   Signatures  apc_hw05_aos720_sy720_bootmon109.exe MD5 d9fc60c0edd0b6bf09fa8dfae39b65b2 SHA-1 8a113727ef5f1512b82f4e468a2184917cd83445 SHA-256 467e1eb88229ade3840bfa9d2dea63ba5afb3a2cf8a0ec4f538874891f77f4aa