EcoStruxure IT Data Center Expert 8.2.0 release notes

[JLehr]

Part Numbers Affected

• AP9465
• AP9470
• AP9475
• AP94VMTRL

See the list of the server appliances (AP9465, AP9470, and AP9475) supported by DCE 7.9.x and newer:

See Data Center Expert 7.9.x and newer - server hardware requirements

Minimum system requirements

The Data Center Expert desktop client is a stand-alone Java application that runs on systems that meet the following requirements:

• A PC with a 1-GHz or better AMD/Intel processor running a 64-bit operating system: Microsoft® Windows® Server 2016 and 2019, Windows 10 and 11
• At least 2 GB of RAM and 20 GB disk space
• Screen resolution should be set to at least 1024 x 768.
• Supported browsers: Microsoft Edge; Mozilla® Firefox®; Google Chrome™

Note: See Known Issues in DCE for details about support for Internet Explorer and Edge.

New features

The Data Center Expert 8.2.0 release introduces support for Federal Information Processing Standards (FIPS) for computer systems used by United States government agencies and their contractors.

The cryptographic modules utilized by Data Center Expert are undergoing FIPS 140-3 validation and are currently awaiting CVMP review on the Module in Process List.

The Data Center Expert 8.2.0 release contains improvements including:

• Simple method to change communication protocol from SNMPv1 to SNMPv3
  

  The Device > SNMP Device Communication > Device Scan Settings option now includes a setting to change the communication protocol between the device and DCE from SNMPv1 to SNMPv3. 

  Note: You must also change the communication protocol on the device.

• Comments column in Active Alarms and Alarm History views
  

  A new column in the Active Alarms and Alarm History views displays the number of comments on each alarm.

• Copy server information from Help > About
  

  A new copy button makes it easier to capture the build information, MAC address, and server serial number from the Help > About display.

• Updated link to the EcoStruxure IT Help Center
  

  The link to the EcoStruxure IT Help Center in the Help menu is now correct.

• Federal Information Processing Standards (FIPS) compliance
  

  You can now install the DCE server and/or the DCE desktop client in FIPS mode. 

  • There is now an option to select FIPS mode when you deploy the server for the first time.
  • There is now an option to install the desktop client in FIPS mode.
  • You can now select the FIPS security policy on the System > Server Administration Settings > Server Access > Security Policy tab.

    IMPORTANT: FIPS mode requires that certificates must include the Subject Alternative Name with the fully qualified domain name (FQDN) and IP address of the monitored device or connected server. New certificates may be required.

  • Help > About indicates whether the server and client are in FIPS mode. You can also hover over the bottom right corner of the client to see whether it is in FIPS mode.
• Run discovery now
  

  In the device discovery wizard, the Run discovery now option is now checked by default.

• Syslog line termination option      
  

  When TCP is selected, there is now an option to specify a line terminator, \r\n by default.

• New API endpoint
  

  The /v1/devices/sensors endpoint was added to the DCE REST API for bulk retrieval of sensors across all devices a caller has access to.

• New event log messages

  The event log now includes:

  • Device label change messages: 
  • Device group messages when a user creates, deletes, or modifies a device group.
  • User group access messages
  • Map change messages 
  • Alarm acknowledgement messages when a user acknowledges, suppresses, or comments on an alarm.
  • Custom properties messages when  a user creates, deletes, or modifies a custom property.
  • Scheduled event messages
  • Surveillance and clip activity messages
  • Web client access messages when a user logs in or logs out of the web client.

Visit the EcoStruxure IT Help Center for more information.

Server operating system

Server OS: Proprietary Rocky Linux 8.10 (RHEL derivative)

Java version: OpenJDK-headless-11.0.24.0.8-3.el8

Windows desktop client

Java version: Adoptium 8u422-b05

Software vulnerabilities fixed in DCE 8.2.0

The security vulnerabilities addressed in this release include:

• CVE-2024-8530
• CVE-2024-8531

The following third-party components were updated to address these specific cybersecurity vulnerabilities:

Apache

• CVE-2015-0250

Linux kernel

• CVE-2024-1086

This release also includes various additional component updates to improve overall security.

See the Data Center Expert Security section in the Help Center for more information.

Issues fixed

The following issues were fixed in DCE 8.2.0:

• The authentication issue introduced in DCE 8.1.x that affected EcoStruxure Building Operation integration was addressed.
• The REST API refresh token now expires at the expected time when a new access token is requested prior to expiration.
• Large configuration backups now complete as expected.
• Syslog messages are no longer missing labels. Lines are now terminated properly.
• Email alerts are now sent as expected when email servers require stricter security.
• Saved reports can now be exported from the web client as PDFs.
• When a client-server version mismatch is detected, the web page to download the client is now launched as expected.

Known issues

• 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

• The list of device firmware available in the Device Firmware Update Catalog is not displayed in the Apply Firmware Update > Select Device Updates option after the firmware update catalog is uploaded. Close and reopen the desktop client to display the list. This issue will be addressed in an upcoming release.

Complete list of known issues in DCE

Software update procedure

The following steps are necessary to update DCE 8.1.0 or 8.1.1 to DCE 8.2.0.

DCE must be at a minimum of 8.1.0 or 8.1.1 to update to DCE 8.2.0. If you are downloading DCE 8.2.0, you will need access to the Internet. 

You must have a valid software support contract to receive the DCE 8.2.0 update.  If you do not, then you will need to purchase one to receive the update.

The DCE software update files are available in the EcoStruxure IT Entitlements portal.Log in and then click Software Updates. More information...

If the DCE update files are not available in EcoStruxure IT Entitlements, contact your local technical support to verify your support contract and get access to the update file(s) you need.

IMPORTANT: Do not reboot the server during the update.

The DCE 8.2.0 update performs a data migration that takes under an hour for most systems. The data migration can take longer if the system has thousands of devices and years of history, and varies based on several factors:

• Number of devices

• Number of sensors connected to those devices

• Polling interval

• Frequency at which sensor values change. For example, input voltage to UPSs can fluctuate throughout the day vs. temperature sensors in a strictly controlled environment that almost always report the same value.

You can see the status of the update on the Data Center Expert web client Home page.

NOTICE: Before beginning an update, remember to run a full backup on your DCE by going to System > Server Administration Settings > Server Backup/Restore, create a backup entry and then click Start.

It is recommended that you perform the server update when you upload the upgrade file to your DCE server. The update will be performed automatically if the server reboots after the upgrade file is uploaded.

1. Download the upgrade.zip file, or contact Technical Support for assistance.
   Note: The restore.iso file may be needed for later use if a re-installation is required. See Restoring using ISO Format for instructions for restoring your data from a restore.iso file from the ISO format.
2. Log in to your DCE 8.1.0 or 8.1.1 server with full server access. Select Updates > Apply Server Update.
3. Click Import to import the upgrade.zip file.
   Note: DCE 8.0 and newer only accept the zipped upgrade file.
4. The Upgrade/New Packages table will update indicating there is an update available for the DCE server. Check the "Install/Upgrade" option for the package(s) you want to upgrade.
   Click the Install Selected button to start the upgrade for the selected package(s). You will be prompted to confirm you want to proceed with the update.
   Click Install Update to start the update process. Do not reboot the server during the update process.
5. When the file transfer completes, DCE will restart and disconnect your console connection. You can point a web browser to the DCE server for status.
6. When the update is complete, point a web browser to the DCE server, and select Download Client.

Restoring Data Center Expert using ISO Format

Warning: Only perform the steps in this section if directed to do so by a Technical Support technician.

Before You Restore:  A system restore will erase all data and restore the DCE hardware server to its factory default settings. Make sure you have a copy of all installed license keys and network settings prior to restore.

1. Download the restore.iso file to create a bootable USB key, or contact Technical Support for assistance.

   For a USB Key, follow the instructions provided in Creating a bootable USB key (Windows or Linux machine).

2. Place the USB key in the USB port of your DCE appliance.

3. Reboot DCE.

4. When the appliance restarts the system restore process begins automatically. This process takes approximately 10 minutes for the 1U DCE Basic, 15 minutes for 1U DCE Standard or 25 minutes for 2U DCE Enterprise.
   When the restore is complete, you will be prompted to remove the USB key and hit enter to reboot the server.
   Note: If the system boots into the existing DCE version, reboot the server and access the BIOS settings. Adjust the boot sequence to boot from USB first.

5. Once DCE has restarted, configure the DCE network settings.

Migrating a Data Center Expert hardware server to a virtual appliance

Before You Migrate: To migrate a DCE hardware server to a virtual appliance, you must purchase and apply an activation key.  Additionally, you must contact APC Support for new node license keys and application license keys for the virtual appliance.

1. Perform a back up of the DCE hardware server, using the Server Backup/Restore option, accessed from the Server Administration Settings option in the System menu.

2. Deploy the demo version OVA, and configure it using the hardware equivalents for the DCE Basic, Standard, or Enterprise server from which you are migrating. The available disk space for the virtual appliance must be greater than the disk space used by the hardware server. You cannot restore to a virtual appliance with fewer CPU, fewer network adapters, less RAM, or less available disk space than the hardware server. See help for Deploying and configuring a DCE virtual appliance, and DCE virtual appliance equivalent configurations.

3. Perform a restore on the virtual appliance, using the Server Backup/Restore option, accessed from the Server Administration Settings option in the System menu. You cannot restore to a virtual machine other than the DCE virtual appliance.

4. Apply the activation key to the virtual appliance.

5. Log in to the DCE client. In the "License Keys" display, accessed from the Server Administration Settings option in the System menu, apply the new node license keys and application license keys you received from APC Support.

Creating a bootable USB Key (Windows or Linux machine)

Instructions for a Windows machine

1. Insert a 4GB (or larger) USB key into your system.

2. Extract the following file to a temporary directory:
   DCExpertUsbFlashRestore_Win_8.1.1_b.zip

3. Open a command prompt to the temporary directory and run mkDCExpertRestoreUsbKey.bat <iso image filename>. For example: mkDCExpertRestoreUsbKey.bat c:\tmp\restore.iso

4. Answer the prompts as appropriate.

Instructions for a Linux machine

1. Insert a 4GB (or larger) USB key into your system.

2. Extract the following file to a temporary directory: 
   DCExpertUsbFlashRestore_Linux_8.1.1_b.tar.gz

3. Open a command prompt to the temporary directory and run mkDCExpertRestoreUsbKey.sh <iso image filename>. For example: mkDCExpertRestoreUsbKey.sh /tmp/restore.iso

4. Answer the prompts as appropriate.

Third-party USB key scripts

The scripts used to create USB keys use the following software:

Software	URL	Windows	Linux
Syslinux	http://syslinux.zytor.com/	X	X
7-zip	http://www.7-zip.org	X
GNU sed	http://unxutils.sourceforge.net	X

[jmcnutt]

There should be an option to download the release notes as a PDF.

[JLehr]

Hi @jmcnutt,

Thanks for your feedback.

You can click the Options icon (three dots) and choose Printer friendly page to save an article as a PDF. 

May I ask why you find a PDF document useful?

Best,

Jackie

[jmcnutt]

Hi @JLehr 

The "printer friendly page" only reformats the page, rather than displaying any kind of download link.  I would still be relying on the "print to PDF" function to put together a legible document, which also wouldn't have any kind of table of contents or internal linking.  (It would also have these comments at the bottom, which would be weird.)

Any time we install updates on a system - a firewall, for example - the new software/firmware/code is copied to our internal infrastructure file server along with the relevant release notes, in case they are needed for later reference, or by another network admin.  Having the release notes as a PDF (as most vendors do) makes this process very easy and also ensures that when I open the release notes, I see the same thing as when my colleagues open them.

[JLehr]

Thanks for this @jmcnutt. We're exploring ways to improve this experience.