Data Center Expert release notes
Contact Support
Submit a support request for additional assistance with EcoStruxure IT software.
Link copied. Please paste this link to share this article on your social media post.
The v7.8.1 release contains security updates and various fixes.
You must contact your local Technical Support and verify you have a valid software support contract to receive the StruxureWare Data Center Expert v.7.8.1 update file.
NOTE: The StruxureWare Data Center Expert v7.8.1 update file is not available for download on this site.
AP9465
AP9470
AP9475
AP94VMTRL
The DCE console 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 2012 or 2016, Windows 10; Red Hat® Enterprise Linux® version 6.0; CentOS 6
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 Internet Explorer® 11; Edge; Mozilla® Firefox®; Google Chrome™ See Known issues for details about support for Internet Explorer and Edge
The v7.8.1 release contains security updates and various fixes only.
CVE-2020-10188 – Telnet server
CVE-2017-1000371 – Kernel: ELF PIE binary on i386 systems
CVE-2019-17666 – Kernel: RealTek wireless drivers
CVE-2019-17133 – Kernel: WiFi ESSID
CVE-2019-17055 – Kernel: AF_ISDN protocol
CVE-2019-14821 – Kernel: KVM hypervisor
CVE-2015-9381 – FreeType buffer over-read
CVE-2015-9382 – FreeType buffer over-read
CVE-2019-11745 – Buffer overflow
CVE-2020-8616 – BIND flaw
CVE-2020-8617 – BIND flaw
CVE-2020-10711 – Kernel: SELinux
CVE-2017-12192 – Kernel: Key Management
CVE-2019-18634 – Sudo flaw
See Data Center Expert Security for more information.
Server OS: Proprietary CentOS 6 - CentOS 6.10 (kernel revision 2.6.32-754.24.3.el6.x86_64)
Java Version: 1.8.0_201-b09
Maintenance Mode improvements: You can now launch maintenance mode from the All devices group as expected. Scheduling Maintenance Mode no longer puts unsupported NetBotz devices into maintenance mode.
SNMP settings: Changing device settings from SNMPv1 to SNMPv3 no longer resets associated notification policies to default.
Web client: Russian characters now display as expected in the web client.
Launch to device: The launch to device option now works as expected for APC devices using NMC2 with firmware version 6.9.4.
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
The Windows client does not restart after server change. After you change the server in the File > Change Server in the installed client, the client closes and does not restart. This only occurs in the Windows client. Linux client installs are not affected.
Complete list of DCE known issues
The following steps are necessary to update DCE v7.8.0 to DCE v7.8.1.
You must have a valid software support contract to receive the DCE v.7.8.1 update. If you do not, then you will need to purchase one to receive the update.
DCE must be at a minimum of v7.8.0 to update to DCE v7.8.1. If you are downloading DCE v7.8.1, you will need access to the Internet.
IMPORTANT: Do not reboot the server during the update.
The DCE 7.8.1 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.
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.
Extract/expand the upgrade zip file into a separate directory on the hard drive of the system that will be running the DCE Console.
Login to your DCE v7.8.0 server with full server access. Now select Updates from the menu bar then Apply Server Update.
Click Import and look into the subdirectory where extracted files are placed. The structure of the extracted fields should contain two folders, "BW" and "NBCCore", and an index file, "nbcpkg.lst"
Select the "nbcpkg.lst" file and click "Open".
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.
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.
When the update is complete, point a web browser to the DCE server, and select Install DCE Client.
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. Please make sure you have a copy of all installed license keys and network settings prior to restore.
Download the restore.iso file to create a bootableUSBkey, or contact Technical Support for assistance.
For a USBKey, follow the instructions provided in Creating a bootable USB Key (Windows or Linux machine).Place the USB key in the USB port of your DCE appliance.
Reboot DCE.
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.
Once DCE has restarted, you may configure the DCE network settings per instructions in the DCE Installation Guide.
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.
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.
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.
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.
Apply the activation key to the virtual appliance.
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.
Instructions for a Windows machine:
InsertUSBkey (no larger than 4GB) into your system.
Extract the following file to a temporary directory:
DCExpertUsbFlashRestore_Win_7.8.1.zip
Open a command prompt to the temporary directory and run mkDCExpertRestoreUsbKey.bat <iso image filename>. For example: mkDCExpertRestoreUsbKey.bat c:\tmp\restore.iso
Answer the prompts as appropriate.
Instructions for a Linux machine:
Insert a 2GB (or larger) USB key into your system.
Extract the following file to a temporary directory:
DCExpertUsbFlashRestore_Linux_7.8.1.tar.gz
Open a command prompt to the temporary directory and run mkDCExpertRestoreUsbKey.sh <iso image filename>. For example: mkDCExpertRestoreUsbKey.sh /tmp/restore.iso
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 |
X |
X |
|
7-zip |
X |
|
|
GNU sed |
X |
|
You can now choose to compress a backup. The compressed backup is a single tar.gz file with a .dce file extension for easier filename filtering. More..
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.