Known issues in DCE

[EcoStruxureIT]

DCE release notes

Known issues in DCE 8.3.0

• When HTTP is enabled without enabling HSTS on the DCE server, the login page for the web user interface is available. Login is not allowed.
  No error is displayed; this will be addressed in a future release.

  If HTTP is not needed, you can modify HTTP and HTTPS settings in the desktop client on the System > Server Administration Settings > Server Access > Web Server tab.

Known issues in DCE 8.2.x

• The DCE VM does not power off from the shutdown option in the DCE client.
• The FIPS mode indicator in the desktop client is not available to Device Viewer users.
• The Updates > Apply Firmware Updates > Check updates option does not contact the device firmware update server as expected. The progress bar is active but no action is taken.
  Customers can download the Device Firmware Update Catalog that includes the latest IEC-certified NMC3 firmware 3.x from the EcoStruxure IT Entitlements portal. An active software support contract is required.
  Customers who do not monitor NMC 3 devices can download the Device Firmware Update Catalog here.

  How to import the APC device firmware update catalog

Known issues in DCE 8.1.x

• The DCE 8.1.x desktop client ignores the client/server mismatch. Attempts to log in to a non-8.1.x server from an 8.1.x client generates errors rather than redirecting to the server page as expected.

• Due to a change in authentication in DCE 8.1 and newer, the integration with EcoStruxure Building Operation no longer works after updating DCE 8.0 to 8.1 or 8.1.1. This was addressed in DCE 8.2.0.

  Please see https://www.apc.com/us/en/faqs/FAQ000267255/

• When a path with a leading backslash (example: \mnt\pool\nfs) is entered into the Share field in the System > Server Administration Settings > Server Backup/Restore > Backup Share Settings display, and the Subdirectory field is blank, the test and the backup both fail. Replace the backslashes in the path with forward slashes to mitigate this issue.

• After updating DCE to version 8.1.0, display sensor values such as firmware revision, hardware revision, model number, and serial number may be reported as unplugged for some Galaxy VS, Symmetra LX, and Symmetra PX250 UPSs.
  Reboot the server to mitigate the issue.

Known issues in DCE 8.0.0

• Multiple versions of DCE 8.0.0

  The current version of Data Center Expert is 8.0.0.154.
  Some customers received DCE 8.0.0.151, DCE 8.0.0.149, or DCE 8.0.0.148.

  
  DCE 8.0.0.154 addresses the following issue in the DCE 8.0.0.151 release:
  Synchronized backups created a Full backup and a new Full backup file.
  Synchronized backups now append new data to an existing Synchronized backup as expected.

  DCE 8.0.0.151 addresses the following issue in 8.0.0.149:

  Self-signed certificates cannot be removed in the System > Server Administration Settings > Server Access > Web Server display.

  Customers who updated their DCE server to 8.0.0.149 can download the 8.0.0.151 desktop client to mitigate this issue.  

  DCE 8.0.0.149 addresses the following issue in the DCE 8.0.0.148 release:

  When the Subdirectory field in the System > Server Administration Settings > Server Backup/Restore >  Backup Share Settings display contains a backslash ( \ ), the backup fails and DCE incorrectly indicates that the backup was successful.
  Replace the backslashes in the Subdirectory field with forward slashes (/) to mitigate this issue.

  To update DCE 8.0.0.148 to 8.0.0.154:

  1. Back up the DCE 8.0.0.148 server. Make sure to backup to a path that does not include a backslash.
  2. Download DCE 8.0.0.154 at the link previously provided, deploy a new server, and restore from backup.

     There is no upgrade option between DCE 8.0.0 versions.

• DCE server update process display in web client
  The DCE server update progress is not accurately displayed in the web client during the update from DCE 7.9.3 to version 8.0. The upgrade completes successfully. This will be addressed in the next release. More...

• DCE Security Policy change requires reboot
  When the DCE Security Policy is changed from Future (most restrictive) to any other policy, the DCE server must be rebooted to maintain communication with devices that use SSL.

• Launch to Device does not work for NMC 1 devices using HTTPS on the private network
  In DCE 7.9.0 and newer, the Launch to Device option does not work for NMC 1 devices that use HTTPS on the DCE private network.
  Connect a computer to the DCE private network to directly access the device's web user interface.
  More...

Known issues from DCE 7.9.x

• Client launcher does not reopen after changing system settings
  In DCE 7.7.1 and newer, the client launcher does not reopen once DCE restarts after changing system settings or using the File > Change Server option. Create a shortcut and add the -h parameter to the Target path.
  More…

• Apply button not enabled in Security Policy option
  The Apply button is not enabled once No is selected in the Security Policy confirmation window. Click Cancel and select the Server Access > Security Policy option again to reactivate the Apply button.

• No confirmation window in Time Settings option
  The server reboots without displaying a confirmation when changes are made in the Time Settings option.

• Email notifications identify the DCE 7.9.3 version as 7.9.2
  Email notifications might identify the DCE version as 7.9.2 after the server has been updated to DCE 7.9.3. This is a display issue that does not affect functionality.

  Note: This issue was addressed in DCE 8.1.1.

• Security Policy Apply button not enabled after selecting No
  The Apply button is not enabled once No is selected in the Security Policy confirmation window. Click Cancel and select the Server Access > Security Policy option again to reactivate the Apply button.

• No confirmation for server reboot in Time Settings option
  The server reboots without displaying a confirmation when changes are made in the Time Settings option.

• DCE 7.9.0 and 7.9.1 server appliance does not upgrade from USB key
  The USB key used to restore the DCE server is missing a package necessary to upgrade to future DCE versions.
  Contact support for assistance. Allowing remote access to the DCE server is required.
  Note: Virtual machine deployment (VM) is not affected.

• Launch to Device does not work for NMC 1 devices using HTTPS on the private network
  In DCE 7.9.0 and newer, the Launch to Device option does not work for NMC 1 devices that use HTTPS on the DCE private network.
  Connect a computer to the DCE private network to directly access the device's web user interface.
  More...

• Multiple versions of DCE 7.9.0
  The current version of Data Center Expert is 7.9.0.196. Some customers received DCE 7.9.0.192, 193, or 194.

  DCE 7.9.0.196 addresses the following issues in previous versions of the DCE 7.9.0 release:

  • Sensor data does not populate as expected.
  • Logs can overburden the system.
  • Return to normal emails are not sent.

To update a previous DCE 7.9.0 version to DCE 7.9.0.196, do one of the following:

Contact support to replace the necessary files. Allowing remote access to the DCE server is required.

OR

Back up the DCE 7.9.0.192, 193, or 194 server. Download DCE 7.9.0.196 at the link previously provided, deploy a new server, and restore from backup. There is no upgrade option between DCE 7.9.0 versions.

Other known issues

• Launch to device does not work for NMC4 devices on the private LAN
  The Launch to Device option does not work for NMC 4 devices on the DCE private network.
  Connect a computer to the DCE private network to directly access the device's web user interface from the desktop client, or use the web client to launch to NMC 4 devices.

• All devices in a firmware update group are selected
  After searching for and selecting a device in the Apply Firmware Updates dialog, and then collapsing and expanding its firmware group, all the devices in the group are selected.

• Alarms do not load in the web client in Internet Explorer or Edge
  Alarms do not load when you access the web client from Internet Explorer 11 or Edge versions lower than 80.0. Alarms load as expected in Firefox and Chrome.
  Note: To update Edge to the latest version, go to https://www.microsoft.com/en-us/edge

• NetBotz rack access cards assigned to every door
  When NetBotz Rack Access is configured in Data Center Expert, the cards are assigned to every door on every pod instead of only those intended. Access is disabled for the unintended assignments.

• Both doors do not unlock on NetBotz 250 and 750
  The Select all option in the Rack Access > Control option in Data Center Expert unlocks only one door on NetBotz 250 and 750 appliances. The NetBotz 250 and 750 do not allow both doors to be unlocked at the same time.

• APC 3.x device setting does not update
  Device credentials are not updated in Data Center Expert for APC 3.x devices when device configuration initiated in the APC SNMP Device Configuration option is used to change the file transfer protocol from FTP to SCP.

• Notification policy reset to default
  The notification policy associated with a device is reset to default when its communication protocol is changed from SNMPv1 to SNMPv3 in the APC SNMP Device Configuration option. Thresholds remain in the original notification policy.

• Some APC SNMP Device Configuration Changes in v7.3 Are Sent One Command at a Time
  Configuration changes on APC SNMP devices with firmware v6.0.0 and higher, excluding v6.0.6 - v6.1.1, are sent to the device one command at a time. It can take up to 30 seconds per user after the "Device Configuration Status" display reports the configuration is complete to apply all the options.

• APC SNMP Device Configuration File Transfer Using SCP Fails
  File transfer using SCP fails on some APC SNMP devices with firmware lower than AOS v6.3.3. For best results, enable FTP on the device, and set the protocol to FTP Only in the “Device File Transfer Settings” display before you select the devices you want to update.
  Additionally, both SCP and FTP file transfer fails on all v6.x devices with touch screens (apc_hw06_aos_xxx). See the Data Center Expert documentation in the Help Center for the most recent information on APC SNMP Device Configuration.

• NetBotz Lost Communication Email Notifications are Sent to All Users
  Notifications for NetBotz Communication Lost events are sent to all Data Center Expert users configured with an e-mail address.

• BootMonitor Module Not Included in APC Device Firmware Update
  The Data Center Expert server does not apply the BootMonitor module as part of the APC device firmware update.

• Data Center Expert Web Client Search Feature Supports English Only
  The search feature in the Data Center Expert web client supports English only. Accented letters and characters that do not appear in English are not returned in the search results.

• Data Center Expert Web Client Search Parameters Require Quotes for Special Characters
  Search strings containing special characters must be surrounded by double quotes to return results. For example, to search for a device by MAC address, the user must type “XX:XX:XX:XX:XX:XX”.
  Note: As the user types a MAC address in the search field, the search bar displays a suggestion without quotes. Using this search suggestion will return no results.

• Data Center Expert Web Client Customized Pages Unresponsive on Older Browsers
  Due to performance considerations, certain browsers may not display all the gadgets on a customized page in the Data Center Expert web client. Upgrading your browser to the latest version is recommended. If you use Internet Explorer, and cannot upgrade to a later version, consider using Google Chrome Frame to enable open web technologies.

• NetBotz Web Client Does Not Load When Launched to a NetBotz Appliance on the Private LAN
  The NetBotz Web Client does not load completely when it is launched from the Data Center Expert user interface to a NetBotz appliance on the private LAN. Users accessing Data Center Expert from the public LAN must use Advanced View to connect to a NetBotz appliance on the private LAN. Alternatively, to use the NetBotz Web Client, users can connect directly to a NetBotz appliance from a system on the private LAN.

• Default Device Node Count Displayed for Data Center Expert Virtual Appliance Demo Version
  The Data Center Expert virtual appliance demo version supports up to 5 device nodes and one camera enabled for surveillance. To monitor 25 device nodes, displayed by default in the License Keys display, you must apply the virtual appliance activation license.

• Limitation on Number of Virtual Sensors
  The number of virtual sensors created can affect server performance. The recommended number of virtual sensors for a Data Center Expert server to monitor is:

  • Basic server: A maximum of 300 virtual sensors
  • Standard server: A maximum of 600 virtual sensors
  • Enterprise server: A maximum of 4000 virtual sensors

• Units in Graphs Included in Alarm Notifications are Displayed in English
  When an email, HTTP POST, or FTP alarm notification includes a graph, the units are displayed in English. The body of the email and the sensor data are displayed in the language for the locale specified in the alarm action.

• Limitations on Requests for Data Using Web Services
  Data requests via Web Services exceeding 3.5MB return no data.

• Subsequent Outlet Control Commands May Fail
  When the user performs an outlet control command, then immediately follows it with a second command, the second command may fail. The user must wait 5 – 10 seconds to issue a subsequent outlet control command.
  Users can verify the command was successful in the web interface of the device.

• Limitation on Global Device Scan Intervals
  Users cannot set their global device scan settings to less than five minutes if there are more than 2026 devices discovered on their Data Center Expert Enterprise server. This restriction is not enforced on device-specific scan settings, but APC recommends that the same policy be applied to these settings.
  For servers monitoring fewer than 2025 devices, it is recommended that the default 5-minute scanning rate be used for SNMP devices, and only adjusted for small subsets of critical devices.

• Limitation on Surveillance Settings for Cameras
  The number of cameras monitored by the Data Center Expert server, and the Camera Resolution and Target Image Capture Rate (frames per second) settings at each camera, can affect server performance. To support a large volume of surveillance data, the recommended camera settings and number of cameras for a Data Center Expert server to monitor, are:

  • Basic server: A maximum of 15 cameras at 10 frames per second, 150 fps total, and a resolution of 640x480
  • Standard server: A maximum of 125 cameras at 2 frames per second, 250 fps total, and a resolution of 640x480
  • Enterprise server: A maximum of 250 cameras at 2 frames per second, 500 fps total, and a resolution of 640x480.